Judah


I've had 3 white screen crashes with X2 in the last hour!  X1 didn't do this to me.

I take it you have reported this to Cakewalk via their website including a description of your system and what you were doing at the time of the crash?

Don't get me wrong, I love X2 a lot more than X1.  But it seems like it crashes a lot more.   I wasn't going to report it until it got out of control.

I was working on a X1 project and doing things like listening to the project and making small adjustments; nothing serious or tasking.

And my specs are as follows.
AMD Phenom II x 6 1090T - 3.2 Ghz OC to 3.9 Ghz
MB GIGABYTE GA-870A-UD3
8 Gbs of memory
(2) 1 TB Internal HD  | WD SATA2
(1) 3 TB External HD
Geforce 570
Windows 7 Pro – 64 bit
Presonus Firestudio Project  (10x10 Firewire)
Sonar X2 64

A few other guys have reported X2 crashing while simply opening and closing ProChannel, or switching between different tracks and busses.

Fingers crossed we may see a patch soon...

I would probably say that switching between tracks is what might of caused my crashes.  Maybe it has to do with the new auto track zoom feature that adjusts when you select a track.  Who knows?

Hey X2 adopters,
Yep,I had about 5 crashes today,but nearly ALL involved instantiating a Waves plugin,particularly the L3LL Multimaximizer,as the last in line,while I try to get more of an idea,about Mastering[!!??!!]

Anyway,Iv'e also lost audible bounce,on both X1exp.,and X2,meaning the bounce to final .wav goes ahead, but I hear no sound!,and If I immediately playback in iTunes it has exported "completely fine"[]...this is all on my Laptop, the desktop,will get the workout,when I can get around to it.

Other than that[it did get scary when it crashed 3 times in a row,just applying the Waves plug],the other 2 times were when I was being a bit silly and seeing how many instances of "Console Emulation" I could stack,and "Save as PC presets",and then,after you guessed it,I tried to load a Waves CLA76..white out,then "Sonar Must Close".

Only 1 of the Waves inclusive crashes,had the "Send Cakewalk Report".

Yes,I'm glad I did'nt do the THD upgrade,as I learned with GR,the basic version,is "basically" good enough,and yes the "scrolling across the floor" is tiresome",but it is a decent "amp sim",and Breverb[which I also did not upgrade] is very appealling,and easily more usable than "perfect space",but P.S.,for me, is getting better,the more I use it,it's just a shame it's 32bit bridged[still].

I tried opening X1,and found it amusing that all the "Console Emu's/Breverb"all show up" but are bypassed,any way since installing X2,my laptop has seemingly,completely lost "audible bounce",but as I'm using ASIO4all/on board Realtek,it's no doubt,more an issue of THAT,still,all was working fine in that regard until X2,oh well its a bit of-"the very good",with a bit of bad,not too worried,but I'm going to uninstall X1,to see if it helps matters.

I had ZERO issues,until I discovered the new "inaudible bounce",and then 5 successive-Waves connected crashes,but no more in the last few hours,and as far as the "manual",I always"used to" prefer the "chm",but if there is a PDF,obviously I'll look for that.

Good Luck All!
Bob

P.S Thanks "qlne"for the PDF/R-Mix link!

tbosco


OK... I'm glad it's not just me with the white-outs.  But honestly, I feel like my (rather new) 4GB RAM machine is now the very minimum that will run Sonar X2.  If I preview 10 or 20 loops, then try to Run the palyback of a sequence, I have a high risk of a white-out or at least a drop out.
Looks like I will have to upgrade to Win64 and 16GB RAM (or more) soon.
But so far, liking X2.

Tony, on the white-outs, I think this is related to your running the 32-bit version of SONAR.  I used to get these very frequently back when I was using that (back in SONAR 8's era), but I have not seen them at all since I went to 64-bit (also in SONAR 8's time).  I was using the identical configuration of machine, which is a Core 2 Duo E6600 with 4 GB of RAM -- I'm still using that today with SONAR X2 Producer x64.
 
The key is that 32-bit only gives you 2 GB of application space, no matter how much memory you have on the system.  A few memory-hogging softsynths (e.g. my projects frequently include EZ Drummer or Superior Drummer 2, Trilogy, Virtual Guitarist and/or RealGuitar and/or Chris Hein Guitars, Garritan Steinway, plus a few other large sample-based modules depending on the genre and project), along with the basic needs of SONAR, can eat that space up very quickly.  Since audio loops also go into memory (as opposed to being streamed from disk like audio tracks), they also eat memory space up quickly.  With 64-bit, though, the application space can be much larger (even larger than the actual memory on the system, though actually using more would create performance problems).  Going to 64-bit Windows and SONAR instantly made this problem disappear for me.
 
That's not to suggest it is okay for these problems to occur in the 32-bit realm.  There still must be something that isn't being handled properly or things might be able to degrade more gracefully.  But, even if they were, the fact would still be that you're needing more memory space than is available in the 32-bit realm, so you'd still have problems, perhaps only with performance, even if things did degrade better.
 
Rick

http://www.cakewalk.com/support/contact/problemreport.aspx

Thanks for your comments rickpaul.  I think you're spot on.
FYI...a lot of whiteouts happen after only just previewing a few of the audio loops and one-shots, or, just clicking the Master bus in Console view then clicking back on a track.

tbosco


Thanks for your comments rickpaul.  I think you're spot on.
FYI...a lot of whiteouts happen after only just previewing a few of the audio loops and one-shots, or, just clicking the Master bus in Console view then clicking back on a track.

That makes sense.  My longstanding theory on that problem (which I had from CWPA9 to SONAR 8 32-bit, but which went away when I went to SONAR 8 64-bit), was that it was specifically rapid spikes in memory usage that put something over a threshold momentarily, and "at the wrong time" (i.e. when something else was going on with the system that, at least temporarily, compromised its ability to handle the additional memory usage), made the difference in when it did and did not occur.  The general gist of my speculation was that something happened that put it over some threshold, but, to respond gracefully (e.g. just have an audio dropout, put up an error message, etc.), something else would have had to have been loaded, but there was, temporarily, nowhere to load it, and things got deadlocked going around in a circle.
 
That also related to my theory on the "poofs" (i.e. when SONAR would just disappear with no crash message at all), which I also have not seen since going to 64-bit. 
 
Rick

Installed X2 Producer on Friday (took several hours, thanks to download issues). Started X2, opened a legacy X1 project, tested it, everything worked fine. Was pretty happy about the new look.  

Shutdown my machine and walked away for a couple of hours. Restarted the machine in the afternoon and Windows wouldn't load. Had to do a system restore from the point before the X2 installation. At this point, I'm quite panicked, but system restore worked flawlessly. My IT background gave me the sense to set a restore point just prior to the X2 installation.  
Once resolved, I re-installed X2 and this time, no issues. Worked on some legacy projects Friday evening to get familiar with it - no issues except for some occasional dropouts (but I had those before. I suspect a conflict between my Alesis MasterControl surface and my Focusrite Saffire PRO 40 interface.)  

Saturday, I recorded a 14-person vocal group. Three songs, minimum 32 tracks each. No issues. Dropouts twice. Granted, I haven't taxed the ProChannel modules yet, but seems rock solid to me so far. 

Baudze  
-----------------------------------------  
Sonar X2 Producer (64-bit)  
Windows 7 (64-bit)  
Intel i7 920 (2.66Ghz)  
9 GB RAM (1066Mhz)  
750TB (OS/Programs/VSTs)  
1TB (Project Files/Samples)  
Focusrite Saffire PRO 40  
Alesis MasterControl surface
Roland Edirol PCR-300 Controller