This might be due to some misunderstandings
There is a list of CCs in PRV when you show the controller pane and choose a controller lane. If the controller you're looking for is not listed, simply type in its number in the edit box. The dialog that shows up uses a drop-down
edit control, which allows you to select from the list
or edit it's value directly rather than a drop-down
list control , which *only* allows selecting from the list.
It's basically the same in the track view as well. If there's no data that exists for the CC you wish to control there, you can simply create the lane for that control number.
What a lot of people don't realize is that it's possible to have both CC automation lanes
and CC midi track data at the same time. CC data from a track is sent out at the same time CC data is generated from an automation lane, and it is
very possible to get them to conflict and wind up with something you didn't want.
Many people prefer to take
existing CC data from a track (say from an existing midi file) and convert it to automation lane data - this way they are working only with automation lanes and this eliminates cross-ups. But there's no need to do this if a track doesn't have preexisting CC data. Conversely, you can choose to work with midi track CC data only in the PRV and forgo automation lanes.
My best suggestion is to work either with midi track CC data, or with CC automation lanes, but not both at the same time.
You can choose to do both simultaneously if you feel comfortable, know the issues involved, and keep track of what's happening.
