I just tried to use the latest VST2 64-bit version together with Adobe Audition in Windows 11. But unfortunately this was impossible for me for the following reasons:

I use a larger screen scaling and not the default 100 percent but 125. This is because I have a smaller screen. Unfortunately, I have the problem that the stereo tool is rendered incorrectly or too large. I have no access to the cancel and apply button at the bottom of the plugin. By the way, I can't see this button at all.

I have also tried to change the size information provided in Stereotool, such as width and height. But these were reset after the next plugin start. Only the scaling available in StereoTool I could change, but that didn't help, because the window is simply displayed too large, and thus I can't work with it at all. It was therefore not possible for me to work with it in any meaningful way on a resolution of 1080p with a scaling of 125 percent.

That's why I wanted to try the VST3 version. But here I got along even less. Immediately after running the plugin, Adobe Audition completely just crashed with no feedback. The plugin was not even displayed to me.

Does Stereo Tool fit the window exactly but overwrite the borders where other Audition things should be displayed? Or does it not fit in the window at all? I'll add logging in tonight's build.

There was a dependency in our VST3 code (which has always been there, even with the old GUI) which assumed a specific initialization order. I removed that dependency yesterday (it crashed in WaveLab before on rendering, and it doesn't anymore), but last night's build failed. I hope to have a working version tonight or tomorrow morning.

Let me put it this way. The window is so big that it goes under the taskbar, you can't see the end of the whole window. I assume that everything is visible in principle, but due to the scaling of 125% and the fact that it goes under the taskbar, you can't adjust it to get to the Cancel and Apply buttons. This is so frustrating. Just can't show that well with a screenshot unfortunately, sorry.

@Hitman: I can confirm that I have an issue with setting Jack > 48 kHz on my Linux system (on Windows it works fine, so it cannot really be something in our code). I just went back to an older version (9.92 release) it does the same thing, so I think this is a Jack issue, not a Stereo Tool issue. Can you check if you also have the same issue with older versions? In both cases, the jackd-logging states that it's running at those higher sample rates.

I have not yet checked what it does with a HifiBerry, the older version definitely did run at 192 but I have to change some cables here to verify that it still does - it does handle any other frequencies so I don't expect it to be any different.

Can you make the build recognize a new filename flag of "_alsa+jack" or something like that, so that both can work together again like 0.54 did? I'd try that with the bugfixes after that version.

Good idea, the nightly build failed so I just added this and I'm restarting it now. Haven't tested it.

Oh. What resolution are you using on your monitor? And can you send the log file?