oyvindo wrote: > That was 0.2.8.0.1 right? > It seems to work - as far as I can tell. Which is good. The delay is > noticeable, but just barely... > So why did this problem surface so suddenly? Was it a CC background > update from Google that screwed up?
I do think it is. As soon as you move to version, 1.24 the problem happens. And Google decides to roll ou FW version the way they want. It might be my bad, but as I've asked here https://stackoverflow.com/questions/44125585/chromecast-audio-firmware-1-24-88047-broken, it really looks like that the 1.24 does not work according to spec. I assume that most people use SDK and probably the SDK is using CCA in a "brute force" way: whenever you want to play a track, launch the receiver, load the track and play. Even if the receiver is already loaded. And when you stop a track, unload the receiver. LMS 7.7, 7.8 and 7.9 - 5xRadio, 3xBoom, 4xDuet, 1xTouch, 1 SB2. Sonos PLAY:3, PLAY:5, Marantz NR1603, JBL OnBeat, XBoxOne, XBMC, Foobar2000, ShairPortW, JRiver 21, 2xChromecast Audio, Chromecast v1 and v2, , Pi B3, B2, Pi B+, 2xPi A+, Odroid-C1, Odroid-C2, Cubie2, Yamaha WX-010, AppleTV 4, Airport Express ------------------------------------------------------------------------ philippe_44's Profile: http://forums.slimdevices.com/member.php?userid=17261 View this thread: http://forums.slimdevices.com/showthread.php?t=104614 _______________________________________________ plugins mailing list plugins@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/plugins
