I have a setup with an Icecast master server playing a continuous stream to a Relay on an AWS instance, which in turn provides an SSL stream to the world using the latest Icecast version 2.4.99.3. On occasion, we will start a second stream for testing purposes. What I'm finding is there is a long delay before the stream shows up, which I assume is related to the default master-update-interval. What I'm wondering is whether there is a way to notify the Icecast relay that I'm starting a new stream, as it seems wasteful to decrease the master-update-interval for something that only is used on occasion. I really don't need the relay to be constantly polling besides making sure our main stream hasn't failed, as we only usually have the one stream. -milton -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.xiph.org/pipermail/icecast/attachments/20220713/3c8f4eda/attachment.htm>
Good morning, On Wed, 2022-07-13 at 17:53 -0700, Milton Huang wrote:> I have a setup with an Icecast master server playing a continuous > stream to a Relay on an AWS instance, which in turn provides an SSL > stream to the world using the latest Icecast version 2.4.99.3. On > occasion, we will start a second stream for testing purposes. What > I'm finding is there is a long delay before the stream shows up, > which I assume is related to the default master-update-interval. > What I'm wondering is whether there is a way to notify the Icecast > relay that I'm starting a new stream, as it seems wasteful to > decrease the master-update-interval for something that only is used > on occasion. I really don't need the relay to be constantly polling > besides making sure our main stream hasn't failed, as we only usually > have the one stream.If the second stream has a constant name you could just use an on- demand relay. That will check the master only when there is a client actually trying to access it. Hope that helps. :) With best regards, -- Philipp Schafft (CEO/Gesch?ftsf?hrer) Telephon: +49.3535 490 17 92 Website: https://www.loewenfelsen.net/ Follow us: https://www.linkedin.com/company/loewenfelsen/ L?wenfelsen UG (haftungsbeschr?nkt) Registration number: Bickinger Stra?e 21 HRB 12308 CB 04916 Herzberg (Elster) VATIN/USt-ID: Germany DE305133015 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 228 bytes Desc: This is a digitally signed message part URL: <http://lists.xiph.org/pipermail/icecast/attachments/20220714/16666a0b/attachment.sig>
I have a setup with an Icecast master server playing a continuous stream to a Relay on an AWS instance, which in turn provides an SSL stream to the world using the latest Icecast version 2.4.99.3. On occasion, we will start a second stream for testing purposes. What I'm finding is there is a long delay before the stream shows up, which I assume is related to the default master-update-interval. What I'm wondering is whether there is a way to notify the Icecast relay that I'm starting a new stream, as it seems wasteful to decrease the master-update-interval for something that only is used on occasion. I really don't need the relay to be constantly polling besides making sure our main stream hasn't failed, as we only usually have the one stream. -milton -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.xiph.org/pipermail/icecast/attachments/20221024/b648206e/attachment.htm>