aghschwabe
You're quite right. And I'm not too worried...the rollback solved the major issue. I'm not one of these chicken little types who woe the death of Cakewalk because of a bad patch.
 
As for plugins, I only got as far as testing out Izotope IRIS, but since it's the centerpiece of my current project, it's kind of crucial that it can run (at all).
 
You're probably right that some optimization somewhere broke something. It's possible the optimizations cut some corners. Oh the joy of sorting through thousands of lines of code to figure out what's happening.
 
Addendum: I should probably use the time I have to figure out the latest couple of updates. I've been so busy I'm falling behind the incremental upgrades. XD

Yeah, man. I hear ya. If you send those crash dumps off to Cake though might help them get it sorted.
 
I'm being selfish in saying that though because I sooper totally want to get myself updated but am a scaredycat... so I let everyone else do the testing. lulz...
 
Really though I'm just kind of too stupid to sort out what problems are caused by what and have a seemingly stable setup going so I don't want to bork it out (currently on Foxboro).
 
I guess Jamaican Plains is sounding pretty stable in general and has all the goodies I want so maybe I'll do that for now until more details on Kingston come out.
 
Cheers.

I've nothing helpful to add here, but I wanted to post to note that "CATASTROPHIC FAILURE" is my favourite error message since the days of "GURU MEDITATION" on the Amiga. Though it must be acknowledged that neither holds a candle to the true classic of the form, Unix's "PRINTER ON FIRE".

aghschwabe

stickman393
Hmm. This is new:
 

 
This is on a project that I mixed down yesterday in Jamaica Plain, without errors. All I did was mute some midi clips that were unnecessary... so it appears to be something in the K update. 
 
I'm rolling back to JP to check that I can mix-down in that version.
Bummer.
 
UPDATE: Mixdown succeeded in JP, as expected. I'll try re-installing K a bit later and try the mixdown again, when I have some time to experiment. Stay tuned.

I'm seeing much the same thing, but without the warning window. Izotope IRIS2 doesn't work at all, replacing synths is causing consistent lockup (the window greys out and then eventual crashes). I'm getting phone-home pop-ups from both Sonar and Izotope.
 
I'll second the request asking how to roll back a version...saving that, I can always restore from backup (three cheers for daily incremental backups).
 
In short: Sonar was bulletproof for me from launch day until now. Currently, Sonar isn't useable in this state. Ouch.

Are you using vst2 or 3?  vst3 works fine here...I've had Iris2 for awhile but hadn't gotten round to installing it.  I just did, to try and replicate the crashing issue.  First, I rolled back to "J" land, then installed Iris2 and all the additional content, added Iris2 to a song I'm working with, which has over 100 tracks of audio, synths, kontakt/falcon/omnisphere2 tracks, lot of Albion One... a song already beginning to stress my pretty robust system.   
 
I verified Iris worked fine...at least the vst3 version...I use vst3 whereever possible, and also wanted to test the bakers new vst3 code.   Iris itself was kinda boring but....  I saved the song, and reupdated to "K" land.  Brought up the song with the iris track... played fine.  Added another vst3 instance of iris.... recorded/played back fine...
 
Don't know if you're using vst3, but from here it works fine.
 
FWIW, if ur using vst2, try vst3. 
 
If you're crashing, hope you sent in the crash reports for trouble shooting.  The diversity of wintel machines is a real challenge and that's why it's REALLY HELPFUL IF YOU POST YOUR SYSTEM SPECS, LIKE MOST OF US DO IN OUR SIG...

John T
I've nothing helpful to add here, but I wanted to post to note that "CATASTROPHIC ERROR" is my favourite error message since the days of "GURU MEDITATION" on the Amiga. Though it must be acknowledged that neither holds a candle to the true classic of the form, Unix's "PRINTER ON FIRE".

As soon as I saw the OP I thought of the Amiga "GURU MEDITATION" error. 
 
Someone once told me how that term originated.  Time fades the memory, but someone at Amiga used to sit cross legged on the workbench (like a guru), and if he moved too heavily it used to crash the machines they were testing, hence "Guru Meditation Error".  IIRC
 
Happy days with Sequence One.  At first an Amiga 500 with 512 KB RAM and a 68000 processor @ 7 MHz.  I then upgraded to an Amiga 4000, with 16 meg ram and a 68040 @ 25 MHz  -  smoking..

Should we all run now!

aghschwabe
I'm seeing much the same thing, but without the warning window. Izotope IRIS2 doesn't work at all, replacing synths is causing consistent lockup (the window greys out and then eventual crashes). I'm getting phone-home pop-ups from both Sonar and Izotope.
 
I'll second the request asking how to roll back a version...saving that, I can always restore from backup (three cheers for daily incremental backups).
 
In short: Sonar was bulletproof for me from launch day until now. Currently, Sonar isn't useable in this state. Ouch.

You will have to submit a more specific report. I just tried IRIS and had no crashes or problems.
Can you submit a bug report with a minidump as well as a simple recipe or project file to repro the problem?
We won't be able to know if there really is a problem or not without these steps. If its crashing a minidump should be created in the %appdata%\Cakewalk folder for the crash.
Also are you using the VST2 version of IRIS or the VST3 version? I created a project with a simple insrument track with IRIS (both vst2 and vst3) and it worked fine.
The problem could very well be specific to your project.

I have no idea if this is related, but I was having some nasty crashes with Kingston (particularly IRIS2). IRIS2 wasn't really the problem. It seems that my iLok was having some issues. Eventually I just did an offline authorization (ditching the iLok for the umpteenth time). Aaaaand...the problems disappeared with the iLok.
 
Again, not sure it's related, but it's the only thing I changed and IRIS2 and it's crashes have resolved themselves after ditching the iLok. Just sayin'.