• SONAR
  • help with take lanes (p.6)
2016/02/12 14:35:33
Beepster
Paul P
Beepster
Already mentioned this one earlier. Select the Lanes you want to remove (they select just like tracks do with a blue button in the top left corner of the lane controls... admittedly there should be some indication there that there is a selection square there but it is). So Shift or Ctrl select the Lanes you want to go away, hold Ctrl, Click the X on one of the selected lanes. They will all go away.



Thanks Beep.  To get rid of all of them it's easiest to just drag out a selection region across the lanes which selects them all, then Ctr-click the "x".




Good one. Haven't tried that. I think you can just drag down the left side to to multi select (like you would with a series of tracks) but I generally am very cautious with my selections so select all particular and crud, inspect, sometimes deselect all ('cause I get paranoid) then reselect... THEN delete.
 
Bit of a time eater but it helps avoid my classic brainfart spazzo moves... which tend to waste WAY more time. lol
2016/02/12 17:39:07
Paul P
Beepster
I think you can just drag down the left side to to multi select (like you would with a series of tracks)...



Thanks again for this bit, I didn't even know you could select tracks by clicking on the first (blue button) then dragging onto the others.  So yes, this does work well for selecting clips with the same procedure, and then you're right there for the ctl-click.
 
2016/02/13 06:26:30
Kylotan
Beepster
Yup. I see it. Those empty lanes are likely from you yanking out the clips to other tracks. As far as that screenshot... dude, flatten that bugger. As you said multiple times you only have 1 take at any give time range (but I was going on the premise maybe you had the occasional section with more than one section you wanted to test out for your final).

They're separate sections. They get moved forward and backward in time to arrange the song. Flattening them breaks that. I might have 20 sections in a song with a ton of unused sections elsewhere in the project. In fact, flattening breaks the whole project. It's the wrong paradigm for this way of working.
 
Also... as I said upthread, if you want all those little snippets to record into the same lane I'm pretty sure all you have to do is arm the desired Take Lane for recording.

You're right, but it's just a hassle. I want to arm the track (one click), not open up the take lanes view, arm a take lane, close the take lanes view (three clicks). It's small but it adds up.
 
Personally if I were forcing that type of workflow I would actually use TWO lanes and switch the arm status between them. So I could record directly into my MAIN lane and if at any point there was going to be an overlap of clips I would arm the second lane and record that part there. That way instead of having auto X-Fades or messing with selecting clips to draw them to the surface for editing I could just have the overlapping clips in their own lanes and edit them independently without the fuddle duddle.

Why would I want to do that when I could just arm the track, record into the track, and slip edit automatic crossfades as needed? 8.5 did that. Platinum almost does that, but creates tons of take lanes into the bargain. I refuse to do extra work to compensate for this backwards step in functionality.
2016/02/13 06:39:31
kb420
Kylotan
 
Why would I want to do that when I could just arm the track, record into the track, and slip edit automatic crossfades as needed? 8.5 did that. Platinum almost does that, but creates tons of take lanes into the bargain. I refuse to do extra work to compensate for this backwards step in functionality.




Good point!  There should still be an option to go back to the old workflow.  I understand that some may find the new features to be better for their workflow,  but that doesn't mean that's the case for every user,  and in every situation.  
There needs to be an option to disable "Take Lanes" completely,  on a track by track basis,  and on a Global basis.  It's a WIN/WIN situation.  The users that like Take Lanes would still be able to use them.  The users who don't want to use Take Lanes can disable them. 
2016/02/13 07:53:24
wetdentist
i comp all the time & nary a take lane is created.  having had problems with them a couple years ago where audio would just disappear (leaving a grayed-out image of the audio that could make no sound, no matter what i tried), i decided to move on from normal comping. 
2016/02/13 08:05:18
Beepster
@kylo... I was pointing out a couple things that I, personally, would do in those situations.
 
You can just use the single lane like I originally stated. Also I think there is a prefs option that allows you to disable "Create New Lane On Overlap". Or it might be a Track Views Option. I'll check it out later.
 
@kb420... You've just been repeating the same thing. As I said earlier on you'd have to replace Lanes WITH something. "Disable them" doesn't make sense. There needs to be a clip management scheme of some kind.
 
@wetdentist.... That sounds like the Mute Tool muting areas of the clips. That was the old recommended way of "Comping" and... IMO... was horrendous (I just manually edited clips instead). Of course we don't have to worry about that now but if you ever end up using the old versions and that happens that's likely the culprit. The Mute tool still exists in SPlat too so it can still happen but the Mute Tool is kind of buried now so it's quite hard to trigger.
 
Cheers.
2016/02/13 10:28:41
kb420
Beepster
 
@kb420... You've just been repeating the same thing. As I said earlier on you'd have to replace Lanes WITH something. "Disable them" doesn't make sense. There needs to be a clip management scheme of some kind.
 
 



Have you ever used anything other than Sonar?  Have you ever used earlier versions of Sonar?  There are other programs that allow you to record without adding Takes,  especially for midi loop recording.  There are also programs that allow you to toggle Takes on or off.  
 
Midi loop recording without adding "Takes":
 
https://youtu.be/G6RqDMDqWuY?t=41s
 
Tracktion is only $60,  and yet they seem to have it mastered.  

https://youtu.be/_C8qcFDi15Q?t=4m10s 
 
In Sonar,  even if you set:
1.) Recording Mode to "Sound on Sound"  
2.) Loop Recording to "Store Takes in a Single Track"  and
3.) Uncheck "Create New Lanes on Overlap"
 
Sonar will create new Take Lanes.  You can see them in the arrangement because only the midi data from the final lane is displayed.   You'll see that all of the other "Takes" are underneath.  You will not see them in the midi editor,  but it's still there and it's just unnecessary for it to be there.  I know you can flatten it,  but what's up with all of the extra steps for something so simple?  
 
2016/02/13 10:58:11
Beepster
@Kylo... I just figured out how to make your workflow happen in SPlat in TWO different ways. It's quite simple.
 
Workflow 1: Parent Track
 
1) Go to Edit > Preferences > Project - Record then
  a) deselect "Create New Lanes On Overlap" and
  b) Choose "Sound On Sound" as the recording mode (not even sure that's necessary but it's what I did)
 
2) On any new tracks quickly open the Lanes and enable the Record Arm button on the lane (there should only be one empty lane at this point). Maybe this could even be setup as a Track Template so you don't have to do it every time.
 
3) Close Lanes. You really don't have to open them again at all if you don't want to and in fact for creating X-Fades the NEED to remain closed.
 
4) In the Track View Options menu make sure Auto Crossfade is selected (I think it's the default)
 
The result is you can record all your segments as you like. ALL of them will get recorded into that one lane even if you record OVER a previous take (I'll describe what that does in a minute).
 
If you want to create overlapped clips just select them in the Parent Track (with Lanes closed) and drag them into each other as you normally would. Your X-Fade is created automatically.
 
Now THAT action (creating an X-Fade) will unfortunately create a new lane and the more you do it you may end up getting more Lanes but SOnar does seem to recycle the lanes sometimes. Not sure what the circumstances are where that would happen. It does seem a little random and should be looked at by the Bakers because to me disabling the "Create New Lanes on Overlap" should at least keep it to ONE new lane for overlap.
 
BUT... it doesn't matter because you really shouldn't have to open Lanes any way. It just works in the Parent Track based on what I was just doing. You can just wait until you are done your structuring and flatten or just totally ignore it.
 
HOWEVER here is another workflow that COMPLETELY stops those extra lanes from happening and allows you to work COMPLETELY in the single Lane at all times. The only "problem" is you have to have that lane visible while editing and Auto Crossfades are done with the Comp Tool instead of forcing the fade across any overlap.
 
Workflow 2: Single Lane
 
So with all the same settings as before just record into the track. All clips will populate the same (armed) lane and if you record over part of an existing clip the new clip will "Overwrite" that section of the old one BUT the clip remains and can be slip edited out back to full size.
 
*Be careful though not to record over the ENTIRE old clip if you want to keep it because then it just completely gets overwritten and requires an Undo action to recover (thus losing the new clip)... so in that case just create and arm a second Lane momentarily or do it in another track.
 
You can drag the clips around wherever you want in the Lane and they will not cause any damage until you drop them. If you drop them to overlap another clip it will overwrite that section. At this point you can blend the clips and adjust the start/end points by just moving the split. This incurs the Crop Tool and it behaves normally EXCEPT because there are no other clips in other lanes it is purely a cropping/crossfade tool.
 
Sooo...
 
1) Arm Track and First Lane
 
2) Record your segments (with or without Lanes open). *Be careful not to completely record over other clips you want to keep but partially recording over them is fine and leaves them completely recoverable via slip editing.
 
3) With the Lane open drag the clips around wherever you like. Dropping a clip onto another or dragging it into another will make the selected clip overwrite the older clip (either partially or completely so again do not completely obscure any old clips you wish to retain). No action is taken until you "Drop" the clip.
 
4) Once the clip has be dropped where you want to create an overlap with another clip drag the split Left/Right to adjust where the first clip ends and the second begins. Drag up and Down to adjust the X-Fade (this is Comp tool action).
 
5) If you ABSOLUTELY need two clips playing at the same time in the same track without any X-Fade action (which I would personally use another track because multiple clips at once in one track sounds like crap to me but whatever) THEN you can create a new Lane and put the overlapping clip there. Both clips will be active and you can use the old editing features in the top half of the clips to edit them together.
 
At MOST you end up with two Lanes (and that's only if you want to clips playing full blast at the same time).
 
To make up for the extra screenspace taken up by the single Lane being opened you can minimize the Parent Track/Track Control area while editing. Just pretend the Lane is your track while you edit.
 
 
==================================================
 
Either of these workflows will force Sonar to do what you seem to want. Admittedly the fact Workflow 1 does create Lanes on X-Fades is a little weird and I think this might be a semi sort of bug or unintended design "flaw" (it should obey the Overlap rule set in preferences) but you shouldn't even have to be opening Lanes. I do think it might qualify as a Problem Report though because it does not seem to work as it should while editing and if it was only intended for Recording it shoudl be expanded to editing as well.
 
Workflow 2 requires Lanes open while editing but ONLY while editing and does pretty much exactly what you seem to want. The fact a lane has to be armed seems really inconsequential compared to how much you seem to want this style of tracking/editing.
 
In BOTH scenarios it really seems like WAY less work/hassle/confusion than how this would need to be done with Layers. Layers were insanely unpredictable IME and demanded a lot more post tracking futzing about. With both of these workflows, particularly the 2nd one, you can at least be certain of what's going to happen to the data.
 
After messing with this a bit and seeing how insanely reliable/predictable/easy it all is I cannot see how your rather simple tracking/editing needs cannot be accomplished without issue (and by simple I don't mean that in a bad way... it's just not a complex workflow compared to the spazzo crap I do).
 
It just may be slightly different. If the problem is "It's different, therefore I don't like it" nothing can be done except to move back to 8.5 as you track and edit. Maybe SPlat can be your mixing environment if you find any value in it at all. I also really don't think another DAW is going help much because they all seem to have elaborate editing/layer/lanes schemes. I could be wrong but it will likely be quite different than even the new Sonar.
 
For me though, as easy as that all is (it's very old school/traditional editing... almost like tape splicing) the proper Comping/Lanes workflow is just WAY faster/easier for me and allows me to REALLY do some crazy stuff that would have taken me ages to do before.
 
Anyhoo... I'm mostly posting this because other people HAVE apparently gotten something out of these posts. It would be nice if you gave these things a chance though because it's not nearly as backwards and cumbersome as you seem to think.
 
IIRC you just recently updated from X1 (layers). There were mountains of these threads at first before people started figuring it all out. One COULD say that "Oh those people just left... that's why no one complains anymore" and some people DID give up and move to other products (or stick with the old ones) BUT many many more, who were unhappy (quite vocally in some cases) eventually gave all this stuff a proper go and now like the new tools/methods way better.
 
I've given you (and others) lots of stuff to try/learn/experiment with. If you just give some of it a go and muscle through some of the growing pains (like we all did) you might see the benefit of these workflows.
 
Layers are dead and I seriously doubt they are coming back. Even if the Bakers had any interest in bringing them back at this point it would be next to impossible without destroying a bunch of other stuff. They just would not fit into the program anymore and it would likely cause a buttload of bugs.
 
Again... good luck with whatever you do.
 
Cheers.
2016/02/13 11:12:46
Beepster
kb420
Beepster
 
@kb420... You've just been repeating the same thing. As I said earlier on you'd have to replace Lanes WITH something. "Disable them" doesn't make sense. There needs to be a clip management scheme of some kind.
 
 



Have you ever used anything other than Sonar?  Have you ever used earlier versions of Sonar?  There are other programs that allow you to record without adding Takes,  especially for midi loop recording.  There are also programs that allow you to toggle Takes on or off.  
 
Midi loop recording without adding "Takes":
 
https://youtu.be/G6RqDMDqWuY?t=41s
 




I already said upthread I used to use Nuendo 2 which had no Lanes... but it STILL had a "layers" type scheme. I also goof around with Reaper and use some of the more basic audio recorders from time to time. I will eventually pick up Cubase and S1 for educational purposes to study them and use them for things Sonar can't.
 
My point was "DISABLE THEM" doesn't say anything. I don't need to see a video of MIDI Loop Recording. I know the workflow. I know what you mean. I know what you want and described ways to acheive it right now AND made suggestions as to how Cakewalk could implement what you want.
 
To imply that I'm an idiot for not being able to read your mind with your repitition of the vague statement "DISABLE THEM" is irksome and why I've been ignoring it until now.
 
If you want it to work in a specific way then YOU need to articulate it and in a way that makes sense/will fit into the current program design without breaking everything else.
 
It can be done. I have ideas for it myself. Articulate your ideas to start a discussion about it. Make a Feature Request with those ideas so the Bakers can see it.
 
"Disable them!" does not help you acheive your goal.
 
I WANT you to get what you need to work. It might benefit my own workflow but good gawd, man... explain yourself so there's a chance the ideas can be considered and implemented.
 
And again... I KNOW WHAT MIDI LOOP RECORDING IS! I know how to do it in SPlat!!!
 
It's not hard but yeah... it could be improved.
2016/02/13 11:19:10
Beepster
Oh and yes... I used X1 which still had layers and they were a nightmare for me. It's not 8.5 but my understanding is Layers worked more or less the same in both.
 
Which I also said upthread. If I had a copy of 8.5 around I'd play with it just to see what the fuss is about but honestly from all the vids I've seen using it really looks like it would be really clunky to use compared to SPlat.
 
© 2026 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account