Thanks, Romain. I appreciate the very informative response. Karl Heyes from the Icecast project has always pointed to poor Ogg implementation by players also.
Not a big deal for us as most of the listening to our Vorbis streams is via our legacy embedded player. Our current web player, TuneIn and most others all use AAC. I'm very pleased with how nicely our new liquidsoap-based source encoder is working. That's currently in final testing and will replace our old source soon. --- Bill Goldsmith Radio Paradise www.radioparadise.com On Wed, Apr 10, 2019 at 2:18 PM Romain Beauxis <romain.beau...@gmail.com> wrote: > Hi, > > > Le lun. 8 avr. 2019 à 17:46, William Goldsmith <b...@radioparadise.com> a > écrit : > > > > OK. I got this working -- although it appears that metadata updates via > this method do not work on ogg/flac streams. I don't get an error (as I do > when attempting a URL update on that mountpoint) but it does not register > with Icecast. > > > > Updates to ogg/vorbis mountpoints via this method also cause the same > stream glitches in some players (notably VLC) that URL updates do. > > > > So a big fail on both intended uses :-( > > > > If anyone has come up with a method to update flac mountpoints or to do > glitch-free vorbis updates, I'd *love* to hear about it. > > The fact that `icy.update_metadata` works for vorbis is really just by > "luck". Icecast has an extensive support for vorbis stream and knows how to > insert new metadata into them. There's no such support for other codec > supported by the ogg container, in which case the function does nothing. > Originally, this function is intended only for format that send metadata > using the icy metadata protocol (see: > http://www.smackfu.com/stuff/programming/shoutcast.html) > > I believe that your glitches problem is a really annoying issue with > players not implementing the ogg stream format correctly. Essentially, if > an ogg stream has multiple tracks, they all follow each other in a > concatenated matter. However, some players are implemented with only a > single track per ogg stream in mind and that causes issues, either playback > stops at the end of the first track or you have glitches. > > Second thing is, when you insert metadata into a ogg stream, it will > finish the current track and start a new one, beginning with the metadata > you want to insert. Thus, triggering the issues on track change I explained > above. > > This has been going on for years and it's pretty annoying to know that > some players still haven't been fixed yet. Your best bet if you need to fix > it would be to strip all metadata from the stream and use an out of band > mechanism to display them, for instance on your website. > > Romain > _______________________________________________ > Savonet-users mailing list > Savonet-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/savonet-users >
_______________________________________________ Savonet-users mailing list Savonet-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/savonet-users
