scook
It is possible to draw/updte CC in an automation lane. SONAR provides a way to convert MIDI controllers to envelops in the Track View Clips menu. 

I was completely oblivious to that...good to know.

scook
It is possible to draw/updte CC in an automation lane. SONAR provides a way to convert MIDI controllers to envelops in the Track View Clips menu. Going the other direction is a little more involved requiring a virtual MIDI cable to record automation data in to a MIDI track.

For reverse direction I use the following procedure:

• select the clip in question. "Copy special...", include "Track/Bus Automation" and exclude "Tempo changes"
• create new temporarily project, add one MIDI track.
• "Paste special..." into the track, including automations.
• "Save" the project as "MIDI Format 1" MIDI file (does not work with format 0!). Close that project.
• "Import MIDI..." into the original project.

Wow, another great tip. Very clever.

azslow3

scook
It is possible to draw/updte CC in an automation lane. SONAR provides a way to convert MIDI controllers to envelops in the Track View Clips menu. Going the other direction is a little more involved requiring a virtual MIDI cable to record automation data in to a MIDI track.

For reverse direction I use the following procedure:

• select the clip in question. "Copy special...", include "Track/Bus Automation" and exclude "Tempo changes"
• create new temporarily project, add one MIDI track.
• "Paste special..." into the track, including automations.
• "Save" the project as "MIDI Format 1" MIDI file (does not work with format 0!). Close that project.
• "Import MIDI..." into the original project.

 
It's too bad dragging the clip to your desktop won't work. Is there a way to know what .mid format the drag function creates?

Of course the most tedious method to edit naughty cc data is in Events View.
 
In PRV you can click-hold a cc node and it will display its data in a tool tip. It would be nice if you could double click it and open an editable properties window like you can for the notes.

Even if you could expand/grow an individual control lane, within the PRV, it would be helpful. Currently they have some adjustable height but More would be better and make detailed editing much easier to see.

rtucker55
Even if you could expand/grow an individual control lane, within the PRV, it would be helpful. Currently they have some adjustable height but More would be better and make detailed editing much easier to see.

A work around is to hide all the controllers except the one you want to work on then increase that controller window size.  This can be a PITA if you have a number of CCs but it does work.
 
PS - I do like your idea much better than this work around!

MarioD

rtucker55
Even if you could expand/grow an individual control lane, within the PRV, it would be helpful. Currently they have some adjustable height but More would be better and make detailed editing much easier to see.

A work around is to hide all the controllers except the one you want to work on then increase that controller window size.  This can be a PITA if you have a number of CCs but it does work.
 
PS - I do like your idea much better than this work around!

 
Thanks for the suggestion but I already do that (Only if I have to) and I agree that it can be a pita when several controllers are used.
 
I spend a lot of my time in PRV and it generally is functional and usable but, It can be a time consuming monster to accomplish simple things. Hopefully X4 will solve some current workflow issues.

MarioD

rtucker55
Even if you could expand/grow an individual control lane, within the PRV, it would be helpful. Currently they have some adjustable height but More would be better and make detailed editing much easier to see.

A work around is to hide all the controllers except the one you want to work on then increase that controller window size.  This can be a PITA if you have a number of CCs but it does work.
 
PS - I do like your idea much better than this work around!

 
Do you use screensets at all? If you can afford to dedicate a few of those in a project to CC editing you can set them up with just the controller you want to edit in each one and then switch between them for editing. It saves having to hide controller lanes all the time as it's already done in the set up procedure.
 
Duplicating screensets makes setup relatively quick as well.

I personally never warmed up to screensets. IIRC there were some issues when they were first introduced and I never pursued them afterwards.  Probably something I should look into again.

I've always wondered why editing CC data in the PRV wasn't as easy as editing automation lanes in the track view. I work exclusively with virtual instruments, many of which have countless articulations controlled by CC data. It would be so nice to have a straight horizontal line set at a default value to begin with, and then be able to add nodes and create fast/slow curves and such. Why hasn't this been implemented? Do any other DAWs have this function?