10 posts
Page 1 of 1
Groove quantize is destroying velocities :shock:

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....

MacMini M2 Pro
Memory: 16 GB
OS X latest version
Apollo X6 Thunderbolt
Studio One Pro latest version

https://open.spotify.com/album/5DQ0uQnTPGAQH4rmaNboE8?si=DH54HeplSO2hVxPFLmUVNQ
User avatar
by robertgray3 on Sun Apr 18, 2021 7:49 pm
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?

Mac OS X Catalina 10.15.7
Mac Pro 6.1
3 GHz 8-Core Intel Xeon E5
32 GB 1066 MHz DDR3
Dual AMD FirePro D500 3072 MB
Quantum 2
User avatar
by Robert Johnson III on Mon Apr 19, 2021 3:24 am
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

MacMini M2 Pro
Memory: 16 GB
OS X latest version
Apollo X6 Thunderbolt
Studio One Pro latest version

https://open.spotify.com/album/5DQ0uQnTPGAQH4rmaNboE8?si=DH54HeplSO2hVxPFLmUVNQ
User avatar
by PreAl on Mon Apr 19, 2021 10:02 am
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.

Intel i9 9900K (Gigabyte Z390 DESIGNARE motherboard), 32GB RAM, EVGA Geforce 1070 (Nvidia drivers).
Dell Inspiron 7591 (2 in 1) 16Gb.
Studio One Pro 6.x, Windows 11 Pro 64 bit, also running it on Mac OS Catalina via dual boot (experimental).
Presonus Quantum 2626, Presonus Studio 26c, Focusrite Saffire Pro 40, Faderport Classic (1.45), Atom SQ, Atom Pad, Maschine Studio, Octapad SPD-30, Roland A300, a number of hardware synths.
User avatar
by Robert Johnson III on Mon Apr 19, 2021 10:51 am
Done!

MacMini M2 Pro
Memory: 16 GB
OS X latest version
Apollo X6 Thunderbolt
Studio One Pro latest version

https://open.spotify.com/album/5DQ0uQnTPGAQH4rmaNboE8?si=DH54HeplSO2hVxPFLmUVNQ
User avatar
by Robert Johnson III on Tue Apr 20, 2021 4:07 pm
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)

MacMini M2 Pro
Memory: 16 GB
OS X latest version
Apollo X6 Thunderbolt
Studio One Pro latest version

https://open.spotify.com/album/5DQ0uQnTPGAQH4rmaNboE8?si=DH54HeplSO2hVxPFLmUVNQ
User avatar
by PreAl on Tue Apr 27, 2021 3:29 pm
Fixed in 5.2.1?

Intel i9 9900K (Gigabyte Z390 DESIGNARE motherboard), 32GB RAM, EVGA Geforce 1070 (Nvidia drivers).
Dell Inspiron 7591 (2 in 1) 16Gb.
Studio One Pro 6.x, Windows 11 Pro 64 bit, also running it on Mac OS Catalina via dual boot (experimental).
Presonus Quantum 2626, Presonus Studio 26c, Focusrite Saffire Pro 40, Faderport Classic (1.45), Atom SQ, Atom Pad, Maschine Studio, Octapad SPD-30, Roland A300, a number of hardware synths.
User avatar
by Robert Johnson III on Tue Apr 27, 2021 4:50 pm
Nope....

MacMini M2 Pro
Memory: 16 GB
OS X latest version
Apollo X6 Thunderbolt
Studio One Pro latest version

https://open.spotify.com/album/5DQ0uQnTPGAQH4rmaNboE8?si=DH54HeplSO2hVxPFLmUVNQ
User avatar
by patricemazmanian on Wed Apr 28, 2021 4:18 am
I don't understand why I don't have this bug!
Maybe Mac / PC? ....

Image

S1 pro 6 -Vienna Ensemble Pro - Melodyne - Notion 6 - Win10 - jBridge 1.65 - Motherboard ASUS Z87-K - i7 4770K 3.5Ghz, 32 Go RAM - GeForce GT 610 1024MB - Audio interface RME Hammerfall multiface II - Faderport - ADAT Interface Focusrite Scarlett OctoPre - EWQL hollywood-orchestra...
User avatar
by Baphometrix on Wed Apr 28, 2021 7:11 am
patricemazmanian wroteI don't understand why I don't have this bug!
Maybe Mac / PC? ....

Image


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.

Studio One 5.2.x Pro (Sphere) | Bitwig 4.x | Ableton 10.x
Faderport 8 | ATOM SQ | MOTU M4 | Windows 10 | i9 9900K | 64 GB RAM | Geforce RTX 2070

10 posts
Page 1 of 1

Who is online

Users browsing this forum: donaldbaarns and 42 guests