If I hit a problem in the Default Media Receiver, where should this be reported? I ask because I've reported a possible issue in the issue tracker, but this has been marked as "Not SDK".
https://code.google.com/p/google-cast-sdk/issues/detail?id=499
I guess this raises the issue of what is in the Default Media Receiver and if the source is available anywhere? For audio streams is it just a wrapper around the HTML5 <audio> tag? And does that mean there's the guts of Chrome running on the Chromecast implementing HTML5+Javascript and so my problem is really with Chrome and it's HTML5 support for <audio>?
It all relates back to wanting to be able to cast audio from desktop applications like VLC, Winamp, Windows Media Player, or iTunes. That led me to media servers like Logitech Media Server, Play To DNLA renderers, Shoutcast radio streams. I've hit some kind of brick wall on all of these. I'm kind of hoping that Cast For Audio will open something up along with VLC 2.2 which allegedly has Chromecast support. And Tunein may eventually get support for casting Shoutcast radio streams from desktop web.
At the moment, the html5 Audio tag is just a bit primitive for playing mp3 streams.
In particular, repositioning the audio stream IN THE RECEIVER, i.e., setting the position attribute of the audio tag, is very responsive, usually only several seconds to buffer enough of the audio at the new position to begin playing. If anything, I would vote for a BIGGER buffer in the receiver. :-) BTW, you don't need to have a custom receiver to do positioning in the receiver, just a sender app that can send the right media control channel commands to the default or styled receiver. Many apps do this.