Serious drum quantizing

trackmixstudio

Recorded these guys over the weekend.
Took about 3 hours a song to edit/quanitze the drums.
Make sure your volume is set low before clicking the link :-)
http://dl.dropbox.com/u/2133088/05%20Decadence.mp3

PaulBrewer

trackmixstudio wrote: »

Took about 3 hours a song to edit/quanitze the drums.

Is that good or bad Track ?

petermaher

trackmixstudio wrote: »

Recorded these guys over the weekend.
Took about 3 hours a song to edit/quanitze the drums.
Make sure your volume is set low before clicking the link :-)
http://dl.dropbox.com/u/2133088/05%20Decadence.mp3

Tourette's????:P

trackmixstudio

Your average rock band would take me about 30 minutes per song.
This track has a 16 time snare blast in the middle with kicks between the snare blasts.
Most fast metal stuff takes about 3 hours per track depending on how much double kick there is and how tight the drummer is.
The real time killer is when the drummer is doing triplet time double kicks.
1 and a 2 and a 3 and a 4 and a.... at 180bpm!!!. Straight 16s (1 and 2 and.. are much easier and faster to edit.
The main problem being that the 1 count alternates between the 2 bass drums every measure and if the kicks don't land exactly on the snare hits (rarely) you have to quantize the kicks separately to the rest of the kit and high pass the overheads so the original kicks aren't audible in them.
Modern metal stuff is very quantized straight to the beat with zero swing.
I see logic's flex edit window in my sleep:p

PaulBrewer

What you want is Beat Detective !

trackmixstudio

PaulBrewer wrote: »

What you want is Beat Detective !

Logic's flex edit in slicing mode IS beat detective. Detect transients then move to grid.
The problem with fast metal stuff is that drummers tend to be more than a 32nd beat out on the fast stuff so in the song I posted you could not quantize to 32nd beats because he wasn't tight enough and also had lots of kick/snare flams during the blast. 16th double kicks with snares between the kicks as in this song = 32nd beats. 32nd beats at high tempo is very hard for even a good drummer to get very tight. Quanitizing automatically tends to leave you with lots of errors. The only way to do it is to quantize snares then manually fix any errors where hits have been move to the wrong interval then once that is done go and do the kicks. Also many metal drummers rush rolls and land WAY ahead of the beat so you have to manually fix each hit on every roll so it lands back on the one count.
There is no easy way to do this music. The best way is to let the computer have a best guess at it then fix everything manually.

woodsdenis

PaulBrewer wrote: »

What you want is Beat Detective !

Elastic Time is much better, Phase coherent Drum quantizing etc. Logics flexitime is their version of this.

MilanPan!c

trackmixstudio wrote: »

Logic's flex edit in slicing mode IS beat detective. Detect transients then move to grid.
The problem with fast metal stuff is that drummers tend to be more than a 32nd beat out on the fast stuff so in the song I posted you could not quantize to 32nd beats because he wasn't tight enough and also had lots of kick/snare flams during the blast. 16th double kicks with snares between the kicks as in this song = 32nd beats. 32nd beats at high tempo is very hard for even a good drummer to get very tight. Quanitizing automatically tends to leave you with lots of errors. The only way to do it is to quantize snares then manually fix any errors where hits have been move to the wrong interval then once that is done go and do the kicks. Also many metal drummers rush rolls and land WAY ahead of the beat so you have to manually fix each hit on every roll so it lands back on the one count.
There is no easy way to do this music. The best way is to let the computer have a best guess at it then fix everything manually.

Why not just sample the kit and then sequence the drum bits?

It's not like a drummer would notice?

ZV Yoda

MilanPan!c wrote: »

Why not just sample the kit and then sequence the drum bits?

It's not like a drummer would notice?

You're not a drummer yourself then?

Of course the drummer would notice!... it's obvious to any drummer whether or not it's their own performance on tape.

Now, whether or not they choose to draw attention to it?... well that's another story entirely...

PaulBrewer

woodsdenis wrote: »

Elastic Time is much better, Phase coherent Drum quantizing etc. Logics flexitime is their version of this.

Word on the (Nashville) street is Serato and Waves Soundshifter is much superior again sonically.

MilanPan!c

ZV Yoda wrote: »

You're not a drummer yourself then?

Of course the drummer would notice!... it's obvious to any drummer whether or not it's their own performance on tape.

Now, whether or not they choose to draw attention to it?... well that's another story entirely...

Yeah, it was a joke.

woodsdenis

PaulBrewer wrote: »

Word on the (Nashville) street is Serato and Waves Soundshifter is much superior again sonically.

For stereo files maybe, you cant quantize 10 tracks of live drums with them.
Try Elastic Time on a whole kit, its brilliant. Cymbals are the only iffy one with time stretching. Most PT users use Elastic Time over Beat detective these days for whole kits, much easier and quicker. Even with loops, changing the feel etc is great. Serato just speeds up/down doesn't it.

progsound

Slip editing ftw Although it still takes ages when im editing metal drums to grid :mad: 3 hours aint that bad tbh