MQA uses a couple different methods of telling a DAC that a file is MQA. And it depends on whether it is passing MQA through to the DAC itself, or if it is doing the first decode and then instructing the DAC do use the MQA filter for the 2nd/3rd unfold (which don't actually work in the same way as the first unfold and is effectively just a specific upsampling filter).Thanks, I'll look at that thread.
I know there is at least a header variable that tells certain dumb devices like my Oppo 205 whether the file is MQA or not. You can use command line tools to set that. I tested an MQA file without the header setting, the Oppo didn't know it was MQA; I used the tool and set the variable and Oppo decoded it correctly. And this works for PCM or FLAC.
But I have other gear that can start playing MQA in the middle of a file and so it seems (but I'm not sure) that it doesn't need that header variable. That suggests either good MQA decoders don't need any help from flags, or that the flag is carried in each block.
Often it uses more than one method just to ensure compatibility.
File metadata is one and this can be added manually or via some command line tools, but information within the audio itself is also used to tell a DAC that the stream is MQA, so that it can still work in situations where the player or DAC cannot be directly told that the file is MQA (or as you mentioned resuming playback from a file halfway through).
How this works is not public of course, but thanks to MQA using XMOS chips and the nature of running things on there it's possible to reverse engineer what is going on. For fun, here is a version of 'Nyan Cat' which your DAC should pick up as MQA as I've applied this signalling to it. (Your player may not though as players seem to sometimes rely ONLY on file metadata for detection). (I'm on my phone atm so this might be the wrong file actually but I think it's correct).
https://drive.google.com/file/d/1IBYFikcWtrIZgf0PRc7YRWmVTsS5Ta_F/view?usp=drivesdk
This signalling within the audio is also what allows software like roon to do EQ on MQA files and still have the DAC recognise it as MQA.
It does the first unfold, applies EQ, and then adds the MQA signalling back on top so that the DAC continues to recognise it as MQA. (I've not looked into how much adding EQ 'breaks' MQA processing actually but it could be interesting to look at)
The interesting thing with this signalling method is that it can cause issues with gapless playback due to not being instantly recognised, because the DAC will use its standard PCM processing/oversampling, suddenly detect that it's MQA and swap to the MQA oversampling filter, and when this happens during a track transition it can cause pauses/clicks/pops or other interruptions.
As a result of this, MQA has 'strongly encouraged' various manufacturers to use the MQA oversampling filter 100% of the time regardless of whether the audio being played is MQA or not. As this solves the gapless issue (but means you're not using a proper reconstruction filter for most content which is not great).
Lots of different devices from desktop stuff like the Topping D90 MQA to portable players like some of the Hiby ones all do this.
Last edited: