Is there an update on the status of this fix? Thank you.
I took a look at our internal tracker today and I can see that this ticket is still under active investigation by the dev team. As soon as we have any additional information to share I will be sure to let you know.
Thanks,
Noris
Hi @noris and everyone else, Iāve been having this exact issue for some time now and had come to the conclusion it must be something Iād done (and didnāt know how to undo) because what sort of business would allow product out the door that does this to your kit?
Having found this thread Iām at least reassured Iām not quite the idiot I suspected I was. But then Iām frustrated to see the thread kicked off in December and in mid February we still donāt have an answer, never mind a fix.
So, 3 days after you last checked @noris, how are things looking on the internal tracker today, please?
Iāve put back up my old system - a Squeezebox Touch to the digital in on my MuSo. Itās now being managed through the squeezebox ecosystem. I couldnāt live with the āsurpriseā of full volume from time to time, indeed looking forward to a fix, taking advantage of Roonā¦
Also getting this with a Muso-QB (but not Uniti).
When Iām sat next to do it I turn the volume down manually before the music comes on. When Iām in a different room initially I donāt get that chance and BOOM - very loud! I hope itās not damaging the Muso when this happens.
Would definitely like this fixing ASAP.
Hi @Andrew_Storey/@Ulrik_Willumsgaard/@Rob_Kirkbride,
Thank you for your continued interest in this issue. We are still investigating this issue with the dev team but unfortunately I am unable to provide an exact timeline of when a fix will be published. All I can say is that the dev team is working on it and I will keep this thread up to date as new information surfaces and work towards a fix begins.
While this investigation occurs on our end, does @johnās post from above help mitigate the issue?
Thanks,
Noris
Hi @noris,
Thanks for the update, what a pity this is taking so long to get fixed. Re Johnās suggestion, itās inconvenient and a āwork aroundā so never ideal, but it offers temporary protection until the correct and permanent fix is made available.
Yours, patiently waitingā¦
Andy.
I also have this issue with my 2 Musoās . The problem with the work around above is that one of Musoās is also used with my Living Room TV and that has to be at around 90% to work at an acceptable volume level . Multi room is also very unreliable since the AirPlay patch was issued , so much so that I tend to go back to the Naim app for MultiRoom which would not be my choice. Iāwas surprised that AirPlay 2 was not included in the 1.6 release ?
I can reproduce this faulty behavior on my two Muso QBs. I would love to get an update when things improve. Thanks!
Me too on 3 Muso QBās
Iāve resorted to using LMS-To-UPNP for these devices
@support is there any update on this issue for Airplay clients such as the Naim Muso and Qbās mentioned here?
Hi everyone,
We are continuing to investigate this issue with Naim. We will be sure to update you all once we have more information. We appreciate your patience as we look into this!
I have a Naim Muso using Airplay. Been used for over 18 months with Roon with no issues.
Since the latest major Roon upgrade (I have the latest version), sometimes when i start Roon playing (my clicking the play icon) the Muso (and Roon) starts playing at 100% volume. The issue is intermittent. Happens maybe 2/10 times.
Same problem here.
This is being investigated by Roon. See this long existing thread:
https://community.roonlabs.com/t/max-volume-on-start-airplay-ticket-open/56288
Stephen
Same issue here. Mu-so and Mu-so Qb all jump to 100% volume. I have set Roon volume limits at 30, but this is ignored.
Many thanks!
The workaround mentioned earlier in the thread was to set the maximum volume in the Naim appānot in Roon. You may find that helps while awaiting a fix from Roon and/or Naim.
Stephen
Thanks Stephen - Will Do!
Given the potential damage to equipment and oneās hearing, especially in our litigious society, I would have expected a quicker fix to this. Itās been at least 3 months. Is there any update here?