Can someone explain why the Spotify application is stable and not the Spotify-Connect function.
I think I've tried to explain this many times before... as far as I understand the issue. In short: the Connect mode is a hack.
Connect mode suffers from the fact that both LMS and Spotify believe they are in control of the playback. Both believe they keep state (shuffling, volume, play/pause etc.). So they somehow have to be kept in sync. This unfortunately all too often doesn't work as expected. Spotify tells LMS to stop playback, while from the LMS side of things there's no such information. Or LMS thinks that the stream is ending, while Spotify believes it still takes a few minutes etc. Spotify thinks it needs to reset the volume, as a new client is connecting, while LMS would rather continue to play in the previous volume etc.
All these conflicts lead to a ton of code dealing with exceptions when to handle a state change and when not. But unfortunately this code is far from perfect.
Is the TIDAL app through the LMS just as flaky ????
Spotty is the only integration providing support for the service native app. Again: this has been explained before. TIDAL doesn't provide the necessary information to us, and we can't leverage the hacks found out there, as Logitech has contracts with TIDAL.
_______________________________________________ plugins mailing list plugins@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/plugins
