Groove template and pool

[pdxindy]

One of the most powerful groove tools would certainly be extracting groove from and existing loop or recording, and being able to apply it to a different midi (or even audio) part

That's what I would like in Bitwig... eventually

[_leras]

I'm hoping it's coming. I'm pretty sur with all the work on automatically completed it'd be a good time to implement something.

I wonder if they have a slightly complicated plan of how to implement it, with some kind of groove undo, or keeping track of edited notes.

I guess just apply groove and set back to full Q would be fine, it would make sense to have a 'set of grooves' used within a project available for quick reuse.

Anyway I have faith in them!!

[fwsuperhero]

I just watched this video


And there are some good points. One of them is that shuffle can be automatized. Is it something that groove-pools in other DAWs can do? Would it make sense to have smth like "apply groove" on top of click which would be a destructive operation but still keep global shuffle for more flexible options? WDYT?

[stamp]

Oooops ..

[stamp]

Extract grooves of imported loops should not be missing... Obviously.

[stamp]

I would Bitwig to implement a groove pool that we can apply per clip in inspector with possibility to choose type and strength(maybe even positive and negative), accent. The grid of said clip could adapt to the groove pool. And to make it the Bitwig add a new editing mode to already existing ones where you have markers like the ones in audio editing to shift the grid around and a lane like velocity lane where you can modify the accents levels for every grid subdivision to create your own grooves.

[bboxdw]

If Bitwig added the ability to analyze an audio clip and convert it to a curve file, according to user-defined characteristics (e.g., converting transients in the audio clip to peaks in the curve), many groove-related things would be possible, esp now that automation and modulation are more tightly integrated.

Add to that more options for manipulating curve files, such as being able to multiply one curve by another (at least some of the math for this should already be in the code for relative modulation), and even more possibilities open up. For example, you could take existing automation clips and manipulate them in different ways with your "groove" curve.

Given the foundation that's already being laid, the Bitwig way of implementing this functionality may end up being quite capable indeed.

[stamp]

If Bitwig added the ability to analyze an audio clip and convert it to a curve file, according to user-defined characteristics (e.g., converting transients in the audio clip to peaks in the curve), many groove-related things would be possible, esp now that automation and modulation are more tightly integrated.

Add to that more options for manipulating curve files, such as being able to multiply one curve by another (at least some of the math for this should already be in the code for relative modulation), and even more possibilities open up. For example, you could take existing automation clips and manipulate them in different ways with your "groove" curve.

Given the foundation that's already being laid, the Bitwig way of implementing this functionality may end up being quite capable indeed.

Envelope follower modulator does exactly that. You can't record the outcome without workarounds at the moment but it works realtime.

I appreciate your enthusiasm. My advice is to read the manual. It will be an eye opening experience. Bitwig has a lot of potential that is not quite visible by just glancing at it.

[bboxdw]

Envelope follower modulator does exactly that. You can't record the outcome without workarounds at the moment but it works realtime.

I appreciate your enthusiasm. My advice is to read the manual. It will be an eye opening experience. Bitwig has a lot of potential that is not quite visible by just glancing at it.

Even after a decent amount of time reading the manual and release notes, I appreciate community for those things I inevitably overlook. And for pointing out new applications and workarounds I may have never considered. Bitwig indeed has a lot of potential that's not immediately apparent.

Yeah, given that envelope follower, onset detection, and detection functionalities in the spectral suite are already present, being able to "record" detected rhythmic or other traits of samples/clips as curves so they can be organized/queried/retrieved from the curve library is one of the only aspects missing.

[stamp]

Envelope follower modulator does exactly that. You can't record the outcome without workarounds at the moment but it works realtime.

I appreciate your enthusiasm. My advice is to read the manual. It will be an eye opening experience. Bitwig has a lot of potential that is not quite visible by just glancing at it.

 

Even after a decent amount of time reading the manual and release notes, I appreciate community for those things I inevitably overlook. And for pointing out new applications and workarounds I may have never considered. Bitwig indeed has a lot of potential that's not immediately apparent.

Yeah, given that envelope follower, onset detection, and detection functionalities in the spectral suite are already present, being able to "record" detected rhythmic or other traits of samples/clips as curves so they can be organized/queried/retrieved from the curve library is one of the only aspects missing.

 

Yeah, I would like that, too.
In the meantime lots of things we can do.
It's always nice to learn new stuff, hehe.
Have fun!

[Cyoon]

It's funny really, in the London based production classes I teach on Ableton and Logic Pro a lot of students are completely unaware that the groove feature is actually there or what it does, especially with Logic Pro. Maybe they're just used to ploddy beats

Sounds interesting, would be nice to know what you teach there, especially regarding break beats. Could you maybe be bothered to create a video on that?

[JoaCHIP]

I've been achieving odd grooves by automating the tempo, but there are a lot of draw-backs to doing this. For instance, tempo delays get very confused. I think this needs to be in the core of the DAW, rather than being added as a plugin.

And there are two things I hope they'll keep in mind if implementing this:
1) The "quantize" function should obviously follow whatever groove pattern you've selected.
2) The grid should also show the selected groove pattern (Studio One does this part wrong).

PS: If we get this, I'll add Bitwig to my groove pattern generator page: https://www.robotplanet.dk/audio/midi_g ... attern.php

[perpetual3]

I've been achieving odd grooves by automating the tempo, but there are a lot of draw-backs to doing this. For instance, tempo delays get very confused. I think this needs to be in the core of the DAW, rather than being added as a plugin.

And there are two things I hope they'll keep in mind if implementing this:
1) The "quantize" function should obviously follow whatever groove pattern you've selected.
2) The grid should also show the selected groove pattern (Studio One does this part wrong).

PS: If we get this, I'll add Bitwig to my groove pattern generator page: https://www.robotplanet.dk/audio/midi_g ... attern.php

The man, the myth, the legend from the depths of the Vault.

[JoaCHIP]

Indeed. Once every year I resurface to breathe and stay in contact with humankind.

[Razcar]

Kick 2/3
Bitwig Drummachine
Triaz
Sometimes battery and atlas to help browse samples
Additional samples placed directly in the arranger, which I later turn into bar length clips.

Are you me? My drum workflow in Bitwig is almost (-Battery) exactly the same

Anyway, another +1 for a groove feature. Miss the MPC groove templates from Logic Audio (yes I'm old)