Roon Certification News, Share


Important Changes to how Roon interacts with your Roon Ready devices:

Dear Roon subscriber,

When we first started our Roon Ready certification program, our goal was to provide a way for our customers to know that they were getting the best possible experience with their audio devices. People have come to trust Roon Ready devices to not only sound great, but work seamlessly in their homes with Roon.

In an effort to continue making Roon Ready a reliable, trustworthy signifier of quality, we are implementing some changes to what happens when a Roon Ready device has not completed the certification process.

What is changing?
Starting September 21st, Roon Ready devices that are uncertified will no longer have the ability to be enabled on the Audio Settings screen. When this change is made, uncertified devices will be discoverable, but cannot be Enabled for use with Roon.

Why is it changing?
The Roon Ready certification allows people to trust that they’re getting the best quality possible, but when products are prematurely released before their certification is complete, that trust is undermined. Not only can it create problematic situations for all parties involved, it hurts the reputation of the entire Roon Ready program.

How will this impact me?
  • If your device is Enabled in Roon’s settings, it will stay Enabled. But if you Disable the device, you will not be able to Enable it again after September 21st.
  • If you purchase a device that is not certified as Roon Ready, you will not be able to Enable it for use after September 21st.
What do you need to do?
  • Avoid Disabling the device after September 21st
  • Contact your device’s manufacturer to make sure that they are working to complete their Roon Ready certification.
We do not have a mechanism for grandfathering specific products, so when we flip the switch on September 21st, it flips for everyone at once.

We hope that taking these steps will ensure that Roon Ready continues to be a sign of quality for our customers. While we can’t comment on specific certifications that are in progress, please reach out to us if you have any questions.

If you have any questions, please head over to the Roon Community.


128x128dpac996
Yikes! I just purchased an Innuos Zenith 3 and have to use my Roon lifetime membership. They are not listed. This is no small issue. I love Roon and without it the Innuos is no good to me. Will I get it after the 21st? Can it accidentally be disabled, even for a moment, in the future rendering it unusable for me with Roon? Yes, both are possible! 
Post removed 
@grannyring, My friend has an INNUOS Sever and is calling his retailer for more information.

I am not a ROON user BUT am surprised they did not provide more time before they implemented these new server certification rules. I have no clue how long it might take INNUOS, for example, to get ROON certified. Can INNUOS get their servers certified before September 21st? I do not know and suggest you call them to discuss (ASAP). Please keep us posted.
So if your electricity goes out and you then have to reboot your non-Roon certified device It seems you are out of luck. Doesn't sound good to me.
You are correct. I sense Innuos has known about this and trust they will come though.  Good company. 
grannyring5,281 posts09-09-2020 2:26pmYou are correct. I sense Innuos has known about this and trust they will come though.  Good company.

Nothing to worry about. I asked Dylan from Roon directly at Roon forums, and this is what he wrote me back:

dylanDylan CaudillRoon Labs: Manager, Technical Support12m thyname:

Does it affect Innuos devices?

No, you will still be able to use Roon with Innuos devices.


Wonder why the Innuos brand is not listed on the Roon site as Roon certified? 
My understanding is only the devices that were advertising as "Roon Ready" but were in fact, not Roon-Ready certified, will be affected. 

I have owned Innuos since 2018, and they never claimed to be Roon Ready. 

Bottom line is, Roon themselves via their chief tech support guy Dylan confirmed that Innuos will NOT be affected. That's enough for me to not worry about this any longer.
It's all my fault I just got the lifetime sub. Roon will probably be a brick within a couple of years. Effin Murphey.
Yes. Because your Pi is technically a Bridge. Not a Roon Ready endpoint. No RAAT requiring certification, Therefore this new rule does not apply.

And not free. You are paying for Roon sub
I am very sorry. Two weeks for free. So 100 email accounts times two weeks is almost a year free. Or whatever the math is 😉 So almost free 😉
Post removed 
Because Innuos never held themselves as “Roon Ready” device. Please read the Roon language and definition. I know it can be confusing for non-Roon subscribers.

The recent move from Roon targets those manufacturers who falsely claimed Roon Ready status. And rightly so. Innuos never did that. It falls under “bridge” definition.

Let me know if you are a Roon subscriber and Innuos owner (either one) and I can expand further on this for you. What Innuos device do you own? 
I have a Zenith 3 and subscribe to Roon. Have to admit that I don’t completely understand the different Roon statuses.  I was very concerned to read the OP on this thread and began trying to figure out if I could get by using the cataloging system on the Zenith.  I emailed Innuous to get their advice (haven’t heard back yet). I was relieved to get your follow up, thyname.  I would appreciate further information.  
In my listening room, I have a Zenith MKII. It hosts Roon core, for which I have a lifetime subscription. 

Between the Zenith and my DirectStream DAC sits a Matrix SPDIF X, which is the device that's enabled in Roon.  I also have 6 Riva AirPlay speakers spread around the house that are enabled in Roon.  If I'm understanding this correctly, after the cutoff, if I disable any of those devices I can no longer enable them?
As I said: Innuos owners have nothing to worry. I further asked for confirmation from the Roon CTO, Danny Dulai, and I got it. Innuos devices are NOT affected. Period. I wish I could post screenshots here.
Post removed 
If you don’t own any Innuos device, why worry? Do you even have Roon? Why is this relevant to you?
Post removed 
OK. Let me pose the question another way: Are you a Roon subscriber, and what device do you use as a Roon endpoint? Answer this, and I can tell you with 100% certainty about your situation. Good?

Otherwise, why do you worry? Please help me understand the severity of your concerns 
Post removed 
oK. Sure. This entire exchange of ours is let’s just say heavenly 😂😂
I have a lifetime Roon subscription running on QNAP and an Innuos Zenith MK3 coming this week which I plan on setting up as the new Roon Core. Will I have any issues or be unable to move my Roon configuration?
This is much ado about nothing or very little. If your roon ready network player is listed on the roon site then you have no concern. So far the only one perhaps two that could be affected are the Chord 2go and one Briscati M3 maybe? There is probably one or two more. Devices that were never listed as roon ready are not affected. The reason has to do with using roon's SDK and licensing. 
I am shocked I am saying this, but I agree fully with what Dow Jones just said
From a purely business sense, it is a logical move.  Why would you want to support, via multiple forums, non-Roon tested and certified devices?  They go through the effort of certifying devices so we know they function.  Those product manufacturers go through the certification process - at an expense.  Tell those product lines that are not certified to get on the ship or lose part of their market share.
Except for my posts now sound totally inexplicable after the guy I was trying to help deleted all his posts for some reason
I know of the NAD M10 first hand being Roon Ready - Uncertified and of course my M3 is in the same boat.  
This does make sense for Roon’s QA process but such moves will cause some degree of angst and consternation for users of legacy stuff that isn’t Roon certified. Personally, i’m hopeful that Bricasti comes through and completes the Roon-Certification process for the M3 because the streaming Roon over ethernet solution has been a rock-star for me thus far.
I would be quite sad to have to revert to a USB streamer, but I would since I have grown to love the analog performance of the M3;
It is my understanding that the Ethernet module/digital boards are 100% identical among the M3, M1, and M21 products, the latter two being Roon Certified and not affected by the 9/21 deadline. Not much of a stretch to think the M3 will soon join the party.
It’s unlikely a firmware update will beat the 9/21 deadline, however, and as such according to Roon if the M3 is not removed/disabled it will still function as-is after 9/21. Additionally, this assumes my Roon Rock does not go up in flames and I have to rebuild. I believe rebooting either the DAC or the CORE will not change the audio device’s "enabled" status and any such power events will not suddenly end the party.

I wonder if Aurender folks are smiling a bit brighter with this news, lol, joke, no harm meant.

Cheers folks and enjoy the music!
@dpac996 The M21 is not RoonReady. It works, but does not have the certification.

The only ones that are RoonReady are the M1, M5 and M12.
ah my bad, yes I meant M12 but dyslexia got the bets fo em.
Thanks for the clarification!!

I have seen some devices disappear from Roon after a power or connectivity outage. Will they reappear or be gone forever after the deadline?

 Is there a config backup/restore option in Roon? I’ll have to go check 

Please see the response I received from INNUOS Customer Support regarding the above ROON announcement:

"The short answer: No, this does not affect Innuos servers. If you go to Roon > Settings > Audio this only affects devices that show there as "Uncertified".

 The long answer:

 There is much confusion about what Roon Core, Roon Ready and Roon Tested really is:

 1. Roon Core - this is a partnership for devices that can act as a Roon Core so they can both act as an endpoint and serve other endpoints.

 2. Roon Ready - This is a certification for endpoint devices - streamers that normally do not have storage and cannot run as Roon Core.

 3. Roon Tested - This is a certification for devices such as DACs that can connect to either a Roon Core or a Roon Ready endpoint.

 You can read a full description from Roon here.

 https://kb.roonlabs.com/Roon_partner_programs

 The current announcement from Roon applies only to Roon Ready devices and regards manufacturers who have initiated a Roon Ready certification process, where they have received SDKs and have unfinished code but are already selling their devices and market them as Roon Ready. You can see the full announcement here.

 https://community.roonlabs.com/t/roon-ready-certification/91655/63

 This is not the case for Innuos. Our devices are Roon Core servers and although they can work as an endpoint, Roon Ready certification doesn't really apply to our product. Currently, Roon only lists partners on their website for Roon Ready and Roon Tested devices. Innuos is a Roon Core partner and, as such, Innuos will not show there.

 We hope this clarifies your friends questions and concerns".


I am not a Roon users but several of my friends are so I contacted ROON customer service for answers.  I hope the above helps.  

If you have any further questions, please contact ROON Customer Support.   Thanks.  

 


I got the same response from Innuous.  Roon couldn’t have made things more confusing if they tried.  But the bottom line is good news and thanks to Innuous for their prompt response and good customer support.  
I was also given the same response. Great news, but far too confusing and a mess to follow.  Not Innuos’s fault as the response was as clear as they could make it. 
Don't understand why Roon would only give companies about 2 weeks to get their components Roon certified? I really don't know what goes into getting ones gear Roon certified but I would think it would take months to do. Anyone have an idea what the process is?
Roon notifed the companies who needed to complete the process in 2018 so they had a bit more than 2 weeks. 
@hgeifman thanks for sharing those details that actually makes perfect sense now