• These commercial threads are for private transactions. diyAudio.com provides these forums for the convenience of our members, but makes no warranty nor assumes any responsibility. We do not vet any members, use of this facility is at your own risk. Customers can post any issues in those threads as long as it is done in a civil manner. All diyAudio rules about conduct apply and will be enforced.

symphonic-mpd

The method has limitations of course, like every other measurement method. But in many cases it's the only possible way. Some dac chips have built in jitter reduction techniques yes, which means measuring the jitter on the clock input won't give you the actual jitter in the sample clock. That information is only available inside the chip itself, where you have no way of reaching it.
And in any case, measuring the clock jitter on the clock input pin of the dac (which I assume is what you want to do) is far from trivial. Let's ignore the really big mash jitter which is easy to measure. We really want to measure in the picosecond range (ideally sub-picosecond). So using any normal oscilloscope is simply out of the question. They are much too slow, and too inaccurate. So we get something like this: https://teledynelecroy.com/oscilloscope/labmaster-10-zi-a-oscilloscopes
Then we can get down something like 5 ps accuracy. Still not as good as we want, but that's not the only problem.

Just hooking up a probe to the traces on the board changes the electrical properties of the system so much that what you are measuring isn't even they way it usually performs.

now we´re getting somewhere, finally we have something, that we ca agree upon, nice...:D
and actually i don´t know how to measure jitter exatly (...guess, i´m just to lazy to look it up...), all i´ve
heard ist, that it is fairly simple whe you have a crazy expensive osciloscope.


I forgot to reply to this. I don't think doing a set of measurements with an AP is impossible. Of course I don't expect anyone to buy one. But this is a big forum, and there is a good chance that someone here knows someone who knows someone who has access to an AP unit. There was one in the EE department of my university for example, would expect that to be pretty normal.


It only needs to be done once, and should not take more than a few hours. If someone really wants to prove there is a difference, they could start by just asking around.


fair enough...

...hmm, so you don´t have a suitable Audio-anayzer...? but i thought....:confused: ... never mind. doesn´t matter...

if you can find someone, who is can do the measurements, i´m happy to provide the testobject, i have a spare
rpi4, which i currently don´t use, i can ship it sweden or anywhere in europe, i´ll even include some sd-cards
with ready-to-use systems on it.
i´m confident, we can come up with a reasonably valid test setup.

no joke, i´m serious, it´s diyAudio afterall, you´re supposed to do somethting, for yourself, and not just talk about it...


what do you think ??


cheerio,
Mirko
 
Hi HenrikEnquist, M_Balou,

If you can arrange a measurement environment and measurement procedure, I would be very grateful.
I would like an objective assessment by a third party.

Of course, I'm willing to help.
Let me know if there is anything you need.
We can ask for help from members who agree with our ideas.
 
The sigma-delta modulator in most oversampling DACs ₍the actual place where DA conversion occurs) runs at master clock frequency, multiples (e.g. 8x) of the bitclock of I2S. Either the DAC (board) has its own master clock (then RPi's I2S is running in slave mode), or the DAC (chip) can/must PLL its master clock from the incoming low-frequency BCLK generated by RPi's I2S (or PLL an external clock to run synchronously with the multiple of BCLK). The PLL may produce a very different jitter than the incoming BCLK. This signal is not available on DAC pins.

IMO measuring the effect in the final analog signal is a valid method, especially for comparing various setups to find the one with best result in the analog domain.

Measuring clock jitter directly takes "just" a proper device, I just received a measurement report from Silicon Labs measuring rms jitter of 93fs.
 

Attachments

  • OUT1.png
    OUT1.png
    39.2 KB · Views: 199
now we´re getting somewhere, finally we have something, that we ca agree upon, nice...:D
and actually i don´t know how to measure jitter exatly (...guess, i´m just to lazy to look it up...), all i´ve
heard ist, that it is fairly simple whe you have a crazy expensive osciloscope.





fair enough...

...hmm, so you don´t have a suitable Audio-anayzer...? but i thought....:confused: ... never mind. doesn´t matter...

if you can find someone, who is can do the measurements, i´m happy to provide the testobject, i have a spare
rpi4, which i currently don´t use, i can ship it sweden or anywhere in europe, i´ll even include some sd-cards
with ready-to-use systems on it.
i´m confident, we can come up with a reasonably valid test setup.

no joke, i´m serious, it´s diyAudio afterall, you´re supposed to do somethting, for yourself, and not just talk about it...


what do you think ??


cheerio,
Mirko
Nono I don't have an Audio Precision analyzer. I got to use one at the university for a few hours to measure an amplifier I had built. That was already 15 years ago. I don't know anyone at that department today, so I don't know if they still have the unit. I would bet that they still do (or more likely a newer one). I'll investigate. There is a high risk that it becomes a long unmanagable chain of asking someone who knows someone who knows someone...



I have a RPi 4, but no i2s dac.



The sigma-delta modulator in most oversampling DACs ₍the actual place where DA conversion occurs) runs at master clock frequency, multiples (e.g. 8x) of the bitclock of I2S. Either the DAC (board) has its own master clock (then RPi's I2S is running in slave mode), or the DAC (chip) can/must PLL its master clock from the incoming low-frequency BCLK generated by RPi's I2S (or PLL an external clock to run synchronously with the multiple of BCLK). The PLL may produce a very different jitter than the incoming BCLK. This signal is not available on DAC pins.

IMO measuring the effect in the final analog signal is a valid method, especially for comparing various setups to find the one with best result in the analog domain.

Measuring clock jitter directly takes "just" a proper device, I just received a measurement report from Silicon Labs measuring rms jitter of 93fs.
This gives me an idea... I have been thinking one step too far. I think it would make sense to start off by checking for any difference in the i2s signals from the raspberry. No dac needed, and the whole thing gets much simpler. That means we "just" need one of those highly specialized super expensive instruments.

We have a really nice spectrum analyser in the RF lab at work. I don't know if it's suitable for this exact task, but I'll ask! And if I ask nicely I can probably play with it as much as I want.
 

TNT

Member
Joined 2003
Paid Member
The sigma-delta modulator in most oversampling DACs ₍the actual place where DA conversion occurs) runs at master clock frequency, multiples (e.g. 8x) of the bitclock of I2S. Either the DAC (board) has its own master clock (then RPi's I2S is running in slave mode), or the DAC (chip) can/must PLL its master clock from the incoming low-frequency BCLK generated by RPi's I2S (or PLL an external clock to run synchronously with the multiple of BCLK). The PLL may produce a very different jitter than the incoming BCLK. This signal is not available on DAC pins.

IMO measuring the effect in the final analog signal is a valid method, especially for comparing various setups to find the one with best result in the analog domain.

Measuring clock jitter directly takes "just" a proper device, I just received a measurement report from Silicon Labs measuring rms jitter of 93fs.

See, here is the problem, that chart starts at 100 Hz, how about 30 Hz? or 10 Hz or maybe even 1 Hz? Thats where many clocks fall apart. They look nice at 10kHz (thats the most common frequency where a time (ps, fs) is given for.

But it's the close in noise that is also a problem. It causes sidebands. And this is what is so dangerous with "femto-seconds" figures...

To measure where it really matters is a really hard task and requires serious equipment and knowledge.

If your are a designer you need to be able to measure clocks, if you are a "customer", you are interested of the analog side i.e. sideband, distorsion, noise etc.

Then there it seems to be music correlated jitter that creates the biggest problem - random jitter not so much. To add to the complex, different D/A topologies (R2R, D/S...) have different sensitivity to jitter and just to end the whole thing... different chip products have sometimes built in strategies to clean out jitter as mention above.

It's a mine-field...

//
 
Last edited:

TNT

Member
Joined 2003
Paid Member
I would like to end to say again that the behaviour of the Pi hardware ert. clock (MASH?) is a pathological behaviour and is most unsuitable for serious audio equipment. If one has any ambition to create a well behaved product and to not start the whole project with a big problem - I would avoid Pi as the Covid19. The make excellent execution platform for signal processing but don't connect them to any audio HW.

//
 

TNT

Member
Joined 2003
Paid Member
Actually the Silicon Labs technicians modified my clock chip configuration to reduce the output integer divider for the DAC/ADC master clocks to get above 100MHz where the measurement does not drown in the instrument noise, from the required 20-40MHz.

Did you get phase noice reading for say 10Hz of your clock? Have you read Andreas thread about low jitter clock? - its often on the front page!

//
 
Nono I don't have an Audio Precision analyzer. I got to use one at the university for a few hours to measure an amplifier I had built. That was already 15 years ago. I don't know anyone at that department today, so I don't know if they still have the unit. I would bet that they still do (or more likely a newer one). I'll investigate. There is a high risk that it becomes a long unmanagable chain of asking someone who knows someone who knows someone...

I have a RPi 4, but no i2s dac.

This gives me an idea... I have been thinking one step too far. I think it would make sense to start off by checking for any difference in the i2s signals from the raspberry. No dac needed, and the whole thing gets much simpler. That means we "just" need one of those highly specialized super expensive instruments.

We have a really nice spectrum analyser in the RF lab at work. I don't know if it's suitable for this exact task, but I'll ask! And if I ask nicely I can probably play with it as much as I want.

it´s nice that you agree with me in the end, leaving out the dac does make it easier, i approve!:up:

and it would be awesome if you could use the analyser at work.

and it makes my quite envious, because we have some fancy equipment in our workshop, too.
and in the past it was totally ok to bring in your stuff and work on it, you could even take home tools
or other equipment over weekend. but some years ago we got new bosses and now we´re noz
allowed to have any fun at work anymore...
 
I would like to end to say again that the behaviour of the Pi hardware ert. clock (MASH?) is a pathological behaviour and is most unsuitable for serious audio equipment. If one has any ambition to create a well behaved product and to not start the whole project with a big problem - I would avoid Pi as the Covid19. The make excellent execution platform for signal processing but don't connect them to any audio HW.

//

pathological ?? Covid19 ??

You may well be hobbled by Google translate...but ??? WTF

"I would avoid Pi"
Your loss and lack of labour and application..sigh.
 
I'm thinking about the first stage of measurements, that would be to measure the bit clock without any dac connected.

The thing to compare would be symphonic-mpd vs a standard distro running mpd.
This only makes sense if I can run the standard distro without mash messing up the clock.

So then my question is, is there any sample rate where it will generate the right frequency without using mash?
 
I still do not understand why a PC should generate the audio clock. It provides HW device slaved to bit clock which can be simply generated from precise master clock located next to the DAC/SPDIF transmitter. The DAC should clock the sigma/delta with the master clock directly, not PLL the multiple from the I2S bit clock.
 
I still do not understand why a PC should generate the audio clock. It provides HW device slaved to bit clock which can be simply generated from precise master clock located next to the DAC/SPDIF transmitter. The DAC should clock the sigma/delta with the master clock directly, not PLL the multiple from the I2S bit clock.
I agree, it should not.

But the claim was (if I understood correctly) that disabling MASH was only part of the improvement, and the other software changes somehow improve the quality of the i2s signals. I find that extremely unlikely, but it's something I may be able to measure (if I can get rid of MASH).
There isn't much point in measuring bit clock jitter when the Pi is slaved to a dac.