SamY wrote: > I'm planning to do that later today. I've been using them as a stereo > pair with LMS for quite a while though and don't recall having a problem > like this. I'm also going to try going back to the pre-dev version as > another test.
Okay. I reinstalled v1.82.2 and the problem also occurs there (along with the return of the track skip-ahead TIME_WAIT problem). I think the reason I didn't notice the volume change problem previously is that I generally would only listen to streaming sources on that Nest Mini pair due to the skip-ahead problem, which makes listening to track-based content too frustrating and, since the unexpected volume changes are triggered by a track change, I didn't encounter the problem. It would seem that the evidence now points to the fact that I am running a stereo pair of Minis, unlike you guys (Paul and Philippe) who do not see the problem on your mono Minis. So, as much as I hate to unpair and re-pair them due to Google Home's buggy and unpredictable behavior, I will try that next. Unless, that is, one of you has another spare Mini around that you can create a stereo pair and test with. Keep in mind that the testing must be done with a multi-track playlist and the volume must be changed outside of LMS during playback in order to set up the conditions for the problem to occur at the subsequent track change. Sam ------------------------------------------------------------------------ SamY's Profile: http://forums.slimdevices.com/member.php?userid=63495 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
