Hi, I've just completed a conversion of the perl Shout-1.0 library to something that will talk to an icecast2 server. I'll be submitting the results for inclusion back to the icecast site. One thing is missing: proper metadata support. this feature has changed since icecast 1; previously it was a single string. now, it's a linked list of key/value pairs. I'd love to add and test this feature, but I don't know how to use it, and can't find any docs on it. can anyone tell me how this feature works? in particular, I'd like to know what keys are valid, and what they do. I'd also like to know which key is used to set the title string on xmms during stream playback. (assuming it's still used for the same functionality). thanks! -paulb ==========================================================================paulb@oasis-software.com "I'm fuzzy on this whole good/bad thing" paulb@foobox.com -Dr. Peter Venkman --- >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.
On Tuesday, 01 April 2003 at 14:25, Paul Bournival wrote:> Hi, > > I've just completed a conversion of the perl Shout-1.0 library > to something that will talk to an icecast2 server. I'll be submitting > the results for inclusion back to the icecast site. > > One thing is missing: proper metadata support. > > this feature has changed since icecast 1; previously it was a > single string. now, it's a linked list of key/value pairs. > I'd love to add and test this feature, but I don't know how to use > it, and can't find any docs on it. > > can anyone tell me how this feature works? in particular, I'd > like to know what keys are valid, and what they do. I'd also like to > know which key is used to set the title string on xmms during stream > playback. (assuming it's still used for the same functionality).The only defined key is "song". Usage: metadata = shout_metadata_new(); shout_metadata_add(metadata, "song", "my song name"); shout_set_metadata(shout, metadata); shout_metadata_free(metadata); The interface was changed to allow more types of dynamic metadata updates, but so far no extensions on the client or server side have been made. -b --- >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.
>From a parallel universe, Brendan Cully <brendan@xiph.org> scrawled..... > The only defined key is "song". > Usage: > metadata = shout_metadata_new(); > shout_metadata_add(metadata, "song", "my song name"); > shout_set_metadata(shout, metadata); > shout_metadata_free(metadata); > > The interface was changed to allow more types of dynamic metadata > updates, but so far no extensions on the client or server side have > been made.awesome! thanks! -paulb ==========================================================================paulb@oasis-software.com "I'm fuzzy on this whole good/bad thing" paulb@foobox.com -Dr. Peter Venkman --- >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.
I'm trying to using metadata now in my application that uses libshout, and am seeing curious behaviour. my icecast2 log says: -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-[2003-04-03 08:45:50] INFO connection/_handle_source_request Source logging in at mountpoint "/cajun" [2003-04-03 08:45:50] DBUG source/source_main Source creation complete [2003-04-03 08:45:58] DBUG connection/_handle_get_request Client connected [2003-04-03 08:45:58] WARN admin/admin_handle_request Admin command metadata on non-existent source cajun -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- it appears that the URL that libshout tries to form is missing the leading slash on the mountpoint name. indeed this is true, because if I modify the libshout api function 'shout_set_metadata' to supply the extra leading slash, metadata works nicely. (well, mostly nicely - the metadata string in xmms ends in '((NULL))'; not sure why, but at least the rest of the string is there...) is anyone available to fix that real quick, or should I file a bug? thanks! -paulb ==========================================================================paulb@oasis-software.com "I'm fuzzy on this whole good/bad thing" paulb@foobox.com -Dr. Peter Venkman --- >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.