I see, thanks for the quick response James.
Hi Folks, Gary from Bryston here. I want to shed some light on where we are with Roon Ready and why it was taken down. Here's a post from Rob at Roon and some additional info from me below:
As you guys have gleaned, yes, one of the clear bugs in the Bryston implementation at CES was an SQ difference between MPD and RAAT. This should not be and is one of the things to be worked out. As a point of contrast, the system running in the TAD demo has both MPD and RAAT. The Roon Ready implementation was chosen for the demos, with MPD as a backup. I am pretty sure that the folks at TAD would not have stood for anything but the best playback they could get for their main demo at CES, so this should be some kind of testimony. Again, this is exactly why we did not want an untested beta circulated. This is an unpleasant, confusing situation for the user community to have to confront and what we are trying to avoid with the Roon Ready program. --Rob
We did it this way because our developer, Chris, was not at CES and few users are on the beta track, but it is clear now that this was a mistake... It was pretty clear on the very first listen that there was something wrong and that this wasn't something to share, but unfortunately, some of you have used what is not at all up to the quality of what we expect our Roon Ready integration will be.
This firmware is nothing like what will ship and is clearly not representative of what Roon Ready can do as an audio delivery mechanism and Bryston did not intend for anyone to get the idea that we were officially Roon Ready at that point.
Sorry for the misunderstandings.
So, know that we're still working on it! Roon Ready certification requires a lot more than just accepting audio. We are impressed with what Roon is, does, and how it sounds on our hardware. That's why we were interested in partnering to begin with.
-Gary
