I have just started using Roon and have been happy but I have found I cannot stream to my Muso either from Qobuz or my NAS.
The track does not play and there is no progress on the slider. This is persistent: it never works.
I have enabled the switch to deal with Airplay compatibility issues.When I look at the signal path it shows Airplay 2.
I have seen other threads on this and thought the issue had been resolved.
I use Qobuz and hold my music on a Synology 720+.
Details on your Core machine: (OS, Hardware specs, Roon build) Synology 720+, OS = DSM 7.2.2, Roon = 2.0 (build 1490)
Several Remotes: Windows\Android\Chrome O/S, Roon = 2.0 (build 1490
Networking details: Synoloy NAS 720+ , Fritzbox router, all on WiFi
Library details: 700+ albums / Qobuz streaming service
I think the compatibility issue exists only with the Mu-so version 1 because it only supports AirPlay 1. (This compatibility issue is not fixed, at least I don’t think Roon Lab stated so, but it was said that they were working on it).
I believe the Mu-so 2 should work with AirPlay 2, though.
However, you may have to add the Mu-so as a speaker to the Apple Home app. (This was, at least, part of the solution for the Mu-so 1, in addition to the compatibility mode). You can try in any case. The process should be the same as explained here for a different endpoint:
My Muso is Gen 1 so does not support AirPlay 1. cause it only supports AirPlay 1. I cannot recall why I thought the issue was resolved but I think Roon Labs were working on this in 2018.
I also saw the advice on adding the Music as a speaker to the Apple Home app. For me to his would getting hold of an Apple device, something I am not going to do
Thanks for the very helpful advice.
I will think at the his point I am looking for Room Labs to confirm there is no solution to this issue and that this is not an issue that they are going to resolve?
I do have a work around via my Naim app as I can group my Atom with the Muso.
Should the topic title not say “Mu-so 1”, then, instead of “Muso 2”? That’s quite confusing.
In the case of the gen. 1 you need to do both things:
Enable compatibility mode
Add it to the Apple Home app.
This always worked in numerous previous cases, but yes, you need an Apple device.
I believe this is they best we have, but they typically don’t provide timelines:
If you need more, you can try to ask in the Feedback section of the forum, but don’t hold your breath. (This thread here is in Airplay which isn’t typically monitored by Roon staff.
Yes apologies for the Muso 2 error. Thanks for the information.
I note the feedback thread is where I should post for support.
Sadly, as I really like Roon, I think I am going to depart as I have a couple of other small niggles with it, which is a shame.
No, the Support section is for support. I meant if you don’t need support (as there is nothing else to do right now) but want to ask if and when Roon Labs will have an update that makes the Gen. 1 work again without an Apple device, then yo can try Feedback as the other forum section that Roon Labs is monitoring. (The Audio Gear Talk and Roon Software Discussion sections are more for users discussing among each other)I
Ah ok.
Thanks for the info.
What is your view of the their support - there seems to be some very poor views of it but people who are unhappy are more likely to complain than happy people praise.
Thanks for your time
Official support can be slow as they are only 4 people and the things they have to figure out can be very complex. It may be Roon bugs that only occur with specific libraries or usage patterns, it may be (and very often is) a misconfigured or faulty customer network, or software as well as hardware issues with a myriad of customer devices, and so on.
Figuring this out without direct access and often based on incomplete information is legitimately a challenge in the best case, even if resources sufficed. It doesn’t help that a significant number of customers are computer illiterate and require extended handholding for resolution steps that could otherwise be completed in 5 seconds.
The small staff size problem is squarely in Roon Lab’s court, and the process could be improved in places, but I think all of us should try and appreciate what a challenging support environment this can be.
In your case, however, I don’t think there is anything that support can do. The issue is in some combination of Roon’s AirPlay 1 backward support (which works with many other devices, though) and something in the Mu-so gen.1’s implementation. This started to happen around spring when Roon added support for AirPlay 2. The issue is known and documented, and all support can do right now is to suggest the workaround (but you don’t have the required Apple device…) and wait for an improvement coming through from development.
FYI @Paul_Langdon3, by chance I came across the central tracking thread for this issue again, and in July they wrote that a fix was in the pipeline. No info about an expected release but maybe there’s hope. In any case, they should publish any news in this thread:
Thanks for all the info. I have decided to stay with Roon for a year and see how it goes.
I did ring the support process a bit opaque but you have helped me out.
Given the thread setting out that Room are actively working in this then I think this thread could be closed?
As I already explained above, it’s because Roon is using AirPlay 2 and the Mu-so 1 you have supports only AirPlay 1. Roon has a built-in fallback for AirPlay 1 and it works out of the box with most AirPlay 1 devices, but for some reason it doesn’t work with the Mu-so 1.
As I also explained above, the solution for the Mu-so 1 is currently to 1) enable the compatibility mode in Roon, AND 2) add the Mu-so as a speaker to the Apple Home app. However, as you wrote, you don’t have an Apple device, so you can’t do this.
The compatibility mode is only for the compatibility between AirPlay versions 1 and 2, but for some reason it is insufficient for the Mu-so 1. (Again, all of this was explained above. You may not like it, but that doesn’t change it).
Unfortunately, the ONLY streaming protocols that the Mu-So 1 supports are AirPlay 1 and Bluetooth. The former currently requires the Apple Home app with Roon, the latter doesn’t help you because Roon can’t send via Bluetooth. For confirmation, here is the best list of Mu-so 1 specifications that I can still find. (It’s for a Mu-so Qb Gen.1 but this is the same as the larger Mu-so Gen. 1):
Therefore, there is no other streaming protocol that Roon could use (like Google Cast, for instance), because the Mu-so 1 doesn’t support any.
In addition, the Mu-so has no hardware inputs, meaning that there is no way to plug it into a the Roon Server computer or into a separate streamer, either.
And therefore, your options currently are:
Get a cheap older Apple Device so that you can use the Apple Home app.
Wait until Roon Labs releases a fix. As mentioned in the forum thread that I linked above, they wrote that they are working on something, but there are no target time lines and it’s probably best to not set expectations very high.
I was not clear enough and maybe should be creating a new thread (I will if I cannot resolve the Muso issue as below). I have parked the airplay issue.
The issue I have now is I am unable to get anything through the Muso now via Roon. This could be a separate issue though.
Turning Compatability mode off makes no difference.
There is no usable input on the Mu-so gen. 1 other than AirPlay. AirPlay doesn’t work for you because currently the Mu-so 1 requires the Apple Home app, which you don’t have.
To clarify, I am currently unable to play music that is my own (held on a Synology NAS) or through Roon radio. Should not require Airplay to do this. Prior to changing compatability mode this was working.
The muso has both optical and stereo line input. So if your computer is relatively close to the muso, you can use a usb dac as an interface. Eg pc playing roon software, usb dac selected as output, connected to muso line input.
Other options are; raspberry pi running roon bridge, usb dac attached, output connected to muso line input. This was my solution when airplay stopped working. I use this every day, with an audioquest dragonfly black.
You might not have the extra bits spare, but it is a solution until airplay compatibility is resolved.
