Hello.
When Play Quantize is set ON and NEXT BEAT I have to hit play somewhere between the 4th and 1st to the chord set starts on the 1st of the next bar witch becomes very difficult when bpm is over 90.
I would love the option to quantize to NEXT BAR.
In bind mode, if I select Articulation → Strumming and play the chords its sounds short even if I let the key pressed.
No sustained chords when strumming is selected.
Thanks.
Welcome to the forum @omarcianno
Have you tried locking to Chord Duration and setting making Chord Duration 4 beats? That should do what you want! (See attached).
And a Strum doesn’t sustain. That is the expected behaviour.
Hi David.
First then all, thanks for your reply. Im going to check the tip about chord duration.
Im no new to scaler and really love the plugin I use it very often sometimes to compose and sometimes just to play for fun and find interesting chord progressions.
About the Strumming implementation I really miss the V2 setup.
I tried the v2 and v3 side by side in Ableton and miss all the options that v2 have, like choose the direction (alternate, up, down, random) that is missing in v3 and find out that v3 don’t play the full chord.
Another thing, Humanize also acts weird to me when I chose Timing, it makes my chord barely audible.
Here is a video I took of the two thing:
Thanks in advance.
I got the same issue in Logic and Scaler 3, no sustain and we missed strumming direction. I didn’t find a solution, and officially no answer. I hope there will be support on this point…
It certainly makes sense in Playback mode, but this setting doesn’t change anything in Live mode… There is clearly a lack of a setting for this mode, as it was in Scaler 2 !!
Oh @omarcianno thanks for the video that is really helpful!
OK so you can change Strumming direction in the Arrange page see attached.
But you have alerted us to two bugs!
This does not solve the problem when playing in Live mode, which is demonstrated in the video of omarcianno, this is only valid with the use of playback mode.
Thank you anyway 
Thanks @Tempo Understood. Both of these are occurring in Live mode and will be fixed with 3.1. hope to get this to you in mid April.
Thanks @davide for your fast reply.
So glad to contribute with the debug task.
I’m aware that in arrange mode there is the option you mention, but I really miss it on the playback mode.
I wish you keep all these really lovely features you have in v2 on v3.
Don’t get my wrong, I think stand alone is cool and being able to load your sound and FX is really cool as arrange mode is a step forward but don’t take away the old good workflow v2 already have.
Kind regards!
Thank you very much for your responsiveness David, I look forward to the update …With perhaps the idea that this feature is separate from Playback mode, for faster access. In the meantime, for use in live mode, I continue to use version 2.
That is all coming soon!
Description:
When recording MIDI using bound keys in Scaler 3, the generated MIDI data is not accurately capturing the timing and velocity humanization of the performance. I have tried dragging the recorded MIDI to a pattern in FL Studio as well as exporting the recording to a MIDI file and importing into a pattern. The issue occurs either way. Specifically:
The MIDI notes are being recorded with incorrect lengths, resulting in chords playing back at a slower tempo than intended. I already verified the Scaler 3 tempo/time sig match the DAW.
Velocity humanization is not being captured, resulting in MIDI notes with uniform velocities instead of the nuanced, dynamic velocities expected from a human performance.
Steps to Reproduce:
Set up bound keys in Scaler 3 and record a MIDI performance using FL keys.
Record the MIDI data using Scaler 3’s MIDI record functionality.
3a. Drag the MIDI using Scaler 3’s MIDI drag into a pattern in FL Studio, OR
3b. Export recording to a MIDI file using Scaler 3 then import into a pattern in FL Studio.
In both of the above cases, the chord lengths do not match the timing they were played in. It’s possible to scale the MIDI in the FL studio piano roll, but it doesn’t seem to always be to the same scale. The uniform velocities occur in both of the above test cases as well.
I’m running FL Studio v24.2.2.
Are there any specific Scaler 3 settings I should be checking to ensure MIDI is being exported correctly when recording → exporting/dragging?
