Ed Smallenburg

149.255.57.97:8148 plays well here. The queue is constantly filled up to 380 or more chunks. 45.43.200.66:25858 has difficulties. The queue becomes empty now and then. It looks that the sender...

149.255.57.97:8148 plays well here. 178.79.158.160:8424/stream plays well here. 45.43.200.66:25858 has still difficulties, because the real bitrate is about 304 bps and my software is not capable to cope with that....

85.214.231.253:8080/stream (without "http://" of course) plays well here. Dubug output: ``` D: Connect to new host 85.214.231.253:8080/stream D: Connect to 85.214.231.253 on port 8080, extension /stream D: Connected to server...

Queue is 0. That means: not enough input from the network. I'm using the latest versions of toolchain and libraries.

``` Pinging 85.214.231.253 with 32 bytes of data: Reply from 85.214.231.253: bytes=32 time=18ms TTL=122 Reply from 85.214.231.253: bytes=32 time=17ms TTL=122 Reply from 85.214.231.253: bytes=32 time=18ms TTL=122 Reply from 85.214.231.253: bytes=32...

121 msec from here and it's BAD. I will try it with increased buffersize, but I cannot change the internal buffers.

There are no "small reads" in the radio, it's always trying to read as much as possible. I checked it with the new version, but the result is the same....

I think there is no solution for this. The code and the primary buffers are part of the ROM program.

It is a good idea, tested it, but it did not work out here for your station. To aggressive I assume :)

Yes, the URL redirects to another location. A software change could be made to follow this redirect. Should not be too difficult.