search for: updinfo

...rce client (from scratch). I’ve got the actual audio streaming part worked out just fine, but the metadata has me scratching my head a little bit. According to the docs, to update metadata for an mp3 stream you’re supposed to issue an http request like this: http://hostname:port/admin/metadata?mode=updinfo&mount=/station&song=test <http://hostname:port/admin/metadata?mode=updinfo&mount=/station&song=test> If I send this request authenticated with the source username/password, I get this, and the metadata is not updated: <iceresponse> <message>Mountpoint will not acce...

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

...so. > 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. Are you sure? It should change whenever the stream source does an "updinfo" command. Otherwise the information hasn't changed and there is no point in wasting bandwidth resending it. > i believe there is a bug in the following line in write_chunk_with_metadata() > in source.c. here is the original: > > if (source->info.udpseqnr == clicon->f...

...s. And only for MP3 and AAC this holds true. Also note that MP3 and AAC are not officially supported by Icecast. They may work, but that's it. We recommend to use Opus for most applications. > you’re supposed to issue an http request like this: > http://hostname:port/admin/metadata?mode=updinfo&mount=/station&song=test <http://hostname:port/admin/metadata?mode=updinfo&mount=/station&song=test> Yes. > If I send this request authenticated with the source > username/password, I get this, and the metadata is not updated: > <iceresponse> > <message...

You did not type the exact string I told you to first of all. You forgot to use the 's after before the h in http and at the end. curl --user admin:hackme 'http://192.168.0.1:8000/admin/metadata?mount=/live&mode=updinfo&song=Artist_name+Title' notice the useage of the 's in my string and not in yours. Your string is launching nonsense into the background via the two &'s, hence [1] and [2]. Follow my string and it will work wonders. Sorry for the delay in reply. -- Cody Tubbs : (Certif...

My bad, try curl -s --user etc etc etc... I suppose that'd help. :] On 13 Oct 2004 at 13:02, Dave St John wrote: > > Here is the error i get now. > > [root@mc1 gork]# curl --useruser:pass > 'http://64.62.252.140:9120/admin/metadata?mount=/live.ogg&mode=updinfo&song=test_name+te > st_Title' > <b>source will not accept URL updates</b> > > > Dave St John > Mediacast1 Administration > Need Support ? > http://mediacast1.com/helpdesk > ----- Original Message ----- > From: Cody Tubbs (wISPdirect) > To...

...source connections. > I use BASH scripts with wget to pass the metadata update which gets data > from my another data stream: > > wget -q --delete-after --http-user=admin --http-password=Top_SECRET > http://audio.domain.invalid:8000/admin/metadata?mount=/MyMount > \&mode=updinfo\&song=[This+is+who+is+talking]+$RANDOM >/dev/null Why don't you use -O /dev/null? Also make sure you both quote the song parameter first to HTTP standards and then to shell standards. I think the redirect of stdout is mostly useless. This also will allow each and every process on the s...

...uppose that'd help. :] > > On 13 Oct 2004 at 13:02, Dave St John wrote: > > > >> > >> Here is the error i get now. > >> > >> [root@mc1 gork]# curl --useruser:pass > >> 'http://64.62.252.140:9120/admin/metadata?mount=/live.ogg&mode=updinfo&song=test_name+te > >> st_Title' > >> <b>source will not accept URL updates</b> > >> > >> > >> Dave St John > >> Mediacast1 Administration > >> Need Support ? > >> http://mediacast1.com/helpdesk > >&gt...

...t 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. > > Are you sure? It should change whenever the stream source does an > "updinfo" command. Otherwise the information hasn't 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&...

Hi Karl, Thanks for your help, About the "Connection:" header, you are right, it's: "Connection: close" and NOT "Connection: keep-alive". The protocol when the SERVER sends the data is http 1.0. It's http 1.1 when the browser requests the data. I don't understand the "Content-Length: 54000000" header either. Also I noticed the flash player on