When I set the Voice grouping on in 3.12, the velocity is inhibited . I cant play at full velocity no matter how hard I hit a key. In version 2 of Scaler this is working fine. If I click on the chord itself it plays at full velocity. I’m almost giving up on V3 because of bad UX and bugs.
EDIT - Actually the Voice grouping sounds completely different from V2 to V3. Like wildly different. Somethings gone badly wrong at your end.
Yes. This bug is really annoying… and still don’t fixed 
There’s no bug here. Many users have requested that Default Velocity be applied to any dragged chords. If you’re default velocity is set to 20 for example, dragging to Section C will give you a max velocity of 20!
So I am assuming this is your issue. Remember Scaler 3 is different to Scaler 2, there is now a standard velocity control be it in Arrange Page MIDI editor or Default Velocity.
If I am misunderstanding please let me know.
I’m not dragging anything, I’m playing from a keyboard.
“I cant play at full velocity no matter how hard I hit a key. In version 2 of Scaler this is working fine. If I click on the chord itself it plays at full velocity. I’m almost giving up on V3 because of bad UX and bugs.
EDIT - Actually the Voice grouping sounds completely different from V2 to V3. Like wildly different. Somethings gone badly wrong at your end.”
Hey @foxrobinson909 No need to duplicate post. I read your first post and I am none the wiser as to what your issue is. Please give me exact steps to try and figure out what you are doing and what’s causing your confusion. Also read my post and try and adjust your default volume. Happy to try and help you but let’s keep the tone nice and positive please.
Hi @foxrobinson909 @Alexander . We have looked into this further and found an issue regarding voice grouping and velocity which we believe you are describing here.
For clarity, the default velocity as set in Scaler’s settings determines the velocity at which chords from sections A and B are previewed when clicking with the mouse. This is also the velocity which chord’s assume when dragged to the main track.
The intended behaviour is that when triggering bound chords via MIDI, the default velocity (or for main track chords the velocity programmed into the chord) determines the maximum velocity.
The issue we noticed is when clicking on chords in section A, the velocity drops substantially once voice grouping is enabled. Or if chords from section A are dragged to the main track, triggering these chords via MIDI with voice grouping enabled substantially reduces the maximum velocity. This does not appear to be the case with chords from Section B and is specific to section A chords.
We have now lodged this as a bug to be addressed as quickly as possible, so many thanks for reporting your findings here.
Thanks Tristan. Good to know it’s not just me doing something wrong.
Perfect! Thank you very much! Waiting the update!
May I kindly ask for this fix to be made a priority? It seems like a rather small bug to iron out, but as long as it’s there, it pretty much renders voice grouping useless (at least for me).
Btw.: Seeing this bug in action in the official YouTube tutorial made me question whether that’s actually intended behavior. I’m glad it’s not 
Welcome to the community @Barret and thanks for being kind!
The bug is fixed and we are moving to beta testing 3.1.3 along with some other quirks we improved. I’d imagine we will release it within seven days! From there, we are steamrolling into 3.2 - a major update with some really cool features we’re excited to share.
Hi @Barret , I came here to post a bug I found, I don’t know if it will be solved too. It’s not with voice grouping, it’s when I use performance.
Will it be solved with the future update too? Or do I make another post?
Thank you!
Hi @Ariakan Thanks for posting that always makes ti easy for us when a user shows a clear example. That is not happening for us in 3.1.2 - Can you please download 3.1.2 from your ‘My Products’ page at scalermusic.com and restart your machine and launch a vanilla session and try again?
I just installed 3.1.2, and I’m having the same issue in FL Studio (the latest version).
In standalone, it’s hard to say. It feels like it happens with some performances and not with others, but I’m not sure, so probably not.
Hi @Ariakan Strange. Scaler 3.1.3 is out on Thursday (October 2nd) so please install that and let us know if it resolves the issue!
Hi! I tried, and it’s fixed now! 
Thank you!