Beepster


And everyone who has used layers will have X1 or another earlier version of Sonar at their disposal. If they bothered me THAT much I would just use X1 for my tracking then open the project in X2 for mixing. I just don't get it. 

Ugh... if digging lanes makes me an arsehole then so be it. I like them. Lanes rule. LONG LIVE LANES!!!

You keep implying those that prefer or miss Layers want to do away with Lanes entirely, why?
No need to rant.
There are good arguments for both, nothing is written in stone code wise.
Why not have both if possible or an option to use either one?

With 27 Lanes I think I would struggle with my method.

my method.

1. Record takes
2. Open take lanes
3. select all take lanes
4. cut where transition is to take place
5. any more transitions required? y-goto 3, n-goto6
6. use ctl mute to select best parts (or erase unwanted parts)
7. close take lanes
8. effect crossfades
9. QED

works a charm and if you might need unused bits use selective mute instead of erase. But with 27 takes I would struggel, normally at most I have maybe 6 takes.

You keep implying those that prefer or miss Layers want to do away with Lanes entirely, why? No need to rant. There are good arguments for both, nothing is written in stone code wise. Why not have both if possible or an option to use either one?

Because I've seen a LOT of serious ripping on them saying they should be removed. I would like to see both implemented not for my own needs but because I like to see others be able to work the way they like.

I'm also writing which digs up all my darkness. So ya'll are getting little slice of that. Sorry. I should probably just go away while I do this. Cheers.

But he could accomplish exactly what he wanted to do before with Remove Empty Layers/Rebuild Layers.

 
Hmmm....   I don't see (m)any empty lanes in that picture.  It's difficult to tell what type of logic would be needed to consolidate them - something I would like in general - and the result might be a wee bit difficult to gage as far as what was recorded when. 
 

Funkybot


I'm with Beepster on this one. Looking at that project, I can't for the life of me figure out what the OP was going for there.

1. Why are there so many takes? 27? What is this project that you have so many takes of a single track? 

Hey Funky - 


Here's my workflow - and yes, it may be idiosyncratic:


I was laying down the bass in sections. I had a guide track, and I was following along. Very short recording, a few bars at a time.
So I have my audio track, record-enabled, and no, I did not expand take lanes. I didn't have any lanes, it was a new audio track.


Also, I was working from the end of the project backwards towards the start. So sue me :)


When I'd finished, I decided to trim up the beginning and end of each clip, to reduce unwanted noise. I knew I would have to expand the lanes at this point.


That's when it looked more or less as the screen shot, except I was zoomed in and could only see grey. I had no idea that each stop-start was creating a fresh take lane. That's insane to me, layers didn't work like that.


I realize now that, if I want to record a track in this fashion, I really need to expand take lanes FIRST, add a couple of empty lanes, then record into them, alternating. The only problem with this is, when you do this, you can't hear any existing recorded material in the other lane (even when "Sound on Sound" option is selected in preferences). And if you record into the same lane, you can accidently delete existing, non-playing clips. F*ck that.


It's just messy, it doesn't correspond to my workflow. I can't be the only one who records piecemeal on certain instruments.


Back to reading the rest of this thread now :)

bapu


Maybe I'm a dolt, but if that OP situation was mine and I wanted all those takes combined into a concise single track I'd just bounce that 'laned' track to another track. And delete the 'laned' track.

Actually that's how I do it.

/POST

That's exactly what I want to do - once I've cleaned up the clip start/end points, which is what I was about to do when I took the screenshot.

Okay... so lemme get this straight. You knew there had been a major change to how takes are handled. You didn't read up on how they work or experiment with them to see what would happen. You recorded into a track blindly with the lanes closed creating a total mess and were shocked when you opened the lanes. Then instead of cleaning it up like you just said you were going to or asking the forum for some advice you take a picture of the mess, start a thread saying it's the apocalypse (which quite literally means the end of the world) and act like this is Cakewalk's problem.

There a lots of people with legit problems... like really bad ones that don't act like the sky is falling. If you want help ask for it. This is completely over the top for no reason. BTW I have no idea what you are talking about as far as not being able to hear previously recorded material. There is a setting that will mute the previous takes automatically. If you want to hear that material you can disable this function in the preferences recording/playback menu or manual right click > Mute/Unmute the take you want to hear. I may be misinterpreting that problem but any take that gets recorded is audible if you make it so. Perhaps the previous take is getting washed out by your input signal. In which case the take you want to play over should be in a different track so you can adjust the playback level to your liking.

Please change this thread title. It is not a freaking apocalypse. 

Yeesh.

Beepster wrote:

[..] You didn't read up on how they work or experiment with them to see what would happen. 

Actually, I have. But this behavior still surprised me.

You recorded into a track blindly with the lanes closed creating a total mess and were shocked when you opened the lanes.

Yup. I guess I was expecting something more compact. 

Then instead of cleaning it up like you just said you were going to or asking the forum for some advice you take a picture of the mess, start a thread saying it's the apocalypse (which quite literally means the end of the world) and act like this is Cakewalk's problem. 

1) I have been cleaning it up this afternoon. 
2) I think I got some advice. 
3) I think it's a funny picture. 
4) I think it is kinda Cakewalk's problem or at least, I would like to make it so.

Please change this thread title. It is not a freaking apocalypse.

Done, because it's easy to do, and being flippantly over-the-top is always dodgy on a forum. 

I have no idea what you are talking about as far as not being able to hear previously recorded material. 

See this thread - you actually helped me via proxy on that one. I still think it's a bug, though. I've filed a report.

Okay. Thank you for changing the title. Sorry for flipping out but I'm a little on edge today and the negativity around here has been wearing me out. I'll help you whenever/however I can. All you gotta do is ask. Cheers and again... sorry for flipping out.

BTW there are some new vids in the stickies sectio of this sub forum about X2. I haven't checked them out yet but I'll bet there is some stuff regarding the lanes in there somewhere.

Beepster


And everyone who has used layers will have X1 or another earlier version of Sonar at their disposal. If they bothered me THAT much I would just use X1 for my tracking then open the project in X2 for mixing. I just don't get it. 

Ugh... if digging lanes makes me an arsehole then so be it. I like them. Lanes rule. LONG LIVE LANES!!!

Not so easy.  Open an X1 project in X2a, and I get all the layers I had deleted for each track in X1 back again in X2--as empty lanes.  Then I have to manually delete each empty lane.  That's just one of the many weird quirks of lanes in X2.
 
To someone else above:  what's wrong with 27 takes?  I sometimes do 50+ takes of a single guitar part and comp the best ones.  Comping was a hell of a lot easier in layers.  Lanes have made my way of working (many takes of certain parts) much more difficult.  That's why I'm just using X1 indefinitely.
 
DEATH TO LANES!!!!