bpa wrote: > You are casting from the phone so this means the phone battery will run > down quite quickly. A better long term would be for the CCA to get its > stream from LMS direct to CCA - this would also enable 96kHz streams to > be sent to CCA. > > Casting a tab requires using the HTML5 Audio subsystem - squeezelite > would need to be rewrittein in html/Javascript to run in a tab and even > then web security regarding sockets would mean a shim layer or > tunnelling could be needed.
BTW, after having made baby steps in understanding how casting works, I'm now cautiously optimisic that the UPnPBridge I wrote can be adapted to chromecast. As you said before, a lot of mechanism are very close and the architecture of squeeze2upnp can be kept unmodified. The control flow (pause, play, volume, time feedback, metadata) seems to be similar and the web server needed by the receiver is the same (unless HTTPS is needed, which would be a real pain for me) ... I have the SSL connection to CCA working but I need to workout this protobuf in C problem. LMS 7.7.2 - 5 radio, 3 Boom, 4 Duet, 1 Touch, 1 SB2. Sonos 2xPLAY:1, PLAY:3, PLAY:5, Marantz NR1603, JBL OnBeat, XBMC, Foobar2000, XBoxOne (sort of) ------------------------------------------------------------------------ philippe_44's Profile: http://forums.slimdevices.com/member.php?userid=17261 View this thread: http://forums.slimdevices.com/showthread.php?t=104383 _______________________________________________ discuss mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/discuss
