Take lane processing - Bounce to clip not working as expected

ok, you would presume that when bouncing a clip in a take lane that the bounced clip would remain in the take lane you want, correct?
 
I have some scratch BGV tracks. I am setting up a practice set of harmonies. I am using Melodyne to put a melody and 2 harmonies based off of the melody.
 
1. I have take lane1 - main melody
2. I insert a take lane2 and CTRL-CLICK drag the melody from lane1 to process the harmony on the lane2
3. I do my edits in Melodyne on take lane 2 to put a harmony up a 3rd
4. I bounce to clip The bounced clip will go to the upper take lane and I have to drag the bounced clip back to the original take lane2
5. Repeat 2-4 but to new take lane3
 
When step finishes, take lane3 results are overlaid on take lane2 and I have to drag take lane3 clip bounce results to take lane3.
 
Should I be able to expect that the bounced clips will remain in their perspective take lanes?

Search for my thread "I still don't like Take Lanes..."

No, I haven't. It's because 1) I was too busy reporting other issues, 2) my take lanes thread lasted unexpectedly longer so I'm sure all bakers who regularly check the forum saw my first post (at least Noel chimed in so he's aware of the issue), and 3) I continue avoiding using the feature, which is obviously half-baked (in terms of MIDI, at least -- I haven't done any audio comping in X3).
 
Btw, I've just followed your steps in the original post (without using Melodyne, which isn't included in my version), and wonder how you can ctrl-click drag a clip from one lane to another. It's not possible here. It just selects a range.

A few...
http://forum.cakewalk.com/Outstanding-Issues-as-of-X3D-and-general-comments-m2952585.aspx#2952585
 

I thought I was doing something out of design scope with this use, but I was creating some scratch vocals/harmonies in multiple take lanes in the same track. 

If I am allowed to do something in a program and it works, it becomes part of my workflow if it designed that way or not. :)

Jlien X
Oh, Ctrl-click dragging is working fine now. Don't know why it didn't work when I tested it earlier...
Anyway, I think Take Lanes aren't supposed to be used in a way you discribed in the original post. I mean, lanes are designed to create one complete track (just one part -- e.g. lead vocal), which shouldn't require bouncing clips in the lanes. I don't know, I'll see if I'm right or wrong when I do audio comping in Sonar in the near future...

I agree with this, Jlien X.
 
Take lanes are meant to be used to contain different takes, that can be comped into a final track.  Bouncing to clips in a lane would therefore not be an issue, as it's not what take lanes are for.
 
I'm not saying there aren't any take lane bugs, just that this is not one of them.
 
@Conley - why can't you do this on separate tracks?  That's what I, and many others, do.

Let's take Alex's example of playing the spoons.  I am known to be somewhat wary of using analogies or metaphors on this forum, as people seem to misinterpret them or their limitations, but here goes.
 
One could hardly complain to a cutlery manufacturer if his spoons did not sound right, or if they bent under extreme syncopated riffing along to a metal track in 17/8.

I ran into the bouncing clip that ended up in a non originating lane issue before I copied the clip to another lane for processing.

Normally, I would put the clip in another track for a different voice. This take lane thought was a very quick and dirty process to get an idea out the door. By no means is it a final part of the project.
 
This issue also can be witnessed with a single clip in a single lane. Bouncing the clip puts it in another lane. It looks like the top most lane is the one SONAR is looking to process.
 
If I have the following:
 
1. single track in project
2. record audio for a few measures
3. expand the take lanes
4. add take lane2
5. select recorded take lane 1 audio and bounce to clip
 
At this point, the clip is bounced to the upper take lane and does not stay in the processed lane. Is that really what is expected? I did not expect that.
 

I dunno..   I think I'm actually with Conley on this one, right or wrong.    If a certain portion of a certain take was the best one but still needed a little Melodyne work, I would make those edits in-place and then bounce the clip, since I'm still (more or less) in the comping process.   Then I'd flatten the comp using all of the desired clips, including the bounced MD version, and move on. 
 
I guess an alternative would be to flatten the comp first, split out the portion that needs MD, and then do the Edit > Bounce sequence... without ever opening take lanes to see where that clip was located.     
 
Moving the clip to a separate track probably is the safest option, but it seems like a bit of overkill for a single "corrected" clip/take.   Then there's shared plugin processing, sends, etc, etc.
 

Guitarmech111

For the old timers - Bring Back Audio View!! It is 40% better!!

Flashback!  
 
Funny thing is, I can't see myself actually using that very often these days - I rarely have much of anything to pencil out.   Although, it could be cool for an instant zoomed-in version of the audio data.  Huh, I wonder what Karl would say about that...