Beta Test: Multitone Loopback Analyzer software

[pkane]

The new version appears as 1.0.52 and asks to update to 1.0.53.
Ghost version perhaps???

Strange. I just re-built and re-uploaded the correct version. Can you please try to update one more time?

 

[Sokel]

Strange. I just re-built and re-uploaded the correct version. Can you please try to update one more time?

Ok now!

 

[pkane]

Can you please show it in a less dramatic way… where we can see where it ends up in cycles, radians, or degrees?

Here's a less dramatic version of the SD Sharp filter phase response (same data, just zoomed out further). Y axis is in degrees:

EDIT: and if you really want something dramatic Here's the frequency response for the same filter (above):

 

[Rantapossu]

Multitone Release v1.0.53 is available. This version is the official release of DSD/DOP 64/128/256 and also adds the phase response plot using one of the multitone test signals.

Changes in 1.0.53​

• Add: support for DSD test signal playback over DOP, supporting DSD64, DSD128, DSD256
• Add: phase plot, calculated when using multitone test signals and the same ADC/DAC sample rate
• Add: Higher sampling rates up to 768k (possibly higher, if your device(s) support it)
• Add: File drag-and-drop (on test signal drop-down) feature to measure files without DAC/ADC loopback
• Fix: when displaying spectrum captured in stereo mode, show full bandwidth of the captured signal

----------------
Some examples of phase measurements (ADI-2 Pro FS filters, measured by Cosmos ADC) @ 44.1k.
Note that the sampling rates must match between the DAC and the ADC to produce a phase plot.

Sharp filter:
View attachment 239492

SD Sharp (short delay) filter:
View attachment 239494

Thanks!

It seems to forget the customized title text of the new phase graph after every measurement:

Before the measurement ( Phase {recordSampleRate/1000}kHz, {fftSize/1024}k fft, {channelsIn} ) :

After the measurement:

 

[GXAlan]

One more feature request.

My Yamaha AVR has a few seconds of delay before it unmutes. I have done the "ALT-R, ALT-S, ALT-R" trick but is there a way for you to add an optional delay? I.E. Start playing X seconds and then start recording?

EDIT: NEVER MIND. Found the warm up time setting!

 

[Rantapossu]

@pkane have you changed something regarding the handling of the calibration files lately?

This is measured with the following calibration file:

20 60 0 20000 60 0

The plot is near the -160 dB line during the whole measurement and during the processing, but it jumps 60 dB up when the measurement is ready. If I add the same measurement from the history, it shows it correctly at the -160 db line.


However it works ok with the October 7th build (v1.0.52), both lines are on top of each other as they should be:

 

[pkane]

@pkane have you changed something regarding the handling of the calibration files lately?

This is measured with the following calibration file:

20 60 0 20000 60 0


View attachment 240114

The plot is near the -160 dB line during the whole measurement and during the processing, but it jumps 60 dB up when the measurement is ready. If I add the same measurement from the history, it shows it correctly at the -160 db line.


However it works ok with the October 7th build (v1.0.52), both lines are on top of each other as they should be:

View attachment 240121

I didn't intentionally change it Let me see what's going on...

 

[pkane]

@pkane have you changed something regarding the handling of the calibration files lately?

This is measured with the following calibration file:

20 60 0 20000 60 0


View attachment 240114

The plot is near the -160 dB line during the whole measurement and during the processing, but it jumps 60 dB up when the measurement is ready. If I add the same measurement from the history, it shows it correctly at the -160 db line.


However it works ok with the October 7th build (v1.0.52), both lines are on top of each other as they should be:

View attachment 240121

Just posted a new version, v1.0.54. Please give it a try. Looks like the calibration step was inadvertently removed after the signal is captured.

 

[pkane]

Version 1.0.54 of Multitone is now available. This is to address the issue of THD calculation using dBFS or dBr units. To avoid confusion, dBr (relative to the fundamental) will now be the default calculation. Harmonic amplitudes will still be shown in the units selected:

Changes in 1.0.54​

• Change: improved method to find the initial sample alignment between test signal and captured waveform
• Change: THD/distortion panel now shows THD relative to the fundamental, regardless of the selected units
• Fix: calibration file was not applied in spectrum plot after capture
• Fix: phase plot custom title not preserved after measurement

 

[Rantapossu]

Version 1.0.54 of Multitone is now available. This is to address the issue of THD calculation using dBFS or dBr units. To avoid confusion, dBr (relative to the fundamental) will now be the default calculation. Harmonic amplitudes will still be shown in the units selected:

Changes in 1.0.54​

• Change: improved method to find the initial sample alignment between test signal and captured waveform
• Change: THD/distortion panel now shows THD relative to the fundamental, regardless of the selected units
• Fix: calibration file was not applied in spectrum plot after capture
• Fix: phase plot custom title not preserved after measurement

Thank you again!

Calibration file works now as it should.

 

[Rja4000]

Check what version

View attachment 237372

And, still:


Source: Application Error
Date: 30-10-22 09:07:54
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic

Description:
Faulting application name: Multitone.exe, version: 1.0.54.0, time stamp: 0x635d8191
Faulting module name: ucrtbase.dll, version: 10.0.19041.789, time stamp: 0x2bd748bf
Exception code: 0xc0000409
Fault offset: 0x000000000007286e
Faulting process id: 0x2734
Faulting application start time: 0x01d8ec36b47f1bdb
Faulting application path: C:\Program Files (x86)\PKAudio\Multitone\Multitone.exe
Faulting module path: C:\WINDOWS\System32\ucrtbase.dll

 

[pkane]

View attachment 240223

And, still:


Source: Application Error
Date: 30-10-22 09:07:54
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic

Description:
Faulting application name: Multitone.exe, version: 1.0.54.0, time stamp: 0x635d8191
Faulting module name: ucrtbase.dll, version: 10.0.19041.789, time stamp: 0x2bd748bf
Exception code: 0xc0000409
Fault offset: 0x000000000007286e
Faulting process id: 0x2734
Faulting application start time: 0x01d8ec36b47f1bdb
Faulting application path: C:\Program Files (x86)\PKAudio\Multitone\Multitone.exe
Faulting module path: C:\WINDOWS\System32\ucrtbase.dll

If you are really determined to make Multitone work on this computer ...

I'd try to uninstall VC runtime 2015 from Windows then re-install it from here:

https://www.microsoft.com/en-us/download/details.aspx?id=53840

The date on your DLL of 2021 appears a bit suspicious and doesn't correspond to the date of that runtime (latest release was 2016, original release in 2015), so possibly it's patched or installed from some other package where it was rebuilt.

 

[Rja4000]

If you are really determined to make Multitone work on this computer ...

I'd try to uninstall VC runtime 2015 from Windows then re-install it from here:

https://www.microsoft.com/en-us/download/details.aspx?id=53840

The date on your DLL of 2021 appears a bit suspicious and doesn't correspond to the date of that runtime (latest release was 2016, original release in 2015), so possibly it's patched or installed from some other package where it was rebuilt.

I suppose this is the one coming with Visual Studio 2019 (Or its updates)

 

[pkane]

I suppose this the one coming with Visual Studio 2019 (Or its updates)

Possibly, the versioning of Microsoft products makes no sense to me if all they changed was the build number between major releases… give that 2015 package a try, just make sure you can reinstall or restore the previous version if that doesn’t work.

 

[pkane]

A quick new feature added to v1.0.55, now available:

Changes in 1.0.55​

• Add: support for measuring the difference between two channels (“L-R” input selector). Added to spectrum, frequency response, phase, and waveform plots

Just a single change to add the "L-R" channel selector to the input channel option drop-down. If using a multi-channel input device, you can also use any two channel numbers instead of L or R (for example "1-2" or "3-7", etc.).

The channel output selector should have two channels specified for this function to work correctly. Alternatively, you use a single output channel and a splitter to generate two inputs to the ADC.

Channel delta replaces the second channel (R) by the difference between two recorded channels, in effect computing channel imbalance in amplitude, frequency, and phase.

For example, blue is left channel, white is L-R computation. ADI-2 Pro FS into E1DA Cosmos ADC set to stereo mode:

Same measurement but showing frequency response error:

And phase difference between channels:

 

[Blumlein 88]

I really want to try this version 55 for the L and R feature. I know in Deltawave, comparing one channel to another doesn't get an incredibly deep null like most people expect. The idea of some of the things that could be audible, and ideas about imaging don't add up when you realize the difference between channels much less between DACs. So trying some of these test signals out to see the results will be interesting. Been a busy week, but maybe I'll get to it soon.

 

[Sokel]

I really want to try this version 55 for the L and R feature. I know in Deltawave, comparing one channel to another doesn't get an incredibly deep null like most people expect. The idea of some of the things that could be audible, and ideas about imaging don't add up when you realize the difference between channels much less between DACs. So trying some of these test signals out to see the results will be interesting. Been a busy week, but maybe I'll get to it soon.

Already measured a lot of stuff some with really good results,some not.
Only think is that I'm lazy to built a nice splitter so I can have accurate results but now I will.

 

[Sokel]

That's what's E-mu looks like (difficult to set levels straight,it's pots are horrible)
(I don't even know if I do it right!)

Spectrum

FR

Phase

 

[pkane]

That's what's E-mu looks like (difficult to set levels straight,it's pots are horrible)
(I don't even know if I do it right!)

View attachment 242414

Spectrum


View attachment 242415

FR


View attachment 242416

Phase

Can you please try reinstalling Multitone from the website? It was updated some minutes after the initial post announcing it, as I remembered I had some test code that disabled L-R processing for ASIO devices (but worked correctly for WASAPI in that older version). The newer version should process both correctly. Your spectrum plot looks suspiciously like L-R was simply treated the same as two stereo, L and R channels, independent of each other.

 

[Sokel]

Can you please try reinstalling Multitone from the website? It was updated some minutes after the initial post announcing it, as I remembered I had some test code that disabled L-R processing for ASIO devices (but worked correctly for WASAPI in that older version). The newer version should process both correctly. Your spectrum plot looks suspiciously like L-R was simply treated the same as two stereo, L and R channels, independent of each other.

Yep,that's what I thought too as I tried L+R and they where identical.
Installing and report back.