> ah, sorry. what do you mean by the source program? streamer? what is > external synchronization?The source program is whatever provides the data stream - ices, for instance. External syncronisation means performing whatever synchronisation you need to get the data you want in a seperate program - not within icecast (or ices).> > btw, where can i find the mp3 straming specs? that is, i would like to > know the data format, metadata format and how they are sent together from > a streaming program to a broadcast server such as icecast.The mp3 data format is available from many places, including the actual mpeg standards documents. The mp3 metadata format is a nasty hack originated by the shoutcast people - do a web search for "shoutcast metadata protocol", there are quite a few explanations of it. Sending to icecast uses HTTP, with the SOURCE method (an icecast extension). Metadata in icecast can either be inline (using the same protocol as for the clients) (though this is rare - I don't know any source clients which support it) or asynchronously through HTTP GET requests to /admin/metadata on the server. Mike --- >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-dev-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.
> The mp3 metadata format is a nasty hack originated by the shoutcast people - > do a web search for "shoutcast metadata protocol", there are quite a few > explanations of it.i searched for "shoutcast metadata protocol", "shoutcast metadata", and shoutcast metadata (2 separate words), "mp3 metadata", on googe web and google groups. i coulnt find anything useful. any pointers pls?> Sending to icecast uses HTTP, with the SOURCE method (an icecast extension). > Metadata in icecast can either be inline (using the same protocol as for the > clients) (though this is rare - I don't know any source clients which support > it) or asynchronously through HTTP GET requests to /admin/metadata on the > server.again, where can i find the details? thanks, deva <p><p>>> --- >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-dev-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. >--- >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-dev-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.
the metadata format is not documented officially anywhere, but really isn't terribly complicated... http://www.smackfu.com/stuff/programming/shoutcast.html hows a nice concise description of it, and was the first result returned from doing http://www.google.com/search?q=shoutcast+metadata oddsock At 04:06 PM 2/25/2003 -0500, you wrote:> > The mp3 metadata format is a nasty hack originated by the shoutcast > people - > > do a web search for "shoutcast metadata protocol", there are quite a few > > explanations of it. >i searched for "shoutcast metadata protocol", "shoutcast metadata", and >shoutcast metadata (2 separate words), "mp3 metadata", on googe web and >google groups. i coulnt find anything useful. > >any pointers pls? > > > Sending to icecast uses HTTP, with the SOURCE method (an icecast > extension). > > Metadata in icecast can either be inline (using the same protocol as > for the > > clients) (though this is rare - I don't know any source clients which > support > > it) or asynchronously through HTTP GET requests to /admin/metadata on the > > server. >again, where can i find the details? > >thanks, >deva > > > > > > > --- >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-dev-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. > > > >--- >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-dev-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.<p><p>--- >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-dev-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.