There's nothing changed in the processing yet. What I did was: I changed the current really bad parameter handling code that I designed around 8 years ago.. When I was doing this project to learn C++... And at the time I had about 30 parameters.
In the old code, I had to write the following code for each parameter:
1 The parameter itself and a default value, inside a processing filter class (that's good)
2 Manually place a new parameter (slider, checkbox, ...) in the GUI
3 Code to send the actual value of the parameter to the GUI
4 Code to read the value of the parameter from the GUI
5 Code to write parameter values to STS files
6 Code to read parameter values from STS files
7 Code to write parameters to the VST interface, including functions to define the VST parameter name and unit, and one to display it
8 Code to read parameters from the VST interface
You can probably imagine why I hated adding new parameters
So, starting last week, I've been redesigning this whole parameter mechanism. Right now I only have to define a parameter in one location (a single line even), and the steps 5-6-7-8 are now automatically generated from that. Step 2, 3 and 4 still need to be automated - but the information is there.
Because writing GUI code takes much effort I came up with a different solution yesterday afternoon: I've added a HTTP-based remote interface. The display from the first post of this thread is what you see when you run Stereo Tool and open
http://localhost:8000/ in your browser
So, you can now remotely control Stereo Tool
(Well, partially - for now only checkboxes and sliders work, and there's no password protection etc. yet).
I'm going to implement this remote interface first, then get feedback from that, and based on that, I'll create a new GUI (which will probably resemble the HTML-interface a lot but it won't have to use standard HTML objects so it can look quite different; the layout will be similar though).