That’s exactly what it says
According to Chord, the 2go streamer (which is currently uncertified) is awaiting certification from Roon and the two teams have been actively engaged over the past year or so. @john can we get some sort of comment on this and whether Roon will finalize certification for the 2go module before the deadline?
Edit: To be clear, Chord has indicated (to me) that the ball is in Roon’s court hence my question.
That is really a great feature! Kudos to you…
Why not simply downgrade those devices to “Roon Tested” (which means they continue to run after 21st) and avoid the whole kerfuffle?
1 Like
Hello @tretneo,
We cannot give expected timelines for Roon Ready certification. When the device has passed certification testing, we will certify it.
-John
I think that’s more on Chord than Roon, when you consider how flaky the performance of the 2go is on the latest firmware… (Disclosure: I own a 2Go and it works ok for me only about 95% of the time. And by the discussions over on headfi, I’m one of the “lucky” ones that has relatively few problems.)
Honestly, I see the 2Go as a poster child example for why Roon needs to put their foot down. It costs them time and effort to deal with supporting products released prematurely that clearly have significant issues and which the end user is more likely to blame Roon than the vendor of the product.
1 Like
Wow! What a great thought! Why didn’t Roon think of that, implement it and move forward? Because they want to punish the end user to put pressure on the vendors.
The leadership of Roon don’t have a clue about who is paying their bills!
1 Like
Hello @7NoteScale,
I strongly recommend reaching out to ELAC regarding this issue. They will be best positioned to determine why your Z3 is misreporting itself to Roon. It could be as simple as needing to update the firmware.
They will have the ability to reach out directly to our technical team if further diagnostics are needed on our end of things.
-John
Not at all, the Schiit DAC is Roon Tested device (ie USB) not Roon Ready device which uses Roon’s SDK to implement network connectivity via RAAT.
Why not simply downgrade those devices to “Roon Tested” (which means they continue to run after 21st) and avoid the whole kerfuffle?
Because it rewards misleading advertising by manufacturers. Chord is the canonical case. They were labeling the 2go as “Roon Ready” when I got mine, in good part because of that misleading label. But it was not, not just in theory but also in practice. Chord and their distributor got my money, but the product is by far the worst Roon endpoint I’ve owned in terms of reliability, even comparing with devices that don’t claim the “Roon Ready” label.
TBH, the 2go was the first (expensive) device I bought because of the “Roon Ready” label, and I feel duped. In contrast, when I bought my much more expensive Linn systems, I knew they worked with Roon but were not “Roon Ready,” and that was OK. There are a few occasional issues between Roon and Linn gear, but that’s what I expected from the beginning. With the 2go, I expected a much higher level of reliability, which I did not get.
You created this mess now you’re gonna solve it or u’ll loose lots of subs renewal in the future.
2 Likes
Unfortunately, neither company is being very transparent about 2go. Chord is indicating that they have been doing their part to get certified and are waiting on Roon and the response from @john a few posts above seems to indicate that 2go hasn’t passed certification testing (is it failing? is that the hold up?) yet. So what’s being done?
I’m also one of the “lucky ones” over on Head-Fi and I’d say my 2go is at a 99% flawless performance rate.
I don’t know what’s happening in Roon’s lab, but I know what’s happening in my home, and it’s definitely not “Ready.”
1 Like
As I understand it, ‘Roon Ready’ is a certification for a product which includes RAAT software and can receive a RAAT bitstream via an Ethernet connection. It’s a network-connected device.
‘Roon Tested’, on the other hand, can be awarded to USB-connected devices tested to work nicely with Roon. I would assume that you can connect your not-certified and falsely claimed ‘Roon-Ready’ device with USB and continue using it. I understand that what will cease to work after September 21st is only the network-connected RAAT integration of such devices.
1 Like
OK, but don’t punish the end user! I paid for the software and expect it to continue to work and don’t care about the language behind it.
2 Likes
Maybe roon should just stop support for any uncertified products. Ie if you have a problem you are directed back to the manufacturer for resolution as it’s their failing in more ways than roon’s.
2 Likes
Hello @Matte_Rocks,
To clarify things for existing Roon users—Unless you do one of the following things, your experience will not be impacted:
A) Disable your uncertified Roon Ready device in the Settings > Audio screen in Roon.
B) Purchase a new device implementing the Roon Ready SDK that has not passed certification testing after September 21st.
Regarding action B, you can reference the Roon Labs Partners Page for a canonical list of Roon Ready Certified devices. With the recent update to our website, this page is now kept in-sync with the in-app certification status for Roon Ready devices.
-John
1 Like
Hi @john
So looking at the partner list you have the gold note IS1000 listed which I assume means certified - however it’s listed as uncertified in Roon itself ??
I have pinged gold note on this but it would be good to understand once a device is certified how is that made visible to us the users. Does the hardware manufacturer need to install a update - or does roon update a database with the correct status ?
Edit - just received a email saying the amp is certified - could this just be a delay / mismatch in the app ?
Thanks
Matt
My Bricasti is a DAC/Ethernet Streamer. I don’t own a streamer I can connect to it. I get my streams via the M3’s ethernet connection and don’t have anything to connect to it via USB.
This may not work nicely for Roon, as in the minds of their affected users it is always they who have to stand up to their product. The users always will feel that it is Roon which doesn’t work as it should, and the discussions today show that there is clearly a tendency to blame the software rather than the manufacturer of the costly and shiny hardware.