Max volume on start of playback via Airplay - Naim Mu-so & Mu-so Qb [Solved]

[ToneDeaf (Ozzie)]

On re-reading properly the response @Mikey got from Naim, I am more and more confused … and increasingly worried. I try to stay optimistic like @PixelPopper, but struggle .

We are creeping close to a year since first reports on potentially equipment damaging incompatibility between Roon and the Mu-so, and it does feel like being strung along. Not even sure by whom!

I for one would now like to cut through the proverbial cr… and get information which allows me to decide if it is time to give up hope on a fix and move on.

I have no real understanding of the AirPlay / AirPlay 2 protocols, including requirements for backward compatibility; or whether Roon and Naim are still actively talking and seeking a solution. Naim’s answer doesn’t suggest prioritisation at their end…

So, the following info seems relevant to make a reasonable assumption on what to expect:

• is Roon’s AirPlay 1 implementation actually fully compliant with the protocol? (I always understood it is)
• is there any real prospect of Roon implementing AirPlay 2?
• is Naim’s AirPlay 2 implementation fully compliant with the protocol?
• does AirPlay 2 compliance require backward compatibility with Airplay 1?
• are Roon and Naim still actively communicating and trying to solve this between them, for the benefit of their customers? Do they have confidence in a solution?

I may have missed answers in threads on this forum - if so my apologies. Someone from @support who wants to chip in on any of the above, perhaps?

(I am not in the blame game, just looking for information so I can decide whether to continue to try and deploy the Mu-so in combination with Roon)

Over to the stream of conscience and my specific ‘problems’ with the response from Naim. For those with too much time on their hands and not easily bored. (Maybe put some music on, but be ready to turn the volume down)

“Only Mu-so and Mu-so Qb 2nd Generation - along with other new-platform Naim products – are officially certified as Roon Ready. Roon availability on earlier-generation products is based on a Roon-derived software workaround that we endeavour to maintain, but which due to resource restrictions is not a priority development area for us at this time.”

In my understanding the first sentence is true, but has nothing to do with the problem. I thought “Roon Ready” is about RAAT, and has nothing to do with AirPlay or AirPlay2 compatibility of the Mu-so? The (first generation) Mu-so was and still is listed by Roon under 'Roon Tested AirPlay devices", which I assume is correct.

I also fail to completely understand the meaning and implications of the second sentence: ‘Roon availability’ - Is this a reference to AirPlay ‘1’ standard compliance?; ‘Roon-derived software workaround’ - also not sure what this means. Was there already a special ‘workaround’ for Roon required before the Mu-so implemented AirPlay 2? - We know that Roon was/is not supporting AirPlay2 - in March Roon said:

Airplay 2 Broken

We haven’t made any announcements about Airplay 2 support in Roon. Right now, Roon does not support Airplay 2. Airplay 2 devices should be able to play Airplay streams, and we fixed some issues related to this in the last few months. So, to be clear, while Airplay 2 devices should work with Roon, Roon is still sending Airplay, and people shouldn’t confuse this for Airplay 2 support.

The bit ‘Airplay 2 devices should work with Roon’ is probably crucial. Does Airplay 2 compatibility include / require correct handling of Airplay ‘1’ streams?

Naim’s answer continues to say:

The original Muso was never Roon compatible. This was something we found we could add by some “workaround” in the software. With the change by Roon this stopped working. Any new “workaround” will involve some complexity.

I guess if we had not added Roon to the original Muso. We would not be in this situation. So no idea of timescale.

Again - the first sentence is confusing in its use of ‘Roon compatible’ and appears beside the point, if the problem is with AirPlay / AirPlay2. The remainder only seems to try and put ‘blame’ with Roon, which does not bode well for collaboration towards a solution.