gswitz,
 
Thanks for confirming what the expected behavior is.  However, following the process I outlined above, X3 did not produce the expect behavior.
 
I agree with usefulness of the comping functions working like they are supposed to.  And I can work around this little niggle if I have to - but if there is a circumstance where Sonar is not behaving as it should, I want to give the bakers an opportunity to fix it.

Oh, of course. I was trying to help replicate the bug. I wasn't clear on whether bug or expectations are the issue. I'll try again to repeat it tonight to see if I can reproduce.

dwardzala
OK, so I just tried what I did last night again.  Here are the settings and workflow.
 
Record mode is comping.
Create new lanes on overlap is checked.
Store takes in a single track is checked (under looping).
 
1) Arm guitar track.
2) Record guitar track (through TH2 - if it matters).
3) Open take lanes - previously recorded material goes into T1 but is not muted.
4) Mute T1.
5) Record second take - wave form shows in main track during recording but disappears (moves to T1) upon stop.
 
Is this correct behavior?
 
If I add T2, it will record to T2, so that will be my workflow if the above behavior is expected.
 
Obviously, I thought that a new take would be created if record was hit after stopping in comping mode, but if that's not the case I can adapt easily.

Hi Dave,
 
I'm looking into this issue and am not able to reproduce. In another post you mention that you are hearing audio while recording in comping mode. The condition this can happen under is if you have Auto - punch enabled and mute previous takes not checked. This will over-ride comping behavior so you can punch in a specific point while still monitoring your current active lane. Is this the case? Do you also have loop markers enabled?
 

I'm seeing the same behavior as gswitz except I am seeing the older takes in the lower numbered lanes.   
 
This does make me wonder what might be different that could cause previous takes not to automatically mute.  Or for the new take to go in a previous take's lane.   Does it happen in every project?   If so it's probably worth sending in.

gswitz
The new behavior of Take Lanes is that the most recent lane sorts to the top. (This is new).
 
[snip]
 
For me, on the second record, I get a new lane (T2) which has the first take in it. I also get a new lane (T1) which has the latest recording in it.
 

Good post, Geoff. I just wanted to point out that your second statement about lane order is backwards. T2 will have the new take in it, and T1 will remain beneath it with the original (and now muted wherever there's an overlap) take in it. Also, if you expand lanes after the first take, you'll already have a T1. The clip in the header area of the track is a Comp clip that is a representation of what's in the lane(s), even when there's only one take lane.
 
BTW, I am able to reproduce a problem like the OP describes (related to opening and closing lanes between takes), but only if Create New Lanes on Overlap is not enabled, and not until the third take. That third take and all subsequent takes end up stacking up in T2. If I have Create New Lanes enabled, I can't reproduce the problem.

Thanks guys for straightening things out. I clearly got that info backwards on the naming.

Dan,
 
I will check to make sure I don't have loop markers enabled (I don't think so) and I will verify that Auto-punch is not enabled later tonight.
 
I should note that this is a new project in X3 that was created from template that was created in X2.  I don't know if that makes a difference, but it is certainly another piece of data.
 
Thanks for looking into this.

I have confirmed that auto-punch recording is not checked (although mute previous takes, which is greyed out, is checked).  There are also no loop points set and loop recording is not enabled.

I just ran a test - new project Normal template (i.e. no tracks) from X3.
 
Record mode is comping
Place new takes in separate track
 
1) Add audio track (set inputs, etc, add TH2)
1a) Open take lanes
2) Arm track (not lane)
3) Record take 1 --> goes into T1
4) Record take 2 (take 1 does not play but the mute button is not lit - this was throwing me off) --> goes into T2 (T2 automatically created)
5) Record take 3 (takes 1 and 2 do not play) --> goes into T2 on top of previously recorded T2 (both play together when played back)
 
Note for this test the length of T1 > length of T2 > length of T3 (not sure if this matters or not.
 
Another test
1) Add audio track (set inputs, etc, add TH2)
1a) Open take lanes
2) Arm track (not lane)
3) Record take 1 --> goes into T1
4) Record take 2 (take 1 does not play but the mute button is not lit - this was throwing me off) --> goes into T2 (T2 automatically created)
5) Add T3 manually and record take 3 --> goes into T3 (takes 1 and 2 do not play)
6) Add T4 manually and record take 4 --> goes into T4 (takes 1,2 and 3 do not play)
 
It seems as if there is a problem getting to the third take lane automatically (and this is where I noticed the problem originally).
 
I will go back to my original project and try it again with the track I am working on to see if I can reproduce the behavior in test 2 because at least the tracks are not playing there.  The auto take lane add for T3 and above looks like an issue.

http://www.cakewalk.com/support/contact/problemreport.aspx
 
This is the best place to submit problem reports like the ones listed in this post. That's the official entry point. While someone else in the forum may notice this and enter it, you shouldn't depend on that.