• Welcome to ASR. There are many reviews of audio hardware and expert members to help answer your questions. Click here to have your audio equipment measured for free!

Beta Test: Multitone Loopback Analyzer software

Guess I did not understand how to display the two recorded stereo channels one in Red and one in Blue.
Seems I see the Generator in Red and the Measurement in Blue in my last post.
Is there a chance to see the two Stereo channels recorded in one diagram and omit the generator output?

My goal is to have a comparison between the 1:1 loopback in the left channel and the loopback with a device under test in the Loop in the right channel?
 
Hi Paul,
I'm on 1.2.9 now as I can't access the link above.

I have made some progress so level ist OK now. I run the ADI-2 pro FS R with -0.5dB volume and +24dBu output level. I now run one test after the other to see which gives reasonable results. I run in STEREO mode as my idea is to have one channel in 1:1 loopback and the other with the device under test inserted in the loop. This makes sense to me as in this mode I can compare the changes the device under test creates.

Last I ran TD+N vs frequency (only) all other tests are not checked in the list. At the end of execution I get the error message attached.
The legend in the generated diagram also looks strange. For the left channel it says THD for the right TD+N. Seems somehow odd to me.

I added my current configuration to enable debugging for you.

Best DrCWO

EDIT:
With THD vs Level I see the same wrong legend saying THD (Left) dB and TD+N (Right) dB. Same Error Message after the measurement was saved here and quite a strange result comparing Right and left...
View attachment 461300


View attachment 461293

That last error message should go away with the new version. Can you download from Dropbox?

https://www.dropbox.com/scl/fi/ljeu...ey=ujiisqs1la9ifeshdvxwp7f3k&st=7xpi7mss&dl=0
 
Guess I did not understand how to display the two recorded stereo channels one in Red and one in Blue.
Seems I see the Generator in Red and the Measurement in Blue in my last post.
Is there a chance to see the two Stereo channels recorded in one diagram and omit the generator output?

My goal is to have a comparison between the 1:1 loopback in the left channel and the loopback with a device under test in the Loop in the right channel?

You can change the measurement displayed by selecting it as Measurement 1 and Measurement 2. If you select THD for both, one will be Left the other Right channels (just make sure you select L+R for the audio input channel selector):

1751835245384.png
 
I saw a strange error message running IMD SMPTE vs Level.
Added my settings so you can try to reproduce...
Also the response looks strange.
The strangest thing: I can't reproduce it :facepalm:
 

Attachments

  • 1751926785133.png
    1751926785133.png
    317 KB · Views: 37
  • ADI-2 Pro FS R.zip
    ADI-2 Pro FS R.zip
    9 KB · Views: 34
  • IMD SMPTE vs Level - Lvl Sweep.png
    IMD SMPTE vs Level - Lvl Sweep.png
    98.4 KB · Views: 43
Without the error message output looks much better. This was my second try with the same settings.
 

Attachments

  • IMD SMPTE vs Level - Lvl Sweep.png
    IMD SMPTE vs Level - Lvl Sweep.png
    77.9 KB · Views: 50
Without the error message output looks much better. This was my second try with the same settings.
Ok, all the tests have passed in single execution mode now with the exception described above.
I will run the complete script tomorrow and see what happens.

Here two quick ideas for further improvements:
  1. Starting of Multitone takes quite a while on my i7. Therefore sometimes I did not know if the double click was caught by Windows or not. A splash screen displayed directly after startup would be great to get quick feedback..
  2. It would be helpful to see a checkbox to enable or disable the complete list of tests with one mouse click.
Best DrCWO
 
I started the complete sequence this morning.
Saw the error again after processing Log Sweep FR (4M). Also the result seems odd...
 

Attachments

  • Log Sweep FR (4M) - Spectrum.png
    Log Sweep FR (4M) - Spectrum.png
    95.5 KB · Views: 36
  • 1751958603832.png
    1751958603832.png
    723.3 KB · Views: 42
Restarted the sequence at Log Sweep FR (4M). No issues here. But I saw the same error at end of DIM 30 test again.
Hope this helps fixing the issue.

Also added the latest settings of the test script

Best DrCWO
 

Attachments

  • 1751962031703.png
    1751962031703.png
    692.7 KB · Views: 49
  • DIM 30 - Spectrum.png
    DIM 30 - Spectrum.png
    160.3 KB · Views: 45
  • ADI-2 Pro FS R.zip
    ADI-2 Pro FS R.zip
    8.8 KB · Views: 48
Last edited:
I restarted the whole script again.
Same issue and error message as I posted here. Seems to be reproduceable maybe also on your system :D
 
Hi, Would it be possible to add the now fairly standard (even if rather "harsh") 2 sigma to the DIN in W&F measurement?

Thanks in advance
;-)
 
@pkane I have a slight issue with the settings part of the main window. It's clipping the right hand side?

I can adjust the size of the graph window, but that just clips the settings section even further.

Desktop resolution is 3840 x 2160.

1754643137332.png
 
@pkane I have a slight issue with the settings part of the main window. It's clipping the right hand side?

I can adjust the size of the graph window, but that just clips the settings section even further.

Desktop resolution is 3840 x 2160.

View attachment 468484
Hmm. Have you tried resizing and closing the app, then starting it again? Does that still show like this?
 
Hmm. Have you tried resizing and closing the app, then starting it again? Does that still show like this?
If I size the app to fill a large part (~80%) of the screen, it seems to behave. But if I resize it back to a smaller area, then it reverts as my screenshot above.

This is after closing and reopening the app both times.
 
If I size the app to fill a large part (~80%) of the screen, it seems to behave. But if I resize it back to a smaller area, then it reverts as my screenshot above.

This is after closing and reopening the app both times.
Yeah, that's strange. What version of Windows are you using? Do you have any graphics settings to increase DPI or zoom level, or font size for the whole desktop? I'm hoping I can replicate this issue, as I've not seen this before.
 
Yeah, that's strange. What version of Windows are you using? Do you have any graphics settings to increase DPI or zoom level, or font size for the whole desktop? I'm hoping I can replicate this issue, as I've not seen this before.
Windows 10, 22H2. GFX card is Nvidia GTX1070.

I have two monitors, but it always starts on my primary monitor so moving it to the second monitor (1920x1080) makes no difference.

I guess the app adapts to the monitor on which it is started from?

EDIT: I moved the shortcut to the desktop on the second monitor, and then it does start on the second monitor - however the problem persists, and I'm not even able to resize it to a point where the entire settings window is visible.

Primary monitor:

1754656236042.png


Second monitor:

1754656236053.png
 
Windows 10, 22H2. GFX card is Nvidia GTX1070.

I have two monitors, but it always starts on my primary monitor so moving it to the second monitor (1920x1080) makes no difference.

I guess the app adapts to the monitor on which it is started from?

EDIT: I moved the shortcut to the desktop on the second monitor, and then it does start on the second monitor - however the problem persists, and I'm not even able to resize it to a point where the entire settings window is visible.

Primary monitor:

View attachment 468518

Second monitor:

View attachment 468517

Thanks, if this is possible, can you try setting scale and layout to 100% from 125% and see if the problem still occurs?
 
Thanks, if this is possible, can you try setting scale and layout to 100% from 125% and see if the problem still occurs?
Ok, set to 100% (primary monitor) the problem goes away (but of course then everything is somewhat small!).

If I set it to the windows recommendation for the primary monitor (150%) the problem persists with that as well.

It's odd that it happens with my secondary monitor which is at 100% though?
 
Ok, set to 100% the problem goes away (but of course then everything is somewhat small!).

If I set it to the windows recommendation for this monitor (150%) the problem persists with that as well.

It's odd that it happens with my other monitor which is at 100% though?

There are often some strange effects with Windows scaling/DPI. I'll see if I can reproduce this.
 
There are often some strange effects with Windows scaling/DPI. I'll see if I can reproduce this.
Yes I had a similar issue with a small dot net app I wrote some years ago. From memory, there was a check box for the object that solved the issue.

I guess that your app is written in C++/C# or similar, so I think you have to construct all the dialogue boxes programmatically?

My knowledge of programming is quite limited as you will have gathered from the above statements lol.

Thanks for your efforts with this, I appreciate it. And appreciate your apps too.
 
Back
Top Bottom