Lest it be forgotten:   it's a bad bad thing to add a track to a group of tracks in PRV (using "pick tracks") and suddenly have every controller on every channel on every track raise their horrible heads again and fill the controller pane.   
 
This is the SINGLE biggest issue on Sonar Platinum for me.     I've worked out a variety of work-arounds, but the basic function is so terrible it should be fixed.
 

I wish someone would vote on this ... it really is the worst thing in sonar platinum as I use it ... worse than crashes, worse than command center writing on the C drive, worse than staff notation weaknesses ...

I think not many people in the Sonar forum show multiple tracks in the PRV and draw/edit controller data. To be honest, I feel the percentage of users in the forum who create synth-heavy projects is quite small. I used to do it a lot, but have never found Sonar's PRV Controller pane intuitive or easy to use. When Platinum came out with some PRV improvements, I created a test project and tried editing controller data in the PRV with multiple tracks displayed, and still found it not user-friendly (probably because I was comparing it to Studio One's very simple and easy to use controller pane). I really didn't like several lanes showing up (which made editing difficult) and didn't like the small add/delete buttons and drop-downs in the lower left corner, too. So I tried drawing/editing everything in the Notes pane (with the Controller pane closed), but there were a few things I couldn't do there, so I gave up. I wouldn't say it's the worst thing in Sonar, but it's definitely one of the weaknesses in the program. So, voted.

Thanks for the vote!   As I've said before, if it weren't for the miracles I can do with special cal programs, I would not even be here posting any more.   But the problem with the controller pane is a huge pain.  #2 pain is screensets fixed to number keys ... even after now months of experience with Platinum, I still occasionally fail to put the focus correctly onto a number-oriented field, like now time, or loop start, or select end, or event position, then rapid-type a series of numbers .... Sonar interprets them as screenset changes, I wait a few minutes, find all my minimized windows have been re-ordered, all the focus on the screen has been changed ... 

So for this specific aspect, what is your request?   I get that multiple track controller lanes aren't exactly optimum, I'm just curious to hear what you would suggest as an alternative - something more concrete to vote on.
 

williamcopper
#2 pain is screensets fixed to number keys ... even after now months of experience with Platinum, I still occasionally fail to put the focus correctly onto a number-oriented field, like now time, or loop start, or select end, or event position, then rapid-type a series of numbers .... Sonar interprets them as screenset changes, I wait a few minutes, find all my minimized windows have been re-ordered, all the focus on the screen has been changed ... 

 
Can't this be avoided by assigning the "Do Nothing" command to each number key in Edit > Preferences > Customization > Keyboard Shortcuts?

To answer the "what specifically" question:  one simple solution would be a PRV-specific thing:  a drop-down list of all controllers to select which controller to show.    That's part 1.    And REMEMBER IT as long as the window is open, even if the contents of the window change by using 'pick tracks' or the like. 
 
And then maybe slightly more complicated, eliminate the "by channel" nature of the controller pane and show those controllers that are WANTED for the ACTIVE TRACK only.    Make it a preference thing, if some don't like this, but I don't see why that would be needed.  
 
And last, while in the Controller pane, change the default for the smart tool so it doesn't grab onto a controller value whenever you try to draw anywhere near a previous controller value.    #3 time waster today in my work
 

To answer about the number keys:  no, bind to "do nothing" does not work.   This has been suggested often, because it looks like it would work, but it doesn't.   Maybe this is a bug.
 
 

williamcopper
And then maybe slightly more complicated, eliminate the "by channel" nature of the controller pane and show those controllers that are WANTED for the ACTIVE TRACK only.    Make it a preference thing, if some don't like this, but I don't see why that would be needed.

Given this model, how would you address the case you brought up previously where you want to edit controllers in one track with reference to values of the same controller in one or more other tracks?
 
Re-using controller lanes without reference to channel would have to be optional to maintain usability for projects that have events with different channels in the same track (i.e. Type 0 MIDI files), not to mention the per-channel model is one way to address the above situation.

williamcopper
To answer about the number keys:  no, bind to "do nothing" does not work.   This has been suggested often, because it looks like it would work, but it doesn't.   Maybe this is a bug.
 

 
Works for me.