Groups in 4.10.13 don‘t work as before
Answered
I am running a standard group with two Flex 2i plus a NAD T778. One Flex is the group‘s primary speaker. The T778 is not always switched on, but until the latest update it was no problem at all to switch it on or off while the Flex‘s were playing. After updating to 4.10.13, if all three speakers are playing and I turn off the T778, after some seconds the others also stop playing while the app still shows the music playing… Stop and start playing via the app doesn’t do anything. There are only two ways to play music again (as far as I found out): power cycle (!) the primary speaker or switch on the T778 again. Something must have changed regarding group handling, and I‘m sorry to say it has changed to the worse…
By the way, I already did the whole „shut down everything, wait five minutes…“ procedure without success.
-
Official comment
Hi Heinz,
I have escalated your feedback to a support request. A member of our support crew will reach out to you soon. -
I have customer having the same similar issue. The audio cuts in and out and rooms disconnect. Everything works fine one zone at a time.
0 -
I discovered that power cycling the primary speaker is not always necessary, sometimes you just have to wait until "connecting to group failed" appears in the app, then you can stop the (inaudible) music and restart it... weird... and inacceptable because this has worked fine since my first Node (N100)…
0 -
No change in 4.10.19 - and no contact from support until today. Quite disappointing.
0 -
No change in 4.12.4, well to be honest - the error message changed to: “Disconnecting group due to disconnected player“… Why not let the remaining players continue playing as it was for many years?
0 -
Updated to 4.12.11 - still no change…
0
Please sign in to leave a comment.
Comments
6 comments