The S2 DAC will show MQB on it’s display when it’s functioning in ‘rendering’ mode, i.e. when something else upstream has done the 1st unfold and is still carrying the MQA signal through to the DAC.
Like what Roon can do now, and Audirvana and the Tidal Desktop App have been able to do for a while.
When the S2 DAC is left to do the full MQA decode, then you’ll get MQA on it’s display.
Brian explained it better in October further up this thread:
Bought the Pre Box S2 Digital a couple of days ago. Nice Little Dac. I play it connected to a NuC (Win 10) or the USBridge. Unfortunately it give’s drop-outs when playing MQA music in Roon, no matter what settings I use, both with USBridge or Windows 10 NuC. The drop-outs are at the beginning of every new MQA track. More people expierence this behavior? It’s kind off useless for MQA this way, and that’s a shame. (It got the newest firmware 2.12)
I use DSP (room correction) which makes Roon do the first unfold, and it seems to remove that stutter you describe. So if you tell Roon to do the first unfold, which I think you can do by setting the DAC as a Renderer only, it should fix the problem.
Or you can set MQA dac capabilities to No MQA support, which will make Roon do the first unfold, and then you can upsample to whatever you like in Roon. You won’t get the second MQA unfold then, but that unfold is basically an upsample so you won’t miss much.
I am experimenting with this myself now, upsampling to DSD512 after first MQA unfold is kinda cool
I changed setup, letting Roon do the 1st unfold. There is still a tiny click at the beginning of each track, but much better than before.
Just gonna wait till the fix comes out.
Hi Magnus. Works for me too with the first MQA unfold by Roon. However, when trying to upsample to 512 for S2D in Roon via DSP, I only get the option of going to 256? Anything I miss?
You need to use the ASIO drivers, and set DSD playback to “Native” to be able to play DSD512. Or use DSD256 and don’t bother with 512, I don’t hear any differences between them.
Its only for MQA and its not a dropout, more of a quick stutter. Still, its a little annoying which is why I let Roon handle MQA and upsample manually, which means no stutter and better sound. And the core problem seems to be with MQA libraries inside the DAC, since some other MQA DACs also have this problem.
I get all that. But my only reason for considering the Pro-ject is for its MQA capabilities. I have hoped it would be an upgrade of my Explorer 2 DAC.
With the problem you describe, I would not consider that an upgrade. The Explorer does very well. FWIW earlier this year I purchased a Meridian 218 zone controller. Bot the Meridian rep and the dealer said the DAC performance from the zone controller would be noticeably better than the Explorer. After a month I decided whatever difference there was, is one I can’t hear. So I returned the zone controller and stuck with the Explorer.
I also have a Bel Canto 2.5 DAC that does very well with non MQA files.