search for: mymetadata

.... there are a few things which prevent using the shoutcast DSP, first is the authentication. Shoutcast has it's own custom authentication protocol, that icecast2 would have to emulate. Secondly, updates for metadata are done via a URL call (/admin.cgi?mode=updingo&pass=password&st=MyMetadata) or something like this. This is also quite different than the way icecast2 has been coded to support metadata updates for mp3. So while it's quite possible to add Shoutcast DSP compatability, it is a matter of emulating a product that noone on this side of the fence is terribly fond of.....

...good coding sense. (Note: I have already registered my ID.) Is there an API call to set the application metadata ID? Here's what I'm doing: myFlacMetadata = FLAC__metadata_object_new (FLAC__METADATA_TYPE_APPLICATION); FLAC__metadata_object_application_set_data (uitsFlacMetadata, myMetadata, myMetadataSize, FALSE); /* this is a BIG FAT NO NO, but I cannot for the life of me find any way in the FLAC API to set */ /* the Application block application ID, therefore I am going rogue and setting it explicitly */ myFlacMetadata->data.application.id[0] = 'M'; myF...

icecast2 is a broadcast server and will broadcast both ogg vorbis and mp3 streams. This assumes that you have a source client which can produce an ogg vorbis and mp3 stream and send it TO an icecast2 server. With mp3 streams, shoutcast mp3 metadata is supported, however you cannot use the shoutcast DSP as a source stream to an icecast2 server. Current clients that we know about that can