search for: metaint

Normally icy-metaint is a line in the http header, but some stream only sends it in the response data is self. Where can I find such a stream? Is that compliant to the standard? Implementation that also parses the response data http://stackoverflow.com/questions/8621353/textview-not-updating-shoutcast-stream-metadat...

...orrespond to a boundary between mp3 frames. given an > mp3 stream, once i found a frame boundary it's easy to keep finding those > boundaries. but i don't know how to arbitrarily find icecast chunk > boundaries if there's no delineating information. The server returns an icy-metaint header which tells where the info will be inserted. If, say, it's 4096 then you'll find the metadata after every 4096 bytes of MP3 data. Unfortunately it does not position itself on frame boundaries. -Brendan --- >8 ---- List archives: http://www.xiph.org/archives/ icecast project hom...

...from the Icecast server. It doesn't pass allow an option for the developer to pass up an Ice-MetaData header for the specified URL. And even if you could, it likely wouldn't be able to parse out the inline metadata within the returned HTTP byte stream (as indicated by the presence of an icy-metaint header). So therefore, my app can't show the current artist and song title on the screen very easily. An alternative option is to continuously make an http polling request for the "status.xsl" page on the server and parse this information out. But polling isn't an ideal solution....

On Fri, 10 Aug 2001, Brendan Cully wrote: > The server returns an icy-metaint header which tells where the info > will be inserted. If, say, it's 4096 then you'll find the metadata > after every 4096 bytes of MP3 data. that's what i originally thought was supposed to happen, which is why i sent the original mail with a bug report, saying i was expecting pe...

Hi, I am writing client software to connect to Ogg streams. I believe Icecast supports sending track information for Mp3 streams, via icy-metadata / metaint. - For MP3 streams, does Icecast also support sending track information 'out-of band' on another port? - For Ogg Vorbis streams, how is song/track information sent and updated to the client? How do I parse this information? Would appreciate if you could point me to some documentation, o...

When "Icy-MetaData: 1" is in the HTTP request to the server, that indicates that the client wants to receive meta data inlined with the mp3 data stream. The metadata interval is reported by the server via the "icy-metaint" header in the response stream. Such data looks like the following within the mp3 stream StreamTitle='Ozzy Osbourne - Crazy Train';StreamUrl='http://myserver.org'; Essentially a series of name/value pairs formatted with single-tick quotes around each value and delimited wit...

i've been trying to get title streaming of metadata to work with icecast 1.3.10. i've found what i believe to be a bug -- is this the right place to file a bug report? it appears that this information should be periodically inserted into the data stream. the behavior that i was seeing was that the information was appearing a maximum of one time and sometimes zero times. i believe there

...changed and there > is no point in wasting bandwidth resending it. ... > > in my local copy, this is the only instance that i changed, and it indeed > > causes the metadata to appear periodically within the stream. > > You've just forced clients to receive updates every metaint bytes > instead of when the metadata changes. Take a look at what modifies > udpseqnr. part of the confusion may be that i'm not actually sure what the right behavior is supposed to be, and i'm guessing based on my observations. (i don't suppose any of this is documented anywher...

...ould. If you > don't, the metadata relaying could have been broken (I think this is > unlikely, though - that code hasn't been changed lately AFAIK) Or connect via telnet and see what's really going on ;-) HTTP/1.0 200 OK Content-Type: audio/mpeg icy-br: 64 icy-genre: Talk icy-metaint: 8192 icy-name: Enemy Combatant Radio icy-notice1: <BR>This stream requires Winamp<BR> icy-notice2: SHOUTcast Distributed Network Audio Server/FreeBSD4 v1.9.2<BR> icy-pub: 1 icy-url: http://sf.indymedia.org/ Server: Icecast 2.0-alpha2/cvs Yes, it copies over the icy headers exact...

Just checked using RealPlayer Windows 10.5 latest release. This also glitches. This is more than likely due to the differences in metadata between SHOUTcast and Icecast2. This is exactly the reason I was asking for the exact differences between the protocols so I can help get these things fixed with the player folks. Real is not the only player with this problem. I may be in the AAC/aacPlus camp,

...from the Icecast server. It doesn't pass allow an option for the developer to pass up an Ice-MetaData header for the specified URL. And even if you could, it likely wouldn't be able to parse out the inline metadata within the returned HTTP byte stream (as indicated by the presence of an icy-metaint header). So therefore, my app can't show the current artist and song title on the screen very easily. An alternative option is to continuously make an http polling request for the "status.xsl" page on the server and parse this information out. But polling isn't an ideal solution....

On Wed, Jun 25, 2003 at 11:34:07AM +1000, Michael Smith wrote: > > > 2) Should relay icy/x-audiocast stream metadata when connecting to > > icecast1/shoutcast/etc so that this information is available to YP > > Eh? It does. I even tested that with someone's shoutcast stream. It works. > Just add >

...ons when a client connects (winamp) what are the incoming headers icecast looks for to signify what type(ogg or mp3) of stream the client is requesting? example (for shoutcast winamp sends icy-metadata:1) shoutcast server then recognizes its a player capable of streaming media so it sends the icy-metaint:8192 to winamp, along with a slew of other icy headers. o here is my dilema example php code fwrite($sp,"GET /my_mp3 HTTP/1.0\nUser-Agent:Secret stuff alpha\nicy-metadata:1\n\n");//works with winamp when requested via php script but fwrite($sp,"GET /example.ogg HTTP/1.0\nUser-Agent...

relaying a shoutcast stream via icecast2 is pretty much unlistenable -- it constantly stutters. for example, shoutcast relay -- http://205.188.234.1:8030/listen.pls icecast2 relay -- http://liveradio.indymedia.org:8001/sf-hifi.mp3.m3u --mark --- >8 ---- List archives: http://www.xiph.org/archives/ icecast project homepage: http://www.icecast.org/ To unsubscribe from this list, send a

...t; I have many ears right about now, and I would really like to see Icecast2 > properly supported. The default can be changed to 8192 easily enough but if there is some parsing issue with real then that would be useful to know. I suspect that for some reason the real player is ignoring the icy-metaint header causing the playback problem. karl.

...stream requires <a href="http://www.winamp.com/">Winamp</a><BR> icy-notice2:SHOUTcast Distributed Network Audio Server/Linux v1.9.5<BR> icy-name:Radio Ostergaard icy-genre:All icy-url:http://radio.home.ostergaard.net/index.php content-type:audio/mpeg icy-pub:0 icy-metaint:32768 icy-br:128 so it maybe the ICY header it's expecting. You could try changing src/format.c:275 to read bytes = snprintf (ptr, remaining, "ICY 200 OK\r\n" "Content-Type: %s\r\n", source->format->contenttype); rebuild and re-run icecast, if it...

...opts = [ 'http' => [ 'method' => 'GET', 'header' => 'Icy-MetaData: 1', 'user_agent' => $ua ] ]; if (($headers = get_headers($streamingUrl))) foreach ($headers as $h) if (strpos(strtolower($h), 'icy-metaint') !== false && ($interval = explode(':', $h)[1])) break; $context = stream_context_create($opts); if ($stream = fopen($streamingUrl, 'r', false, $context)) { while($buffer = stream_get_contents($stream, $interval, $offset)) { if (strpos($buffer, $...

...any use of udpseqnr > within a client_t structure need to be conditioned with use_udp ? > > in my local copy, this is the only instance that i changed, and it indeed > causes the metadata to appear periodically within the stream. You've just forced clients to receive updates every metaint bytes instead of when the metadata changes. Take a look at what modifies udpseqnr. Metadata works fine for me without this change. What are you testing with? -Brendan --- >8 ---- List archives: http://www.xiph.org/archives/ icecast project homepage: http://www.icecast.org/ To unsubscribe from...

...(winamp) what are the incoming headers icecast >looks for to signify what type(ogg or mp3) of stream the client is requesting? > >example >(for shoutcast winamp sends icy-metadata:1) >shoutcast server then recognizes its a player capable of streaming media >so it sends the icy-metaint:8192 to winamp, along with a slew of other icy >headers. > >so here is my dilema >example php code >fwrite($sp,"GET /my_mp3 HTTP/1.0\nUser-Agent:Secret stuff >alpha\nicy-metadata:1\n\n");//works with winamp when requested via php script >but >fwrite($sp,"GET...

...ver. It doesn't pass allow an > option for the developer to pass up an Ice-MetaData header for the > specified URL. And even if you could, it likely wouldn't be able to parse > out the inline metadata within the returned HTTP byte stream (as indicated > by the presence of an icy-metaint header). > > So therefore, my app can't show the current artist and song title on the > screen very easily. An alternative option is to continuously make an http > polling request for the "status.xsl" page on the server and parse this > information out. But polling isn&...