At least you didn't get the popup I get often "SONAR cannot in good conscience mixdown this catastrophe for dissemination to the general public. We apologize for the inconvenience."

Consider yourself lucky.

Plz confirm you are doing realtime or 'fast' export, and the file format/specific steps. Cheers..

aghschwabe
 I'm getting phone-home pop-ups from both Sonar and Izotope.
 

Could you please elaborate on this? What are you seeing with these "phone home" pop ups?
 
Do you mean the Sonar crash reporter or something else?

The mixdown issue is very unlikely to be specific to kingston. The were no changes to that code. It may be just that you ran into a specific issue based on what you did. If you get a repro or can send the project we will investigate, but there is no need to roll back. No known issues in this area.

Btw don't panic with that error message :) its just a generic message for an E_FAIL error meaning some function failed in the bounce. Nothing catastrophic will happen lol

About the only potentially catastrophic thing that happened is that the exported file I was replacing didn't exist after the failed bounce/mixdown. But I think that's okay, considering. It did ask me if I wanted to replace it before it started  :-)
 
@DrAvalanche, yes, it was fast bounce, 44.1/24 wav export. But as Noel says, no changes in this area and I haven't been able to reproduce. I'll keep using Kingston going forward until something else crops up.
 

Phone home pop-ups are the little "An error has occurred" box which asks you to describe what you were doing when the crashes occurred. So far my descriptions include, "Starting Sonar...hang," and "Crashed while loading a VST (Iris 2)" as well as "Playing back audio...hangs...crashes."
 
I was going to do a screen grab of the phone homes that pop up, but the system is totally locked and I can't do anything until Sonar finally gives up the ghost. But loading IRIS 2...100% success rate in everything up to and including Jamaica. With Kingston it's a 100% fail rate to load.
 

Ah... yeah, those are the usual crash reporters. I thought you were describing something new/weird.
 
That's normal in a crash situation.
 
Thanks.

It is "normal," but not for Sonar. I've also had a number of dump crashes (where Sonar just unloads and shuts down without warning).
 
IRIS2 is fine as a standalone in both 32-bit and 64-bit, but in Sonar, it's discouraging. I'll just have to wait for updates...in the meantime, time for a roll-back (and TY Cakewalk for making rollbacks so easy in Control Center...just right click on the product and select the version to revert to...fantastic!).
 
UPDATE: Rolled back to Jamaica Plain...all problems with loading VST's, weird sounds (screeching from IRIS et al) are gone. The Plain in Jamaica stays mainly in the...er....nevermind. Not going to be visiting Kingston again until there's a fix. That was grim. AND it happens to everyone.
 

I was saying that it's the normal crash behavior. Certainly not normal for Sonar in general or good at all.
 
Sounds like you've got a lot of third party stuff in play though so maybe it's exposing conflicts with those plugs in Kingston.
 
Still... not good.

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