Hello @Stephen_Seay,
Your frustration is understandable. We also hate it when things (especially audio gear and software) don’t work as one would expect them to… it’s why we created the Roon Ready program in the first place.
Roon Ready partners are invited to reach out to us at any point in the device lifecycle, pre-or-post certification, with any questions they may have regarding the Roon Ready API or the certification process. Our dedicated Partners team triages all incoming messages to ensure that each inquiry receives a satisfactory response, often with direct input from our developers.
Additionally, all Roon Partners receive pre-release Roon “Alpha” builds to test their devices with.
It is the manufacturer’s responsibility to implement the Roon Ready API on their devices in a way that meets our certification requirements.
Roon made a change (few months back) that broke Bricasti’s Roon functionality and never bothered to tell Bricasti that the change was coming so they didn’t even have a chance to test it.
To the best of my knowledge, we were not made aware of any “issue” regarding the Bricasti M5 breaking with a Roon update from Bricasti or any of our users. Additionally we have not received reports of any other Roon Ready devices breaking with recent Roon updates.
Can you describe in more detail what transpired here? If there was a technical issue with RAAT that caused issues for our users we’d be very curious to hear about it.
-John