Thank you @unincognito for your detailed answers.
First our product isn't RoonReady, we are in the early stages of development for Roon support and have simply made what we are working on available to the general public.
I perfectly understand you still are in the early stage for Roon support.
This is very good from Bryston to be one of the first to support Roon via RAAT.
Currently the display doesn't show anything, but there API does allow for it.
Nothing will ever scroll on the display of the BDP-1 or 2, support in the micro that controls the display never had that implemented.
The button are not currently able to control roon, but there API does allow for it.
OK, so is it possible that, in a later stage, you will use Roon API to enable BDP display and buttons ? IMHO it would be positive for User Experience.
As for sound quality, my boss emailed me from CES (vegas show) when I first implemented the feature saying it sounded not very good. The protocol does seem to require quite a bit of bandwidth and/or frequent access to the network.
My A/B setup for my boss was a BDP-1 (juli@ card) running MPD hooked up to a BDA-2 via coax and BDP-2 (new IAD card) running Roon hooked up to the same BDA-2 via the second coax. All inter connects where Bryston made interconnects and the rest of the system was single ended rca to a B60 with a pair of Grado SR125's.
With the same song playing on both units within about second of each other and James not knowing what he was listening to otherwise. Picked the BDP-1 running MPD as his favourite each time, i would say depending on how good your system is and how critical you are that there could potentially be a pretty noticeable gap between the two.
Do you talk with RoonLabs about this gap ?
Except for more network ressources required from Roon do you identify others issues in Roon and/or RAAT technical implementation VS BDP HW/SW architecture to explain the sonic differences against MPD ? Do you plan to try to bridge the gap ?