Who wants Ableton Live´s Groovepool in Bitwig

[Greenstorm33]

Really hope something like the groove pool is coming sooner rather than later. Definitely my number one most desired feature.

[billcarroll]

Wouldn't be upset to have it. I also really like the way Studio One handles it as well.

[reeloy]

....with no doubt...something similar to abletons groove pool AND some direct audio to midi/further pitch detection functions are pretty much all that's left to miss.....

[mosska]

i really hoped for it to appear in bitwig 4.

[_leras]

Really hope something like the groove pool is coming sooner rather than later. Definitely my number one most desired feature.

I'm sure something like this is in the works. I'm also sure they'll do something better than Live.

[OdoSendaidokai]

Im sure they did the first step with the Seeds . A pool to save values. Maybe we will get the Groove Seeds

[aer72]

Since the introduction of Bitwig 4.0 beta, I feel like a groove "operator" with some random elements in addition to a fixed groove.

[_leras]

I could go either way honestly.

If you have a drum clip and want to apply a different groove to your hi-hats and your snare then note-based would be nice. However you could also split your drums into different clips for different grooves.

I'd rather be able to apply the groove per drum lane then. Or yeah, just split the drum clip out.

I think per clip is best. You can indeed split out high hats if you want a different groove on them.

I hope this is in 4.1

[_leras]

Since the introduction of Bitwig 4.0 beta, I feel like a groove "operator" with some random elements in addition to a fixed groove.

I also think this is how it will play out. It could be really good and make it a very visually aided process.

If it is this way, lets hope it plays out well.

[SLiC]

Reason has a pretty unique and interesting regroove mixer, steal from everyone don't just copy Live!

[pdxindy]

Since the introduction of Bitwig 4.0 beta, I feel like a groove "operator" with some random elements in addition to a fixed groove.

I also think this is how it will play out. It could be really good and make it a very visually aided process.

If it is this way, lets hope it plays out well.

Operators are applied per note. That doesn't makes sense for groove. Even groove per clip would be annoying when I want a whole track to have the groove and I have to apply groove to all the individual clips. I would rather just be able to apply groove to a track.

[_leras]

Since the introduction of Bitwig 4.0 beta, I feel like a groove "operator" with some random elements in addition to a fixed groove.

I also think this is how it will play out. It could be really good and make it a very visually aided process.

If it is this way, lets hope it plays out well.

Operators are applied per note. That doesn't makes sense for groove. Even groove per clip would be annoying when I want a whole track to have the groove and I have to apply groove to all the individual clips. I would rather just be able to apply groove to a track.

well... ultimately groove is applied at a per note level. but I totally agree it's usage is at a higher level, clip or maybe track. though for me being able to change up the syncopation between sections is something I'd want to be able to do.

[pdxindy]

well... ultimately groove is applied at a per note level. but I totally agree it's usage is at a higher level, clip or maybe track. though for me being able to change up the syncopation between sections is something I'd want to be able to do.

Yeah, from a workflow perspective, I can select 30 clips on a track and apply a groove to them all. Then maybe take a couple clips and change it.

Or I can select the track and apply the groove to it. Then select a couple clips and move them to a second track with a different groove.

In the first clip based approach, I need to keep track of which clips have which groove applied as I move them around, swap clips and so on. I would find that more fiddly and would take more mental attention. It would be flexible but not as straightforward workflow wise.

Track based means it is easier to keep track of (pardon the pun). Visually, any clips on the track I know what groove is applied without having to select clips and look in the inspector. It is also easier to swap grooves, make a duplicate track, apply a different groove and mute tracks to compare and so on.

Track based appeals to me more, but I would adjust to a clip based approach as well.

[jcolyer0620]

+1

[lokanchung]

For per notes groove, groove based quantization can be a option too. Also, it would be useful to set grid lines to follow grooves.