I managed to finish work earlier than normal; so as well as listening to VFR Europe's AAC 96 stream whilst cycling home I turned on an old laptop with XBMC/Kodi and the Shoutcast addon; as this connected to the downstairs TV (XBMC found the milkdrop installation automatically!) and a cheap Chinese "hi fi" system with aux input is more appealing to listen to and watch than normal telly...
At first I just got a repeating buffer of the Shoutcast stream from here; and thought it was the old laptop being overloaded; but when I checked airtime there was a warning of "bad answer".
It must have packed up during the last hour or so as it was halfway through Robbie4Evers mix; the AAC streams were unaffected as they are derived from a 192k MP3 Icecast stream to a different server in DE (the playout in NL) that transcodes it via Liquidsoap (doing all of it on one server eventually causes Airtime to go pear shaped).
I had to restart the shoutcast server to get things running correctly again. I've had this happen (occasionally) before; with a "broken pipe"(?!) message. It could be Airtime sending flawed data; or some known bug in Shoutcast.
Whatever it is; it seems to be a greater issue with Shoutcast (we had all sorts of similar strangeness when Party Vibe Radio was doing the live shows); and the server had to be regularly restarted. Icecast seems more resilillent.
What should I be looking out for? I notice in the error log a lot of multiple connections from a UK IP and MPEG OVERRIDE but these aren't shown as listeners (it might just be that the client is also getting confused by the defective data); the source log (where I'd expect to see the NL IP from Airtime) is blank. Perhaps I'm looking in the wrong place?
At first I just got a repeating buffer of the Shoutcast stream from here; and thought it was the old laptop being overloaded; but when I checked airtime there was a warning of "bad answer".
It must have packed up during the last hour or so as it was halfway through Robbie4Evers mix; the AAC streams were unaffected as they are derived from a 192k MP3 Icecast stream to a different server in DE (the playout in NL) that transcodes it via Liquidsoap (doing all of it on one server eventually causes Airtime to go pear shaped).
I had to restart the shoutcast server to get things running correctly again. I've had this happen (occasionally) before; with a "broken pipe"(?!) message. It could be Airtime sending flawed data; or some known bug in Shoutcast.
Whatever it is; it seems to be a greater issue with Shoutcast (we had all sorts of similar strangeness when Party Vibe Radio was doing the live shows); and the server had to be regularly restarted. Icecast seems more resilillent.
What should I be looking out for? I notice in the error log a lot of multiple connections from a UK IP and MPEG OVERRIDE but these aren't shown as listeners (it might just be that the client is also getting confused by the defective data); the source log (where I'd expect to see the NL IP from Airtime) is blank. Perhaps I'm looking in the wrong place?