Playback errorUnable to open item for playback (Unsupported format or corrupted file) : "http://bistro.fm:9000/"
Failed to render the file
Hi Chinch,Are you suggesting that putting the path to lame below will influence the Vorbis Streamer 1.1 plugin? kode24 what do you reckon?
Great detailed info. That helps out a lot (to everyone that may read and want to help). As far as the LAME encoder path influencing the Vorbis Streamer, no; that's why I originally said I don't understand LAME's role in the process, unless you were transcoding from MP3 to OGG or vice versa... it would still be good to have that info about what is your internal format, what you're wanting to broadcast to the relay servers, even as much as bitrates, etc. Obviously LAME doesn't do anything with OGG/Vorbis files, but FLAC.exe would, using this switch:--ogg When encoding, generate Ogg FLAC output instead of native FLAC. Ogg FLAC streams are FLAC streams wrapped in an Ogg transport layer. The resulting file should have an '.oga' extension and will still be decodable by flac. When decoding, force the input to be treated as Ogg FLAC. This is useful when piping input from stdin or when the filename does not end in '.oga' or '.ogg'.I've never used any other encoder like anything from Xiph foundation, so I will be honest and say that the OGG or Vorbis format that you'd stream, I'm not really familiar with... but anything you use to encode or decode, transcode... I would at least be sure to test adding the full path to the option you mentioned. With my limited knowledge, I don't see a problem with using that FLAC encoder/decoder to take something from MP3 to a streamable container format like that... just use a bit of piping or command line juju to get it done, but certainly not impossible. Any more detail you can give me on the formats and anything else? kode24 is gonna be far more helpful than I am whenever you get a response there, but I'm just trying to help whatever I can in the meantime....
The result is that a connection is made to the shoutcast server, even yp are updated when I hit play but no music is streamed....Winamp just remains silent.
Crossfading and Shoutcast doesn't do well in Winamp for instance, but I'm not sure if that's the problem here in foobar as well.
I would really like foobar to be able to stream to a shoutcast server.
not being able to pass the stream data onto the correct plug-in
Quote from: hac on 20 April, 2012, 10:30:17 AMThe result is that a connection is made to the shoutcast server, even yp are updated when I hit play but no music is streamed.that's most likely from it not being able to pass the stream data onto the correct plug-in (since it's basically assumed that SHOUTcast is MP3 or an AAC).
The result is that a connection is made to the shoutcast server, even yp are updated when I hit play but no music is streamed.
sounds like a possible explanation, so why is that?
I don't understand the text you wrote in brackets...
As for "demand" ... how many webradio broadcasters are there? Compared to users not so many - but it may gain quick popularity with those few that are currently stuck with commercial stuff like sam broadcaster, especially if they notice foobar can be remote controlled from a phone.
As a developer, the Shoutcast metadata format is atrocious. Winamp was far and away a superior Nullsoft product when compared to Shoutcast....Please don't ruin good Vorbis streams with Shoutcast metadata.
i assume you mean the StreamTitle=xxx insertion? if so then there's not much which can be done about it if people use a v1 based DNAS or a v1 only client as that cannot be changed. if using a v2 DNAS and v2 compatible client then the metadata comes through in it's own 'metadata' packet type which is xml inside it so it's a lot more flexible over the v1 method though maybe xml wasn't a great idea since it's larger than it necessarily should be (but that's now something which is inplace so there's not too much which can be done to change it). there's more details about the specification and xml-based metadata here.
As an added bonus, when you rip that stream, it is magically an entirely valid Vorbis file, and it even uses the metadata as new-track markers.
into the stream between packets.