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.

Our posts crossed.
 
I guess this doesn't work, so shouldn't become part of your workflow..

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.

What will it take? Take lanes are not tracks. Why is this impossible to understand?

I sm sorry if I sound frustrated, but by understanding this concept, SONAR will open up to you and make sense and allow you to be productive in a pleasing way.

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.
 

Well as the spoons were played on Motörhead's Ace of Spades. If Lemmy was ringing me up and complaining about sonic quality of his spoons I think I would probably have to listen or pay the consequences. My main point was that unintended consequences is generally what creates genius and art. Anyways...

Back to Conley's point. If certain functionality shouldn't be used with takelanes, it should be disabled. End of story. If you don't know how to use an ejector seat then don't put it in a car otherwise you might hurt your head.

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.
 

the way I processed this track and expectations is how a lot of the old timers would probably think to do it first. That has been my cakewalk DAW work flow for a very long time.

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

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...