You should open a support ticket, they won't fix it if you post it here...
 

Yeah, I just entered it to the bug report from the link above. Hope they able to reproduce it.

vladasyn
Ok- the Piano Roll showing wrong notes on the roll is reproducible after computer full restart. It related to freezing software instrument and then unfreezing and attempting to change notes. After it unfreezes, it shows keyboard not aligned with the greed.

 
Please try this please with a brand new project. If it is reproducible at your end then far more specific steps will probably be needed like this example (always start from a brand new project):
 
http://forum.cakewalk.com/The-last-event-cont-event-rolls-off-the-clip-when-the-clip-is-moved-Confirmed-by-CW-m3004953.aspx#3004953
 

vladasyn
If somebody can submit it to the bug report, please, do so. I already spent whole evening dealing with it. It is a bed time. Thank you.

You can submit a problem report here:
https://www.cakewalk.com/Support/Contact/Problem-Report
 
You are probably better off contacting Cakewalk support if nobody else can reproduce. If somebody else can reproduce the issue with Platinum I or another host will also move this issue to the problem reports forum, if you give very specific steps so this is very easy to reproduce , then this is more likely to happen.
 
Thanks..
 
(Update: I see you have submitted a problem report thanks, could you also paste the issue number here please...).

Alex, why should I start in the new project? The point is that it became unstable in given point of the project. I can not recreate all the steps that were ever taken in this project again to reproduce it. Also if it happens in one project, it means, it happens. We should not give it excuses, like, "Oh, this does not count because it had software synth inserted. This does not count because it already had a drum track..." The bottom line- I should be able to do all operations I did without causing it to crash and become unstable. If it not happening in another project does not mean that it is ok for it to happen in this project and we should overlook it. Too many problems get overlooked this way. There is no "ideal' environment. If you testing a car, you not going to keep it in the lab, you will take it to the road test. Well- New Sonar is unstable when used. It is not our job to take it to the lab again. We do not get paid for it. We pay for it to work.

You should go to bed...

vladasyn
Alex, why should I start in the new project?

If you want the issue to be fixed by developers they need steps to reproduce your issue. The way to do that is give steps from a new project. Otherwise it is a wild goose chase, anything could be the cause. So sure if you want to register your disappointment with a bug that is understandable. But nobody is going to be able to fix the bug if they or others cannot recreate it at their end. Developers spend a lot more time fixing bugs than searching for them.
 
It understandable what you think is right and wrong but this is the reality I'm afraid. Perhaps you will be lucky and cakewalk has already given steps to repro by another customer, assuming it's not a dodgy plugin or something... Then you won't need to do anything...

This is exactly my point. It can be "anything" and "anything" can cause it to fail. And it should not. It was happening on a new track with a new instrument. Obviously the problem is with unfreezing the synths. And this is important. I need to be able to freeze synth without hesitation. A lot of times I would leave synths unfrozen in case I want to use the same sound later in the song. This creates overload on the CPU. It is good to know that synth freezes and unfreezes without issues. In Sonat X3, it would do it easily. Done it million times. Unfreeze and synth is nice and fresh with selected sound ready to be used. With New Sonar- it does not unfreeze very well- some how it affects the MIDI track. I don't see how. It may have something to do with zoom. If you ever look in Piano Roll on frozen MIDI track- the piano keys turn in to the numbers. I do not like it, I don't know if it meant to do it or if it another issue. Instead of piano there is a table of numbers. When you unfreeze the synths, the numbers supposed to convert back in to the image of keys of a keyboard, and they do not convert very well. Also Copy. Paste and Drag getting massed up and cause crash. I submitted report to Cakewalk. I know this is not minor accidental issue. I can tell the difference. Been using Sonar for years. This is permanent problem that needs to be addressed. But you can try to reproduce it just for fun. Insert software synth with MIDI and Audio track, record midi notes, freeze instrument, look at your MIDI track in Piano roll. You will see numbers (unless it just me). Then unfreeze it and try to enter manually new notes. Then see if they correspond to the keys. Right click on a note and see if it says A6 and not Eb7. If it shows wrong notes, try to drag them from place to place and aggravate it till it gives up (or not). That is what happened.

the key is to islolate the issue that's why we asked to try in a new project ....
 
is it doing it in every midi clips or a specific one ...if yes , witch synth is linked to ?
do you have a instrument track or the midi and audio separeted ?

The synth used was reFX Nexus. I have tried it in the new project. The issue with notes being in the wrong place indeed related to zoom. When it unfreezes, it somehow changes keyboard size that does not match the greed (notes). When manipulating zoom, it gets in place instantaneously. So this is good thing. I moved the track back and force for few minutes- it did not crash yet. I will work with it more and see what happens.  

I just did what you said to do & did not have the problems you did. Freeze/Unfreeze Etc and all the notes stayed the same & displayed correctly in the PRV & the keyboard did not change size.