• SONAR
  • X2a: Lane Pain -- Comping issues (weird delete/ move) (p.2)
2012/12/31 04:40:29
FastBikerBoy
If fading is a preferred comping method that is also easy.

  1. Split clips at desired points.
  2. Either Mute/delete clips not needed or select those that are.
  3. Select "Fade clips" from the clips menu, set your preferences and click okay.

If you click on "Only show when pressing shift" the dialogue won't open every time and use existing settings instead.

Each to their own but there's no need to drag clips around the lanes, although of course you can if you wish.
2012/12/31 05:07:33
Saxon1066
Tom Riggs


Even so I generally clone the track then mute and archive one copy and save the project before any comping. Just paranoid I guess.
A good policy!  I do it too, but the pileup of archived clips seems to be what caused performance issues for me in X2a.  The rewind to now time and undo/redo actions were sluggish.  I didn't have that problem with brand new projects with only a few tracks, but with larger projects and many archived tracks/takes, I can't use X2a at the moment. 
 
I still have weirdness when copy/pasting clips into new take lanes for comping with X2, but performance issues in X2a.  So I'm between Scylla and Charybdis.
2012/12/31 07:47:13
Tom Riggs
@Saxon1066 are you certain the tracks are archived and not just hidden. If so I think You should report you findings as archived tracks are not supposed to be processed in any way. I suppose if you had a very large amount of them it could cause disk issues.
2012/12/31 12:49:36
Keni
Tho I have a definite "extreme" dislike for the Lanes, if they are not supposed to allow movement from one to another it would be even worse than I'm currently experiencing... that's one problem I haven't had with the Lanes...

I can copy or move clips from  lanes on the same track or others....

I prefer working where I typically split/mute portions of takes until I finish with a song-length composite... Then I drag-copy the pieces to a cloned empty track... Finally archiving the original track and add a "archived" tag to the track name before hiding...

This way I now have a single track/lane for the part and an archive of all the original takes (hidden)

If it's a vocal track and I use V-vocal or such, I will often (tho not always) Bounce the track to another and archive/hide the intermediate track so my final track has no v-vocal or such...

But I also vary this approach when I feel the need/desire... there are more variations than I can shake a stick at! ;-)

For me Lanes aren't really much different than layers were other than their' screen appearance and the extra functions we had (even tho buggy)... But the screen real estate translates into constant adjusting/re-arranging of the screen in order to see what I need... Screen real estate has become an increasing difficulty since the release of X1 with larger buttons, more space between buttons and different grouping. I almost nver need the automation buttons read/write but I do need the archive button constantly. In 8.5.3, I could see the archive button and allow the read/write to remain off screen.... etc.... The list goes on....

So while working at "curing" the "screen clutter" some complained of in earlier Sonar releases, now we have the opposite... Lots of space wasted and lots of extra work created to manage that space all the time....

I now spend far more time adjusting the display in Sonar than ever before and it takes away from the music mind/work....

I sincerely hope that The Bakers are working at some solutions to these things even more than fixing the bugs that they still carry as it's made working with Sonar a constant repetitive drudgery (for me) in my work methods.... and yes, I have adopted some new methods in an attempt to use Sonar the way they seem to want to force us to work now which also makes my work slower and more tedious but at least I am working still...

I do love some of X's improvements but it seems most of them are related to the plugins in the PC which I could have easily received as dx/vst plugins and remained in 8.5.3 and been much happier...

Sorry.... I'm ranting again.... But I just did a lot of vocal tracks and compositing and I'm still shaking from the aggravation I felt while doing it...

Keni



2012/12/31 12:53:11
Beepster
Vid didn't work for me.
2012/12/31 12:59:25
VariousArtist
Beepster


Vid didn't work for me.


Sorry about that Beepster, I had the video set to "private" instead of "public", when what I really meant to set it to was "unlisted".  Please try it again....
2012/12/31 13:08:09
FastBikerBoy
So while working at "curing" the "screen clutter" some complained of in earlier Sonar releases, now we have the opposite... Lots of space wasted and lots of extra work created to manage that space all the time....

I now spend far more time adjusting the display in Sonar than ever before and it takes away from the music mind/work....

That's where screensets become really useful, setup the views you want as screensets and switch between them. Changes are really quick that way.

I can see why you are frustrated if you stay on one screenset and adjust that as needed. That'd send me crazy too.
2012/12/31 13:18:04
Beepster
Yup, working now. This is very similar to the issue I was having while editing. I wasn't sure until I saw that vid though. Essentially trying to select or move clips around was selecting multiple clips and it was causing some real problems. However it wasn't within lanes it was over multiple tracks but I wasn't working the same way you are so if I did I'd imagine I'd have the same issue. What I've been doing to avoid this is locking the Pos/Data in the Inspector on every single track not being edited and then making my cuts, moves, slices, etc on the unlocked track and it has been working. It is however a huge pain in the butt. 

All I can think of to solve this on the Lanes level of editing is to actually lock the individual Clips. I think they can be isolated for locking in this manner by Right Clicking or in the Inspector. Not sure though. I posted a thread asking the Bakers to take a look but they didn't stop in. Once I figured out my workaround I didn't bother emailing support because I've been busy. I was hoping the patch would fix it but it does not seem to be mentioned and I am not installing the patch due to all the complaints about it on here.

So yeah... I think you're gonna have to just lock stuff until they fix it. Thanks for confirming. If more of us send in bug reports maybe it'll get fix. It quite literally makes editing impossible without constantly locking and unlocking the tracks/clips.

Cheers. 
2012/12/31 13:26:45
Beepster
Oh and another workaround at least for the extra selections is to make your selection then use the Deselect key binding to remove the clips/tracks that you don't want selected. Ctrl + Click on the unwanted track I believe. I have tested this thoroughly though as I've just been using the Inspector to lock the tracks. It's easier since in a big project it's hard to scroll through everything to figure out everywhere that has been randomly selected.

Major MAJOR problem. Not sure why it's not being reported more often.
2012/12/31 13:36:05
VariousArtist
Beepster


Yup, working now. This is very similar to the issue I was having while editing. I wasn't sure until I saw that vid though. Essentially trying to select or move clips around was selecting multiple clips and it was causing some real problems. However it wasn't within lanes it was over multiple tracks but I wasn't working the same way you are so if I did I'd imagine I'd have the same issue. What I've been doing to avoid this is locking the Pos/Data in the Inspector on every single track not being edited and then making my cuts, moves, slices, etc on the unlocked track and it has been working. It is however a huge pain in the butt. 

All I can think of to solve this on the Lanes level of editing is to actually lock the individual Clips. I think they can be isolated for locking in this manner by Right Clicking or in the Inspector. Not sure though. I posted a thread asking the Bakers to take a look but they didn't stop in. Once I figured out my workaround I didn't bother emailing support because I've been busy. I was hoping the patch would fix it but it does not seem to be mentioned and I am not installing the patch due to all the complaints about it on here.

So yeah... I think you're gonna have to just lock stuff until they fix it. Thanks for confirming. If more of us send in bug reports maybe it'll get fix. It quite literally makes editing impossible without constantly locking and unlocking the tracks/clips.

Cheers. 
Thanks Beepster, but the REAL problem for me was less about moving clips and more about deleting unwanted takes.  What I think is occurring is that some of the lanes get assigned the same internal "index", so that anything you do to one lane might actually affect a completely different lane.  If you look at the video, you can clearly see that selecting one lane highlights a completely different lane.  Check the link below which should be positioned at the appropriate location in the video (about a minute in):
http://www.youtube.com/watch?v=KwsfmG2On6k&feature=player_detailpage#t=64s
 
See how selecting one lane also causes a select of another.  So while I delete one of these lanes because I don't want the take or it is empty, then the other one gets selected and deleted too!
 
This sample project in the video is actually a scaled down version of one that had many more tracks, lanes and stuff going on.  So while I was deleting takes I came to find out that I was losing much more than I intended.  Luckily I'm forever making backups and updating my own version number in the project name that I was able to recover what I was losing.
 
Locking the lanes won't change this behavior, although I appreciate the suggestion. 
 
 
 
© 2026 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account