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.

Or, can't you activate multiple backups and just use revert thingy?
Very useful.
 
It's on one of the Advanced sections in preferences.
 
EDIT: my bad - it was about patch reverting, not project reverting.
 
Save a couple of times, and then apply new patch to have something to revert to.

Please people.
 
When fixes and new toys are inserted in an older basic program,(  X2's upgrade to X3) the old shell is used and new things added. There will always be an occasional collision between the two and cake is going way beyond expectations as far as working with us to get this straightened out as fast as possible.

I've had point 4 on X3b too. Very frustrating. Generally speaking, what with the initial Waves issue, I've become very trigger happy on my CTRL+S.

Gregmang
 
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.

 
Yes, it chewed up a few hours on our end too. We are on this, and are aware of it's existence. 
 

Gregmang
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.

 
That is a frustrating experience, especially when working on a deadline. Sometimes the paranoid engineer in my head constantly tells me to version my projects manually so that I physically see the project save correctly. Is this specific to SONAR X3? Or has this happened to you in other versions?
 

Gregmang
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.

 
Cool, I'm glad to see that you were able to find a workaround. Could you forward me the problematic project so that I can take a look at it?
 

Gregmang
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.

 
See my response to 2 and 3. How many clips do you have in this session? How many tracks were you freezing at the same time? Also, how many plugins do you have running in this session?
 

Gregmang
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.

Recreating projects is not fun, have you ever tried manually dragging and dropping a project into a new project to troubleshoot what the cause of the crash is?
 
-Make a new project
-Go to the Media Browser
-Select the "Move Up One Level" button until you get to your C Drive
-Locate your Cakewalk Projects folder
-Locate problematic project file
-Drag and Drop it into your current project, do the problems persist?
 
This could be a configuration thing between the two versions. Did you migrate your settings from SONAR X2 to SONAR X3? Also, how are your buffer size settings look.
 
Lastly, we may or may not be able to take a look at the crash. Did you send a problem report or a ticket into Technical Support?
 
-DG

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.

Not advisable, that won't be clean for a restore. You haven't considered other files that may be copied and what happens with the registry, any interference from other applications later on. You can't beat full backups (i.e. clone your hard drive beforehand) and the patches + Windows ability to roll back. Also a good idea to back up your project folders.
 
Cheers

Alex

Dan Gonzalez [Cakewalk]

Gregmang
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.

 
That is a frustrating experience, especially when working on a deadline. Sometimes the paranoid engineer in my head constantly tells me to version 

 
Dan, I'm sorry, you guys have done, and are still doing a lot of good things in X3, but you have to address the easily corrupted projects in Sonar as a high priority before, or with X4. There is simply no excuse for how easily users can end up with corrupt project files in Sonar. A majority of users on this forum will reply with, "that's why you gotta backup regularly" or "that's why I never autosave and hit Ctrl+S constantly" or some variation on "blame the user" (there's some already on this thread), but the fact of the matter is it's far too easy for Sonar to corrupt files and your user-base has become so used to these issues that they've conditioned themselves to work around it.
 
Honestly, in my using Reaper and Studio One (which I've spent a lot of time in lately, more than Sonar other than the last week), I've never given this any thought and never had a corrupted project. When I've gone into studios and worked on Pro Tools, same thing: it never came up. I mixed an album in Logic at friend's place, I never backed up, he never mentioned it either, no corrupted project files at any point. Maybe that's just luck (it's certainly anecdotal evidence, yes), but I have to think this is something Sonar can improve upon.
 
Maybe 1) shut down the audio engine during saves for added safety, 2) add a check to the save routine to make sure the project isn't corrupt before committing changes, 3) look into creating a new project file format that's less prone to corruption (Reaper's project files are actually text files that can be edited in Notepad if needed), or something else.
 
Fixing this, would go a long way towards addressing some major stability concerns. And I bring this up not to criticize, but rather to shed some light on an area where I think you guys can still improve Sonar.

Funkybot
Dan, I'm sorry, you guys have done, and are still doing a lot of good things in X3, but you have to address the easily corrupted projects in Sonar as a high priority before, or with X4. There is simply no excuse for how easily users can end up with corrupt project files in Sonar. A majority of users on this forum will reply with, "that's why you gotta backup regularly" or "that's why I never autosave and hit Ctrl+S constantly" or some variation on "blame the user" (there's some already on this thread), but the fact of the matter is it's far too easy for Sonar to corrupt files and your user-base has become so used to these issues that they've conditioned themselves to work around it.

+1 to that
 
And I'd like to add bringing projects and also templates over from previous versions - you got all these usable templates set up from previous projects and then a new version is released; when you run into problem you're eventually asked if that was created with the latest version or not - in case of using templates you never start from scratch with the latest version ... so, you're never on the save side ???
 
 
 
 

Dan Gonzalez [Cakewalk]

Gregmang
 
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.

 
Yes, it chewed up a few hours on our end too. We are on this, and are aware of it's existence. 
 

Gregmang
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.

 
That is a frustrating experience, especially when working on a deadline. Sometimes the paranoid engineer in my head constantly tells me to version my projects manually so that I physically see the project save correctly. Is this specific to SONAR X3? Or has this happened to you in other versions?
 

Gregmang
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.

 
Cool, I'm glad to see that you were able to find a workaround. Could you forward me the problematic project so that I can take a look at it?
 

Gregmang
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.

 
See my response to 2 and 3. How many clips do you have in this session? How many tracks were you freezing at the same time? Also, how many plugins do you have running in this session?
 

Gregmang
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.

Recreating projects is not fun, have you ever tried manually dragging and dropping a project into a new project to troubleshoot what the cause of the crash is?
 
-Make a new project
-Go to the Media Browser
-Select the "Move Up One Level" button until you get to your C Drive
-Locate your Cakewalk Projects folder
-Locate problematic project file
-Drag and Drop it into your current project, do the problems persist?
 
This could be a configuration thing between the two versions. Did you migrate your settings from SONAR X2 to SONAR X3? Also, how are your buffer size settings look.
 
Lastly, we may or may not be able to take a look at the crash. Did you send a problem report or a ticket into Technical Support?
 
-DG

 
 
Hey Dan -
 
 
Thx for you response - its much appreciated.
 
Yes, I have backups and used them to finish work last night - but all in X2 as X3(c) wasn't up to the task.

 I will completely uninstall X3 this weekend and reinstall and see if I have any improvements.


At this point I have not opened a trouble ticket but will after my reinstall/testing if necessary.


 
Thx again !
 
 

Funkybot

Dan Gonzalez [Cakewalk]

Gregmang
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.

 
That is a frustrating experience, especially when working on a deadline. Sometimes the paranoid engineer in my head constantly tells me to version 

 
Dan, I'm sorry, you guys have done, and are still doing a lot of good things in X3, but you have to address the easily corrupted projects in Sonar as a high priority before, or with X4. There is simply no excuse for how easily users can end up with corrupt project files in Sonar. A majority of users on this forum will reply with, "that's why you gotta backup regularly" or "that's why I never autosave and hit Ctrl+S constantly" or some variation on "blame the user" (there's some already on this thread), but the fact of the matter is it's far too easy for Sonar to corrupt files and your user-base has become so used to these issues that they've conditioned themselves to work around it.
 
Honestly, in my using Reaper and Studio One (which I've spent a lot of time in lately, more than Sonar other than the last week), I've never given this any thought and never had a corrupted project. When I've gone into studios and worked on Pro Tools, same thing: it never came up. I mixed an album in Logic at friend's place, I never backed up, he never mentioned it either, no corrupted project files at any point. Maybe that's just luck (it's certainly anecdotal evidence, yes), but I have to think this is something Sonar can improve upon.
 
Maybe 1) shut down the audio engine during saves for added safety, 2) add a check to the save routine to make sure the project isn't corrupt before committing changes, 3) look into creating a new project file format that's less prone to corruption (Reaper's project files are actually text files that can be edited in Notepad if needed), or something else.
 
Fixing this, would go a long way towards addressing some major stability concerns. And I bring this up not to criticize, but rather to shed some light on an area where I think you guys can still improve Sonar.

Thanks for the kind words and your professional insight on this matter. We are really trying to turn things around this product cycle. You guys have been a big help so far, and that is most definitely certain. That being said, it's hard for us to resolve an issue when it's presented outside of our internal support system.
 
I haven't seen this specific issue on my end in Marketing or Tech Support so could you provide me a way of reproducing this, or maybe some project files that exhibit this behavior? Maybe a support ticket or a problem report number? SONAR isn't the only culprit when it comes to project corruption. Plugins, Audio Files, and Downloaded MIDI files have caused major issues as well. I would love to work towards a solution for this if it is causing major stability concerns. 
 
-DG

Gregmang

Dan Gonzalez [Cakewalk]

Gregmang
 
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.

 
Yes, it chewed up a few hours on our end too. We are on this, and are aware of it's existence. 
 

Gregmang
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.

 
That is a frustrating experience, especially when working on a deadline. Sometimes the paranoid engineer in my head constantly tells me to version my projects manually so that I physically see the project save correctly. Is this specific to SONAR X3? Or has this happened to you in other versions?
 

Gregmang
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.

 
Cool, I'm glad to see that you were able to find a workaround. Could you forward me the problematic project so that I can take a look at it?
 

Gregmang
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.

 
See my response to 2 and 3. How many clips do you have in this session? How many tracks were you freezing at the same time? Also, how many plugins do you have running in this session?
 

Gregmang
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.

Recreating projects is not fun, have you ever tried manually dragging and dropping a project into a new project to troubleshoot what the cause of the crash is?
 
-Make a new project
-Go to the Media Browser
-Select the "Move Up One Level" button until you get to your C Drive
-Locate your Cakewalk Projects folder
-Locate problematic project file
-Drag and Drop it into your current project, do the problems persist?
 
This could be a configuration thing between the two versions. Did you migrate your settings from SONAR X2 to SONAR X3? Also, how are your buffer size settings look.
 
Lastly, we may or may not be able to take a look at the crash. Did you send a problem report or a ticket into Technical Support?
 
-DG

 
 
Hey Dan -
 
 
Thx for you response - its much appreciated.
 
Yes, I have backups and used them to finish work last night - but all in X2 and X3(c) wasn't up to the task.

I will completely uninstall X3 this weekend and reinstall and see if I have any improvements.


At this point I have not opened a trouble ticket but will after my reinstall/testing if necessary.


 
Thx again !
 
 

Ok great, please PM me if you have any further issues on this.  I would really love to help out in any way I can.
Thanks!
-DG