lackluster strumming
Max Output Level: -86 dBFS
- Total Posts : 211
- Joined: 2008/12/27 17:20:43
- Status: offline
RE: Start Here using Audiosnap and Audio Snap with multi trk drums
2009/02/17 14:28:27
(permalink)
That is correct. Some of the most critical people i've met. Music snobs.(don't tell them i said that.) Just try our methods. mine and tim's and anybody else who is on this thread. the guy on the gearwire video said you might use one method for some clips and the crossfade method for others. It's something that takes a little bit of practice but you'll get it. quentin
|
lackluster strumming
Max Output Level: -86 dBFS
- Total Posts : 211
- Joined: 2008/12/27 17:20:43
- Status: offline
RE: Start Here using Audiosnap and Audio Snap with multi trk drums
2009/02/17 14:30:20
(permalink)
I agree with the arguing thing. where are your problems? post them somewhere so we can hear them/see them.
|
lackluster strumming
Max Output Level: -86 dBFS
- Total Posts : 211
- Joined: 2008/12/27 17:20:43
- Status: offline
RE: Start Here using Audiosnap and Audio Snap with multi trk drums
2009/02/17 14:33:55
(permalink)
do you live in the states? lower 48? send me a pm with your number and i'll call you. it'll be quicker.
|
lackluster strumming
Max Output Level: -86 dBFS
- Total Posts : 211
- Joined: 2008/12/27 17:20:43
- Status: offline
RE: Start Here using Audiosnap and Audio Snap with multi trk drums
2009/02/17 14:38:35
(permalink)
congratulations on becoming a bronze member.
|
feedback50
Max Output Level: -79 dBFS
- Total Posts : 564
- Joined: 2004/05/31 12:08:15
- Location: Oregon, USA
- Status: offline
RE: using Audiosnap and Audio Snap with multi trk drums
2009/02/17 15:37:31
(permalink)
Here is response I gave Treeflight when he was struggling with a similar issue. The idea is to create a master time base for all tracks, using it as imported transients (from pool) to all tracks needing correction. Then generate a perfect track that has the desired timing, using it as a new pool source. The net result is that it substantially minimizes phasing issues. Better explained below... This is what I do for multitrack drums with audio snap. (sorry if this is a little involved). The problem is usually that there are few drum tracks that don't suffer a lot of bleed from other mic's, so getting them all to quantize the same is a laborious process. I usually clone a snare track, gate it and bounce it. I enable audio snap and use this track to export it's transients to the pool. Next, I import those transient markers to all the other drum tracks (rather than just enable audio snap on those tracks). Careful with random adjustments of the thresholds as it can mess up some of the other tracks. I then disable export to pool from the gated snare track. I am usually trying to sync to a click, or sequenced synth drum part, so I select the snare hits in the synth track and export transients to pool on that track. I next quantize each track to pool and bounce them individually. Of course I select the best algo before bouncing. This slides all the drum tracks the same amount maintaining rough timing and phase issues between tracks. Obviously if you're not syncing to a click you could simply quantize second copy of the gated snare track and export transients to pool from there.
|
Lord Tim
Max Output Level: -74 dBFS
- Total Posts : 837
- Joined: 2003/11/10 10:33:43
- Location: Australia
- Status: offline
RE: using Audiosnap and Audio Snap with multi trk drums
2009/02/17 21:01:32
(permalink)
Hmmm... you know that's something I hadn't thought about: cloning a track, applying EQ/gates, etc. and getting the transient snaps from that much cleaner track and applying it to the non-affected tracks. That way you do what I was complaining about earlier that was lacking from the AS palette: having a cleaner signal to detect the transients better which you can then apply it to the un-affected tracks to tighten up their timing. I think the moral of this thread for everyone trying to help out is that there's many ways to achieve great results using AS when you understand how it works. Some people prefer to split clips, some people stretch, some use a master track as the guide, some use overheads, etc.. Everything has its merits and everyone has a workflow which works great for them. Finding the one that works best for your specific project is the right way to go, regardless of how anyone else says it must be done.
|
Funkybot
Max Output Level: -75 dBFS
- Total Posts : 796
- Joined: 2003/11/06 16:32:13
- Status: offline
RE: Start Here using Audiosnap and Audio Snap with multi trk drums
2009/02/17 23:06:55
(permalink)
ORIGINAL: Lord Tim Funkybot, I noticed that your post was in reply to mine (or was it this forum software that did that automatically?) and it seems to suggest that my method doesn't work and/or I haven't worked with multitracked drums with Audiosnap before. Definitely not the case for either point there.  I previously did a lot of work with a program called Beat Quantizer by Zero-X, and it worked very much along the same lines as how I'm doing it in SONAR: bounce down the tracks with core timing of what you want to do to a master track, set your markers up on that, add them to the pool and apply them to the other tracks so everything moves in sync, quantize the master and then make sure the pool gets quantized too (which will mover every track at exactly the same distance so no timing discrepancies occur). I don't understand why you can't use the ProTools method you mentioned as the easier alternative with SONAR. Just going through the method step-by-step: 1. Group the clips that make up the drum track Check, can be done in SONAR. 2. Select the overheads track and enable AS Check, but I'd prefer to do a master timing track personally because where AS falls down is its detection routine for complex material like overheads - I'll get to that in a bit. 3. An option should appear that asks, "Apply Transients for Parent Track to All Grouped Tracks? Yes or No?" OK, this is where you do it differently in SONAR. You right-click all of the other tracks at that point and do Audiosnap -> Apply AudioSnap Pool Transient Markers. That will copy those markers from your overheads to your other tracks in exactly the same place. Bear in mind that this will be slightly different timing to the close mics because of the distance, etc. but it'll all be exactly in the same place on all of the tracks, ie: keeping the phase relationships consistent. 4. Clicking yes should apply the transients from the overheads to all the grouped drum tracks. Those transients will now be linked/grouped so that any change I make to one, will apply for all tracks in the group (unless I manually indicate otherwise). This is an extra step in SONAR, you need to Quantize To Pool for those tracks whenever you make a change to whatever your master timing track was, and in the case of this example, that was the overheads track. 5. Manually adjust the transient start times so that you're not cutting off any hits in their direct channels and add them where needed. Once done... 6. Split At Transient Markers 7. Quantize the Audio Clip Start Time And for this part, I'd quantize just the master timing track (overheads in this example), and then go to all of the other tracks and quantize to pool so they align with the markers that moved when you quantized the master timing track. Then when you're done, bounce to clips to apply the changes and use the offline stretching algorithm. That's not a lot different, really, and just one more step you have to take into consideration - quantizing to the pool every time you make any timing changes to the master track. No splitting necessary either if you let it stretch the audio rather than cutting and cross fading. EDIT: spelling Lord Tim, that might be a workaround, but I wonder how well it will work. So you'd basically bounce everything down, create the transients on the bounced down track, then apply those transients to the multitracked original takes and quantized? I'll give it a shot and report back. I still think the best method would really be improved clip grouping and adjusting things manually. Cakewalk simply needs to look at the combination of Beat Detective and Pro-Tools grouping features to see how elegant a solution that is. There's a reason we've been hearing live drums locked to grid for years: it's because Pro Tools made it simple. Sonar is on the right track, but I'm disappointed that we aren't quite "there" yet.
post edited by Funkybot - 2009/02/17 23:16:34
Intel i7 4790k, ASUS Z97-A mobo, 16GB Kingston DDR3 RAM, Windows 10 x64, UAD2 Duo, RME Fireface 800, Sonar X1/X2 Producer
|
Funkybot
Max Output Level: -75 dBFS
- Total Posts : 796
- Joined: 2003/11/06 16:32:13
- Status: offline
RE: Start Here using Audiosnap and Audio Snap with multi trk drums
2009/02/17 23:28:33
(permalink)
Lord Tim, that method though sloppy in my quick test, did preserve the phase relationships. I didn't know about the right+clicking to add the pool transients as new transient markers. So while I might never do this on drums, it will probably work great on multi-tracked bass where I'm only dealing with two tracks. Thanks!
Intel i7 4790k, ASUS Z97-A mobo, 16GB Kingston DDR3 RAM, Windows 10 x64, UAD2 Duo, RME Fireface 800, Sonar X1/X2 Producer
|
Lord Tim
Max Output Level: -74 dBFS
- Total Posts : 837
- Joined: 2003/11/10 10:33:43
- Location: Australia
- Status: offline
RE: Start Here using Audiosnap and Audio Snap with multi trk drums
2009/02/18 00:08:25
(permalink)
Yeah, that's what I mean about that part being hidden in a right-click context menu. That drove me insane trying to find that elusive step that every other quantizing program had! But yeah, it takes a bit to get everything sounding good even with that method but with patience you can get some really good result from it. That said, I've also used the split method and gotten some killer results from that too, so there's lots of ways to do the job. Hanging out for Audiosnap 2.0 though!
|
endoverend
Max Output Level: -88 dBFS
- Total Posts : 102
- Joined: 2004/03/21 23:30:13
- Location: California
- Status: offline
RE: Start Here using Audiosnap and Audio Snap with multi trk drums
2009/02/18 15:27:54
(permalink)
ok, the best scenario i could come up with for "perfection" with audiosnap on multitracked drums everything done manually on the overhead tracks due to the complexity of the transients - first drop the transient markers at zero threshold and zero sensitivity and weed through the garden VERY carefully use your ears! and wear headphones cranked , dont be afraid of disabling lots of markers! be aware of the cymbal bleed in the tom tracks as they sustain....need to match the overhead crashes i had the toms gated hard and still had to work on them a bit, im going to use drumagog on the next song and just get them in time and not trip on the bleed phasing remember if you drag them from the tip they dont move the audio - only from the stem to move the audio. they are frequently dropped at the wrong point! (cant trust audiosnap most of the time) word up: i used the bounced samples - post drumagog - kick and snare so that i would remove any potential latency from the processing at the same time as the audiosnap, this will resolve issues with phase in the overheads related to triggers being a bit late. sounds good. (super-sonic pak is worthy) the kick and snare and toms i did manually as well to punish myself and get faster at this my goal was to get the drums really close to the click so i could use many midi instruments and loops "in time" like shakers ect. for me there was no pool, no nothin but enable the transients at zero threshold and sensitivity and manually comb through the song this was the only way to gurantee my clients that no artifacts will be in their song tracks. this was all i needed to know - how to get it "perfect" now i have an workfow timeline i can estimate per song 5-6 hours this is billable hours and ok with me as long as it sounds PRO a musical note: when the kick and snare get nudged the hi hat / ride gets out of time (surprise!) so get the hi hat/ride right and the rest is easy i would fix the kick and snare and then the madness began..... hope this answers a methodical workflow for the perfectionists out there. if only i could manually make one overhead track perfect then apply the edits to all tracks in the drumset automatically....... PLEASE ADD YOUR METHODS TO THIS POST! EOE
Win 7 64, I7 2600k, 16gb Sonar X2A, RME FF 800 Pro Tools 11.01HD Native Card 16/16 I/O built by www.studiocat.com
|
endoverend
Max Output Level: -88 dBFS
- Total Posts : 102
- Joined: 2004/03/21 23:30:13
- Location: California
- Status: offline
RE: Start Here using Audiosnap and Audio Snap with multi trk drums
2009/02/18 18:52:58
(permalink)
please add your techniques to this thread, we still have not completed a consensus on how to use audiosnap in the method intended by the manufacturer for multi tracked drums the workarounds are really time consuming.. whats your method? thanks EOE
Win 7 64, I7 2600k, 16gb Sonar X2A, RME FF 800 Pro Tools 11.01HD Native Card 16/16 I/O built by www.studiocat.com
|
Lord Tim
Max Output Level: -74 dBFS
- Total Posts : 837
- Joined: 2003/11/10 10:33:43
- Location: Australia
- Status: offline
RE: Start Here using Audiosnap and Audio Snap with multi trk drums
2009/02/18 20:40:24
(permalink)
ORIGINAL: endoverend if only i could manually make one overhead track perfect then apply the edits to all tracks in the drumset automatically....... That's what the pool is for. Get your transients how you want on the overheads track, copy them to all of your other tracks, align your overheads in time how you want, quantize the others to the pool. That's it. That's the only way you'll preserve your phase relationships unless you spend days zooming in really close and moving each marker manually and hoping that your eye is good enough to see where it lines up with a previous track. The only fiddly part is to get the first track aligned right, enabling and disabling the markers and making sure they're in the right place. After that's done, everything else is automatic if you use the pool, and choose the right stretching algorithm when you bounce to clips. (That's the trick - until you bounce to clips, it will sound pretty awful).
|
endoverend
Max Output Level: -88 dBFS
- Total Posts : 102
- Joined: 2004/03/21 23:30:13
- Location: California
- Status: offline
RE: Start Here using Audiosnap and Audio Snap with multi trk drums
2009/02/23 14:40:40
(permalink)
Get your transients how you want on the overheads track, copy them to all of your other tracks, align your overheads in time how you want, quantize the others to the pool. That's it. is this the answer to the question? make one overhead track done manually then add it to the pool then quantize all the other tracks to the pool? is this what you are describing? if you cant trust audiosnap to drop the markers accurately on the transients........ you still have to comb over every inch of every track carefully.
Win 7 64, I7 2600k, 16gb Sonar X2A, RME FF 800 Pro Tools 11.01HD Native Card 16/16 I/O built by www.studiocat.com
|
nprime
Max Output Level: -51 dBFS
- Total Posts : 2423
- Joined: 2004/08/16 19:19:49
- Location: Vancouver
- Status: offline
RE: Start Here using Audiosnap and Audio Snap with multi trk drums
2009/02/23 15:11:43
(permalink)
May I point out the obvious here? The actual "professional" answer? Unless the drummer has died or moved away I would have re-recorded the tracks. Your paying clients should have been more careful and more critical when they were in the studio recording and not just settled for "almost right" on the drum track. The session should not have wrapped up until everyone was happy with the drummer's performance. It is the producer's job to spot this. He is in charge of the money and the session. He should have rehearsed his band more thoroughly before committing time and money to recording them. The drums are the foundation on which everything else is laid. "Almost" is never good enough for the drums. If the drummer can't deliver the performance he shouldn't be in a studio recording. My experience with Digital Audio is that it is always faster and easier to do another take then it is to fix it. Especially with drums. I'm really tired of the current attitude that the magical DAW can fix a less than ideal performance. No one seems to have the balls to just say "Do it again" anymore. Just look at all the time you have wasted trying to use an imperfect tool to fix an imperfect performance. That's time you won't get back. Sorry for the rant.
Listen Sonar 5PE Intel DP35DP, E6750, 3 GB, 80GB/320 GB Scope (6 DSP) w/A16 interface PadKontrol, Legacy Series MS20, EZDrummer.
|
Lord Tim
Max Output Level: -74 dBFS
- Total Posts : 837
- Joined: 2003/11/10 10:33:43
- Location: Australia
- Status: offline
RE: Start Here using Audiosnap and Audio Snap with multi trk drums
2009/02/24 00:15:02
(permalink)
In a perfect world, I agree with you. But it ain't a perfect world. Budget restraints can dictate how much time you can spend on drum tracks (and any tracks really), so sometimes it's just not real to do take after take until you get something amazing. Additionally, the drummer you may be tracking could be an average player but a key member of the band. Do you have the band replace him for someone who can nail the part and kill the band or work with what you have? And if you subscribe to the "but you should keep his performance as it is because it's honest" school of thinking, we should probably not bother with compressors or EQs or anything like that to make anything sound better because it's not honest either, when you break it all down. The other thing is too, what if you were wanting to lock in dead in time with a sequenced part? A drummer's timing could be awesome, but it's rare to find a drummer who is mechanically tight for an entire track so you don't get any sync problems when you're lining up to a drum loop or synth arpeggio or whatever. There's a lot of applications to use AudioSnap for a drummer, and while I absolutely agree that the best way to get a killer performance is to do take after take until you get a killer performance, sometimes AudioSnap is the best and sometimes only way to do the job. @ endoverend: yep, that's what I'm describing. Yes, it can be time consuming making sure that first track is right, but after you have that down, that will adjust all of the others via the pool in sync, so that's the only track you need to fix.
|
DH123
Max Output Level: -86 dBFS
- Total Posts : 220
- Joined: 2008/01/14 23:15:02
- Status: offline
RE: Start Here using Audiosnap and Audio Snap with multi trk drums
2009/05/18 23:21:39
(permalink)
Holy crap - this works but this is the first time I've done something like this with multi-tracked drums. 14 tracks is KILLING my Q6600. Just built a new I7 daw but haven't moved to it yet. PLEASE tell me the CPU speed increase helps!!!!
|
musicroom
Max Output Level: -51 dBFS
- Total Posts : 2421
- Joined: 2004/04/26 22:31:02
- Status: offline
RE: Start Here using Audiosnap and Audio Snap with multi trk drums
2009/05/18 23:46:17
(permalink)
ORIGINAL: DH123 Holy crap - this works but this is the first time I've done something like this with multi-tracked drums. 14 tracks is KILLING my Q6600. Just built a new I7 daw but haven't moved to it yet. PLEASE tell me the CPU speed increase helps!!!! Sorry, but research shows that a faster cpu means slower performance. :) Seriously, from what I have read, I7 users are a happy group.
Dave Songs___________________________________ Desktop: Platinum / RME Multiface II / Purrfect Audio DAW I7-3770 / 16 GB RAM / Win 10 Pro / Remote Laptop i7 6500U / 12GB RAM / RME Babyface
|
DH123
Max Output Level: -86 dBFS
- Total Posts : 220
- Joined: 2008/01/14 23:15:02
- Status: offline
RE: Start Here using Audiosnap and Audio Snap with multi trk drums
2009/05/19 09:34:15
(permalink)
I'll have to try this with ASIO4All before I get my new interface because this KILLED my PC. No wonder pros go for the dual-quad PCs like the Mac Pro.
|