I know that the beat detective / slip edit / whatever has been gone over a thousand times on here. I just think this has some value for people. I'm in protools 10 so I can multitrack beat detective if i want, but i find this better. These ideas can always be applied to any DAW.
1. Determine what drum hits you want to quantize to. In most metal projects that I don't want super robotic I use the kick and snare. Feel free to use the tom hits as well.
2. If im rolling most of the lows out of the overheads i tend to do the kick separately from the rest of the kit.
3. This is the key. I want to now make a "guide track". This will be made up of the hits i want to quantize to. In this example i will do the kick and snare together.
4. The next step has nothing to do with sound/tone. Apply a transient designer on the kick drum, and one on the snare. All we are doing here is exaggerating the transient so that beat detective will find them easier. Also try to keep the level between the kick and snare close. You can also put a gate first if trying to keep ghost notes and small hits out.
5. Bounce/Record/Print the kick and snare to a new track. This is the guide track.
6. Now using Tab to Transient or Beat Detective begin to slice up the guide track.
7. Group the drums together so the edits affect all the drum tracks as a whole. Also be aware that you don't want any breaks/gaps in the regions of the drums. (except the guide track)
8. Turn off Tab to Transient. Now when you press tab you will go the regions instead. This will now take us to every transient in the guide track. In Keyboard focus mode hit Tab, B, Tab, B, Tab, B throughout the track. OR Use Beat Detective Region Separation. Both have advantages. Some will argue that beat detective has the Trigger Pad option to allow the cut to be ahead of the transient. Just remember that now we are quantizing the region start not the transient. If the pad is 10ms when all said and done just nudge everything back 10ms when done. Just to be weird for some reason I use 6ms trigger pad and a 3ms crossfade time.
9. Now you can Hard Quantize (cmd 0) or use beat detective and quantize all the parts.
10. Using beat detective smoothing to fill and crossfade (people tend to use the default 5ms). If using Beat Detective to separate some people will say the crossfade time should be half of the trigger pad time.
This has been gone over before but I thought the Guide track and transient designer idea was very helpful.
I hope someone gets something from this.
1. Determine what drum hits you want to quantize to. In most metal projects that I don't want super robotic I use the kick and snare. Feel free to use the tom hits as well.
2. If im rolling most of the lows out of the overheads i tend to do the kick separately from the rest of the kit.
3. This is the key. I want to now make a "guide track". This will be made up of the hits i want to quantize to. In this example i will do the kick and snare together.
4. The next step has nothing to do with sound/tone. Apply a transient designer on the kick drum, and one on the snare. All we are doing here is exaggerating the transient so that beat detective will find them easier. Also try to keep the level between the kick and snare close. You can also put a gate first if trying to keep ghost notes and small hits out.
5. Bounce/Record/Print the kick and snare to a new track. This is the guide track.
6. Now using Tab to Transient or Beat Detective begin to slice up the guide track.
7. Group the drums together so the edits affect all the drum tracks as a whole. Also be aware that you don't want any breaks/gaps in the regions of the drums. (except the guide track)
8. Turn off Tab to Transient. Now when you press tab you will go the regions instead. This will now take us to every transient in the guide track. In Keyboard focus mode hit Tab, B, Tab, B, Tab, B throughout the track. OR Use Beat Detective Region Separation. Both have advantages. Some will argue that beat detective has the Trigger Pad option to allow the cut to be ahead of the transient. Just remember that now we are quantizing the region start not the transient. If the pad is 10ms when all said and done just nudge everything back 10ms when done. Just to be weird for some reason I use 6ms trigger pad and a 3ms crossfade time.
9. Now you can Hard Quantize (cmd 0) or use beat detective and quantize all the parts.
10. Using beat detective smoothing to fill and crossfade (people tend to use the default 5ms). If using Beat Detective to separate some people will say the crossfade time should be half of the trigger pad time.
This has been gone over before but I thought the Guide track and transient designer idea was very helpful.
I hope someone gets something from this.
