193,853 users have contributed to 42,898 threads and 257,860 posts.
In the past 24 hours, we have 4 new thread(s), 15 new post(s) and 88 new user(s).
I would use such a feature to rename the parameter because I have not way in kontakt 6 to rename the automation parameter name. I thought this was just an issue with VSTs but it is also an issue with AUs. When the instrument scripts are locked in Kontakt and we cannot change the Automation name in Kontakt the mappings are lost everytime a VEP instance is saved and then reopened. The parameter in VEP will all match up to first name in the automation of Kontakt.
When the instrument scripts are locked in Kontakt and we cannot change the Automation name in Kontakt the mappings are lost everytime a VEP instance is saved and then reopened. The parameter in VEP will all match up to first name in the automation of Kontakt.
I too would greatly benefit from such a feature.
My DAW (Studio One) does not provide its own aliasing facility. It displays whatever VEPro transmits. In theory this is fine, but in practice it is less than ideal.
1. I use a lot of plugins that only expose a generic list of parameters. I make heavy use of Plogue Bidule, for example, as a wrapper around most of my instruments (using it to perform heavy manipulation of the MIDI input and audio output), and Bidule's parameters are simply named "Param0001", "Param0002" - not very useful. Bidule does not provide a way to rename these (it's VST2 only), so I'd love to be able to rename them in VEPro. That way I could see something actually useful in my DAW, based on how I'm using that parameter.
2. Even with generic names, the VEPro name is quite long. Even if I clear my track name (not ideal), I get something like "2 Bidule VSTi x64 - Param 0001". Now, I'm completely in agreement with how VEPro is handling these generic names - I don't think there's a better way to generate a name, by default. That said, these names cause me a problem. I use a PreSonus FaderPort 8, which communicates nicely with Studio One, and lists the automation parameter names on its display. Problem is, when the name is more than 8 characters, it gets truncated - and StudioOne does a poor job of truncating. It cuts off the unique ending of these parameter names, and leaves me with a truncated name that is identical for every Bidule parameter (e.g. "2BidVSTx"). Which leaves me completely in the dark as to which of the parameters I am controlling (typically upwards of 30 to 40).
I sympathize that both of these issues come from software other than VEPro: Bidule's inability to rename parameters, StudioOne's inability to alias automation parameters (despite it being requested in the feature requests), and StudioOne's poor job of truncating names. However, given that a discussion of parameter aliases has been opened here, and given that it seems like something that would be reasonably intuitive to add into the existing system (simply setting an alias after mapping a parameter), I'm really hoping this is a feature that VSL will add to VEPro. It is unlikely this will be addressed in Bidule or StudioOne.
Thanks!
Steve
Well I kind of thought this would be sorted by now - and again I came across a need again. This time with the UVI plugin library Ravenscroft.
I am using the VEP client plugin hosted inside Komplete Kontrol.
In the mapping window the parameter names are like:
1 RAV/UVIWORKSTATION/Reverb etc
Inside Komplete Kontrol the parameters are all named 1RAVUV. Not very helpful really.
Please add some kind of alias short name feature.
Otherwise I'd say this parameter mapping is just useless.
And since this is just something to make an existing feature actually USEABLE - I'd rather not have to pay for this as an upgrade.
I've enclosed a screenshot of the VEP instance shoUwing mapping names. Its just unworkable as things are right now.
Hi Paul, I also think having the ability to rename parameters would be great and speed up the work a lot.
Thanks very much
Alias capability would be very useful to me as well.
A lot of us! Anyone that want to see automation parameters clean in their daw or in the screens of their controller.
@MS said:
Is it not possible to just add the for an "alias" name that us users can optionally just set ourselves?
I think that could be reasonable. I'm just wondering how many would actually use such a feature?
