Two tracks open in PRV.   Two notes at different pitches beginning at the same time.    Select the track with the higher pitch.    Open controller pane, make sure 'velocity' is visible.  Curse cakewalk for the other controllers cluttering up the view.   Now try to adjust the velocity of the selected note by dragging the velocity bar up or down. 
 
Bug:  the LOWER note, in the UNSELECTED track, is adjusted and becomes the selected note. 

This one?
http://forum.cakewalk.com/Wrong-track-when-changing-velocity-in-control-pane-m3162693.aspx
 

yes indeed, the very same one... sorry hadn't noticed the earlier post
 

maybe our hosts can combine such posts?

Didn't see that anyone logged problem report, so here ya go:
 
CWBRN-32621 "Editing Velocity in PRV Controller Pane changes active track to last track"
Repro steps:
1. Create new project
2. Insert 3 MIDI tracks
3. Import the same groove clip into all 3 new tracks
4. Select all 3 tracks and open PRV
5. Make track #1 active
6. Hover the mouse over a velocity bar to get double arrows and click the bar to edit
 
Expected results: Track #1 should remain active and dragging the mouse up and down should change the velocity value in Track #1.

Actual results:  Track #3 becomes active immediately after clicking the velocity bar and all edit are now directed to Track #3.
 
Notes:  The only way to prevent the active track from being changed is to lock all tracks not being edited. In the sample project, locking track #3 will cause the active track to change from track #1 to track #2. The problem appears to only occur when the multiple tracks have events at exactly the same time with same velocity.
 
Would one of the Forum Hosts please merge this thread with http://forum.cakewalk.com/FindPost/3162693?
 

The PRV with multiple tracks is a great idea that has been implemented miserably.  And the shame of it is that with a few seemingly minor changes, it could work well for almost everybody.  I put a few of those suggested changes on this thread.
 
http://forum.cakewalk.com/In-PRV-controller-lanes-are-practically-unusable-please-fix-this-m3166007.aspx#3201598
 
Let's hope that Cake can pull themselves away from all the digital processing glitz and focus the next update on fixing these basic problems.