Now I get it, and that's wonderful.
Now I can easily make CC curves:

1. Drawing a straight line (F9):
   
2. Dragging the center point to the right:
   
3. That' it:
   

Thank you Cakewalk!

Very nice job on the PRV ... Thanks one & all...

Just wanted to join the thanks-giving train!
 
Since I do a lot of stuff with EWI and dealing breath CC among other CCs, this new PRV transform tool is GREAT!  This is exactly what I've been wanting!
 
(Although, could I ask that while autofocus mono-phonic is on, and you change the length of a note, it also automatically scales the length of the CC data?  :D  Or make it a toggle option... although right now, at least the transform tool itself makes this pretty quick to approximately match... )
 
Seriously, thank you!

rogeriodec
But you still need to have a tutorial.

I was able to pretty much work out the transform tool in around 10 minutes without the docs.  It's quite intuitive.

Just load up a dummy project, chuck some controller events on a PRV.  Click on the transform tool , click and drag a few nodes and see what happens.  Try right clicking a few nodes and see what that does too.

Try right clicking on the transform button itself and explorer the menu options there as well. The Auto focus is handy in that it automatically surrounds selected events with the transform window.

Part of the fun of these things is loading things up and see what they do. 

Also, remember the 2017.4 update includes updated help files that have sections that describes the new transform tool in more detail.

Thanks Cakewalk

ampfixer
IF we don't do a lot of midi, is there a compelling reason to update this month? Serious question.

No. Bu as the updates are cumulative, you will end up with all that's in this release whenever you next update anyway.

Cakewalk has still to solve the problem of the real-time MIDI reverb and chorus settings in the track inspector pane.  When recalling a previous save on MIDI tracks the dials stay set to zero (0) however in the view event list the previous values are set in the in line controller values.  Sonar X3 recalled the setting and displayed them on the reverb and chorus dials respectively for each track.  It has been along time and many requests to Cakewalk to fix this.  This occurs when generating and recalling MIDI (.mid) tracks only.  When saving and recalling a project bundle the reverb and chorus seen to be correct.  However, sometimes I want to work with just MIDI files.

Leonardo2
Cakewalk has still to solve the problem of the real-time MIDI reverb and chorus settings in the track inspector pane.  When recalling a previous save on MIDI tracks the dials stay set to zero (0) however in the view event list the previous values are set in the in line controller values.  Sonar X3 recalled the setting and displayed them on the reverb and chorus dials respectively for each track.  It has been along time and many requests to Cakewalk to fix this.  This occurs when generating and recalling MIDI (.mid) tracks only.  When saving and recalling a project bundle the reverb and chorus seen to be correct.  However, sometimes I want to work with just MIDI files.

We'll take a look into this.  When you say recalling previous save, do you mean saving a project, closing it and then opening it? 
 
Keith

Keith,
Yes.  When I save a MIDI only project (.mid) files such as backing tracks for a live performance and come back to it say the next day and load the MIDI file for more updates the reverb and chorus information can only be viewed using view track events.  With Sonar X3 as well as X2 and X1 the reverb and chorus settings are visible the track inspector pane real-time dials.  When selecting a different track the values of the reverb and chorus dials change respectively however NOT in Sonar Platinum.  Although when working with a Cakewalk  (.cwp) project file values ARE shown respectively.
Thanks,
Leonardo2

ampfixer
IF we don't do a lot of midi, is there a compelling reason to update this month? Serious question.

FYI, there were two fixes that didn't get mentioned unrelated to MIDI.
1) VST3 program change compatibility.  We addressed the crash reported against plugins built with the lastest VST3 SDK  In addition, program changes now work with VST3s that support them.
 
2) there was an issue where track sort (by name, etc.) could result in view updates getting stuck and other weird behavior.with the track strips.
 
Both of these are in the 04 update.