[icecast-dev] metadata handling

Michael Smith msmith at xiph.org
Thu Apr 3 06:25:39 PST 2003



On Thursday 03 April 2003 23:55, Paul Bournival wrote:
> 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.

Your application is required to give a mountpoint that includes the leading 
slash. libshout should probably treat it not being there as an error, though 
it doesn't currently.

<p>>
> (well, mostly nicely - the metadata string in xmms ends in '((NULL))';
> not sure why, but at least the rest of the string is there...)

Not sure why that is, I haven't heard anything about this from anyone else. I 
don't know much about mp3 metadata in the real world, but it apparently works 
for many people (amazingly).

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 at xiph.org'
containing only the word 'unsubscribe' in the body.  No subject is needed.
Unsubscribe messages sent to the list will be ignored/filtered.



More information about the Icecast-dev mailing list