Hi Everybody -
 
I've been a user since Pro Audio days and please believe me when I say I sorta know what I'm doing, have decent equipment and all that jive. However I firmly have come to believe there are serious problems with the X3(C) patch.

Since I installed the "C" patch -

1. Ran into the now infamous Console Emulator "what the hell is that noise ?" bug.  Applied workaround (uncheck 64-bit processing ).  Odd but works. BTW - this chewed up a few hours.
 
2. For no apparent reason Project A hung in X3(c) while trying to substantiate a Breverb on a vox PC bus. Figured autosave would "save" me.  Wrong.  Dreaded "truncated file" message. Ummmm...ok.  Tried "shift" while launching the file.  Nada. Zilch. No time for this as I have a semi-deadline.

3. Opened up the ORIGINAL Project A in X2(b).  Substantiated Breverb on exact same vox PC buss (because I am a glutton for punishment evidently).  No problems.  Finished mixing, mastering, shipped to customer.  Happy customer. Yay.

4.  Because as I mentioned earlier I am a glutton for punishment I (hours later - as in 30 mins ago) I opened up Project B in X3(c) for another customer (with no looming timetable). Spent a good deal of time reworking a lot of honestly shoddy tracks and got them sounding good enough to export.  CTRL-A time. And it froze. I've NEVER had any Cakewalk DAW freeze on me when doing a CTRL-A prior to export.  WTF ?? Holding my breathe I went to my autosave and got....drumroll please....the "truncated file" message.

5. Opened up ORIGINAL Project B in X2(b).  Performed pretty much the same mixing (btw - by this time I was NOT happy to have to recreate what I had already accomplished  the previous 1.5 hours). CTRL-A, export, load into my mastering toys and voila.  Completed.  Yay.

The score ? Sonar X2(b) 64 bit - 2, Sonar X3(c) 64 bit - 0

Guys - what the heck is going on ?
 
Bakers - would it assist you if I sent one of the "truncated" autosave .cwp's ?  

Argh....


PS I had forgotten how much I liked the track header color change when you selected a track in X2(b).  Can we please get it back in X3 ?

Interesting to me. Fractalite and Long time Cake user.
Narrow it down to Breverb? 
Getting ready to move from X2 to 3.
Old plugins?
These issues always pop up for me on upgrades.
X2b is very stable for me right now.
 
Uncheck 64 bit?? to get clean sound??
Not good

OK can I ask this.... is there a way until these issues are fixed by the bakers to painlessly revert back to X3b? Seems many if these problems stem from X3c that were otherwise not a problem in X3b. Will repatching X3b work?

studio343
OK can I ask this.... is there a way until these issues are fixed by the bakers to painlessly revert back to X3b? Seems many if these problems stem from X3c that were otherwise not a problem in X3b. Will repatching X3b work?

If you have a system restore point prior to your download of X3c, that'll get you back to X3b in about 10 minutes or so.

Gregmang
Guys - what the heck is going on ?

Inadequate project backups before trying a new patch/release?

Lynn

studio343
OK can I ask this.... is there a way until these issues are fixed by the bakers to painlessly revert back to X3b? Seems many if these problems stem from X3c that were otherwise not a problem in X3b. Will repatching X3b work?

If you have a system restore point prior to your download of X3c, that'll get you back to X3b in about 10 minutes or so.

I've discovered a quicker/easier way, IMHO.
 
Before applying any patch....
 
copy "{your-path}Cakewalk\SONAR X3 Producer" and "{your-path}Cakewalk\Shared Utilities" folders somewhere safe. Restore those if the applied patch is suspect.

that's a great idea!! thanks.

Shame though we would have to resort to that. Any chance that the baskets are working feverishly on these issues and a fix is imminent?

bapu

Lynn

studio343
OK can I ask this.... is there a way until these issues are fixed by the bakers to painlessly revert back to X3b? Seems many if these problems stem from X3c that were otherwise not a problem in X3b. Will repatching X3b work?

If you have a system restore point prior to your download of X3c, that'll get you back to X3b in about 10 minutes or so.

I've discovered a quicker/easier way, IMHO. Before applying any patch.... copy "{your-path}Cakewalk\SONAR X3 Producer" and "{your-path}Cakewalk\Shared Utilities" folders somewhere safe. Restore those if the applied patch is suspect.

studio343
 Any chance that the baskets are working feverishly on these issues and a fix is imminent?

I have no idea if they are. Since the presence of the bakers on the forum is quite high in recent days one can hope.

Gregmang
 
PS I had forgotten how much I liked the track header color change when you selected a track in X2(b).  Can we please get it back in X3 ?
 

 
You just need to go to Preferences > Customization > Colors and uncheck the "Show strip colors." The track strips are still color-coded (the leftmost section only) so I think it's better than X2a.
 
Btw, why do people type X2b when they mean X2a? This is the third time I witnessed it. 

Helpful hint on ontrack header,
Sorry Yes X2a, for me, duh