I ran into a problem using Ogg on streamer.
Fortunately, Iain and hopped onto the chat and stated that there is an ogg header problem which will leave a client to keep buffering, and buffering, etc.
Usually turning on stream titles in the encoder will fix this.
An Ogg Vorbis stream has a header that preseeds the actual encoded audio data. It contains the current song title, the decoding tables for the audio, + some other gubbins. The header is supposed to be marked in a particular way to indicate it is a header, by some flags in particular some index bytes all being zero.
But on some encoders, if you disable stream titles, the header changes. The zero index bytes are no longer all zero. Having looked at the Ogg Vorbis specs I'm sure this is wrong, but some players apparently cope with it.
Unfortunately this causes Streamer to not pick up the malformed header, and without a header the stream can't be broadcast or played.
I suspect other players work by not looking at the index bytes, but by looking for a change in the stream signature. Each song is a mini stream with a header and following body, and each block of header/stream shares the same signature, and it changes with each song. Winamp at least uses this method because if I make all the signatures the same for all songs it does not notice any new headers so doesn't show song title changes.
AACPlus seems to be a lot more stable, but it's not an integral part of the player yet.
And is unlikely to be for a while. I use Fmod to do the audio, and the author of that has stated he won't be including aac/+ in it for licencing reasons.
The only alternative would be to borrow winamp's decoders, but I can't put these in a streamer installer. So it would involve messing around collecting the files yourself like you have to do for oddcast for example, and that is no good for the dumb listeners who half the time complain about having to click even once to make it work.