Beta-test: DeltaWave Null Comparison software

[Grooved]

Just added a page to DeltaWave website with data reprocessed from the Gearslutz AD/DA loopback test page.

It's a subset of all the files. Since this was done automatically, by a script, there may be some things that are mislabeled. Let me know and I'll fix them:

https://deltaw.org/gearslutz.html

Ordered by increasing value of PK error metric, here are a few top contenders:
View attachment 118372

Hi pkane, I will intsall your lastest release, thanks for the work on this software ;-)

I saw that you can edit some information in the results page for the loopback test :
the Echo AudioFire 8 almost at the top was synced via ADAT, which means it has ADAT ports, so it's the 2nd version.
It's called AudioFire 8a, and has AK4620B ADC/DAC chips
The 1st version (8 without "a") has no ADAT port and CS4272 chips.

The AudioFire 12 is in the same case (AK4620B or CS4272), but we don't know which one it was (only the Firewire ports pointing differently).
Last, the AudioFire 4, don't know too, but both versions have less differences (AK4620B for 2nd versionn, 1st version has AK4620A)

I saw an error for the MOTU 828 MK2 : I used the file I recorded with my 828 MK2 USB, and got far higher numbers than the one here :
-56.7 GSRMS, -56.7 DWRMS, -90.3 DW RMSEQ (dBFS), -100.3 DW RMSEQ (dBA) and -107.9 DW PK Metric (dBFS)

Can you check the file you have for this device ?
I will also run it from the 828MK2 Firewire

I also saw that there's an RME Babyface Pro test on GS with headphones outputs that gives better results than the XLR outputs, maybe it can improve the other DW results

 

[pkane]

Hi pkane, I will intsall your lastest release, thanks for the work on this software ;-)

I saw that you can edit some information in the results page for the loopback test :
the Echo AudioFire 8 almost at the top was synced via ADAT, which means it has ADAT ports, so it's the 2nd version.
It's called AudioFire 8a, and has AK4620B ADC/DAC chips
The 1st version (8 without "a") has no ADAT port and CS4272 chips.

The AudioFire 12 is in the same case (AK4620B or CS4272), but we don't know which one it was (only the Firewire ports pointing differently).
Last, the AudioFire 4, don't know too, but both versions have less differences (AK4620B for 2nd versionn, 1st version has AK4620A)

I saw an error for the MOTU 828 MK2 : I used the file I recorded with my 828 MK2 USB, and got far higher numbers than the one here :
-56.7 GSRMS, -56.7 DWRMS, -90.3 DW RMSEQ (dBFS), -100.3 DW RMSEQ (dBA) and -107.9 DW PK Metric (dBFS)
View attachment 130909

Can you check the file you have for this device ?
I will also run it from the 828MK2 Firewire

The file name is listed in the first column in the spreadsheet. If you check the GS thread, it's the one from here:

MOTU 828 MkII:
laurend: 6.1 dB (L), 6.2 dB (R), -56.7 dBFS (L), -58.0 dBFS (R)

When I run this file with the latest DW, I get this:

 

[pkane]

Hi pkane, I will intsall your lastest release, thanks for the work on this software ;-)

I saw that you can edit some information in the results page for the loopback test :
the Echo AudioFire 8 almost at the top was synced via ADAT, which means it has ADAT ports, so it's the 2nd version.
It's called AudioFire 8a, and has AK4620B ADC/DAC chips
The 1st version (8 without "a") has no ADAT port and CS4272 chips.

The spreadsheet I posted contains descriptions extracted directly from the GS compilation thread. I would rather not modify them, as they will not match the text in the thread. Echo AudioFire 8 is described this way in the GS post:

Echo Audiofire 8 with ADAT clocked by RME HDSP 9632 (schtim): 0.1 dB (L), 0.1 db (R), -46.3 dBFS (L), -47.7 dBFS (R)

 

[Grooved]

The spreadsheet I posted contains descriptions extracted directly from the GS compilation thread. I would rather not modify them, as they will not match the text in the thread. Echo AudioFire 8 is described this way in the GS post:

Echo Audiofire 8 with ADAT clocked by RME HDSP 9632 (schtim): 0.1 dB (L), 0.1 db (R), -46.3 dBFS (L), -47.7 dBFS (R)

Are using a script that can change it automatically if it's changed on GS ?

The file name is listed in the first column in the spreadsheet. If you check the GS thread, it's the one from here:

MOTU 828 MkII:
laurend: 6.1 dB (L), 6.2 dB (R), -56.7 dBFS (L), -58.0 dBFS (R)

When I run this file with the latest DW, I get this:
View attachment 130922

Can you use mine to confirm the result I got ?
It's not on the list yet, but I submitted on GS this file and it was tested with this result on GS :
-13.872 µs, 0.1037 dB (L), 0.0911 dB (R), -56.7294 dBFS (L), -58.0631 dBFS (R)

File is : MOTU 828 MK2 USB 3-4 to 3-4 : Link

 

[pkane]

Are using a script that can change it automatically if it's changed on GS ?

Yes. I'll have to re-run the script to update the list, but it goes through GS post with all the files, extracts the files and runs DW to measure them and then generates a spreadsheet.

Can you use mine to confirm the result I got ?
It's not on the list yet, but I submitted on GS this file and it was tested
MOTU 828 MK2 USB 3-4 to 3-4 : Link

Here's what I get:

 

[Grooved]

Here's what I get:

View attachment 130929

Thanks!
I see a little difference, I just did the test one more time after updating DW. Here is what I get (a bit more on DWRMS, a little bit less on other, same in PK Metric but with a increase on the right end at -101dB while yours never goes up to -103dB). What can explain it ?

 

[pkane]

Thanks!
I see a little difference, I just did the test one more time after updating DW. Here is what I get (a bit more on DWRMS, a little bit less on other, same in PK Metric but with a increase on the right end). What can explain it ?
View attachment 130943

Small differences are likely caused by differences between versions of DW. I tweak algorithms from time to time, and, of course fix bugs that are reported. The differences should not be large, unless there was a major bug fixed (or introduced!)

 

[pkane]

DeltaWave Version 1.0.67 is now available. Notable changes in this version are:

• Fixed: upsampling caused an index out of range error under certain conditions (@Pluto)
• Added: FFT Scrub plot will now update automatically in sync with playing music (press play next to Ref or Comp files)
• Added: A few new sizes of Tukey FFT Windows
• Added: Import of IR WAV-format files

 

[bennetng]

@pkane

Could you change the floating point export format to type 3?
http://www-mmsp.ece.mcgill.ca/Documents/AudioFormats/WAVE/WAVE.html

For example, Audacity, Reaper and Spek cannot recognize the exported 64-bit files if type 1 is specified.
Also, could you add 8-bit wav import support? This should be trivial, but useful for illustration/visualization purpose.

 

[pkane]

@pkane
View attachment 133173
Could you change the floating point export format to type 3?
http://www-mmsp.ece.mcgill.ca/Documents/AudioFormats/WAVE/WAVE.html

For example, Audacity, Reaper and Spek cannot recognize the exported 64-bit files if type 1 is specified.
Also, could you add 8-bit wav import support? This should be trivial, but useful for illustration/visualization purpose.

Easy enough

Please give v1.0.68 a try: https://deltaw.org

 

[bennetng]

Easy enough

Please give v1.0.68 a try: https://deltaw.org

The 8-bit file is not centered at -inf dB in the waveform view?

 

[pkane]

The 8-bit file is not centered at -inf dB in the waveform view?
View attachment 133187

Humph! Must be the unsigned value that's causing it. Let me fix it.

 

[pkane]

Humph! Must be the unsigned value that's causing it. Let me fix it.

Updated! This is using the same version number, so you'll need to uninstall the old 1.0.68 first.

The new one should properly scale 8-bit unsigned samples.

 

[bennetng]

Updated! This is using the same version number, so you'll need to uninstall the old 1.0.68 first.

The new one should properly scale 8-bit unsigned samples.

Excellent! Thanks.

 

[pkane]

Version 1.0.69b of DeltaWave is now available:

Changes in 1.0.69b

• Added: minimum phase filters can now be used in addition to linear phase ones
• Changed: Improved group delay plot to more closely match phase variations
• Changed: Cepstrum plot to use time (quefrency) scale on the X-axis, changed annotations to show frequency and period

Minimum phase filters can be selected in settings:

Cepstrum plot can be used to find echos, as well as reflections/reverb in a recording. For example, an echo at 0.5sec added using Audacity to a music file is easy to spot:

And here are the reverb/reflections in an un-manipulated music recording:

 

[Pdxwayne]

@pkane, may I know if there is any audible different between captures based on the following? Anything else I can provide?
Thanks!

 

[pkane]

@pkane, may I know if there is any audible different between captures based on the following? Anything else I can provide?
Thanks!

View attachment 139608

View attachment 139609

Whatever happens at 1:55 and 2:13-2:15 mark can be easily audible under right conditions. The rest is also at a fairly high level (-62dBFS) which can be audible as well, but less easy to hear.

 

[Pdxwayne]

Whatever happens at 1:55 and 2:13-2:15 mark can be easily audible under right conditions. The rest is also at a fairly high level (-62dBFS) which can be audible as well, but less easy to hear.

Thanks you very much!

This is part of my new thread at https://www.audiosciencereview.com/...clean-sounding-as-the-other.24778/post-838531

I hope you don't mind I quote you there.

Thanks again!

 

[pkane]

New version of DeltaWave 1.0.70 is now available.

Changes in 1.0.70b

• Added: support for log-frequency display in spectrograms
• Fixed: the name of FFT window Tukey0.01 was misspelled

Spectrogram log frequency display is controlled by the same Log Axis option as before:

Here's an example:

 

[mysiak]

I am trying to compare 2 audio files and I struggle to interpret results from this app. Could someone please help?

I recorded a short audio, while playing a test video on Youtube - it contains pure left, pure right and mixed audio. One file is just simple loop headphone out -> line in. Second file is recorded with an "audio gadget" in the path and I would like to know if it does anything audible (if yes, what does it do?).

Files were too large for an attachment, so I uploaded them here: https://ufile.io/f/vr1fy

Btw. I tried to match L channels and it seems to be working fine. But when I switched to R channels, no audio was detected nor matched. Are my files from Audacity "broken" or did I miss something in the app?

Thanks in advance!