Undefined Controllers names

[CLAUDE MARC BOURGET]

I ask a question here of two forums: Avid and VSL.

If we work with Pro Tools and Vienna (VSL) and we add more controllers available in Vienna, the automation tracks in PT tells us: "Controller undefined". So if we add 5 controllers, we have 5 controllers undefined ... difficult to interface! Even the colors are fixed ...

So why not give PT the opportunity to rename the controllers?
Or: why VSL does not meet the list of automation within the parameters of its plug-ins (to transfer just the names)? The customer is trapped between two teams of programmers ...

[CLAUDE MARC BOURGET]

A VSL technician could answer this question? Why controller names in the plug-in "Instrument Pro" (for example) are not transmitted to Pro-Tools, as do the other plug-ins from other banks? The results give "undefined" controller. I must not be the one to ask this question. There may be a trick to circumvent this defect ? I favor total VSL, but on this point, I can only ask me.

Thanks.

[andyjh]

 In VI Pro you assign a controller number to a function (i.e Master Attack), you are not naming the CC itself, so although you may have assigned CC22 to Master Attack, CC22 is only ever CC22, and in the MIDI spec CC22 is "undefined", which is why it will always show as that.

All the DAW programs I have used, certainly do not pick up any CC function name form the VST plug in and pass it to the host, though I have not used PT, it always seemed to be the most inferior in terms of MIDI control of all the DAW's out there - unless this is one unique function that PT has sneaked in.  You'll need a PT user to confirm/deny this.

You say VSL does not do it, but do any VST plug in's send their assigned CC function to PT by name?

[CLAUDE MARC BOURGET]

Pro Tools since version 7 (we are at 10), is very good at noon. This judgment has changed the face of facts. But I understand that, for non-users of PT, this judgment remains.

However, to our question of plug-in, it's automation. The plug-ins typically transmit their parameters to the DAW (for automation). For controllers, the identity of it (the function, as you say) is also transmitted. At the stage of choosing between the parameters of automation, as needed, the user sees a list of controllers (C20, C21, C22, etc.), with names. The controllers are configured in the plugin. DAW then, at that time, shows a series of tracks in which each automation is named.

Here three image captures. Play in the list of Eastwest (instrument). That in Epure (which is an EQ), and the years Vienna Instrument Pro ...

PLAY :

EPURE(EQ):

Vienna....