Silvio Gazquez

Best takes for the whole kit at different times.  

Yes, i get the grouping thing but what i¡m struggling now is with selecting  parts on different track lane.  I can't find a video tutorial on that

Thanks,

Hmm ok, i will try that option. Thanks!

i'd like to know what's the best workflow for tracking multi drum takes and being able to choose takes.  

I know how to do comping on 1 track but when you have 10 tracks I'm not seeing a way of doing this easily.

So, to make it clearer, i want to track  at least 3 takes of a 10 track drums but what is the easiest way to choose the best parts of each take?

23 minutes ago, slartabartfast said:

The first thing I would try when one program installation seems to break another program is to reinstall the broken program. If there is a "repair" option under  "Apps & Features" under the application try that first--but that is uncommon. If a re-install fails check to see if you have everything you need to do a complete new installation and then un-install the broken program and try again. Pay attention to the locations where your installation is writing files. Often enough the problem is that a program overwrites an existing file with one that is incompatible with the older program. 

I re installed it a few times, in fact i tried with both vegas 15 and 17 and  same thing. I will try to change the install folders by default and choose a different one.

Thanks,

11 minutes ago, Chuck E Baby said:

http://forum.cakewalk.com/SOLVED-Freeze-when-scanning-opengl32swdll-m3622849.aspx

Ok, i think i already tried that, will check anyway. I think I wasnt clear, Cakewalk works fine, sony vegas freezes since I installed CbB

1 hour ago, pwalpwal said:

what is that dll it's stuck on? (image is too blurry to read...)

opengl32sw.dll

Hello, 

I have Sonar 6 and installed Sony Vegas Pro 17 and worked fine. Then I installed Cakewalk by Bandlab and 

Vegas didnt open anymore.  It gets stuck here (see image)

I have a PC - i7 64 bits - win 10. 

Any suggestions?

yeah, I have watched a few tutorials but werent a big help. I will check that one anyway.

Thanks for your help!

14 minutes ago, David Baay said:

I happened to stumble across the following posted by Lord Tim on the old forum a while ago, and thought his suggested procedure was nicely succinct.  Note that the purpose of applying a common set of transient markers to all tracks is to ensure that stretching doesn't introduce any phase errors with room mics and bleed across other mics:

Record the takes (duh)

Select each track, enable Audiosnap and set the threshold level to 100% to disable the transients

If this is a simple drum track with no kicks playing in time with the snare (so you're getting possible flamming), I bounce kick and snare to a new track ** (see note below)

On that track, enable Audiosnap, drag the threshold slider down until it detects most or all of the hits, adjust accordingly by moving transients around or inserting / deleting as necessary.

On that track, right click it and choose Pool > Add Clip to Pool

Select every other track, right click on one and choose Pool > Apply transient pool markers

Manually tighten or quantize your guide track as you see fit.

Select every other track, right click and choose Pool > Quantize to Pool

No splits, no crossfades needed, no weird gaps, no endless clips. All of the phase is correct and it just works.
 
** Audiosnap has a BIG problem with ghost notes and weird detections. What I tend to do is put a gate on the kick and snare track and get them extremely clean sounding (to the point of them sounding bad, but so there's a definite attack to each hit, and no noise between the hits) and the bounce THAT to a new track. You can delete the gates after that. You new guide track will have super clear hits and Audiosnap will be a million times better at detecting the transients.
 
This gets a bit more complex with double kick work where things fall on the same beat, or places where you want to set your timing guide from something else (ie: you have a killer ride pattern which is a bit off but that's where everything follows.) You need to decide what is most important, quantize minus any overlapping hits, then go back a few more times and lock in those remaining transients with the rest of the group. Not ideal but I've had great results from doing that.

Thanks for your feedback. It sounds kind of complicated and like this type of quantizing with multitracks in cakewalk is not pretty convenient.

Isn't there a non cakewalk plugin or other tool to use instead of audiosnap? inside cakewalk of course

Hey,

I was wondering if it's possible to quantize an 8-10 live drum tracks with audiosnap?

I wasn't able to find much tutorials about that...

By the way, I just remembered that i had another issue  in another PC. Its an i7 64 bits with win 10. 

So i had Sonar 6 and installed Sony Vegas Pro 17 and worked fine. Then I installed Cakewalk by bandlab and 

Vegas didnt open anymore.  It gets stuck here (see image)

Ok, will try that then, thanks again!

10 minutes ago, msmcleod said:

Audio quality is exactly the same.

The only difference between the two is that ASIO generally has better latency. This isn't always the case though, sometimes WASAPI can be just as good.

So in order to change to wasapi I have to install focusrite wasapi drivers? Sorry for my ignorance 😃

2 minutes ago, msmcleod said:

Audio quality is exactly the same.

The only difference between the two is that ASIO generally has better latency. This isn't always the case though, sometimes WASAPI can be just as good.

Ok, will check all that.. Thanks for your help!

2 minutes ago, msmcleod said:

For dedicated audio devices such as the 2i2, ASIO is usually best as it bypasses all the Windows layers and accesses the audio device directly.

However in Windows 10, WASAPI can perform almost as good if not the same as ASIO for most modern devices.

 

I see... but what about in terms of audio quality? 

42 minutes ago, msmcleod said:

Focusrite have acknowledged an issue in their driver switching between ASIO / WASAPI that causes a blue screen (and I've heard reports of the same happening in the very latest driver when changing ASIO buffer size).

Until they fix this avoid swapping between WASAPI and ASIO.

If you can, avoid using your 2i2 as your Windows device (set Windows to use your on-board sound device), and use ASIO exclusively in Cakewalk.

If you do need to use your 2i2 as your Windows device, then use WASAPI mode within Cakewalk, and ensure that Windows is using the same sample rate as Cakewalk (keep an eye on this... Windows updates has a habit of changing it).

 

Ok, will check. Whats the difference between wasapi and asio? is one better than the other?

Thanks,

Silvio.

15 hours ago, msmcleod said:

@Silvio Gazquez - what audio interface are you using?

Scarlet 2i2 2nd gen

Hello there, 

So I'm getting the windows  blue screen of death pretty often lately while opening cakewalk projects.

Anyone had the same problem?

I have a PC i5 with 20gb ram, running windows 7 64bits 

Thanks,

Silvio

awesome, thanks!

Hello, 

I was using sonar for a few years. Now that i downloaded cakewak by bandlab, when i open an old sonar project i dont see the arrows to 

expand or collapse the track height. So I just have to dragg it with the mousse what makes the workflow pretty tedious.

(i attached a file so you can what i mean... there's no arrow)

Someone could help?

thanks,

Silvio