Help please: Convert PRV controller data to Track View envelopes

Clips>Convert Midi Controllers to Envelopes not working for me.
 
I select time track, clip and time range. Go to Clips>Convert Midi Controllers to Envelopes. Get the midi shapes popup window select the controller and channel, Click OK and then nothing happens. What am I missing please?
 
Also sometimes the controllers I'm using in PRV are not listed in the Midi Shape selection dropdown. How do I get them there?

Is working here.

What are you trying to convert?

I don't think "Velocity" controllers can be converted but Pitchbend and others can.

You can type the controller # in and see if it works, but if the listing box is blank then its probably not available for that track.
 
Steve

Well that explain it then. You have a Virus!

Seriously, I've only tried this on virtual synths and they vary. I haven't used outboard MIDI gear in a while so that might have something to do with it. I think Sonar responds to a particular device regarding MIDI controllers. If it can't communicate with it you'll get a blank screen.

Read up on your device and check out the Sonar Help PDF download if you haven't already.

Steve

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.

Ah Got it. Thanks SuperG.  I didn't realise you could type a controller number in to the controller selection field. In Win 8 it just looked like a dropdown selection only list list to me.

Now envelope conversion is working for me. This might help one or two others as well. Many thanks.

I still think that you're better off running split Audio/Midi tracks, rather than Simple Instrument Tracks, simply to avoid these sort of problems.

If it works for you using split then there's another reason not to use SIT's (apart from all the other well documented reasons)