Scaler (latest version) still has problems with multiple scaler instances in some situations. I’m using two instances.
2. instance: I dragged several chords from the Explore area to the main track and listened to them on the master keyboard. There, the velocity values of the individual notes were terribly messed up. Even adjusting the velocity of the individual notes, which only works very roughly in Scaler, didn’t improve things. Dragging and dropping into Cubase produced different velocity values again.
After restarting Cubase, Scaler forgot the key.
Using multiple scaler instances can cause problems in some circumstances.
But if you recreate everything in a new, empty Cubase project, everything works perfectly.
You can specify a default velocity value in Scaler’s settings which dictates the velocity at which chords are previewed using the mouse and for chords added to the main track. This should be working as expected when dragging chords from the Explore page and be retained when dragging chords to your DAW in Scaler v3.1.1. So please confirm that this is the version you are currently using.
Note there will also be a v3.1.2 update released quite soon with a variety of improvements including some related to velocity so hopefully this will further improve your experience using Scaler 3.
Would you mind clarifying what you are describing here? These are not issues I am aware of in the current Scaler v3.1.1 release.
Yes, I’m using version 3.1.1. - The latter issues occur when there are multiple Scaler instances in the Cubase project. I always run into problems with that sooner or later! I always work with complex projects.