8b12
Bug or feature?
I'm getting some stuttery effects when I automate the amount knob of the groove pool.
It can sound very cool, that's why I ask Bug or feature.
My test was with some kicks and e 16th note hihat. Then you can hear very clearly that its not fluent, can be cool as said. but i was expecting something else.
Maybe I'm wrong expecting it more fluent, then I have stumbled upon a nice way to make freaky fills
If this is a bug, I like it as a feature, maybe call it a midi Jitter parameter
djod
[amo] Timing inconsistency when changing groove amount fast.
[amo] Timing inconsistency when changing groove amount fast.
Last edited by djod on Sat Feb 21, 2009 2:28 pm, edited 1 time in total.
Tested some more and this can't be a feature, but It can have a nice effect.
Put amount to 100%, Try an Mpc swing and set the quantize to a 1/8Ts, play a 16th notes sequenced hihat and tweak the timing and the quantize (please make them it automatable (also the random and velocity) These changes are fluent. Now play with the amount knob and it start to jitter or stutter.
Put amount to 100%, Try an Mpc swing and set the quantize to a 1/8Ts, play a 16th notes sequenced hihat and tweak the timing and the quantize (please make them it automatable (also the random and velocity) These changes are fluent. Now play with the amount knob and it start to jitter or stutter.
Re: [amo] Timing inconsistency when changing groove amount fast.
Hi,
This should have changed in some beta, please try in beta 17. Sorry if it broke something you liked, but there were CPU spikes related to the editing of the Timing slider.
Regards,
Amaury
This should have changed in some beta, please try in beta 17. Sorry if it broke something you liked, but there were CPU spikes related to the editing of the Timing slider.
Regards,
Amaury
Ableton Product Team
Re: [amo] Timing inconsistency when changing groove amount fast.
Hi,
I moved the thread away, assuming that it is not a problem anymore. Please open a new thread if you experience something similar again.
Regards,
Amaury
I moved the thread away, assuming that it is not a problem anymore. Please open a new thread if you experience something similar again.
Regards,
Amaury
Ableton Product Team