PreSonus Forums

Groove quantize is destroying velocities

Please enlighten me if I'm missing something.
Velocity slider does nothing

Makes groove quantize pointless (for me)

2016 - 2017
viewtopic.php?f=151&t=17667
viewtopic.php?f=213&t=18585

Edit: got a freeze/Q/restore velocity macro working, but that a workaround after 5 years is still necessary....

You're not missing anything, but the forums aren't really that great for getting older issues fixed. Maybe try socials then follow up with a Support ticket?

Thanks for confirming.
Moved on to some other DAW because of the constant S1 bugs, giving S1 another try.
Will do socials. Ticked is probably a waste of time for a 5 year old known bug, but will give it a try

I would link to this thread on the studio one discussion thread as well. That does get read by Presonus as far as I can see.

Done!

Hi, Robert,


We have been able to reproduce what you have reported to us and have passed this along to our QA Team for their investigation. Should this issue be addressed in a future build of Studio One, you will see it in the release notes for that build.

(hope for the best)

Fixed in 5.2.1?

Nope....

I don't understand why I don't have this bug!
Maybe Mac / PC? ....

patricemazmanian wroteI don't understand why I don't have this bug!
Maybe Mac / PC? ....

Except in the first half of your example video, the velocities are NOT preserved? Look close. The Notes themselves shift slightly to match the groove bend markers. But the original note velocities all shift one step to the left. Sure their relative heights are unchanged compared to before, but now every note has the velocity that was originally assigned to the NEXT note in the sequence.

To see this, look close at the 2nd note in your example. It's a yellow-colored note at A#2. When you apply the groove, the note itself shifts slightly to the right. But it's associated velocity completely jumps over to the FIRST note in the pattern (the G2). Literally ALL of the original velocities jump one note to the left from their original position.

I've verified this on my own system (in 5.2.1). The behavior is consistently 100% repeatable, unexpected, and wrong.

User expectation is that note events would shift to the nearest bend marker in the groove grid, and the original velocity attached to each note would correctly move WITH its original note.