• SONAR
  • Take Lanes: Clip can't be copy-pasted into a lane of different T number [Confirmed by CW]
2014/02/25 08:36:30
icontakt
A known take lane issue officially confirmed by CW recently. Below are the steps to reproduce it if you're interested...
 
1. Create a new project.
2. Drag a file (either MIDI or audio) from the Browser into the Track view Clips pane (this creates a track).
3. Drag the same (or a different) file from the Browser into empty space of the Track view Clips pane (this creates another track).
4. For each track, click the Take Lanes button to show the lane.
5. For each track, click the Add Take Lane button to add a new lane. Now, you see two tracks with two lanes each.
6. For each track, drag the clip in the 1st lane into the 2nd lane.
7. Perform the following:
(A) Copy the clip in the 1st track's 2nd lane by Ctrl+C, select the same track's 1st lane, and then paste the clip by Ctrl+V.
(B) Copy the clip in the 2nd track's 2nd lane by Ctrl+C, select the 1st track's 1st lane, and then paste the clip by Ctrl+V.
 
[Expected Results]
Both (A) and (B) result in pasting the clip into the selected (destination) lane, which is 1st track's 1st lane.
 
[Actual Results]
Both (A) and (B) result in pasting the clip into 1st track's 2nd lane.
 
 
Issue#: CWBRN-24086
Reported on Feb 13, 2014
Confirmed and submitted to development on Feb 14, 2014
2014/02/25 09:58:07
flameout
I have been battling this one for a long time.  They seem to have a mind of their own sometimes. In fact, cut and paste seems to have more bugs then this.
 
For example, say I want to take a section of a song, copy it, or cut it, and paste it at a different location.  Something I was doing all the time up through X2.  But in X3, the tracks have a mind of their own. When I insert, some tracks move over, sometimes one or two won't.  (and I am not talking about Region FX tracks). Believe me I used to do this with wild abandon so I know what I am doing.
 
The work around is to insert a blank space (all tracks) in the song equal to however many measures the piece I am copying is.  When I do that, the space does successfully open up a gap. I then paste with overwrite.  That works fine, every time. But every time I do this, instead of satisfaction, I feel annoyed.
 
I keep thinking that something so fundamental to daw operation as cut and paste, tracks and take lanes, is so basic to the operation, that cake would have made that a priority to fix. 
 
This is not the only cut and paste bug I have discovered.  Using take lanes and the new comp recording feature are severely limited by the unreliability - and the seemingly craziness and randomness of pasting in the lanes and sometimes, the tracks themselves.
 
Maybe X3e...
 
Rick
 
 
2014/02/25 12:49:15
neirbod
Thanks for clearly identifying the problem.  I have wrestled with odd cut and paste behavior with lanes as well.  I am not sure if this problem you identified is the root of all the issues I have seen, but it certainly is a contributing factor.  Let's hope X3e fixes it.
2014/02/25 13:16:26
brundlefly
I'm a little surprised the inability to paste to specific lanes was "confirmed" as a bug. Though it's admittedly a surprising omission, it seems to me this is a feature that's never existed. Clips always paste to the same lane from which they were cut/copied (or to the next highest available if pasting to a new track). X2 worked the same way, and layers in X1 and earlier didn't allow choosing a "destination" layer, either. Pasting just isn't fully lane-aware. If you want something to go to a specific lane, you have to drag and drop.
2014/02/25 15:44:17
wetdentist
i've had many instances where the audio that used to be in a take lane would no longer make any sound, even though a visual representation of the wave existed. but if i bounced to clip, it would be a flat line.  it did not matter if i copy/paste to new lanes or tracks, or if i drag and dropped.  very weird.  now i bounce all my take lanes to tracks. 
2014/02/25 16:05:18
brundlefly
If a clip is silent on playback and goes flatline when bounced, it was likely muted. As you probably know, SONAR used to display the universal "No" (circle with a slash through it) symbol on muted clips, but now just grays them out which can easily be overlooked.
2014/02/25 17:14:33
CoteRotie
brundlefly
If a clip is silent on playback and goes flatline when bounced, it was likely muted. As you probably know, SONAR used to display the universal "No" (circle with a slash through it) symbol on muted clips, but now just grays them out which can easily be overlooked.


 
I miss the circle with slash.  
2014/03/03 15:45:51
Splat
I can reproduce this bug #1.
2014/03/19 09:47:36
Splat
According to Jlien X not fixed in X3E.
2015/11/03 12:56:53
lingyai
icontakt
A known take lane issue officially confirmed by CW recently. Below are the steps to reproduce it if you're interested...
 
1. Create a new project.
2. Drag a file (either MIDI or audio) from the Browser into the Track view Clips pane (this creates a track).
3. Drag the same (or a different) file from the Browser into empty space of the Track view Clips pane (this creates another track).
4. For each track, click the Take Lanes button to show the lane.
5. For each track, click the Add Take Lane button to add a new lane. Now, you see two tracks with two lanes each.
6. For each track, drag the clip in the 1st lane into the 2nd lane.
7. Perform the following:
(A) Copy the clip in the 1st track's 2nd lane by Ctrl+C, select the same track's 1st lane, and then paste the clip by Ctrl+V.
(B) Copy the clip in the 2nd track's 2nd lane by Ctrl+C, select the 1st track's 1st lane, and then paste the clip by Ctrl+V.
 
[Expected Results]
Both (A) and (B) result in pasting the clip into the selected (destination) lane, which is 1st track's 1st lane.
 
[Actual Results]
Both (A) and (B) result in pasting the clip into 1st track's 2nd lane.
 
 
Issue#: CWBRN-24086
Reported on Feb 13, 2014
Confirmed and submitted to development on Feb 14, 2014




I was at least relieved, intially, to see that I was not the only one having this problem, but then got pretty bummed out to see that, despite having been confirmed and sent to the bakers some 21 months ago, the bug persists in Platinum Hopkinton.   
 
Sometimes I can work around by copying the clip, and, provided there is a large enough empty space somewhere to the side of the clip (i.e. in its home lane), set the now time to the empty space and go Edit / Paste; and then grab the resultant copy with the Move tool and drag it down to appropriate space in the new lane. 
 
But inexplicably, sometimes (like now, when I really need it to happen) I can't -- it just won't work, and instead, what the OP notes occurs. 
 
Little (inexcusable) bugs like this really screw up my workflow. Having them fixed is worth a lot more to me than new features each month. I'd rather have what should be a bread-and-butter, 2 second editing operation actually take 2 seconds, than get Style Dials or what-not.  Get the basic plumbing before thinking about jacuzzis, grandma always said...
 
Anyone else have ideas for workarounds? 
 
How does one check in with the Bakers to see if there's any progress likely? 
 
 UPDATE (solution?) : After posting, I think I found a way to make the unreliable workaround I just described work. One you've got the copy made, right -click it, choose Bounce to clip, and then it can be moved (with the Move tool) to another position in another lane. At least that's what's happening here -- can any one else reproduce?   
 
Still, kind of irritating, the 40 minute detour it took to get here. Bakers! Please fix for us, and our children, and our children's children...
12
© 2026 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account