jatoth

Anderton
 
No. It's unreasonable to expect Cakewalk to test Platinum with a wide variety of bad installations to see what happens. The source of the problem wasn't SONAR's scanning process, the problem was multiple installations of the same plug-in in multiple folders. That's wrong from the gitgo. The user was lucky that it worked okay in X3 but the fact is the scanning process continues to be improved in several ways (e.g., from what I understand it now works in Vista, which it didn't in X3). If the scanning process is more rigorous, it's reasonable that it would be less tolerant of user-created problems. 
 

 
So you are saying, X3 did it wrong, but it worked. Platinum does it right, and therefore it crashes.
X3 was obviously more forgiving. Was it a development decision to make Platinum less forgiving? Or did the bakers just miss the reasons X3 was coded to be more forgiving?
 

The thread in question involved migrating from 32bit X3 to 64bit Platinum and 32bit plug-ins crashing. The resolution (installing the 64bit version of the plug-ins) was complicated by installation issues on the PC. The user resolved the problem by uninstalling the plug-ins and reinstalling them. IOW, in this example, 32bit X3 worked correctly and 64bit Platinum does too as long as the correct version of the plug-ins is installed.
 
This is different than the original problem mentioned here except for the use of 32bit plug-ins. I believe the 32bit plug-in used in this thread has not been updated in some time. It is reasonable to expect problems over time when updating everything else but the abandoned software. The issues may be made worse by relying on bridging technology to extend the life of old plug-ins.

mgh
although i haven't anything to add from a technical POV, Jamesyoyo is far from a newbie and was a stalwart of the Songs forum back in the day when I used to frequent here a lot. You can rest assured he is using a pro set-up from a hardware perspective and will have done all the basic tests to try to find the culprit.
 
right, as you were...

+1.
 
It would be nice to be able to mark a post 'helpful' more than once. I think I'll request that.

Michael:
 
You should be a counselor.  Your advice applies to much more than technical issues with computers and software.
 
Paul

I agree that the problem does not necessarily lie with Sonar. But I also can't stand responses that say "if you are a pro you shouldn't be using it until it's stable". While obviously any pro needs to take his/her own precautions to create a stable working environment, that kind of comment only deflects from the problem that's being discussed and somehow makes it sound as if the user is at fault for buggy software (or OS or memory). No matter how tiring it may be for developers or passionate users, the attitude should always be one of commiseration and problem solving. Otherwise just don't say anything.

Obviously the person who has the problem has to want to work with the community too and try to not get stuck in the frustration of it all.

michael diemer
I can't add any technical expertise here, as I use Sonar 8.5, and am not knowledgeable anyway about the technical details of DAWs. However, perhaps I can offer the OP a little moral support. 
 
Awhile back, I was having problems with display driver failures in Windows. It affected both Vista and Seven drives. It was extremely frustrating. Nothing I tried worked. I got help from the Windows forums, but still no solution. I came to the conclusion that Windows was to blame. I would not hear of any other explanation. The reason was that the problem only happened in Windows, not in Linux. Ergo, Windows was at fault. I got a bit snippy, causing the forum folks to get defensive. I finally uninstalled all Nvidia drivers, and installed VGA drivers. I lived with crappy graphics for awhile, until one day I removed the memory upgrade I had done a couple years previously. I can't even remember why I did this, but the problem immediately went away.
 
So the problem was caused by a bad memory module. The forum folks had suggested this as a culprit, but I was so convinced it was Windows' fault that I stubbornly refused to try something that would have solved the problem. Instead, I started bashing Microsoft, and pointlessly trying to learn Linux so I could switch to that. (Not advisable for DAWs, of course). Now, I can profess to love Windows and Microsoft again, and regret the fact that I bad-mouthed them. I went back and apologized to the forum hosts.
 
I understand your frustration, James. You spend money and expect it to work, and when it doesn't and the problem is not obvious, you look to cast blame somewhere. But technology is extremely complicated, obviously, and we all have different setups. But the only solution will come from taking the extended hands of Craig and the Cakewalk and forum staffs, and work with them to help you solve the problem. It is solvable; even I know that. Because a lot of really bright people who also care about helping other musicians, are more than capable of dealing with any issue that comes up. Don't let your emotions blind you. Get the help you need, and the problem will be solved. Listen to the voices of reason here!

 
I'm happy you're a member here Michael. I 2too2 had daw problems a while back. WIN8.1 and sonar X3 was a pain. Not X2 - that version ran well. But x3 was almost unusable at times. It was frustrating trying to correct this problem (glitchy graphics and overall sluggish x3). What kept me from believing it was x3 was the fact that so many people here proclaimed x3 to be the most stable version to date. So I knew it had to be a problem here. As it turned out I had 2 problems that were discussed here. First, I had a failing graphics card - Jim Roseberry pointed that out to  me and suggested a card that I did indeed install. And secondly... I had made the mistake of loading Win8 over top of Vista. I knew it was a bad idea, but I somehow thought I would be exempt. What was I thinking? Anyway - a new graphics card and a fresh install of Win8.1 over a clean drive all equaled peaceful success. So I'm absolutely supporting your post. 

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.

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.

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.

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.

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

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.

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. 

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. 
 

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.........
 
 
 
 
 
 
 
 

.....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.