I believe it should be the same.the dac version without mqa support is the same of the dac of this topic? I mean, same Measurements?
We aren't sure about that.the dac version without mqa support is the same of the dac of this topic? I mean, same Measurements?
Maybe nothing noticeable in measurements, maybe not. But without certitude, We can't say X-Sabre Pro MQA and X-Sabre Pro (non-MQA) measure the same.X-SABRE PRO (MQA) used the ES9038PRO advanced 8-channel D/A chip, and its inner DSP unit and analog circuit have the high performance and better user experience. The new generation XMOS XU216 USB asynchronous transfer interface and new AK4118 S/PDIF receiver chip,
We aren't sure about that.
From @MatrixAudio website:
Maybe nothing noticeable in measurements, maybe not. But without certitude, We can't say X-Sabre Pro MQA and X-Sabre Pro (non-MQA) measure the same.
We aren't sure about that.
From @MatrixAudio website:
Maybe nothing noticeable in measurements, maybe not. But without certitude, We can't say X-Sabre Pro MQA and X-Sabre Pro (non-MQA) measure the same.
Also, not only this is an upgraded product, the MQA was significantly more expensive at launch.
This question was mostly answered by Matrix on page 4:I believe it should be the same.
Because one of the most popular marketing mantras is "bigger numbers must be better".
But in that situation, the dithering is in any case not harmful in any way - and has to happen at some point anyway.
I would say perhaps not harmful. In a DSP/convolution engine for playback, there is a fixed time-budget to consider. Although, if selecting a variate from a TPDF, adding it to a sample, truncating/rounding, and checking overflow is blowing that time-budget, one is likely doing something wrong elsewhere in processing...
Curious why you say, "... dithering... has to happen at some point anyway"?
My thinking is that lack of dithering is likely inaudible for most music, even at 16 bits, and almost certainly at 24 bits of depth.
Happy to be shown the error(s) of my thinking though...
np thanks for answering, but does this mean that async mode is not bitperfect due to ASRC while sync mode is?You are asking me a little too late given my poor memory. I am fairly certain I just changed sync/async mode.
Well, nothing is bit perfect inside these DACs as the PCM data is upsampled anyway before conversion to analog. As long as ASRC doesn't show errors of its own in the measurement data, then it is not a concern. That is the case here.np thanks for answering, but does this mean that async mode is not bitperfect due to ASRC while sync mode is?
Hmm, i see i actually thought sync would have better jitter measurements as then the clock used is the CCHD 957 45/50mhz clock which has better specifications, the ASRC clearly does a good job then.Well, nothing is bit perfect inside these DACs as the PCM data is upsampled anyway before conversion to analog. As long as ASRC doesn't show errors of its own in the measurement data, then it is not a concern. That is the case here.
I am actually surprised the DSD files played back without a hitch, this gives me some hope but it looks like Linux MQA playback is unlikely to happen without some help from the ALSA kernel driver developers.
Not that I am too frustrated by this failure. I have started this project out of curiosity only and have no vested interest in MQA standard personally. I just like to learn how things work (or not).
Since these signals are sent over USB and the device runs in asynchronous mode, there is no way to "add" jitter to the signal.Hi amirm! How do you perform the Jitter Noise test? Did you add jitter by APX555 manually or just run a 12kHz FFT averaging? I tried to run 12khz FFT tests and some of them are similar to your results but others goes abnormal after only several averaging. May I know your detailed setup and filter choise for jitter test?
I have the old version (non-MQA) and it accepts 32-bit PCMHello! I am interested in buying this dac and would like to ask a question. In the specs on the matrix site it says that it supports usb audio PCM 16-24Bit, so it does not support 32 bit pcm via usb audio?
I would prefer DSD256 version very slightly, although I am pretty sure I would not be able to spot it in a blinded ABX test. So much for MQA format for me, I've had my curiosity satisfied and do not find any reason to delve into it any further.
I thought that the design was that only when the MQA circuit was engaged was the DAC geared to produce a sound endorsed by MQA. The main reason, I thought, was to not have the DAC coloring the sound, as so many boutique DAC do.