James, I offer this to look into.
 
My buddy Daryl1968 was having major PITA with Platinum.
 
Turns out he somehow got two versions of drivers for his interface installed. Made Platinum get it's knickers in a twist pronto.
 
Just a thought.
 
 
P.S. I did not read the whole thread.
 
For what it's worth THIS SONG had similar specs to your project and it was mixed in Platinum (and was actually started from an X2 project). Platinum never felt buggy to me.

To the OP:
I apologize if this question was already answered.
Did you install X3 and all sonar plugs and samples to default paths?
 
 
============
Saddness prevention:
I NEVER use SAVE. Save is destructive. I use SAVE AS every few minutes, and each time add a letter to the file name.
With a new version I add the version to the file name.
And I always add the current month to the file name: Great Project 0415 a.cwp.
Yes I end-up with dozens of project files.

x3 install as admin...has this been done?,,,((could cause all kinds of issues if not....did not see it mentioned, so I put this out...as a question,)) some times in a rush to play with the new toys..some times one forgets to follow instructions to the letter.

Asides, someone posted this
 
Several people chimed in to say that if you set the MIDI Channel field to "none," all channel assignments were in fact preserved during a bounce. Clearly there was no bug, just that the OP expected a particular default instead of having to choose whether or not to assign all events to a single channel.
 
But that someone failed to recognize (or believe? or read?) that what those several people contributed were guesses, and not right .. in other words, wrong.   The point got minimized by EXACTLY this technique: quote erroneous comments without tracking down whether they are or are not correct. 
 
As to Kontakt being involved, in the OP and other comments throughout,  I don't think necessarily so: problems with "many clips" have arisen without Kontakt and without ANY vst in older sonar versions.    Yes, mixing 32 bit with 64 bit IS a source of errors, but otherwise I don't think it is a good idea to point the finger away from sonar and toward some plugins. 

dubdisciple

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.

I agree with your 32 vs 64 bit view. I wont put them in a project. I waited for SampleTank 3 to use all those sounds and that was a long wait. "But they worked before". Dub is right, that was probably luck. Even if it has nothing to do with this issue, someday it will be a problem. I have observed that when someone comes in with a problem the first thing that needs to be done is "talk them down off the ledge" and help them be open to help. I hope he will get his problem fixed. I know the generous people in these forms will help if it leads to SONAR  or not. And lets find every bug we can. We have updates and fixes every month now. Saying it's SONAR is no more or less virtuous than saying it is something else. It just slows down the hunt. 

williamcopper
Asides, someone posted this
 
Several people chimed in to say that if you set the MIDI Channel field to "none," all channel assignments were in fact preserved during a bounce. Clearly there was no bug, just that the OP expected a particular default instead of having to choose whether or not to assign all events to a single channel.
 
But that someone failed to recognize (or believe? or read?) that what those several people contributed were guesses, and not right .. in other words, wrong.   The point got minimized by EXACTLY this technique: quote erroneous comments without tracking down whether they are or are not correct.

Huh?!? I posted that. I didn't specify you by name because I didn't want to draw attention to your making a mistake.
 
You posted a thread with the following title:
 
"CWBRN-32278 Midi 'bounce to clips' changes midi channel --- design fllaw or bug?"
 
bvideo was the first of several people who gave a definitive answer: Whether bouncing to clips changes the MIDI channel or not is an option, as specified by changing the MIDI Output field. This was not a "guess." How can you say what he posted was "wrong"?
 
Then bvideo did another post, indicating step-by-step how to do what you wanted, and asking you to explain any differences between your procedure and his. You did not respond.
 
I then posted and assumed it was pilot error because I'm not stupid enough to think SONAR couldn't have some as-yet-to-be-discovered bug. However, all your "steps to reproduce" did was specify how to reproduce one of the two possible options for clip channel assignment behavior when bouncing. So I gave a very detailed explanation (not a guess) of how the MIDI Output field works, as well as two other possible fields which could be confusing if set to "none." You did not respond to that post, either to confirm that what I described solved your problem or that I was missing some way to reproduce an actual bug. 
 
Then SquireBum confirmed what bvideo said, Again, not a guess. Again, no response from you. How can you say what he posted was "wrong"?
 
I posted that given the difference between our results and yours, maybe the three of us didn't fully understand your problem. That was a guess, but the only explanation I had for why you didn't obtain the results we did. You did not respond to indicate that we didn't understand your problem.
 
bvideo again gave a further explanation of how the process. Again, no response from you. How can you say what he posted was "wrong"?
 
Eventually SteveC said he felt the documentation should be clearer, and the discussion veered into the relationship between track level and clip level events, which had nothing to do with your original comment but threads often veer off in different directions after a problem has been solved.
 
You never returned to the thread either to confirm that you had figured out how bounce to clip works, nor to give further information on a scenario where it was not possible to preserve channel assignments when bouncing to clips. Obviously, there's a way to preserve channel assignments when bouncing to clips.
 
I don't see how any of this minimized your initial premise for the thread. Several members of the community gave you a detailed response that was not based on guesswork, and provide detailed explanations and step-by-step instructions on how to solve your problem. After the problem was solved, you just disappeared...no feedback, no follow-up. If there's any minimizing going on here, it's your minimizing the helpful responses that people gave so you would know how to bounce clips without changing channel assignments. Most people circle back to a thread to note when a procedure has solved their problem.
 
I have no idea what you're taking issue with. Perhaps you could explain what I have supposedly misrepresented with at least a minimal degree of specificity. What the people above said solved the issue on which your thread was based. They were not making guesses and they were not wrong. 
 

I ask about the installation of X3 to default paths partly because of what THE CRAIG mentioned in his first response, and for my own understanding of issues I am having related to paths and the inability to choose paths S15
 

bapu
James, I offer this to look into.
 
My buddy Daryl1968 was having major PITA with Platinum.
 
Turns out he somehow got two versions of drivers for his interface installed. Made Platinum get it's knickers in a twist pronto.
 
Just a thought.
 
 
P.S. I did not read the whole thread.
 
For what it's worth THIS SONG had similar specs to your project and it was mixed in Platinum (and was actually started from an X2 project). Platinum never felt buggy to me.

 

 
And the 2015 Herb Hartley Award for Lamest Attention Seeking Thinly Disguised as Attempt to Appear Helpful goes to.........
 
 
 
 
 
 
 
 

I went from X3 to Platinum - and am very happy.  It works with lower latency.  And no problems.
I imagine there are a lot of people like me.  Sorry some people are having some issues.  I have been with Cakewalk a long time and followed this board a long time, it seems like all releases have some issues.  Hopefully, for those experiencing some now, they will either be able to fix the issue that may be due to their own computer, or get the info to Cakewalk so they can fix it in an update.
 
I am Using a UAD OCTO and many soft synths, East West, Vienna, Miroslav, BFD, Garritan, etc. - no issues.
 
Bottom Line: This is a great product.

.....2015 Herb Hartley Award for Lamest Attention Seeking Thinly Disguised as Attempt to Appear Helpful goes to.........
 
 
 
 hey paulo,
posting such a provocative personal jibe certainly grabbed my attention.
it is possible the poster was presenting the track in good faith rather than self-aggrandising.(if that`s a word?)
 
tony.