Hello!
 
I have a nearly complete project on a Windows 8 64 bit DAW running X3.  I opened the project in Platinum running on my Win 7 64 bit DAW.
 
On playback, it sounded like there were random, missing midi notes in the drum and electric bass tracks.  On closer inspection, I found the notes were still there but their velocity was so low I couldn't hear them.  [EDIT: actually I think I made a mistake reporting the values had changed.  Most were NOT changed but were silent.  See answer below.)
 
Has anyone else experienced this?   My primary DAW is the Windows 8 64 bit machine running X3.  I wanted to test drive Platinum and try out a few X3 projects in it before upgrading the Win 8 DAW to that Sonar version.
 
I have other unfinished projects that I don't want to impact by upgrading.  Thoughts?
 
Thanks in advance...
 
Marc 

Update:  I reviewed a few more notes that were "silent".   Their velocities were accurate (unchanged) but they were not playing a sound.  I verified they were not muted.  I merely clicked on them to invoke their audible note and re-played the passage and they played as expected.   Curious bug.  
 
I really don't want to have to listen to find this type of problem in other midi tracks in this or any other project.  Could be most painful.   
 
Maybe this has to do with opening a project on a different DAW with different OS, sound card, Sonar version, etc etc. Maybe it doesn't have anything to do with upgrade from X3 to Platinum?
 
Bewildered.  

You just opened the project in Platinum, and some individual velocity values are numerically lower? I haven't heard of that, and can't imagine how it would happen. Are you sure yo got the right version of the project? Are you opening it over a network connection or transferred by removable media or...?
 
EDIT: Cross-posted. Sounds like some mute/solo or automation/offset state was not read properly in the new environment. I suggest you double check all the track/lane/clip statuses in X3 that might be relevant, and see if something's not initially in the same state on opening it in Platinum.
 
 
 
 

Check the MIDI buffer setting in Platinum's preferences. It tells Sonar how far ahead to read MIDI tracks, and by default it is 250ms which can lead to dropped MIDI notes on playback. If it is at 250 try setting it to 500 or 750ms.

brundlefly:  Thank you for your response, input and advice.  Much appreciated.
 
tlw:  That fixed it.  It was set to 250ms in Platinum.  I bumped to 750ms and it appears that all is well now.  THANK YOU!

Last update:  I was finally able to check my Win8 64bit DAW running Sonar X3.  The setting for midi playback was also set to 250ms. 
 
It's still true that changing the setting to 750ms on the Win7 64 bit DAW running Platinum fixed the problem on that machine.  Again, hats off to tlw.  I'm using midi but I'm pretty much a novice.  For me, this type of thing is like trying to find a missing period (".") in pre-COBOL II code.  :)   Tnanks again, tlw!

The 250ms MIDI buffer and the various problems it causes turns up so often on the forum it's ridiculous. I guess 250ms must work for some, maybe most, people or we'd see it even more often, but even so it obviously causes problems for quite a few people, myself included in the past. So I just set it at 500 from the start.

What would be interesting is to know why it's a problem on some DAWs but apparently not on all, unless lots of Sonar users search for the symptoms and find the answer here or elsewhere.