Working on a pretty involved electronica tune with 40+ tracks.
 
The amount of glitches (not sound, but software) that I have encountered has really left a bad taste in my mouth.
 
Autosave works whenever it wants. It has no correlation to the settings I have.
 
 
I cut clips and they refuse to move (no matter if I have Snap To Grid on or not) to the first tick of the measure unless I remove the offset in the clip pane. I honestly have never seen that offset thing happen before. Then, later they move again! And if I try to nudge them back into position, they disappear!

I have a 1/4 measure tempo change in bar 70. Bouncing synths has shown everything after that measure to be offset late. 
 
The kicker is the ProChannel. I just had a glitch where EVERY HIGH BAND IS SUDDENLY NAILED TO +16. As I got to each track and take it back to 0, the graph doesn't budge. I have to turn off the eq to get the graph correct.
 
Seriously, Cake: WTF? I have been with you guys since v6, and this stuff just. keeps. coming.

jamesyoyo

The kicker is the ProChannel. I just had a glitch where EVERY HIGH BAND IS SUDDENLY NAILED TO +16. As I got to each track and take it back to 0, the graph doesn't budge. I have to turn off the eq to get the graph correct.

That one is a killer! When that happens, just scrap the project. Seriously. I've had that happen on a lot of projects and once it starts ... it's like something gets corrupted and it does not stop happening. When it happens once, it will come back in that project. :(

I was remixing a project the other day ... took hours. Out of the blue, all of the 'Gain' sliders maxed out and I couldn't undo it. I had to go back to each track and reset them. Keep in mind, they all weren't set to zero ... I had just got done setting them all up.

Seriously, Cake: WTF? I have been with you guys since v6, and this stuff just. keeps. coming.

Sorry to hear that James. I know you delve in to Sonar a lot deeper than I do. Maybe some of these guys around here will listen to you and wake up a little.

Have you seen the forum today?

It was a war zone over this kind of thing.

They are either going to have to fix this crap or shut the forum down to keep it at bay.

Hey James!

I've had a lot of problems with X2a (which I installed this week) ... but its better than 853 ... my former 3-legged horse.

I have a similar apparent problems with the clips ... 'sometimes' not moving after slicing them.  I'd have to 'work-around' in various ways :).

X2a is not that elequent, but enveloping tracks 'seems' faster now (most of the time).

ProChannel EQ "HIGH BAND" woes?

 ... I'm hoping that's a Sonnitus EQ *crossover-bug* or something (in my case, I've imported several projects from 853 where Sonitus EQ doesn't update to PC-EQ quite well ... and gets erratic.

Bouncing Synths has had other peculiarities for me (like girthless drums and such) ... so I usually export synth audios to the windows-desktop at 0-volume and no effects and drag it back into the project.

('Hopefully an X2b is around the corner)

Blessings,

hi james:
just curious why you upgraded to X2-was it because X1 didn`t meet your requirements or was it because X2 offered more production wise.
not being provocative but wouldn`t it be better to rollback to a version that was stable for you rather than acting as a de-facto beta tester for Roland with the obvious frustration you are experiencing,until the inevitable patch comes out?
no offense intended!
 

This verdict for you!!X2 is the best PRO DAW in the market for me.Best

There really must be more variables at play. X1 on my laptop is quite a mess. X2a on my new desktop with RME interface is the most stable environment I've ever worked in.

Yes I am seeing some real quirky things happen also in X2a, however I'm yet to seen the pro channel eq glitch.

I had a new one happen to me tonight - slip editing a clip while playing the project and all of a sudden there was no audio from any of the clips on the same track as the one I edited! It was as if that track was magically muted after I edited one clip. The only cure was to re-open the project.

I know a lot of you are having problems with X2 and X2a and understand the frustrations. I so far seem to have escaped the issues and with X2 andupdates to  X2a on Win7 and since upgrading to Win8 have had no crashes, sticky fadders or pro channel madness. Ok not been pushing it too hard, most of my stuff is Superior drummer on seperate outs, bass guitar, three or four other guitar tracks and the occassional VST synth. A hand full of FX, Breverb, TH2, delays the usual stuff, and for checking mix I have ARC set up. All runs smoothly.

I installed X2 along side 8.53 on XP. I then installed Win 8 over the top of that installation and added X2A. I had all sorts of major problems. Cakewalk support suggested a clean reinstall of X2+X2A deleting all registry entries. I decided to go one step further and re-install Win 8 on a clean C Drive and then installed X2 + X2A.

The difference in X2A functionality was striking. Most of my issues, and all the big ones, went away. I still have some minor bugs (mute button in mute/solo group, C++ runtime error when exiting X2A project with Virus TI which is probably not Cakes fault anyway ) but nothing stopping me getting work done.

If you are having problems, if you can, try a clean install (or at least delete Sonar registry entries). it made a big difference for me.

James it's the same opinion I have.

It's seems that X2a doesn't like my video card nor my Roland
UA-101....or my system at all.
I go back to many years with to many versions to not realize that
this version has many, many issues.

Finally made it through my first project with it. Very disappointed.