Has the out-of-cycle software release, addressing a potential security issue across Roon apps, been publishesd for manufacturers of “Roon-ready” devices?
I’m concerned because my “Roon-ready” devices have not received from producers the appropriate firmware update lately?
My understanding, from what has been said, is that the 2.60 release of Roon Bridge is probably functionally identical to the previous 1.8 release.
I believe that the issue that prompted the update was more to do with the signing mechanism.
Certainly, my Arcam ST60 has not missed a beat and it has not had any firmware update.
Finally, I believe the Roon Dev kit is designed explicitly so that functional aspects of RAAT can be reworked/upgraded without the need to update firmware in all devices with it embedded.
Or if it was, I suppose that it doesn’t need a firmware update by the manufacturer. From the link:
Support for new streaming services, file formats, DRM schemes, etc can be supported without a firmware upgrade. In fact, the only reason an upgrade should be required is to fix a low-level bug, or to access more hardware functionality. This is really important. Not all partners/hardware have easy firmware update paths that can be done at home. Our acceptance of this reality has deeply influenced RAAT’s design. Just as with Google’s Cast devices, the majority of the business logic is delivered to the device at run-time as a script. This means that we are capable of completely re-designing the audio streaming and buffering logic without updating device firmware. This is absolutely critical, since most of the bugs + evolution in a system like this relate to networking, not audio. Other than Cast, we are unaware of another system that is this flexible.