Whle new additions are appreciated, are there plans for some of these bug fixes that keep getting overlooked each update?
Passing mousewheel and all keys into to VST3 plugins. It is absolutely painful to load VST inside Scaler. Even browsing presets is tedious, as is editing sounds, when mousewheel does not work and QWERTY keys do not even always seem to work. Rather than mousewheel, a combination of mouse clicks, arrow keys, and num pad +/- are all that works to move controls or browse presets.
Keep VST plugins open when using Scaler so users can change/tweak sounds and also use Scaler interface without always re-opening the plugin. This is the only host/tool I know of where the plugin window closes the instant a user touches the host/tool interface.
The MIDI editor is still extremely painful to use. If all it will ever do is draw whole notes or let users adjust a note in a chord up or down, maybe a different interface from piano roll would be the way to go.
Please, STOP TAKING ACTIVATIONS FOR EVERY UPDATE!!! I keep getting told this does not happen by Scaler team, but every tiny update uses an activation and anyone who bothers on your side could test this themselves with any host and a Windows 11 machine. The activation method is completely annoying. I have used 5 activations messing about with updates.
Etc…
Those types of things keep me from using Scaler much. Again, while I appreciate new stuff and the complexity of what is being done, basic features that were released months ago still do not work well and personally I would prefer to see those improved rather than add new things.
I use Reaper and in fact the other plugins e.g. Jun-6V or Pigments just go behind Scaler 3, and are not closed. So, by just dragging them left or right, I can use Scaler and plugin(s).
Were you trying to offer a solution, or just reporting all is well in your preferred host? If that was intended as a solution, I do appreciate the effort, but otherwise it is not productive to say ‘it works for me’ on the bug reports or feature requests of others. I also note that Reaper passes all mousewheel and keys properly to Scaler, but that still does not solve my issue (or the issue for others) in other DAWs. Neither Maschine nor Sonar (both latest versions) handle plugins properly through Scaler, although Maschine, Kontakt, or any other sub host loaded in either does handle plugins properly, so there is something unique to Scaler that is the cause here.
What you are doing with window arrangement, I consider a workaround I cannot use and should not have to. Reaper too will still push the plguin window to the back if you don’t separate the plugin off any part of Scaler. I don’t want to have windows floating all over the place to work around Scaler’s problems, especially as I often work off one large monitor, or even a laptop screen when traveling, and prefer the DAW maximized and plugin interfaces large. Some plugin overlap on the host window is normal, so I should not have to physically separate the two on different screen positions or one pushes behind the other window. Maschine, Kontakt, or any other VST host/subhost works how I would expect within a DAW, Scaler does not when it hosts plugins. It needs its own “float plugin” option perhaps.
There are at least two other posts that are not mine in the forums complaining about the same plugin window closure behavior. In Sonar and Maschine, the two hosts I use most, the loaded plugins inside Scaler do not stay open if you touch anything on Scaler.
So far, no acknowledgement from the developer on if they hear us or have any interest in basic plugin hosting improvements.
My idea was to offer a kind of solution: If the plugins hosted in S3 are not completely closed but only pushed back, just by finding them and position so that they are visible after that , would be a solution.
I thought quite a long time that plugins were closed, and I found they are not, so this is faster access for me. If some users did not try going behind, they cannot know.
But if this does not work with some other DAWs, this could also be plugin container handling of the DAW rather than S3 problem per se. I never used anything else but Reaper and I always mention what works, or not, in my specific configuration.
This might work for someone else, and not for everyone.
We hear you, we read every post, we make every effort, we will always endeavour to improve. We can’t respond to everyone unfortunately. Thanks for your patience.
