Audio streaming, particularly with Shoutcast on the Android platform, is a black art. Often it's a case of if it works great, if it doesn't then nobody seems to know why. Having found that my latest client's single stream takes 30 seconds to start from when the 'start' button is clicked I fear I may lose said client given it's always the developers fault!
I have generally found that if a url ends with a port number then we stand a good chance that it will play, however they are using Shoutcast 2 which allows multiple streams to come off a single port - and it's these that the underlying Android Media player seems to struggle to start to play within a reasonable time.
Now it's often the case that adding ';/' to the end of a URL will force an otherwise sulky stream to play on certain equally grumpy Android devices as it apparently forces Shoutcast into 'MP3 OVERIDE mode' - at least on Shoutcast version 1. But what of version 2? Has anybody had any experience of getting Android to play streams off a Shoutcast version 2 server? And if so what was your experience?
As much as this is less of a question and more of a discussion point I am not expecting many (or any) answers, but there again I can't think I am the only one having problems with audio streaming on the Android platform.
OSX 10.9.4 Android 4+ Titanium SDK version 3.2.3.GA