Hi all,
I just got the new Marantz MCR 60n DAB (in Europe) because I trusted official information from both Marantz and Roon that this device is Roon Ready. Unfortunately my Roon Server only identifies it as an AirPlay2 endpoint.
As there is no firmware update pending, for me it means the device is not Roon Ready 
Anyone any idea what to do please?
Hi Marek,
With Airplay2 you can stream Roon with 44 kHz, i.e. cd resolution. Higher resolutions are downsampled to 44 kHz. You could achieve high res with external apps like lms-to-upnp or Roon extension upnp, if you need that and can hear the difference.
For lms to upnp: GitHub - philippe44/LMS-uPnP: Integrate UPnP players with LogitechMediaServer · GitHub
Did you try restarting your core and the Marantz?
If it still doesn’t show up as Roon Ready, raise a support issue with Roon.
The Marantz website only states that this device is Roon Tested (i.e. Airplay), although Roon says it is both Roon Ready and Roon Tested. Perhaps this means that a firmware update is on the horizon. Or maybe Roon made a mistake here.
The device is pretty new. I wouldn’t be surprised, if the firmware with roon ready function isn’t yet available. Sometimes companies advertise things they haven’t yet fully implemented and deployed.
You should ask Marantz, not roon.
Marantz’s own model tech. data says “roon ready”, the manual shows the “roon ready” label. But yes, on the model’s web page it shows “roon tested”. 
The Marantz website here says it’s roon ready.
There have been cases (eg WiiM Amp Pro) where the firmware release was been delayed.
Both Marantz and Roon should be able to resolve.
Very likely wrong label. Everywhere else it says roon ready.
FWIW I bought the WiiM Amp Pro having seen it was Roon Ready on the Roon website.
I wan’t alone!
When I installed it - it didn’t show as roon ready.
There was some discussion on the WiiM and Roon forums and it turned out the approved firmware wasn’t quite ready for release.
I think it was 3/4 weeks until it was released.
So it’s possible the same has happened here.
Did the firmware update when you first set up the amp? If not, it can sometimes take a while and you may need to force an update … make sure you have good connection to the internet.
Try power cycling the amp first. You should be able to see the firmware in the HEOS app:
settings → my devices - choose your amp → advanced.
A firmware update can be triggered from there.
Hope it helps - been there myself - with a different Marantz device.
Yes, but restarting Roon Server did not change anything…
Just ask Marantz 
>Did the firmware update when you first set up the amp?
No it did not update. Also the HEOS app says: “Update status: FIRMWARE CURRENT”
OK power cycle and reboot are the only other things I can suggest. Odd. I’m sure it is ROON ready!
UPDATE I missed there were two versions of this product 
below is for the MCR 60n and not for the more recent MCR 60n DAB model.
—-
It’s listed on Roon’s partners page as both Roon Tested and Roon Ready …
I would suggest you require assistance from Roon technical support to get their advice.
To equip the Roon Technical Support team to assist you directly, please follow this link to provide the details of your case to Technical Support:
There are 2 models: MCR 60n and MCR 60n DAB. Roon only lists the former as Roon Ready. You could therefore argue that MCR 60n DAB is not.
This also aligns with the product page over at Marantz, which says exactly the same thing. MCR 60n is Roon Ready and MCR 60n DAB is only Roon Tested.
I still believe the MCR 60n DAB is supposed to be Roon Ready (some day in near future at least…) as the following leaflet is included with the manual:
It’s common that manufacturers jump the gun.
but it doesn’t matter what the leaflet says. If the Roon website doesn’t list it as Roon Ready, then it isn’t (yet).
All confusing - hopefully it is certified roon ready soon - and then a firmware update should come automatically and you’ll be in busines!
I suggest that you open a TSR as @Carl proposed so that you get a definitive answer from Roon Labs.
There have been cases where manufacturers’ model numbers were slightly different, yet the firmware used was the same for both variants. One would correctly register as Roon Ready in Roon, while the other would not, because of the slightly different model number.
