- Joined
- Feb 23, 2016
- Messages
- 22,962
- Likes
- 42,618
Changing from IIR to FIR didn't make a difference. Changing from Hann to FIR Kaiser did not make a difference
That is it. If (no limit) is in filter two, even if filter two is off it works. If any other value is in filter two, though set to off, then filter one doesn't work.
View attachment 90406
View attachment 90407
That is it. If (no limit) is in filter two, even if filter two is off it works. If any other value is in filter two, though set to off, then filter one doesn't work.
View attachment 90406
View attachment 90407
All the FFT choices are nice edition and doubly so that you show the parameters of them when choosing.Updated DeltaWave version 1.0.54 is now available.
Changes in 1.0.54b
- Added: new FFT window types, including multiple Kaiser
- Added: FFT Window explorer with time- and frequency-domain plots and measurements
- Changed: Delta Spectrogram window scale is now locked to Spectrogram 1 and 2
- Fixed: under one specific combination of filter settings, filter 1 @start was being ignored
To activate FFT Window explorer, click on the question mark in settings, under Spectrum:
View attachment 90522
You can explore and compare other windows once there:
View attachment 90523
The results I have been getting with DeltaWave seems to be somewhat random.
I have been testing a fully digital loop. I made three different recordings in a row, of the same test tone, where the only variable between the recordings was the randomness of the triangular dither.
One of the recordings measured 144dB of difference, 220 dB of correlated null and 4ps of jitter.
The second measured 72dB of difference, 95 dB of correlated null and 1.2 µs (!!) of jitter.
The third was somewhere inbetween.
All three recordings sounds exactly the same to my ear and the diffmaker calculated corr depth around 190dB on all three.
I think the algorithm of DeltaWave gets confused with very complex test tones - the more complex and chaotic the test tone, the more obviously wrong measurements I'm getting.
How short sample is too short?It’s not the chaotic nature of the test tones but usually periodic test signal or too short a sample that’s the culprit. White noise samples work just fine, for example.
How short sample is too short?
Yes, that's about the length I was using - 30-50s. What would you say is the optimal length for the most accurate results?30 seconds is what I usually use at a minimum. DeltaWave tries to compute clock drift and that requires a number of samples of FFT size that are spaced out to measure clock differences over the length of the track.
Yes, that's about the length I was using - 30-50s. What would you say is the optimal length for the most accurate results?
The results I have been getting with DeltaWave seems to be somewhat random.
I have been testing a fully digital loop. I made three different recordings in a row, of the same test tone, where the only variable between the recordings was the randomness of the triangular dither.
One of the recordings measured 144dB of difference, 220 dB of correlated null and 4ps of jitter.
The second measured 72dB of difference, 95 dB of correlated null and 1.2 µs (!!) of jitter.
The third was somewhere inbetween.
All three recordings sounds exactly the same to my ear and the diffmaker calculated corr depth around 190dB on all three.
I think the algorithm of DeltaWave gets confused with very complex test tones - the more complex and chaotic the test tone, the more obviously wrong measurements I'm getting.
Welcome to ASR.Jumped the wagon yesterday. Wow - I can say I am deeply impressed by DeltaWave, great ideas and great implementation, dear @pkane! I had tried to use Audio DiffMaker, but ultimately I did fail, as presumably did many others. DeltaWave does so much more, and it proved to be stable up to now. I am pretty sure DeltaWave is going to be THE go-to reference software for such purposes.
Let me just start out with a minor "housekeeping" bug report: On my Windows 8.1 (don't know about W10), the installer places the software into "C:\Program Files (x86)\PKAudio", no matter what. Of course, the 64-bit app should end up in "C:\Program Files\PKAudio". The installer doesn't pick up my changes for the installation directory. Task Manager of course shows that the app is 64-bits.
So I embarked on a long-standing project of mine, the obnoxious audio watermarking of files purchased / downloaded from various web-based (HiRes and CD quality) shops. Wow again, DeltaWave worked like a breeze! My current results are really saddening. Personally, I consider watermarking an insult (to say the least) on the artists, the original sound engineers, and last but not least us customers, many of whom buy the same music over and over.
This forum nicely can display screen shots. If some of you folks want it, and if the moderators don't object, I will post screen shots with my watermarking analysis on this thread here. I think DeltaWave shows the watermarking in an astoundingly clear manner. Of course, if watermarking has been detected and analyzed sufficiently elsewhere, I would like to receive some links to such publications and be quiet on it. I am aware of https://www.mattmontag.com/music/universals-audible-watermark and the links therein. The HiRes purchases I looked at were done only about a year ago, they are ECM Records releases, who are an independent company, but rely on Universal Music Group for distribution - too bad. UMG seems to continue watermarking to this day, at least until a year ago.
Jumped the wagon yesterday. Wow - I can say I am deeply impressed by DeltaWave, great ideas and great implementation, dear @pkane! I had tried to use Audio DiffMaker, but ultimately I did fail, as presumably did many others. DeltaWave does so much more, and it proved to be stable up to now. I am pretty sure DeltaWave is going to be THE go-to reference software for such purposes.
Let me just start out with a minor "housekeeping" bug report: On my Windows 8.1 (don't know about W10), the installer places the software into "C:\Program Files (x86)\PKAudio", no matter what. Of course, the 64-bit app should end up in "C:\Program Files\PKAudio". The installer doesn't pick up my changes for the installation directory. Task Manager of course shows that the app is 64-bits.
So I embarked on a long-standing project of mine, the obnoxious audio watermarking of files purchased / downloaded from various web-based (HiRes and CD quality) shops. Wow again, DeltaWave worked like a breeze! My current results are really saddening. Personally, I consider watermarking an insult (to say the least) on the artists, the original sound engineers, and last but not least us customers, many of whom buy the same music over and over.
This forum nicely can display screen shots. If some of you folks want it, and if the moderators don't object, I will post screen shots with my watermarking analysis on this thread here. I think DeltaWave shows the watermarking in an astoundingly clear manner. Of course, if watermarking has been detected and analyzed sufficiently elsewhere, I would like to receive some links to such publications and be quiet on it. I am aware of https://www.mattmontag.com/music/universals-audible-watermark and the links therein. The HiRes purchases I looked at were done only about a year ago, they are ECM Records releases, who are an independent company, but rely on Universal Music Group for distribution - too bad. UMG seems to continue watermarking to this day, at least until a year ago.