TuneNet V2.9

Working fine until today.
Today when the scan runs for radio stations, it doesn't find any and ends in an error message -
Error obtaining station listings.

Nothing wrong with the network connection, Yam and Odyssey working fine.

Anyone else having an issue?

Cheers

Hi, same issue here.
Don't know when it started.

@ddni

It was fine here up until yesterday evening when i switched it off.
I found a new station I liked as well and was hoping to listen to it again today while i'm in lock down.

Just my luck.

Cheers

check your envarc tunenet folder for last_tune file. The details may be there.

@ddni

Ah that's handy, I've saved that now.

Cheers

Add another one to the list.. checked out that file, just showed the last place I streamed.

I'm guessing wherever it's pulling its list from has changed?

just checked and same here?

tried deleting last entry in ENVARC but still can't scan any stations at all?

update: tried deleting evrything in ENVARC and still nothing?

haven't changed anything in settings...

Most likely a server side issue, the server might be down, or the might have changed the API of the site. Or maybe it has something to do with SSL. as its web api.

Where does TuneNet pull the list of stations from?

Does it work now? I noticed that my own internet radio player program also didn't get the station list from Shoutcast few days ago (it reported connection timed out), but now it does again today. Quick googling told that there were some major server changes going on recently.

@jPV

Sadly no, still not working.

Cheers

Not sure what is going on here, I just accessed the top 500 endpoint in a browser using the Tunenet API key and got a valid response, ie xml with the expected (or as best as I can tell anyway ) data.

There must be some subtle change in the xml that's messing up tunenets parseing of it.

It would appear that there is some leading junk on the xml response that didn't used to be there, which can be seen when grabing the xml data via ARexx

eg

Have now added a workarround for this "junk" in TuneNet 2.10

@broadblues

That's great, thanks.
Any idea when that will be released?

Cheers

@broadblues

That looks like a BOM - Byte Order Marker - (slightly distorted from some program's attempt to display it as text).

There is a special place in Hell for people who insist on putting a BOM into a UTF-8 coded file. It simply doesn't make any sense, because UTF-8 by definition consists of single bytes, and one byte cannot have any order among itself.

Unfortunately, there are many "developers" out there who don't know any better.

God, the time I used to waste trying to convince people of this back when I was coding PL/SQL code to read XML files received from the outside ...

If possible, the sanest approach is of course to make your code resilient to that nonsense (which I couldn't in PL/SQL, but you luckily can).

Rant over ... oh, it's good to be retired

Best regards,

Niels

@nbache

lol I'm still more than a few years from retirement and in totally different field BUT fully understand what ya mean

@broadblues

Found a bug though, if you simply drag a pls file directly into the playlist the file cannot be reproduced .. i can see the name of the stream (the radio name) correctly listed in playlist, but the file cannot be played at all in this method ..
But no problem if instead i put the same radio address manually from the open url menu
In compare AmigaAMP seems support both method for opening streams, drag and drop of a pls file, but also via open url menu

Hi

The new version of TuneNet has been packaged and uploaded to Updater tool today. This will fix the station listing problem.

Thanks to Andy for his quick fix.

@amigakit

Thanks updated and working fine!!