i dont think changing Scaler 3 UI velocity settings works in the Main Track C section. i say don’t think in case I’m doing something wrong. but it works in the A and B sections
The reason we can’t have UI Velocity affect the main track is that would override all the velocity settings for each chord and volume controls. It just wouldn’t work. So as you pointed out triggering via MIDI you can use your own performance velocity but we want users to adjust the chords via the mixer/velocity.
Another good way to handle this is to use the chord follow track for the Chord volume and use the main track with ‘chord mute’ on to output only the keys lock volume.
We will be making the main track chord velocity default to 87 on mouse click as users are finding it too loud (fair enough it is currently defaulting to 127!)
1 Like
thank you. yeah it is currently way too loud.
1 Like
@davide Can I suggest you use the UI Velocity value as the default velocity for the notes on the main track or have another setting in the preferences for UI Main Track Velocity.
I would suggest a lot of users click the UI to preview chords, and it would be nice to be consistent between different sections of Scaler. Of course, this doesn’t prevent users changing the velocity of chords / notes in the main track to their own liking, it just makes the experience more consistent. At the moment you have to alter the main velocities manually to bring them down to a suitable level.
@r3coil But then clicking, binding and playing would result in different velocities. I would prefer to keep everything as 110 velocity by default and 99% of users won’t touch that default setting. ATM the issue is Scaler UI velocity is 110 and main track is 120.
@davide I am not entirely sure I follow you. If I understand Scaler correctly, you can already have different velocities for clicking (set via Scaler UI preferences), binding (played as per external midi instrument), playing (set via the individual chord / notes on the main track).
What I am suggesting is the default velocity for the chord / notes on the main track uses the UI Velocity in preferences. At the moment it is hard coded to 120. Users are still able to edit the chord / note velocities on the main track; it is just about setting the initial default value of the chord/notes on the main track to the UI Velocity in preferences.
110 is great..as long as everything is the same by default its great…Will we get any email when the update drops? Cause I never got any for the updates. I was on first version until recently. 
EDIT- but yeah like @r3coil said, why not make it so that UI velocity setting changes the Default velocity of the Main Track chords as well? User would still be able to change individual chords velocity in the arrange page as they do now. But only the Default velocity would be controlled by UI velocity setting.