I am recording vocals for my project in a separate file. I have 3-4 takes of each vocal part I'm recording. Man, there's a lot of frustration with this process.
 
1. I record multiple takes, then when I do processing on them (transposing and/or changing length) they appear to still be separate takes, but they have apparently merged into one take that can no longer be handled separately. So I have to edit one by one.
2. I am having terrible trouble copy-pasting them into the real project. I will grab my takes, Ctrl-C, move to the target project, then try to paste. It will overwrite existing takes, even if I have added enough empty lanes to paste them into and selected the first empty lane. 
3. So, I create a new track to paste them into and create a bunch of extra lanes (all this, incidentally, should be unnecessary - if Cakewalk wants us to use take lanes, they should make it easy on us and figure out what's in the clipboard is takes and create lanes etc for us) but when I paste into the empty track, it again merges all takes into a single clip.
 
As far as I can tell, the only way to do this is to edit, copy and paste each take separately. Extremely time-consuming. Am I doing something wrong??
 
Also, as a side note, SONAR SHOULD NEVER EVER EVER OVERWRITE EXISTING CONTENT WITHOUT WARNING THE USER. This seems like Rule #1  to me. 
 
I've been a Cakewalk user exclusively since 1989, and the take lane concept has been the most poorly executed blunder in their history. Anymore, I just assume that it's going to work in whatever the most inconvenient way possible, and I'm usually right.

jkoseattle
 
I am recording vocals for my project in a separate file

 
Just curious - why are you doing that?

jamesg1213

jkoseattle
 
I am recording vocals for my project in a separate file

 
Just curious - why are you doing that?

When I have a music bed that is rich with FXs etc. I sometimes export a mix to separate project just for tracking vocals at low latency vs. freezing everything. And you can't freeze buses, so there is that too.
 

hmm...
 
This isn't making a whole heckuva lot of sense. I understand what you are attempting but some of the methods and results seem wrong/murky and I don't have time right now to dig into it all or test it BUT...
 
If resources are the problem and you are indeed tracking to another project with a mixdown backer I'd personally do a mixdown/bounce and put it in a special track that goes direct to Master (I keep a track in all my projects specifically for mixdowns), then temprorarily Archive enough resource intensive tracks to make the project less sluggish, Solo the "Export/Bounce" track and the track(s) I'm recording into (so those are the only two audible as I track).
 
After the tracking is done I'd crank my buffers back up, unarchive/unsolo everything and mute the "Export/Bounce" track.
 
That keeps everything in the main project.
 
Maybe you are tracking somewhere else though thus using the other project. This method would still work though if you prep it beforehand and take it with you.
 
As far as the technicalities... as I said, could be a lot of things but I am Blapples deep in some other surpise chaos today.

bapu

jamesg1213

jkoseattle
 
I am recording vocals for my project in a separate file

 
Just curious - why are you doing that?

When I have a music bed that is rich with FXs etc. I sometimes export a mix to separate project just for tracking vocals at low latency vs. freezing everything. And you can't freeze buses, so there is that too.
 

I wouldn't go that far with mixing if I didn't have the vocals in the project, but that's just me.

Could it be that your are trying to use Take Lanes in a non-intended way? They work just fine for their intended use. That is not to say that your cannot get creative with their use, but if it is causing frustration, then I would explore what exactly are you trying to accomplish and look for all the different tools you could use to best accomplish that rather than try and force Take Lanes to do something they were not intended to do. In the end, this will bring much less frustration.

Sylvan
Could it be that your are trying to use Take Lanes in a non-intended way? They work just fine for their intended use. That is not to say that your cannot get creative with their use, but if it is causing frustration, then I would explore what exactly are you trying to accomplish and look for all the different tools you could use to best accomplish that rather than try and force Take Lanes to do something they were not intended to do. In the end, this will bring much less frustration.

 
+1!
Take Lanes are great for comping and Speed Comping is still one of my absolute favourite features in SONAR, really a huge time saver.
BUT: I only use Take Lanes for this specific task.
When I got my preferred takes together, I use "Flatten Comp", copy the Comp Track to a new track, archive and hide the old one (including all Take Lanes).
Then I start editing, processing, whatever with a solid new track.
 
I had to change my workflow a bit when Take Lanes were introduced but I'm glad I did.
 
It's way easier for me to change my workflow than the program I use... 
Especially when the outcome is far better than the previous flow.
 
Give it a try!
 
Best,
Klaus

I use them all the time, but I refrain from monkeying with individual takelane clips; that way lies madness and it appears to me that it's not really how take lanes are intended to be used. Here's what I do.
 
Set loop on, record as many takes as I want (for me, that may be several thousand :) ). To review, show the take lanes and then use the smart tool with the selection icon active to click and hold on a take and drag to highlight a section. This will automatically make the selected portion the "main audio" allowing you to audition the take. You can highlight different parts of different takes and Sonar will compose them all into one take on the fly. Once you're happy, flatten it and you're golden. Once you have a completed track you can process, clip, move, etc all you want. 
 
Thanks how I use it, and I ask nothing more of it than that. In return it behaves for me. Good luck!

Those who are happy with Take lanes don't do these:
 
- record to more than several lanes per track,
- record more than several clips per lane,
- use clip automation,
- adjust split points, and
- copy/cut and past clips across lanes.
 
And I've been very unhappy with the feature (I submitted a couple of FRs but they've been unimplemented...)

It seems to me those that are happy with the feature use tthem as they were intended. I think of take lanes as the very first step in editing - they are for organising the raw material. Once I have the takes down, I go through with the selection tool and isolate the sections that I want then flatten the track. Take lanes job done! All other monkeying proceeds from that point.
 
It's a bit like saying this car is rubbish because it sank when I tried to drive it across the lake.