Vienna Symphonic Library Forum
Forum Statistics

194,027 users have contributed to 42,906 threads and 257,900 posts.

In the past 24 hours, we have 4 new thread(s), 19 new post(s) and 105 new user(s).

  1. Home
  2. Software
  3. Vienna Instruments Pro
  4. VEP7 - Automation parameters - need for rename or "alias" facility
  • M
    M

    I've tried to make the presented parameter name as short as possible, while still keeping all information required to identify which plugin/parameter it controls.

    If you have any ideas on how to improve this, I'd be happy to hear it!
  • D
    D

     

    Is it not possible to just add the for an "alias" name that us users can optionally just set ourselves?
  • M
    M
    last edited
    last edited

    @Daniel Stenning 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?
  • civilization 3C
    civilization 3C
    last edited
    last edited

    I would, for one or two things. What BFD3 exposes to VE Pro is a single automap; which I edited to get objective names so that I don't have their hardwired eg., 'high tom 2' where in fact I put a cymbal there, so after a point it's all ''BFD3 ch(05) gain" etc and every preset may be different.

    Short of the user-determined name, I think you could lose "Vienna" in the string 'Vienna Synchron Player"; cf., "Kontakt" is just "Kontakt", not "Native Instruments Kontakt"
  • R
    R

    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.   

    Image

    Image
  • civilization 3C
    civilization 3C
    last edited
    last edited

    @rlw said:

    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 don't actually understand that last sentence, but something's very wrong on your end, 'mappings are lost when...'.
    The majority of what I use in Kontakt has fixed automation (almost all SonicCouture is now, I was able to retain one earlier version which isn't sold anymore.). The only time I lose mapping is disabling the channel w. Kontakt. Same with Reaktor. I could not stand to lose automation mapping. 
  • Z
    Z

    I would DEFINITELY use such a feature. As it stands the Logic Pro smart controls revert to the VEP naming convention applied in the VEP automation...and that makes it impossible to read in Logic and the user must refer back to VEP to determine what is what. Very frustrating.
  • S
    S

    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
  • D
    D

    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.  

    Image

    Image
  • PaulP
    VSL Team
    PaulP

    Hi Daniel,

    What do our colleagues at Ravenscroft say? They pick the naming scheme that is displayed. 

    But it's a good idea to add a way to rename parameters, and this is also on our wishlist already. 

    Best,
    Paul

    Paul Kopf Product Manager VSL
  • L
    L

    Hi Paul, I also think having the ability to rename parameters would be great and speed up the work a lot.

    Thanks very much
  • DaddyOD
    DaddyOD

    Alias capability would be very useful to me as well.

    Synchron - Woods, Brass, Perc I, Str Pro, Elite Str, Duality Str & Sordino, Prime Studio - Woods, Perc, Solo Str, Ch Str, Orch Str, App Str, Harps, Choir Studio Dim - Brass, Strings VE Pro, MIR Pro 3D, Vienna Suite Pro Cubase 14, Studio One 6, Dorico 5
  • D
    D

    A lot of us! Anyone that want to see automation parameters clean in their daw or in the screens of their controller.

    @MS said:

    @Daniel Stenning 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?
  • B
    B

    Yes! renaming automation parameters is a must!