Elk saidI have neither seen nor heard anything. Paul previously told us it will likely be next week.
Why do you think it is out and why do you believe it is v3.3.3?
Elk saw it on the remote site.
Elk saw it on the remote site.
Given that the update won’t work with Roon for MQA (I assume fine for non-MQA) and Roon have just released a fix then I wonder if there might be a delay in releasing the update to enable PSA to amend it.
What do you mean by a ‘Roon fix’ ?
Version 3.3.3 will probably be released on Monday without support for Roon, but will support MQA and Tidal, with Roon/MQA support coming later.
Dennis
Thanks for that update, Dennis.
So with the Tidal support, can you play Tidal direct to the Bridge or do you need other software?
rogerdn saidWhat do you mean by a ‘Roon fix’ ?
The Roon fix is the MQA enable in Roon. Which does not work in the current version.
Dennis
Dennis Kerrisk saidVersion 3.3.3 will probably be released on Monday without support for Roon, but will support MQA and Tidal, with Roon/MQA support coming later.
Dennis
Any idea how much later ?
tkiat said Elk saw it on the remote site.Ah ha! Sneaky you are. :)
Dennis Kerrisk said@dennis - as you know, Brian (Roon CTO) posted today that the new "fix' depends on "build 242 being broadly available".The Roon fix is the MQA enable in Roon. Which does not work in the current version.
Dennis
The currently available version of Roon is indeed build 242. Has been for a day or two. That said, I have zero idea what he meant by the term “broadly”, for as far as I know, it’s available world-wide. So… why does the fix not work in “the current version”? As that appears to be build 242.
Thanks for the help, and thanks for the transparency as to what the plans are.
Dennis Kerrisk saidVersion 3.3.3 will probably be released on Monday without support for Roon, but will support MQA and Tidal, with Roon/MQA support coming later.
Dennis
Not from the Tidal app which does not support external players, but from Mconnect.
Dennis
scolley saidDennis Kerrisk saidThe Roon fix is the MQA enable in Roon. Which does not work in the current version.
Dennis
@dennis - as you know, Brian (Roon CTO) posted today that the new "fix’ depends on “build 242 being broadly available”.
The currently available version of Roon is indeed build 242. Has been for a day or two. That said, I have zero idea what he meant by the term “broadly”, for as far as I know, it’s available world-wide. So… why does the fix not work in “the current version”? As that appears to be build 242.
Thanks for the help, and thanks for the transparency as to what the plans are.
Because there need to be changes on the bridge to incorporate the new version of the RAAT protocol to make it all work. The new RAAT-SDK was just released this morning, so it will take time to get it incorporated
Dennis
rogerdn saidAny idea how much later ?
The new RAAT-SDK was just released this morning by Roon, so it will take our Bridge people a couple of weeks or less to get it incorporated.
Dennis
Sorry to keep asking questions Dennis but will the new Bridge update support non-MQA Roon or will Roon not work at all until the new RAAT SDK is incorporated?
Dennis - does this mean that Roon will not work at all with the first release? Or is it just MQA will KT work?
if no Roon at all, I had better wait or no playback for me 
Dennis Kerrisk saidThe new RAAT-SDK was just released this morning by Roon, so it will take our Bridge people a couple of weeks or less to get it incorporated.
Dennis
Ahh… Thanks Dennis. Now I understand.
It by “does not work in the current version”, you were referring to the RAAT-SDK, and not Roon itself. Got it. Thanks for the clarification.
This was BAD timing for you guys, with the Roon RAAT-SDK announcement happening on the moment of your B2 MQA release. Bummer. But IMO delaying the Roon specific modifications is only fair to the larger DS community. We Roonies can wait.
Thanks.
Very gracious, scolley. I am certain you are eager.
Elk saidEager indeed Elk. But the facts are the facts...Very gracious, scolley. I am certain you are eager.
It appears that Roon made their announcement today about changes that some “Roon Ready” partners would have to make changes to support receiving MQA files from Roon. Apparently one of those partners was PSA. The rest is history…
PSA has been cranking to supply MQA support that so many of us have been chomping at the bit for. And then this pops up as a previously unknown impediment to a contentment of the community to taking advantage of that new capability?
I appreciate the accreditation of being gracious. Really. But to hold off an update (in a significant way) that the community at large has been anxiously waiting for - based on last minute news - would be (IMO) grossly unfair. And if I were not a Roonie, frankly… I’d be p*ssed.
Honestly I had hoped the upcoming release would be delayed to accommodate this. But that was before Dennis posted that this was a matter of weeks. A day, sure. But weeks? Let it the release GO. Please. People are waiting.
I just hope that everyone receiving the benefits if this impending release will please share what they hear on the back of the change. It’ll give all the Roonies something to look forward to listening for in the coming weeks. 
OK this is a lot of potentially confusion information. Let’s see if I can summarize correctly.
So the BrigdeII update will be available next week including Tidal and MQA support but not for MQA that comes through Roon although Roon (without MQA unpacking) will be supported in both updated and not updated bridges. Since Roon changed the protocol PSA needs to do some additional changes to support MQA through Roon support which will cost a couple of weeks more.
So PSA cannot help this last minute change from Roon. However I suppose for most of us this 3.3.3 update will be useless as the MQA source is Tidal via Roon, right?
A different question: how do you update the BridgeII in the DS Junior? Stick as well, or over network?
Cable-guy saidHowever I suppose for most of us this 3.3.3 update will be useless as the MQA source is Tidal via Roon, right?
I don’t believe this to be true. Right now we have to use Room to stream Tidal only because the Tidal integration in the Mconnect app does not function with the Bridge II. The pending firmware update, 3.3.3, will change this. So, from what I understand, once this firmware is released, we can stream Tidal (MQA included) directly from the Mconnect Control app to the Bridge II - Roon not required.
Cable-guy saidTidal can be played via the mConnect app, MQA won't work now via Roon.OK this is a lot of potentially confusion information. Let’s see if I can summarize correctly.
So the BrigdeII update will be available next week including Tidal and MQA support but not for MQA that comes through Roon although Roon (without MQA unpacking) will be supported in both updated and not updated bridges. Since Roon changed the protocol PSA needs to do some additional changes to support MQA through Roon support which will cost a couple of weeks more.
So PSA cannot help this last minute change from Roon. However I suppose for most of us this 3.3.3 update will be useless as the MQA source is Tidal via Roon, right?
A different question: how do you update the BridgeII in the DS Junior? Stick as well, or over network?
The DSjr updated the bridge over the network
Dennis