IMD Measurements: "Generator" vs "Input" Level Discrepancy

[reallystate]

I have such a keyboard. I can check if your keyboard shortcut works for me. For example, the smoothing toggle works for me on the latest version.

I also have a Cyrillic keyboard, and even the usual copy and paste commands don't work in the application on Linux.

 

[sm52]

on Linux

I have Windows 10-64. Most likely, your problem is related to Linux.

 

[reallystate]

In the latest beta version (103), after taking a screenshot, the cursor still changes its position.

 

[reallystate]

Why is an infinity sign sometimes shown under the graph instead of the value? After restarting the app, this error disappears, but then appears again.

 

[John Mulcahy]

That would suggest a value has become zero, so the conversion to dB is infinite. I'd need to see the mdat file to investigate further.

 

[John Mulcahy]

In the latest beta version (103), after taking a screenshot, the cursor still changes its position.

Works OK for me, can you be more specific? Any particular graph?

 

[reallystate]

That would suggest a value has become zero, so the conversion to dB is infinite. I'd need to see the mdat file to investigate further.

Last time, after some actions, all measurements showed the infinity sign instead of a number, but this time only one measurement did it

 

[reallystate]

Works OK for me, can you be more specific? Any particular graph?

 

[John Mulcahy]

Last time, after some actions, all measurements showed the infinity sign instead of a number, but this time only one measurement did it

I have fixed that for the next build. It would happen after switching the X axis between input and generator.

 

[John Mulcahy]

That graph capture is certainly interesting, those colour scheme changes don't happen on Windows or macOS in the same circumstances. The cursor also stays where it is on Windows and macOS, even when placed at the far right edge as in your example.

 

[reallystate]

Is it possible to make these buttons translucent since it is inconvenient to place the cursor under them?

 

[John Mulcahy]

Yes, I have done that for the next build.

 

[reallystate]

I can make the sorting alphanumeric rather than lexicographic in the next build.

Thanks for all the fixes that were implemented in the latest beta version. The issue was fixed in the context of the list of imported measurements. Can you also please fix it in the list of files stored on the disk, which opens when you click the Open button located in the upper left corner of the screen?

 

[reallystate]

After updating from 105 to 106, and also to 107 beta, the interface looks too large compared to what it was before.
Earlier

Now

 

[reallystate]

Also, after updating to beta versions 106 and 107, the THD+N graph is displayed incorrectly. It's drawn along the noise floor line, whereas it should be closer to the noise (N) level. And even returning to version 105 does not help to fix the problem.

Moreover, this incorrect display occurs in all measurements created in earlier versions.

 

[reallystate]

By the way, keyboard shortcuts still don't work on the Cyrillic layout.

 

[John Mulcahy]

After updating from 105 to 106, and also to 107 beta, the interface looks too large compared to what it was before.

Check your font size setting in the View preferences. Font scaling is now automatic, per the Windows display scaling.

 

[John Mulcahy]

after updating to beta versions 106 and 107, the THD+N graph is displayed incorrectly. It's drawn along the noise floor line, whereas it should be closer to the noise (N) level

Displays normally for me. Your image doesn't show THD+N, only THD, so difficult to comment on that graph specifically.

 

[John Mulcahy]

By the way, keyboard shortcuts still don't work on the Cyrillic layout.

I've done all I can on that, sorry.

 

[reallystate]

Check your font size setting in the View preferences. Font scaling is now automatic, per the Windows display scaling.

I was able to rescale the interface elements and get the previous font size by changing the font size to 10, but now the icon size is significantly larger than before and interface elements like the sine wave and levels window are blurry.

 

[reallystate]

Displays normally for me. Your image doesn't show THD+N, only THD, so difficult to comment on that graph specifically.

In the dark user interface, THD+N is a light gray line. If you take a screenshot using the app and select a light background in the settings, the line will remain light gray. In the graph above, this line is just barely visible and is located near the noise floor.

 

[reallystate]

Thanks for all the fixes that were implemented in the latest beta version. The issue was fixed in the context of the list of imported measurements. Can you also please fix it in the list of files stored on the disk, which opens when you click the Open button located in the upper left corner of the screen?

Can you please fix this as well?

 

[John Mulcahy]

That's THD, you haven't selected THD+N for that graph, the value is the same as the N trace in the legend.

I was able to rescale the interface elements and get the previous font size by changing the font size to 10, but now the icon size is significantly larger than before and interface elements like the sine wave and levels window are blurry.

What Windows version and display scaling factor are you using?

 

[reallystate]

That's THD, you haven't selected THD+N for that graph, the value is the same as the N trace in the legend.

I'm sorry, it's my mistake.

 

[reallystate]

What Windows version and display scaling factor are you using?

I'm using Linux and 150% interface scaling. Until version 106 the interface looked perfect.