During a session today, I realized a few things X2a needs: 1) Needs to be able to listen to previous Lane when tracking a new one (ala punch in without punching in the traditional risky way); I have a vocalist who liked to track in lines (punching in and out), versus takes. Doing the same on guitars with multiple mics takes tons of tracks. Can't do this with Lanes at all, because the previous Lane mutes when the track is set to Record. Well, most of the time this is the case. 2) X2 is REALLY hard on I/O during tracking 20+ tracks at 96Khz. I had many issues today with Drop-Outs. The band was ready to pack up and leave. I had to crank up the playback latency to 512 to keep this from breaking again. This was after uninstalling nearly everything else on the system. 3) PLEASE fix the bugs in the T(x) lanes! What a pain to deal with!! If you haven't seen them, you're one of the few. Cakewalk knows them. They still exist in X2a. 4) Track View needs to be re-thought. It's a bit disorienting at times compared to X1. Also, is there a minimize height for ALL tracks at once? 5) The Mute buttons on tracks and lanes are not always indicative as to what's going to happen. For example, if you Mute a track, but none of the lanes, the lanes may still (at times) play back anyway. I think this is really a bug. 6) When zoomed out, enabling the Loop markers places them so close together that you have to zoom in really far to split them up. Could they be deployed at a useful loop start-start distance which can be edited quickly when zoomed out?

If you are tracking a band push the latency slider to the far right 4096 or whatever- that's the beuaty of recording audio, you don't need low latency, and you don't need it when mixing or mastering either.

Looks like another noob rage thread.

brconflict


4) Track View needs to be re-thought. It's a bit disorienting at times compared to X1. 

Well, just shows you can't please all of the people all of the time. I think Track view was greatly improved in X2. Auto track zoom is my favorite new feature.

brconflict


During a session today, I realized a few things X2a needs: 1) Needs to be able to listen to previous Lane when tracking a new one (ala punch in without punching in the traditional risky way); I have a vocalist who liked to track in lines (punching in and out), versus takes. Doing the same on guitars with multiple mics takes tons of tracks. Can't do this with Lanes at all, because the previous Lane mutes when the track is set to Record. Well, most of the time this is the case.

Shouldn't do. The same take will mute if punching into a specific take but if just punching others definitely should be audible. I usually mute the track to stop that. Have you checked your recording preferences?

2) X2 is REALLY hard on I/O during tracking 20+ tracks at 96Khz. I had many issues today with Drop-Outs. The band was ready to pack up and leave. I had to crank up the playback latency to 512 to keep this from breaking again. This was after uninstalling nearly everything else on the system.

I don't use 96Khz so don't know the answer to that one but obviously that is also interface dependent as well.

3) PLEASE fix the bugs in the T(x) lanes! What a pain to deal with!! If you haven't seen them, you're one of the few. Cakewalk knows them. They still exist in X2a.

You'll need to be specific, the only bug I've seen so far is the T0 bug but that seems to have gone in X2a. There are a few design 'issues' though.

4) Track View needs to be re-thought. It's a bit disorienting at times compared to X1. Also, is there a minimize height for ALL tracks at once?

I think you may be getting confused by autozoom. Turn that on & off with Shift+Z, it's a feature that I personally love at times but if you want X1 behaviour turn it off. To minimize all in one go press Ctrl+A then hold shift and resize one to minimum.

5) The Mute buttons on tracks and lanes are not always indicative as to what's going to happen. For example, if you Mute a track, but none of the lanes, the lanes may still (at times) play back anyway. I think this is really a bug.

Can't say I've ever seen that.

6) When zoomed out, enabling the Loop markers places them so close together that you have to zoom in really far to split them up. Could they be deployed at a useful loop start-start distance which can be edited quickly when zoomed out?

Would selecting the region and then pressing Shift + L help? They follow the last setting anyway so all you have to do is open them up in the first place.

"Looks like another noob rage thread."
I think that's a little harsh.
Lanes are "buggy"; empty lanes, "holes" between lanes, slip edit and fade issues: = BUGGY.
Can't comment on the 96k, what are your system specs?
The big question here is, Why are you tracking a paid session with X2?
X1d Expanded is a SOLID & ROBUST audio production suite.
I've been working in X2a on a couple of covers the past week, constant issues, "little niggles", crashes; I love the "look & feel" but man!
Notice I said "covers", at my age I can't handle the left brain/right brain stuff in the same session.
One single issue and creativity is out the window...
I know the Bakers hate this but look at the history.
Sonar 8, 8.5, X1, X2; none of these are "right" when installed off the DVD's.
8.5.3 very solid, X1 wasn't "stable" until the C patch; "D" is solid; that's the history.
X2b hopefully will tie it all together, until then BR; I feel you pain!

Tom

Thanks, Tom. You know exactly my perception of Sonar. And I was wrong to track a paid session with X2. That is my fault. I expected to be accused as a noob rager because I'm frustrated, but I don't know how else to explain what I'm really not liking. I feel I've had more problems with basic functions in Sonar than I did with other DAW's in the past. X2 is pretty amazing when you list everything it really can do, but simply, I have more issues with basic performance when in Production/Sessions than I do when I'm trying to use some of the many awesome tools and special features of Sonar. I still feel X2 is a feature-rich bundle of incredible gems, but it seems the development framework is giving me lots of trouble. I will respond to a few niggles here: 1) For muted Lanes, I just have to create new tracks for tight vocals where the singer needs to do a lot of punch ins where the end of one word flows into the beginning of the next word. Cumbersome, but we did this. I'd prefer if I could do this in Lanes instead. I get lost quickly in the newer Lanes vs X1's Layers. I'll just track in X1 next session. I disabled Auto-Zoom as well. If I could change the color of Layers vs. the actual tracks, and maybe color them each individually, maybe that would help. That mono-tone cold, gray gets me lost. It'll get better hopefully in the future. 2) For the Drop-Outs, I disabled Auto-Save, and haven't had any more issues. I dunno if that should be happening, anyway, but that's what fixed my issue. 3) Yeah, I saw the T(0) before X2a in less than 2 minutes after I first started X2 for the first time. On Saturday of this last weekend, I saw issues where I would see two T(1)'s or two T(2)'s. One would have audio, and the other would be empty. If I deleted one, the other would go with it. I also had some occurrences where a new Lanes would be added "above" the previous lane, which seems only cosmetic. 4) Yeah, the Mute buttons were unpredictable to some degree. In my case, even though the Track was muted, all the Lanes would still play, unless they were each individually muted. Didn't make sense to me why. However, if the track wasn't muted, then I muted the Layer, the Track mute button would light. Very confusing, to say the least. 5) For the Loop markers, and keep in mind I sincerely can't use Sonar's Zoom functions the way others seem to be able to. It messes with my head to badly. X1 was even worse. So, i still have to zoom way in to split up the yellow loop markers. Just more work for me.

I also have frequent problems with the mute buttons on lanes.  This is not just noob rage.  There is something wrong with the GUI in X2a.  Muting a lane can randomly have no effect, and the lane plays back anyway.  This is only the beginning of my problems with lanes.

brconflict


Thanks, Tom. You know exactly my perception of Sonar. And I was wrong to track a paid session with X2. That is my fault. I expected to be accused as a noob rager because I'm frustrated, but I don't know how else to explain what I'm really not liking. I feel I've had more problems with basic functions in Sonar than I did with other DAW's in the past. X2 is pretty amazing when you list everything it really can do, but simply, I have more issues with basic performance when in Production/Sessions than I do when I'm trying to use some of the many awesome tools and special features of Sonar. I still feel X2 is a feature-rich bundle of incredible gems, but it seems the development framework is giving me lots of trouble. I will respond to a few niggles here: 1) For muted Lanes, I just have to create new tracks for tight vocals where the singer needs to do a lot of punch ins where the end of one word flows into the beginning of the next word. Cumbersome, but we did this. I'd prefer if I could do this in Lanes instead. I get lost quickly in the newer Lanes vs X1's Layers. I'll just track in X1 next session. I disabled Auto-Zoom as well. If I could change the color of Layers vs. the actual tracks, and maybe color them each individually, maybe that would help. That mono-tone cold, gray gets me lost. It'll get better hopefully in the future. 2) For the Drop-Outs, I disabled Auto-Save, and haven't had any more issues. I dunno if that should be happening, anyway, but that's what fixed my issue. 3) Yeah, I saw the T(0) before X2a in less than 2 minutes after I first started X2 for the first time. On Saturday of this last weekend, I saw issues where I would see two T(1)'s or two T(2)'s. One would have audio, and the other would be empty. If I deleted one, the other would go with it. I also had some occurrences where a new Lanes would be added "above" the previous lane, which seems only cosmetic. 4) Yeah, the Mute buttons were unpredictable to some degree. In my case, even though the Track was muted, all the Lanes would still play, unless they were each individually muted. Didn't make sense to me why. However, if the track wasn't muted, then I muted the Layer, the Track mute button would light. Very confusing, to say the least. 5) For the Loop markers, and keep in mind I sincerely can't use Sonar's Zoom functions the way others seem to be able to. It messes with my head to badly. X1 was even worse. So, i still have to zoom way in to split up the yellow loop markers. Just more work for me.

Paragraph -Wonderful concept really

did U get lost, s-man? heh heh.

To OP: It does make things easier to read when you put each #'d item on it's own line.

ie:
1) xxxxx

2) yyyyy

3) yme yme yme

etc.


Steve

It would be nice if you could in Firefox ! I have to use IE to post formatted messages here and everytime I do I'm infested with tracking cookies. If I put my cookie handling higher the forum no longer works at all. So I'll forego formatting once in a while, and pardon those in the same predicament :-)