Beepster
He's opinionated but AFAIK he's a true pro and contributes a lot (although usually in the Songs area).

 
Which is why I think working with support would be helpful, and why I keep mentioning it. He can probably define the issue with more precision than the average user, thus either speeding up a resolution for him or identifying a problem that needs to be fixed.

Appreciate all the responses. Yes, this was started in X3 but again, I haven't even finished writing the damn thing so I am no where near the individual track plug-in phase (where the memory problems usually are a likely culprit). In this case my quad core is barely registering on the usage meter. There are maybe an average of 6 instruments per Kontakt instance, and the two Philharmoniks are have 10 midi tracks each. There are A LOT of midi notes and in PRV the way Sonar utilizes graphics display drivers for me has always been an issue. I did start another song on Platinum and experienced similar "SONARPLT.EXE is not responding" messages.
 
But again:
is it unreasonable to expect a project to work in Platinum that is working perfectly fine in X3?
 
Either way, I will contact CW support on Monday and get back to y'all if there is a resolution.

jamesyoyo
Appreciate all the responses. Yes, this was started in X3 but again, I haven't even finished writing the damn thing so I am no where near the individual track plug-in phase (where the memory problems usually are a likely culprit). In this case my quad core is barely registering on the usage meter. There are maybe an average of 6 instruments per Kontakt instance, and the two Philharmoniks are have 10 midi tracks each. There are A LOT of midi notes and in PRV the way Sonar utilizes graphics display drivers for me has always been an issue. I did start another song on Platinum and experienced similar "SONARPLT.EXE is not responding" messages.
 
But again:
is it unreasonable to expect a project to work in Platinum that is working perfectly fine in X3?
 
Either way, I will contact CW support on Monday and get back to y'all if there is a resolution.

Just a follow up... when those dropouts were happenign to me they seem to be related to some weird sliver clip of MIDI that would not go a way. If I touched it in anyway (delete, slip edit, anything) X3 woudl crash. It was extremely bizzare and I probably should have called support to report it but it was easier just to finish in X2.
 
Point is... yeah, we should be able to expect projects to transfer and so far I've been doing alright with my current project started in X3 transferred to SPlat but I'm ready for a fudge up based on that experience.
 
However if NEW projects in SPlat are causing screwiness then that ain't right so definitely call support and hopefully the report will result in a more stable product for us all.
 
Currently I've only installed the base of Braintree. Partially due to time constraints and partially because I'm kind of digging the method of staying a month behind on things to see what others report about new releases and goodies.
 
Anyway, good luck to ya. I'm sure it'll get sorted.
 
Cheers.

Anderton

Beepster
He's opinionated but AFAIK he's a true pro and contributes a lot (although usually in the Songs area).

 
Which is why I think working with support would be helpful, and why I keep mentioning it. He can probably define the issue with more precision than the average user, thus either speeding up a resolution for him or identifying a problem that needs to be fixed.

Definitely. I'm an arse for not being more proactive in this regard because I seem to be the type who stumbles across very obscure things that don't affect others. I guess I use the program in strange ways or something (I'm kind of thick). I do probably have a lot less on the line than others and as far as I'm concerned I am currently sponsored by the forum members so I should earn my keep. Honestly though I have not been running into too many issues lately anyway.

I don't know why this works or if I am imagining this but:
 
In my large projects, as time goes by, my system becomes less responsive... SPACE BAR won't stop or start playback, etc....
 
A simple CNTL S (save) clears this up for awhile.  But this condition has existed since X1 for me and is still there today in PLAT.....  and this is across two different DAWs now... different DAWS same issue.
 
It should be noted that I too use large sample libraries and use KONTAKT as the host.  Perhaps KONTAKT and SONAR are the common denominator?
 
Jim

jimkleban
It should be noted that I too use large sample libraries and use KONTAKT as the host.  Perhaps KONTAKT and SONAR are the common denominator?
 

Maybe, maybe not...NI does update frequently and I've found it pays to stay on top of things, but it could be more about how Kontakt uses RAM vs. disk streaming or some similar aspect. In the past I found it's crucial to understand and use Kontakt's purge function for best results with any DAW.

jimkleban
I don't know why this works or if I am imagining this but:
 
In my large projects, as time goes by, my system becomes less responsive... SPACE BAR won't stop or start playback, etc....
 
A simple CNTL S (save) clears this up for awhile.  But this condition has existed since X1 for me and is still there today in PLAT.....  and this is across two different DAWs now... different DAWS same issue.
 
It should be noted that I too use large sample libraries and use KONTAKT as the host.  Perhaps KONTAKT and SONAR are the common denominator?
 
Jim

i know that at one point several VSTs would have memory leaks which would cause issues over time - Sonitus Delay was one of those if MY memory serves...perhaps that is still occuring?

williamcopper
And moderators, especially you volunteers:  PLEASE don't try so hard to minimize every problem report.   Yes, some are exaggerated, but most of us wouldn't bother if it weren't real.
 

It's  not that we are seeking to minimize, but more an attempt to figure out the problem by getting to the root of it instead of broadly declaring platinum is buggy beyond what is typical.  For many people using IK 32 bit vsti's working smoothly in 64 bit Sonar X series is the exception. I gave up years ago. So, from my experience,  the plugin working in X3 was exception and luck and the Platinum experience was back to normal. Of course I realize that the OP is not going to see it that way. At the end of the day the empirical evidence still points seems more like an issue of the quirks that show up when using mixed bit plugins than any particular set of platinum bugs. 
 
I propose trying the exact same project with a trial version of ST3 with the orchestral sounds imported and see if the exact problems still occur.

@jameyoyo
 
see my post above. I had the type of dilemma. In my case, it was Sonar X2 that worked fine, but X3 was almost unusable. My guess is that X3 simply exposed my faulty PC setup. Still I hear you and understand how reasonable your question sounds. But speaking from experience, and knowing others were singing the praises of X3 - it was my system. No doubt about it. BTW - Platinum has been very stable on this same machine. All the best and I hope you find your answers.

Unfortunately there isn't a way for others to test projects to see if a crash can be duplicated.