How do Beat Detective with Cubase (tutorial) ¯\(°_o)/¯

Kazrog

Kazrog, Inc.
Mar 6, 2002
5,540
17
38
California
kazrog.com
Check out what I found doing a bit of Googling today:

Link: http://www.clubcubasenashville.com/PAGES/TIPS_&_TRICKS.htm

¯\(°_o)/¯

Some of this is a bit redundant and wordy if you're experienced with Cubase, and if you have auto crossfades on, then obviously you don't have to worry much about that step. That being said, the technique of creating a guide track to do your group region slicing is great! :cool:

Full text:

------------------------

Well, I knew that if we talked about this topic at the Nashville Club Cubase/Nuendo that we would come up with some even better tips for editing multitrack drums... and we really did. Below is a step by step method for lining up drums to a grid. Now... before you say... WOW!! Look at all those steps... Why can't we just have Beat Detective, I must ask: "Have you really used Beat Detective?" I have. And using the methods below, there are less steps, and it is faster. Really. It sounds a LOT better too! It looks like a lot, because I have written it in great detail... however... it's not. And once you get the hang of it.... you will be overjoyed at how fast you can ACCURATELY line up drums to a grid (in Cubase SX and Nuendo 2.0 ANY grid... even one generated by a groove quantize derived from a drum loop, any other audio file, or your own swing setting made in the quantize setup... !!).
For this example, we are going to assume the drums were cut to a sample accurate click track that matches the tempo in Cubase/Nuendo. I will get into tempo matching at a later date... this is all I could get to today.

1. Create a Folder Track (for SX and Nuendo 2.0 users), and put all drum tracks in the folder.

2. Solo the parts you want to base your fixes off of (kick, snare, toms, perhaps the HH if you REALLY want to get serious)
icon_smile.gif


3. Export the soloed tracks to a new track (again, kick, snare toms only).

4. Now, put the exported track right above your folder track.

5. Highlight the newly exported track, right click on it and select “detect silence” (audio>detect silence).

6. Set your minimum opening time to the lowest setting… 1ms, and adjust your open and close threshold so that only the hits are getting through, and then compute (leave all other settings at the default). You should now have only the hits (snare, kick, tom) highlighted in blue. Process.

7. Now in the arrange window you will see that each hit has been cut out visually. I personally highlight all those parts now and drag the length of one of the clips to the right a little (which will adjust them all the same amount) so that there is some space between the beginning and end of each clip!

8. Now, we make our snips! Turn on the snap on the arrange window, and set it “Events”.

9. Now select the scissor tool. As you glide the scissor tool over your drum folder track below… you will see that it’s cut point indicator SNAPS to the beginning (and end) of the Hits in the exported audio track we made!! So, you can now easily go through the folder track and make snips at the beginning of each hit which will apply to ALL the drums in the folder (or group in Nuendo)! No guessing, no zooming. (If you are using Nuendo 1.x and you don’t have a folder track, you just group the drum tracks “cntrl-g” so that all cuts will be made simultaneously to all the drum tracks). Using this method you can quickly slice up a verse, a chorus, or the entire song if you need to.

10. Now that all your slices are made… here comes the fun part. As stated above, we are assuming for this example that the drums have been cut to a click track and that track is equal to the tempo of the song. So, select the grid that you want all the hits to be lined up with. Let’s say for ease of understanding…. Just straight 16th notes on the grid. So at the top of the arrange window, leave “snap” on, and change it back to “grid”, “use quantize” and then 16th notes in the quantize amount. Now, just highlight your folder track (or drum group) and type “Q” on the keyboard! Voila!! All your clips just quantized to the nearest 16th note!! You are done lining up your drums! Now remember, in Cubase SX and Nuendo 2.0 you can use hitpoints to generate your own groove quantize. Soooo. If you had a loop the drummer was “supposed to be playing to”, you could use that loop to create your groove quantize. Then, instead of setting the grid to snap to straight 16th notes, you set it to snap to the groove quantize you created. Then, when type “Q” all your drum snips will snap to THAT grid!! It’s a beautiful thing.

11. So… what about those gaps and overlaps that are now all over my drum track you say?? After a lot of research and futzing around with it… I have indeed discovered that crossfades are the way to go. Using the crossfades in Cubase SX/Nuendo are amazingly transparent! Simply highlight all the audio (you can’t highlight the folder this time, you have to highlight all the actual drum tracks) and type “x” on the keyboard. It will create crossfades for the overlaps… AND GAPs. How does it do this? It’s complicated, but basically for gaps… it pulls the length of the file over to the right (using the original part) so that it overlaps the part to it’s right. Then it crossfades them. This CAN create double hits! So, you have to mess with your crossfades.

12. To “mess with your crossfades”, with all the audio still highlighted, click on one of the crossfades (represented now by a big X between the two parts). The crossfade dialog box will open up. I have found the best starting place for drums crossfades is for the part on the left to fade our almost immediately, and the part on the right to fade in immediately after it. That will make about 97% of your crossfades fully transparent. Expirament with this, once you get it just the way you like it… save it as your default (click “as defult") in the crossfade window)! Now, next time you hit the “X” it will use your default. You can add multiple crossfade presets as well!

13. Now listen to your track. If you hear any strange double hits, clicks, or anything that doesn’t sound perfectly natural…. Adjust your crossfade right at that spot until it goes away. Again, once you get your stock crossfade preset right, you won’t have many of these.

14. Now you are pretty much done! Doesn’t that drum track sound better now?? As you have done this… you may have discovered that computing all these crossfades is pretty intensive work for your computer. Because of that you may want to do the song in sections, depending on how powerful your computer is. When you are done, I highly recommend bouncing those tracks to a new track so your computer is not constantly working to calculate the crossfades. (right click file, then audio>bounce selection…. Replace? Yes).

15. Be sure to save your project with a new file name at each step so that you can go back to any given point.

16. Hey…. You are done…

--------------
 
Sorry to skew from Beat Detective. Have been thinking about this for a while about crossfading.

Is this how most engineers use crossfade to connect intricate guitar rhythm parts down to the 16th or 32nd note during tracking?

Especially for technical or death metal material that do not seem to have any breaks and stops during transitions from section to section in the song. It sounds flawless without any audio pops of overlapping takes.

It seems almost impossible to have one long passage done in one take. In order to get it super tight, perhaps these guys record it riff by riff and apply crossfading?
 
similar to what I did.
make sure to grab all the fades and move them a bit to the left, reduces fucked up transients (equivalent to trigger pad on BD).
I also created a macro for most of the steps (next event-slice-next event).
In the end I was as fast as anyone with BD I dare say but you still can only quantize 100%=sucks.
you can add 2 extra steps to get iterative quantize (convert to midi, iteratively Q midi...use that as reference for Q audio) but that's just a major PITA.
 
The cut seems to be too long of a portion (i.e. there is noise before the hits and too much after) and I'm having trouble getting it to work out. Just sounds like a phasey mess. I'm new to this whole drum editing thing.
 
Shane: If you are already doing this technique can you make a Jing video (or similar) so we can see this in practice? I'll have a look at the steps when I get home but a picture, as they say, is worth a thousand words.
 
PURE GOLD! :worship:
We can haz sticky? :rolleyes:

I came across that several months ago but didn't try it right away and forgot to bookmark. After that I couldn't find it anymore. :loco:
Plus it's way more comfortable to read here due to the darker background. :)
 
Lasse: you still have Cubendo?!? That's cool if you do! Check this out if you want to make a FREE screen capture video (limited to 5 minutes). It saves as a .swf, but if you just simply put it on a server it will play in FireFox on it's own when you link it. It is completely free and I have used it a few times to help friends out on AIM with Cubase stuff - MUCH easier than typing it out lol. Oh and yes, it's Mac compatible.
 
I just did a few tests and it really works great. At least on rather eays drum parts. I haven't gotten into the more complicated stuff yet.

One thing I've discovered: When detecting silence a Pre-Roll of around 12ms works way better than the standard 30ms.

Lasse: How did you set your X-Fades? Thanks.
 
I'm hoping Lasse or Shane can make a video using the software I linked so we can watch how it's done rather than read!
 
I've only been using Cubase for a few months, and I'm loving it, but I'm still learning some of the finer points of the program. Before that, I was using Digital Performer and Pro Tools for years. Any time I had anything to do with real drums, I'd run Beat Detective, and I haven't had to deal with real drums in a long time.

I have a couple of projects coming up where I'm going to be producing bands with real drums, and I'd like to resist the urge to go into Pro Tools, because I am so much happier in Cubase in every way. I will be experimenting with this technique, and see where it leads me, and I may post a video also, but Lasse will probably beat me to it.