Quantcast
Viewing all articles
Browse latest Browse all 6235

Streaming Radio: HTTP connection is not closed

Hi guys,

I have problems with streaming radio from an own satellite radio streaming server (don't have wired internet here), which is a separate Raspberry Pi with a VDR installation on it.

My squeeze setup, here acting as streaming client, is a piCorePlayer with integrated LMS and Jivelite on 7 inch screen.

The radio stations are set as favourites in LMS, pointing to the VDR streaming server, e.g. 192.168.0.100:3000/ES/1052

Usually, this works really well: the display goes (quickly) from
"Connection being established" over
"Buffering"
to
"Now Playing".
Everything fine, I am listening radio.

Sometimes, however, when I change the radio channel by choosing another favourite, the satellite radio server accepts the HTTP connection, but does not send any audio because it cannot tune to the transponder (bad signal). In this case, the piCorePlayer display gets stuck at
"Connection being established". I cannot even stop the connection in Jivelite.

The problem now is that the LMS does not close the HTTP connection because it still waits for an audio stream. And because of this, I cannot tune to another radio station. LMS requests a new HTTP connection, but does not close the old one, and the server is stuck at the old one and does not accept a new one. I can only proceed if I "motivate" the server to close this HTTP connection by itself, but that is not feasible for normal use, as it is headless.

I would have expected that LMS closes the HTTP connection after a certain timeout period, but it doesn't. I know that there is this timeout setting, but it doesn't seem to have any effect in this case.

I have tested another streaming client instead of LMS / squeezelite: VLC Player on Windows 10. With it, it works properly. VLC closes the HTTP connection at latest when I request a new HTTP stream.

Does anyone have a clue whether this LMS behaviour (obviously different from that of VLC) is desired? Why does it not close the HTTP after a certain timeout? Should I activate special logging to track that?

Thanks for your help!

Viewing all articles
Browse latest Browse all 6235

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>