Thanks for this update @Torq I did not get this email so I need to check whats going on.
Thanks again.
2 Likes
Looked further in to this and is related to Network Audio Devices that capitalize in the “Roon Ready” wording and take advantage of the market when there is no such thing.
Everything else will be the same so as @Torq stated, not a real concern tbh.
Note: The above is a personal statement gather of data from community posts and not of Official Roon.
2 Likes
Oh, it’s still a concern.
It’s a smaller concern than if it wasn’t just un-certified (i.e. haven’t finished certification) “Roon Ready” devices, and it’s not all Roon’s fault, but this is the sort of thing that Roon customers should have been made aware of a year ago (when Roon announced this position to manufacturers).
How much of it is he-said/she-said I don’t know, but there have a been a number of responses from major manufacturers already saying they’re waiting on Roon for final certification (and have been for some time).
As a customer, I would expect them to either a) clear ALL pending (in-progress) certifications before disabling the ability to enable them and/or b) give actual customers rather more notice.
2 Likes
Except you have the likes of Chord saying the 2Go certification is waiting on Roon. And yet as an owner of the 2Go, I know for a fact it is not “Ready”. It mostly works for me, but I’d never give it a certification pass even with the current 1.0.3 firmware…
As you said, there is unfortunately a lot of he-said/she-said going on here. And I suspect that’s partly why Roon is putting their foot down.
3 Likes
I got you, I think there is more to this that meets the eye. There is many companies advertising the roon ready wording and capitalizing on it, Thats what I am referring too. Whatever they have in the backlog for certifying is not of a concern, we will only know one side of the story. We can only assume who is right and who is wrong.
1 Like
This, very well said and very well put.
1 Like
Thanks for the update. I’ve been having issues with their community forum board this week. Always curious is to why something that works fine suddenly goes sideways.
I have one uncertified Roon device connected. A PS Audio Stellar Gain Cell DAC. That looks lie it would fall under your update category. PS Audio also said they had no interest in certifying the Stellar Gain Cell DAC either.
Will this affect the use of a Raspberry Pi as a Roon endpoint?
1 Like
Interesting from another site where a user contacted Roon management and asked a series of questions. :
from Roon CTO:
"This change prevents manufacturers from signing the Roon Ready license agreements, obtaining our SDK, building hardware using our technology, and then skipping our certification/review process and releasing unfinished, unreviewed products straight to customers.
We don’t charge for certification, but going through our certification process is a hard requirement for manufacturers to use use our technology. It is the only way that we can maintain the quality + support level that people associate with Roon Ready.
A tiny minority of manufacturers have released uncertified devices. We have been communicating with manufacturers about this coming change for over a year, and have provided ample time for them to come into compliance, and most of them have."
and
“This is only about manufacturers who licensed the Roon Ready SDK from us commercially, then violated our license by skipping the Roon Ready certification process. It’s not very many manufacturers. We began communicating with manufacturers about this in 2018. They have had ample warning to sort things out.”
from Roon technical support manager:
"This does not affect non Roon Ready devices like USB DACs, Roon Tested devices, Airplay, Sonos, etc. These devices will continue to be supported. If your device does not specifically say Uncertified on the audio settings screen, it will not be affected."
2 Likes
The Pi is not using Roon’s RAAT network protocol, which will soon require a device certification. So, it should be fine. Uses DLNA?
It’s my understanding that RAAT forces TCP communication (instead of the “spray and pray” method of UDP) amung other proprietary differences. Thus, error checking is baked in to the communication method, and bit-perfect can be assured.
If your Roon core is on windows 10, open a command prompt and type “netstat -ab”. You should see a TCP Roon connection to your Pi.
3 Likes
Sweet! Thank you. 
Hmmm…hope I get my Sonnet Hermes delivered prior to the 21st so I can see if it’s certified. It should be as it’s listed as Roon Ready on the roonlabs website.
1 Like
This is from roonlabs blog. The guy responding on the part of Room is Danny - Roon COO:
You have not spoken to the right person at Chord. This is not the case. We are waiting for new firmware from them.
Agreed, this is the type of behavior that will become impossible after September 21st. The manufacturers of these devices are cheating the process, and you were “duped” into believing it was signed off by us as Roon Ready. This is an example of the trust of the Roon Ready program being eroded by misbehaving manufacturers.
This is one of the things that needs to be fixed before they will be certified. That said, you will still be able to use the 2go via Airplay until they get their act together.
3 Likes
Roon Bridge, which you get in Ropieee for example, uses RAAT. Roon Labs provides Roon Bridge to end users, but they don’t allow vendors to pre-install it. So, you can put Roon Bridge on your open endpoint, either directly or through Ropieee, DietPi, and the like, but you cannot get it pre-packaged by a vendor.
1 Like
Thanks for that info. There you go then. =)
Looks like Pie2Aes is supported.
3 Likes
Sonnet says this won’t be a problem for Hermès as it’s fully certified.
3 Likes
Incorrect, It uses RAAT and TCP with Roon bridges.This only affect devices which have cheated the certification process. Ronn birdge software does not require certification as they do not use the SDK.
1 Like
A more clear explanation here:
3 Likes
Some interesting info:
3 Likes
It is interesting that there is so much confusion concerning compatibility of Roon with streaming devices (which are inherently computer devices). History has taught me that I need to be absolutely sure that any new device will be compatible with what I have. The way to determine that is by strict attention to the many certifications that you find in the computer industry.
Streaming audio is no different, and the components can be even more expensive. So, whenever I research a “Roon Ready” or “Roon Certified” device, I go to the Roon Partner’s website and make sure that the device is listed appropriately.
Call me cynical, but I don’t necessarily trust the device manufacturer to be candid about their certifications. Instead of listing their device as “Roon Ready”, they should be listing the device as “Roon Ready Certification Applied For” or a similar statement. Then the consumer would understand the risks involved in purchasing that device if they wanted Roon compatibility.
6 Likes