brconflict
Had some more weirdness in X2a today. It's been "relatively" solid for the most part today, aside from just the burning issues with Lanes and Mutes, which just means I still find it twice as easy to save a take and open a new template rather than trust the Take Lanes as is, but we ran into some really odd behavior today.
1) Had cases where only two or three tracks were selected, but when you did Ctrl+Click on a selected fader and move it, ALL faders moved, not just the two or three selected.
I was running in to this too. There seems to be a severe problem with how Sonar 'selects' tracks for some folks.
I keep everything in folders. I hit Ctrl-F to bring everything in to view. I had one guitar track highlighted in a project and I was splicing it up and removing dead space between fill in parts. I play it back ... and everything above that track in other folders (but not the other tracks visible in the guitar folder), even though they were not highlighted, were spliced and gone exactly where I had spliced and trimmed the guitar part.
It happened a lot until I started getting in to the habit of hitting Ctrl-Shift-A (This de-selects everything as apposed to Ctrl-A that selects everything.) before I select anything that I'm going to adjust in a group or on it's own anymore. It's become my second nature keystroke sequence like Ctrl-S used to be before I set up Auto-Save.
I had it ruin hours of work when I was setting up my gains on a large project one afternoon. The problem is, some adjustments can't be undone ... and with one slide of the bar on one track that wasn't even highlighted ... all my gains pegged out and I had to redo it all.
2) Had a case where meters weren't working for a track until I clicked the track to select it. then the meters started working.
I've seen that a couple of times, but not to the extent that I've seen the select problem. I mainly see it with Pro Channel modules when it does happen. When I see that kind of thing start to happen, from experience, I know something has gotten whacked in the project and I try to finish it immediately, or if I'm not too far in, I scrap it and start over.
3) Had a track record, but when I stopped the transport, the recorded audio disappeared. Even Ctrl+Z and Redo didn't recover the audio. It's like it never recorded to disk.
Had that happen a couple of times in one project. I attributed it to the project being corrupted because I only saw in that one, but I can confirm I have had this happen.
4) Got a mono track that has nothing but a stick-count on it. It's Panned to the center, but the audio is only in one output (Left-channel). The track is identical to the track the stick-count came from and routes to the same buss.
Make sure you don't have something set in Offset Mode. That has thrown me off a few times. Now ... you may say, "I've never activated offset mode." Well, you didn't ram all your faders up either ... Sonar did it. ;) Hit 'O' to go in to Offset Mode. That overrides all your track volume/pan settings in normal mode. You can tell when you are in offset mode by '+' signs showing up next to the words 'pan' and 'volume' on your tracks and buses. It will look like this ... "Pan+" and "Volume+". Keep in mind, on Midi tracks "Velocity+" is always like that even if you are not in Offset Mode.
Obviously, none of this can be re-created, but this is making me scared to continue using X2 at all. I don't want to try and track drums again until I know full well every single track is going to record well. After today's session, I'm putting X2 away completely until X2b comes out. I just hope Cakewalk can actually find these issues and fix them.
Don't give up on it yet. Try the Ctrl-Shift-A tip, check offset mode for the panning problem, and as for the recorded track disappearing, that sucks, but I have seen that once and ended up scrapping the project. Fortunately I wasn't that far in to it, and hey, it's not like I'm in a multi-million dollar studio, or doing this for a living. I can completely understand if you don't want to deal with it.
You touched on something there when you said it can't be re-created. I saw another response to your post here asking if you reported it ... the problem is ... if you can't come up with a repeatable scenario ... you're basically wasting your time sending in a trouble report. For your own satisfaction and to keep record, it's a good idea, but don't expect anything to addressed unless you can come up with a repeatable formula to make all this happen on their end.