So are these "security codes" different to the "decoding libraries" referred to in the dealer release of 23 December 2015 (see below). This seems to imply that every time there is a firmware upgrade there must be reference back to the studios. Anyone understand this apparent two stage process? Or is there a DRM type code from the studios for each MQA file generated? If so, that sounds like an unwieldy system.
I know as much as everyone else here —which is to say nearly nothing— but I wonder if these security codes are the ones mentioned
here on MQA's web site .
Every MQA encoder will need access to an HSM (Hyper-Security Module) that issues the encrypted signatures contained within each file. Costs of owning and implementing HSM within your environment will generally range between £5,000 - £20,000 but it’s important you discuss this with your technical team and MQA.
...
The HSM module should optimally sit within the same network as the encoding computers. Its sole job is to hand out signatures for embedding into the file. A remote or cloud-based HSM is possible but performance will be degraded.
Does this mean that the MQA firmware will need to be updated every time a new content provider (label/studio) signs on to provide MQA music?
Google Search
|
Meridian Systems
|
Meridian Streaming
|
Restaurant
|
WiKi
|
Duncan's Meridian Info
|
Board Rules
|
Restaurant Rules
