Vienna Symphonic Library Forum
Forum Statistics

200,530 users have contributed to 43,200 threads and 259,097 posts.

In the past 24 hours, we have 2 new thread(s), 10 new post(s) and 68 new user(s).

  1. Home
  2. Software
  3. Vienna Instruments Pro (legacy)
  4. VEP Feature Request - CC Transformer

  • VEP Feature Request - CC Transformer

    Y
    Y

    Hi VSL,

    Firstly I would like to say that VEP is running GREAT here. I've got a 240 patch template slaved to Logic and it's really very solid. I've got 2 duplicated systems running here so we can write and mix in both rooms simultaneously. By being careful with IPs and network cables I've got the 2 systems set up so that simply dragging and dropping Logic projects across the network allows projects to be seamlessly opened in either room!

    I would like to please suggest that a basic midi CC transformer should be implemented in VEP on a per instance level. The reason for my request is the whole "Logic won't send CCs 7 & 10 to an AU instrument" issue.

    By using Logic MIDI transformers in the environment to convert CC7 and 10 to alternative CCs I've been able to get the data for Volume and Pan through to VEP (on CCs 25&26 in our setup). This works fine in Kontakt, because I've been able to write a KSP Multi-Script to convert the alternative CCs back onto 7 & 10. It's also fine for a lot of other plugins that provide a midi learn facility. BUT for plugins that have fixed CC controllers and no MIDI learn, the best solution is to use CC11 (expression) to control level, and to use pan only on a set and forget basis. (My primary example of this is EW PLAY). If a basic CC transformer was implemented on a per instance basis, this would mean that by combining a couple of transormers in the Logic environment with the opposite transformers in VEP, it would be possible to make all plugins behave as normal!!!! This would be a massive improvement for all Logic users - I wouldn't have to be scripting Kontakt, going through banks of faders learning them to alternate CCs, and more importantly I could control levels and pan in PLAY! I'm sure that the vast majority of pro users (especially those using Logic) would find a little CC transformer uttlerly invaluable!

    I know that the real issue here is Logic's odd MIDI behaviour on AU instrument channels (intercepting CC7 and 10 to controll the fader and panner for that audio channel). A simple "CC7 & 10 control plugins not faders" checkbox in the Logic preferences would sort it out this issue too. However, I think it's much more likely that you good guys at VSL will hear my request and may consider implementing it! I'm sure there are plenty of other instances where a CC transformer would be extrememly useful to other users (besides those using Logic) as well!

    Thanks for considering my request!

    Regards,

    Will Rice

    p.p Sheridan Tongue
  • D
    D

    I think that this is unnecessary. I don't think it's the job of the VSL programmers to waste time programming around the "features" of one specific sequencer, particularly when there is already the workaround that you mention.

    i think that this is a request that needs to be sent to Apple.

    DG
  • Y
    Y

    DG, although I definately agree that this is something that also needs to be taken up with Apple; let's not forget that a LOT of VEP users are using this "one specific sequencer".

    Given that VEP is designed to work with Logic as well as all the other major sequencers, I do think that any feature that would make VEP work more effectively with any of said major sequencers is well worth consideration and certainly wouldn't be a waste of VSL programmers' time. I also don't forsee that a CC transformer is a particularly complex/ time consuming request from a programmers persepective. I'm sure there are also other users who would find a CC transformer useful. Let's see what the VSL guys, and the rest of the VEP community says...

    Also my point was that there isn't a workaround for plugins without scripting or MIDI learn built in. Which is quite a lot of plugins, including PLAY!

    I may well also start an e-petition on this that can be signed off by all VEP & Logic users and then sent to Apple.
  • D
    D

    Well, we're all entitled to have an opinion. I just don't happen to agree with you.

    However, I think the e-petition to Apple is a good idea though, as the CC7 problem ,in particular, affects all Logic users who want to use multi-timbral instruments.

    DG
  • Y
    Y

    As promised, I have created an e-petition to get Apple to add a preference for this MIDI CC interception behaviour

    http://logicprocc.epetitions.net/

    I would really appreciate it if all Logic & VEP users would take the time to sign it, and help promote it. I will post it into the VSL forum again as its own thread, and I'll post it at Sounds Online and VI-Control.

    When there are a decent number of signatures I will send some emails to Apple linking them to it.

    Will
  • O
    O
    Just 2 cents, but I think an AU spec update should take far more precedence. One MIDI port is ridiculous in this day and age.
  • P
    P
    +1 on this. I just got Logic and this one issue stopped me dead in my tracks. What a waste of money. Back to Cubase for now I guess.
  • A
    A
    Is is very simple to create a cc7 to c11 transformer, or the opposite, in Logic and save it as a template. That said, I prefer to bring the sounds from VE Pro to come up on auxes and automate cc7 on those and use MIDI automation (Hyperdraw in Logic) cc11 for the individual patches.