- Joined
- Feb 23, 2016
- Messages
- 23,115
- Likes
- 43,015
Here is a result with a Topping D10 balanced feeding the Babyface pro.
So you're getting a little bit better result with the Babyface loopback.Here is a result with a Topping D10 balanced feeding the Babyface pro.
View attachment 163738
Would it just push the graph up with the peak being on 0 but getting a wrong result on noise ?And here are the first two (IMHO obvious) wishes:
1. Add buttons to show only blue or white (so one can toggle the view between all three states)
2. Add Auto dBr, so that the highest peak is set to 0 dBr and the scale is also auto adjusted. Makes it much easier to get the values (ratio) of noise floor and harmonics from the screen.
...
So you're getting a little bit better result with the Babyface loopback.
I'm note sure if it's as much important in this test than in a loopback difference checked with DeltaWave, but did you sync both devices with the SPDIF signal (SPDIF optical out from D10b to SPDIF optical in of the Babyface, to lock the Babyface on the D10b) ?
Done or not, could you please compare both cases?
Would it just push the graph up with the peak being on 0 but getting a wrong result on noise ?
I just checked with one device and was getting the same noise level for a 0, -10 and -20 dB signal level, only tone and harmonics were lower, so if I take the -20dB signal result and push it up to align it with 0dB, the noise would end up 20dB higher while in realty, it was on the same level than when I sent a 0dB signal...
Did no check the drift value, no sync indeed. Would be curious to know if there's a difference with another test, synced this timeThere’s a 16ppm clock drift reported in that recording, so the clocks were not synced.
Yes, but the tool was already adjusting the result, if not the graph, am I wrong ? I did not spend time checking that but it was the impression I got.dBr is in units relative to a specific signal. In the case of Multitone, it's relative to the largest amplitude of the signal. Noise is also relative to this watermark. In other words, noise level is not expressed as the absolute level that you might see in dBFS measurements, but relative to the maximum amplitude.
Did no check the drift value, no sync indeed. Would be curious to know if there's a difference with another test, synced this time
Yes, but the tool was already adjusting the result, if not the graph, am I wrong ? I did not spend time checking that but it was the impression I got.
Thanks @pkane ! I missed an important thing reading too much fast, it was with dBr and you have added "Spectrum in dBr" option in the last version.
Back to drift, I'm a little bit surprised that I get no drift at all between Tone2 Pro and Cosmos ADC (without any sync), just a bit of delay which is something normal in this case I guess (no dBr activated in this test) :
View attachment 163864
Was looking at the Sinewave instead of MultitoneDrift calculation requires a multi-tone signal, preferably with at least 32 tones or more. You can tell if you're looking at a dBr display because it will have (dBr) in the title, like this:
View attachment 163867
For those wondering here is the Topping D10 balanced feeding the Babyface Pro with the clocks locked via SPDIF.
View attachment 163905
Here it is with a 200 tone signal.Thanks, but it seems it's not the same conditions : this one is 1000 multitone while the unsynced one was a 200 multitone
Not quite the same, so I wonder if I did somthing wrong. I'd like to see the entire dynamic range dropping from near 0dBFS, if possible. @pkane pls hlp!Good work! If you want to replicate my measurements, these are the settings for multitone test:
Sample rate = 192 kHz
FFT size = 256k
Averaging = 8
Not quite the same, so I wonder if I did somthing wrong. I'd like to see the entire dynamic range dropping from near 0dBFS, if possible. @pkane pls hlp!
View attachment 164575