Icecast Streaming Media Server

[relen]

My apologies if this is dealt with elsewhere - I tried loads of search terms but either got nothing or everything.

We produce programming 24/7 with a different presenter handling each day (as a rule). Our presenters are in different timezones all over the world, so the handover between one and the next is often done by kicking the existing source at a suitable point (while the originating system is unattended); the superseded presenter then turns off their source client after they wake up (for example).

This means there is often a period of overlap where one source client is driving the stream while another (the previous presenter's system) is trying to get in and failing. During this period, the metadata from BOTH source clients is displayed to listeners, the currently-displayed metadata depending on which source client last sent an update. This is not optimum.

Is there a way of configuring the server so that only the metadata of the currently-streamed source client is displayed and the metadata from the contending source client is ignored (just as its audio is ignored)? Or is this a bug?

You would think that the default would be that the metadata from the source currently driving the audio stream would be the ONLY one displayed, but in fact the metadata from a contending source client will also be displayed, even if that contending source client is not successfully accessing the server audio-wise.

Any ideas or observations welcome. We cannot assign different priorities to different mount points as we don't know who will supersede who, and I am not sure this would solve the issue anyway.

Thanks in advance for any helpful advice.
--Richard E

[iunderwood]

What are you using for a source client?

It sounds like the source uses admin requests to change the Metadata on the stream, which doesn't require a client to be logged in.
_________________
++I;

[relen]

[karlH]

someone reported something like this a week or so ago, what I've committed to trunk (post 2.3.2) is to block metadata update requests made by source clients unless the IP is the same as the one matching the stream. It's not perfect but should handle most if not all cases. You can get a snapshot from trunk to use that, or let me know if it needs to be a win32 build.

karl.

[relen]

Brilliant! Thanks! I think that would probably cover us.

I'll ask our server provider to look at this thread and let me/us know whether or not there is any need for any additional work.

Best,
--Richard E
_________________
Radio Riel - Real radio: your reality
http://www.radioriel.org