Undefined Controllers names

[cmbourget]

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 ...

[cmbourget]

A technician at Avid could answer this question on pro-tools? Why we can not rename a controller "undefined", or rather identify it, if the identity is not automatic?

[daeron80]

I get what you're saying. I'd like to see the ability to name them, too. It's a great idea. I'll suggest it on ideascale.

But it's not really the programmers' fault. They were left undefined by the engineers who designed the MIDI spec back in the early 1980s. "Undefined" in this case means only that they have no standard function. Their purpose is not specified by the standard, and they are thus available for any purpose that (then) future hardware or software designers might think up. Now that we're commonly using scads of CCs for plug-in automation, it does get annoying to see multiple lanes of "undefined." I make a list on a sheet of paper to keep track of which number is for which parameter of which plug-in. Shouldn't have to use pen and paper to help a computer with such a simple matter!

[daeron80]

So, I mean, you could like vote for it if you want to...