In this post, we clarified the position we were taking in regard to uncertified Roon Ready devices. After hearing back from many Roon users on the subject, we’ve come up with a solution to address the concerns we heard.
We believe this solution addresses the concerns of most affected users while also pushing the industry towards a higher standard.
First, let me reiterate our goals:
Enforce the Roon Ready licensing terms, thus ensuring that Roon Ready devices made available to the public can be trusted to provide a great experience
Ensure partners do not release beta quality and/or uncertified Roon Ready devices to paying customers
Ensure that the Roon development and support teams have what they need to properly support Roon Ready Devices for all customers
Next, let me explain anti-goals (things best to be avoided):
Denying users the ability to use devices that may have been sold under the false pretense of being certified Roon Ready devices
Making it difficult to change a Roon configuration because one happens to be stuck with hardware that may be uncertified.
The announcement that we would be deprecating the ability to enable uncertified Roon Ready devices (but keeping existing devices enabled) on September 21st met the goals but in retrospect did not pass muster against all of the anti-goals. Most specifically, anti-goal #2 was violated.
Without a software update and the lengthy process related to testing and releasing, our choices on how to address this are limited, but we believe we have a solution:
There are a group of Roon accounts that already have access to uncertified Roon Ready gear in development: developers employed by the manufacturers.
The solution is to turn those paying end-users who are affected, into “developers” so they can keep using the uncertified devices while the manufacturers complete their work and testing.
Why does this work?
Let’s talk about how this solution fits the goals again::
It enforces our Roon Ready licensing terms by removing the ability to use uncertified Roon Ready devices from most users that may be sold these uncertified devices
It ensures manufacturers will not release beta quality and/or uncertified Roon Ready devices to paying customers because those customers will not be able to enable these devices. Come September 21st, “public betas” will not be possible.
Device manufacturers will have to finish certification if they want to make marketing claims or sell on the features of Roon Ready support. If they do not, new sales will be severely reduced as most of the current and future Roon users will not be able to access these devices.
And now the anti-goals:
It allows existing users to maintain full access, with the caveat that these devices may be unstable and the current policy that they can/will not be supported by the Roon Support Team will continue.
As long as the user does not change Roon accounts, it keeps their access the same as before.
What does this all mean for me?
- Existing Roon accounts using uncertified devices as of September 21 can request to keep all access to their currently owned uncertified Roon Ready devices before September 21st. Once access is granted, they will see no changes to their access or ability to enable/disable those devices.
- All other Roon accounts will no longer be able to enable uncertified Roon Ready devices on/after September 21st.
So, how do I get the fix?
Fill out this form: https://zfrmz.com/hQNRXlk8iLiJaQeIN2Dv
Everyone, thanks for your feedback and for putting up with our growing pains. We really do appreciate that you are all passionate enough about Roon to voice your opinions.