Hmm two questions.. First, a while back someone emailed me with a patch against the icecast source that seemed to allow metadata to be enabled without all the goofed up skipping and so on that happens by default. Can someone contact me with this again? I've lost the patch.. Second, to the icecast guys.. what exactly is the problem with metadata currently? Would it be terribly hard to just stream out an ID3 tag when the song changes and when a new user connects, at the beginning of their data? I don't see any reason to send it at a particular interval, just on-change from the source is enough I would think. AFAIK an ID3 tag is simply an invalid frame in the stream that is skipped by any respectable decoder, and making the frame invalid is trivially simple.. I'm having a hard time understanding why this doesn't work. It's a real kick in the nuts to have to use shoutcast and all it's BS problems to just be able to show the song titles in winamp, which is undoubtedly the most widely used player. -Asym http://rfnj.org --- >8 ---- List archives: http://www.xiph.org/archives/ icecast project homepage: http://www.icecast.org/ To unsubscribe from this list, send a message to 'icecast-request@xiph.org' containing only the word 'unsubscribe' in the body. No subject is needed. Unsubscribe messages sent to the list will be ignored/filtered.
At 17:05 8/11/2001 -0400, you wrote:>you tell me. Works alright here, except in xmms which has a bug in its >shoutcast metadata handler. I've submitted a patch at bugs.xmms.org >for it.Hmm.. well with the current version of winamp and the previous two it would and does skip if I have metadata enabled.. it'll start anywhere from ten minutes to an hour into the stream and then just get terrible. If the listening client is restarted, it goes away for an indeterminate amount of time, then happens again..> > the song changes and when a new user connects, at the beginning of their > > data? > >probably not, but nothing would read it.How do you figure?> > I don't see any reason to send it at a particular interval, just on-change > > from the source is enough I would think. AFAIK an ID3 tag is simply an > >not necessarily.When would it not be enough? What I'm suggesting here is that the icecast server interpret the metadata it gets from the source (which it obviously can do or it wouldn't know the song titles, etc) and then instead of sending them out in this same format, it sends them out as an ID3 tag.>because the clients skip the "invalid frame"?Clients skip "playback" of the invalid frame, but they do parse it for a valid ID3 header.. this is how ID3 works. The first characters of the frame are ID3 which both simultaneously identifies the frame as ID3, while invalidating it as an mp3 frame for playback (Valid frames are all bits on).>The protocol you're talking about is exactly how shoutcast does >it. I've had no problems using shoutcast-style metadata to feed a >current winamp from a current icecast.I understand that is how shoutcast does it, I'm trying to find out why icecast doesn't do it the same way. I've used 1.3.11 and it still has the same problem.. If icecast were doing it the same way as shoutcast, then I think it would work better.. and not have that glaring warning in the config file about using metadata at all.. something to the effect of "this doesn't work quite right and probably never will." I'll give it another whirl and see how it goes just for the sake of doing it.. but if anyone remembers that patch they sent me, I'd love to have it again. It was very simple and worked like a charm. -Asym http://rfnj.org --- >8 ---- List archives: http://www.xiph.org/archives/ icecast project homepage: http://www.icecast.org/ To unsubscribe from this list, send a message to 'icecast-request@xiph.org' containing only the word 'unsubscribe' in the body. No subject is needed. Unsubscribe messages sent to the list will be ignored/filtered.
On Saturday, 11 August 2001 at 16:53, Asymmetric wrote:> Hmm two questions.. > > Second, to the icecast guys.. what exactly is the problem with metadata > currently? Would it be terribly hard to just stream out an ID3 tag whenyou tell me. Works alright here, except in xmms which has a bug in its shoutcast metadata handler. I've submitted a patch at bugs.xmms.org for it.> the song changes and when a new user connects, at the beginning of their > data?probably not, but nothing would read it.> I don't see any reason to send it at a particular interval, just on-change > from the source is enough I would think. AFAIK an ID3 tag is simply annot necessarily.> invalid frame in the stream that is skipped by any respectable decoder, and > making the frame invalid is trivially simple.. I'm having a hard time > understanding why this doesn't work.because the clients skip the "invalid frame"?> It's a real kick in the nuts to have to use shoutcast and all it's BS > problems to just be able to show the song titles in winamp, which is > undoubtedly the most widely used player.The protocol you're talking about is exactly how shoutcast does it. I've had no problems using shoutcast-style metadata to feed a current winamp from a current icecast. Please give icecast 1.3.11 a try, it should handle a general skipping problem (not related to metadata) better than the last couple versions. -Brendan --- >8 ---- List archives: http://www.xiph.org/archives/ icecast project homepage: http://www.icecast.org/ To unsubscribe from this list, send a message to 'icecast-request@xiph.org' containing only the word 'unsubscribe' in the body. No subject is needed. Unsubscribe messages sent to the list will be ignored/filtered.