Yep, overhauling the groove preset creation, audition and management system in Cubase is what I would consider to be a great new core feature for a future Cubase update.
It is currently very un-intuitive, scattered and clumsy.
Yes, great topic, cubase definitively need to update the groove pool.
Just to add a point to your list: what would be nice is a per project quantize panel list.
The problem now is that if you make a track with some swing in it and you create a quantize preset for it it just add into the quantize list with regular 1/8-1/16 presets that are useless in that situation, it make no sense. I would love to be able to say: for this track I only need 1/4-1/8 with swing lets say, and for this one 1/8 and 1/4 quintuplet, etc…
I think the architecture of the groove/quantize in cubase is way better than in ableton for example because the grid can actually reflect it but it just need some attention and little worflow tweaks from steinberg to get all the power from it.
I’m new to all this and am unfamiliar with groove presets but am looking for more flexibility in managing pattern bank presets. I have created a few pattern bank presets with my favorite drum beats. The pattern event pull-down selection menu works fantastic to quickly switch between up to 43 patterns, which seems to be plenty for my needs. After that the list doesn’t fit my screen, so rather than scrolling with the down arrow I find it better to switch to another pattern bank preset.
I would like to see more utility functions for organizing pattern bank presets. For example, the ability to:
change the order of patterns within a preset,
delete multiple patterns in one go,
copy patterns from one preset to another preset, and
export all patterns used within a project or track to a new preset.
I haven’t figured out my workflow yet, but so far to me it seems better to work with pattern events rather than export them to MIDI events. A down side is that only one pattern bank preset can be used at a time. So if my patterns are split across multiple presets, then the work-around is to use multiple VST drum track instances. The utility functions above would let me easily overcome that.
Please let me know if it would be better to make this a separate feature-request post.
Hi there! Bumped into this thread while looking for a solution to a somewhat similar problem.
Sorry if this just something I missed in settings – is there a way to make the Quantise Preset selection project-based, as opposed to it being a global setting? Say, if I have three tracks I’m working on, all with a different swing setting… when I switch between the sessions, I have to remember to switch the Quantise Preset before quantising.
So asking for a way to make Quantise Presets project-specific. Anyone know how to do this?