Not an expert, but here's a post one of the Roon developers posted on their forum along these same lines:@CANiSLAYu understood - thanks!
Does that mean that if I see MQA48k at the top it is -not- unfolding, or no unfolding is possible, or that something else is wrong, or none of those things
There are four different rates here, which causes no end of confusion:
- The MQA container rate (i.e. 44.1k or 48k) which is how the MQA gets to you. It has nothing to do with anything else and has no bearing on rendering rates.
- The transport rate of decoded MQA (“MQA Core”) from the MQA decoder to the rendering part of a DAC. This can be from Roon (or any other MQA decoder) to the DAC, or within the DAC itself. MQA Core is always 2x rate (88.2k or 96k) and has no bearing on rendering rates.
- The original sample rate of the master. Roon reports this and so do/should DACs. It it relevant to rendering only insomuch as there may be additional recoverable information for original sample rates >96k.
- The rendering rate of the DAC, which is purely hardware dependent. Any MQA can be rendered at any rate, but the DAC is very unlikely to be reporting this.
So in short, UAPP should be passing the MQA signal along to the M15 DAC to do the core unfold and any subsequent unfold (depending on the sample rate of the file), and it should be unfolding it to 2x in this particular case, but the player is going to show the original sample rate of the master in the notification bar (this is a requirement of MQA standard).