I've just scanned through about 40 bugs that I submitted in the last 12 months or so (all confirmed by CW) and decided to start bringing up several of them here to explain why I want them fixed in particular and to see if others are also affected by the issues (if you think it's a bad idea, please read this post).
 
The first issue I'm posting is this:
 
What is the issue?
In this screenshot, a MIDI clip is selected and the Event List shows the last event in the clip is a controller event (modulation), whose value is 0.

 
If you move this clip or copy-paste it to a different position, the last event disappears from the clip moved/pasted. If you slip-edit the clip to the right (i.e. drag the right edge of the clip to the right), the last event shows up again.

 
Who are affected by this issue?
MIDI users who frequently record controller data (pitch bend, modulation, sustain, etc.) and move/copy clips a lot and prefer to work with "Non-destructive MIDI Editing" disabled.
 
What CWBRN# is it?
CWBRN-24451. The steps to reproduce the issue can also be found in this post (for forum members).
 
Why is the issue so serious?
Since the last event disappears and gets ignored, the clips that come after the clip play notes at a wrong pitch (when the last event hidden is a pitch bend event), wrong modulation level, etc. To prevent this, users have to insert a dummy event at the end of each clip whose last event is a controller event. The worst case I experienced recently is when I copied all MIDI clips in an old project and pasted them into my latest project template I created in X3d. What happened is that all MIDI clips of this type lost (hid) the last controller event when they are pasted into the project template, which made many clips play at a wrong pitch, wrong modulation level, etc. I had to insert a dummy event in many clips, and I have LOTS of old projects whose clips I'm planning to migrate to the latest project template.
 
Any other comments?
The reason why this more-than-a-decade-long bug is starting to affect me seriously is becasuse I've come to record more controller data these days and also move clips a lot more than I used to. A clip should contain exactly the same data when it is only moved.
 
Thank you

I can't say I've been affected by this myself, at least not that I'm aware, but I will certainly "+1" your request since the results seem fairly obvious!
 

Thanks Steve. Being on this forum for a year or two, my impression is that the majority of users here mainly record audio, and the rest record MIDI either mainly or equally, but probably only a handful of them use the bender lever or expression pedal frequently and move around short clips, or maybe they prefer non-destructive editing, or......maybe they just don't notice that some clips in their project in fact sound somewhat off pitch or shaky. 
 
What I'm trying to say is that there must be a good amount of users around the world who have this happen (whether they're aware of it or not). Anyway, what's important here is that there's no good workaround to this issue. Opening the Event List and inserting a dummy event at the end of the clip every time after recording this type of content isn't certainly a good one. I hope CW will fix this soon. 

This is at or near the top of my list of niggling issues that are way overdue to get fixed. As a Piano player, almost everything I record ends with a sustain pedal up event. When that event isn't processed, the final notes ring on indefinitely. When I copy a clip to layer acoustic and electric pianos, I always have to fix this.
 
Note, however, that the final controller event isn't gone; it's just that the clip is slip-edited back to the end of the last note. Pulling the clip boundary back out will reveal the missing event and restore it to functionality (and visibility in the Event List).

brundlefly
Note, however, that the final controller event isn't gone; it's just that the clip is slip-edited back to the end of the last note. Pulling the clip boundary back out will reveal the missing event and restore it to functionality (and visibility in the Event List).

 
Yes, that's what I also discovered (about a decade ago) and mentioned it in the original post. Pulling the clip boundary back out is good only if you aren't going to move or copy-paste the clip again. In my case, I move clips more than once in many cases (hence the cumbersome "dummy event" workaround) and, as I mentioned, I even move entire clips between projects.
 
This really should be fixed IMO.

So this doesn't happen with Non-Destructive midi editing enabled? Or is it just easier to "fix"

Doesn't happen if Non-destructive MIDI Editing is enabled.

I was very excited when I found "Final CC64=0 sustain pedal up event not copied when non-destructive MIDI editing is disabled" in the Bug Fixes section of Noel's blog post, and I rushed to check if it's not just sustain pedal but also pitch bend and modulation. And.............YES!!! This more than a decade-long bug is now fixed in SONAR 2015!!!

I still can't believe it. Am I dreaming? Really really glad that I no longer have to add a dummy event after the last controller event in the clip. A BIG arigato to you, Bakers!!! 

Yeah that was a simple calculation error where the crop test was incorrect. 
There were some other 15+ year bugs fixed with MIDI CC rendering. Pedal events could be rendered from the cropped out area of the clip which could lead to unexpected behavior. Controller searchback would also see stuff it shouldn't have.
There are lots of MIDI editing and rendering fixes and improvements in this version - a lot more than we've done in a long time.

I use MIDI a lot. Normally I end up moving clips or groups of notes within PRV so I can't say I've ever seen this, or realized it was happening. Or maybe I do everything non destructively. Either way I'll have to watch for it.