Strange. It seems like the file you are playing is not an MQA file, if it was then it would show this in the source line in the signal path. Sometimes things are wrongly labeled in Tidal/Roon. When I try to play what I think is the same file I do indeed get MQA in the signal path.
Dean, I believe the behavior you are seeing is correct. I could not find that the Ares II supports MQA, and while the original Meridian also does not support MQA. The Meridian Explorer 2 supports MQA if that is the device you have.
That track isn’t MQA. That aside Roons MQA decoder like any MQA decoder can only unfold the first stage called decoding this will be to 88.2/24 for 44.1 based material or 96/24 for 48 based material. To get the full MQA ORFs you need an MQA capable DAC to do the rendering stage it cannot be done in software. The Denafrips isn’t an MQA capable DAC, not sure what your meridian one is but likely that isn’t either.
The only thing that matter is the signal path as the format being played not what anything else says. But yes it’s likely he’s not on the Hifi+ tier or hasn’t set to the correct one, but that doesn’t change the fact that one oh is DACs are not MQA capable possible both and won’t go higher than Roons first decode.
Denafrips isn’t MQA the Meridian no model number given so hard to know. But I would say no. I have MQA dacs but not on the Hifi+ doesn’t always go hand in hand. Still get MQA decoding on all the 16bit MQA which they have tons off.
Thanks to everyone for your replies. You are correct that neither of my DACs are MQA compatible (my Meridian DAC is a balanced audio component, not a desktop DAC). However I do have the software MQA decoder selected so I’m sure that @CrystalGipsy is likely correct in that the software decoder is limited to 44.1 and 48 with an output of 88.1 or 96 although I have seen MQA 176.4 decode to 88.2 with the software decoder.
The version of the content in my example showed as being MQA which you can see in my screenshot (there are many versions of this album). I have also seen this same behavior on all other high frequency MQA so I think it’s a limitation of the software although it seems odd that it wouldn’t default to the highest frequency it can support which in this case should be at least 24/88.2 and not 16/44.1
I do have the highest level account for Tidal but I forgot that in general I had my MQA preference set to “Treat MQA as better than CD quality but not as good as lossless hi-res content” (which I have found to be true) but again, I’m not sure why this option would result in a hi-res selection playing at CD quality instead of 24/88.2. Anyone know why?