Stereo Tool

Not yet, but will be soon(ish)

We might take you up on that offer!
I've tried to fix this, the changes will be in beta 18. Could you see if it works?
Thank you for providing the information about labeling! It's hard for us to properly support this kind of functionality when we have no idea where to start or how to test it.
There is an "ask confirmation on close" setting, which saves you from having to modify the .ini file.
It should be present in the web interface as well.

Try setting [Application Settings > Preferences > On pressing close] to "Always close"
Maybe set [Application Settings > Preferences > On closing from tray icon] to "Always close" as well
We'll take a look at it.

I'm missing the settings to adjust output buffers.

You need to dig a little to find them.

I/O>
Audio I/O>
Normal Output>
More Normal Output Settings>
"Sound card driver issues workaround, use only if you get constant glitches"

Appreciate it

A question, can you add the Jack backend in the same executable alongside ALSA, cause from what I see the gui is designed to carry more categories for input/output.

Also, I would really like the Ctrl+scroll/drag key binding for granular control of sliders.

Thanks

Minor: The scope wants to keep previous data (scrambled) in the same space when swapping to/from True Bass and Processing, as opposed to repositioning itself to the center or clearing entirely.

Reproduction:
Open scopes on Processing
set scale low enough to show phosphor glow/fade
Open scopes on True Bass
Watch scope while switching back to Processing

There are probably more, but this is the first one I noticed this happening with. Beta 17 64bit

The zoom factor was indeed not saved/loaded correctly, that will be fixed in the next beta


The screen size issue was caused by a mismatch in what value was saved:
The old gui saved the size already compensated for dpi (i.e. the size as what it would have been at 100%)
The new gui just saved the current size and the current dpi and compensated during loading

This meant that a window of 1500x1500 at 150% in the old gui would get saved as 1000x1000, then when loading the new gui it would check the saved dpi (150%) against the current dpi (also 150%) and think: yep this is right, I'm done. The result: a window that is 100/150 = 2/3 the size.
Combine that with the zoom not saving, and presto: we get the behaviour in your screenshot.


The biggest problem (saved value mismatched) will be 'fixed' in the next beta.


There's also some other mismatching: it looks like one of the guis saves with borders and the other one without, but I'm not going to spend development time on this since it's not technically a bug in either of the interfaces.

Should be fixed in the next beta

The new web interface is being used. That specific issue was about the old one. I can't find a setting to change back to the old one in the web interface, if the older one still exists.

Put /st after the port for the old web GUI.