Stereo Tool

In instalation setup can be added license.

_________________
control point
control point2

Cool, so this was very easy. I'm posting what I did in case somebody comes across this down the line.
Right CTRL + Numpad Forward Slash (divide) restarts the soundcards using this autohotkey script:

>^NumpadDiv::
whr := ComObjCreate("WinHttp.WinHttpRequest.5.1")
whr.Open("GET", "http://127.0.0.1:8080/json-1/list`%7B`%2210439`%22`%7B`%7D`%7D", false)
whr.Send()

I don't understand what you mean. Are you suggesting an update to the installer to allow registration key entry? VST3 doesn't really have an installer though.

Posted BETA072, which is very close to a release candidate (for Enterprise at least).

The new web interface is greatly optimized and reduced in half by size compared to the previous beta posted here. This is a major rewrite, please let me know if you see anything weird. It should work the same as before.

Edit: By size I mean loading size - it's 422 kB now. It should look and act the same as before, but it might load faster.

If this is now better, the new web interface is still with screen readers and presets cannot be changed. But that's why plugins can be configured in the new web interface, which was not possible before in the old web interface, now with screen readers we can adjust the plugins as we wish. The only thing missing is that we can change the preset. However, how do I do it for now? From the old web interface with 9.2 beta, I copy the taj.dll file, then save the presets on HdD and then restore the .dll file of version 10. Then in the new web interface, I configure the plugins according to my wishes, make the volume presets and then access the old web interface from 10 pplugins and save your presets. So then in the old web interface with /st I can go to load presets and listen to the presets I saved. For now, that's the only way I can work, but I'm managing, that's important.

Beta 072 vst2x64 OBS 28.0.3

Saving presets seems to be broken and I don't know if it's Host related. It saved a 9kb file with no active settings even though I had imported a fleshed-out preset and re-saved it. Then upon closing the interface and toggling the "open interface when active" box, it reloads the settings the VST was initially loaded with. Very odd. 066 did not behave this way.

Going to try Reaper and report back.

edit: Okay yes it doesn't want to save a preset properly from Reaper either.

What are you doing exactly? I just tried it in Reaper (on Windows, I assume you're using Windows?) and I see no issues. I've tested the 64 bit VST2, with old and new GUI, and even 32 bit bridged. They all seem to work fine. This was with version 075 (which I'll upload in a moment), but nothing has changed in the last few beta's.

My steps, in Reaper:
- Load VST plugin (first time, so there are no earlier settings)
- Select a preset
- Save that preset with the "+" button in Reaper
- Reset all settings in Stereo Tool to factory defaults
- Select the preset that I just saved in Reaper
This loads everything again.

- Unload VST
- Restart Reaper
- Select VST again
- Select the earlier saved preset again
This also loads everything again.

Just to make sure, I saved to a Stereo Tool .sts file as well - that worked fine.

Edit: I also just looked through the code changes, and the only thing that changed in the VST2 code since BETA066 is the handing of the window size. This is weird...

Now I'm confused. I was actually talking about the preset manager in ST itself, not the preset manager in Reaper. I have never used the + preset thing and have always loaded things internally. I'll be testing out the + in the future.

What I did
-Load VST, which comes in neutrally in this build regardless of previous settings -- At least in OBS. It may always default to neutral in Reaper, unsure.
-Select a preset
-Export current settings to file

The saved file is 9kb and contains micrompx info. Do I DM it to you?
Loading it up results in completely neutralized settings.

edit: okay I was mistaken, it was not working in 066 either, and I cannot be sure which version I had last that it did work in. Will be doing more testing.

Ah! Sorry, I assumed it was something VST specific. I'm trying to reproduce it now...

EDIT: Ok, confirmed. I see it here as well. Looking into it now. It appears to be ok in the stand alone version - weird.

Ah, the other issue I was experiencing with it loading up neutralized regardless of previous settings in OBS seems to not exist in 066. I was unsure if they were related.

I found the bug. But it looks like it was already there in BETA066 (and way further back as well), so I'm confused. The export button was only exporting things that cannot be stored in VST parameters, ie strings.

Coming up with empty settings is unrelated to this; hosts need to store the settings themselves, using the method that I described before (the thing with the + - but that happens automatically, you won't notice that).