Vienna Symphonic Library Forum
Forum Statistics

194,206 users have contributed to 42,912 threads and 257,931 posts.

In the past 24 hours, we have 1 new thread(s), 15 new post(s) and 87 new user(s).

  1. Home
  2. Software
  3. Vienna MIR & Vienna Suite
  4. VE PRO & Logic 9 - AU automation
  • M
    M

    Another question:

    When VE Pro hosts a 3rd party plugin eg Omnisphere, can we still use Logic's automation features for parameters within that plugin, or is this function lost?
  • M
    M

    Automation of hosted 3rd party plugin parameters is not possible, but any MIDI automation of course works.
  • A
    A
    But if you you are bringing in the audio into Logic Pro i.e on auxes, you can automate the auxes with host based automation, correct Martin?
  • M
    M

    Ashermusic:

    You could certainly do this, but it would only effect ( affect?) the actual audio coming in to Logic or whatever host is used.

    I was more concerned with automation of Plugin parameters, for example automating filters, internal pan/send/fx parameters etc. It seems that this will not be possible using VE PRO.

    Unless I am misunderstanding......

    Martin, you say MIDI can be sent. So, could one use (for example) the MIDI learn feature in Omnisphere or Stylus RMX to receive MIDI data and thereby automate plugin parameters?
  • K
    K
    You can send any MIDI to your connected VE Pro instance, so MIDI learn can indeed be used to automate plugin parameters. Also, volume, pan and the first 4 send sliders can be automated on the first 64 channel strips of the connected VE Pro instance using regular parameter automation.
  • H
    H

    Hi Jay

    I had a good long think about how I was going to set up my template when moving to VE Pro, and while all my audio arrives back into Logic via auxes, I decided against controlling instrument volumes through them, instead opting to automate the VE Pro plugin parameters which route through to VE Pro fader levels etc. I chose this because:

    - you can display the automation on the same Logic track as it's relevant MIDI regions in the arrange page - volume data is superimposed over the note information (which also saves hundreds of additional aux tracks in the arrange)

    - when moving or copying regions the automation data stays with it (should you so choose)

    Having instruments' volume etc recorded onto separate tracks to the MIDI seemed like a hassle for me. Obviously automation post arrival (Logic sends etc) has to be done via the auxes.

    Cheers

    Harry
  • M
    M

    Thanks Karel for confirming that - it really helps in deciding whether or not to upgrade to VE Pro.

    I have been using VE2 extensively over the last month and would enjoy the extra features that VE Pro offers.

    Thanks also to Harry - your reasoning makes complete sense and is exactly in line with the way I like to work. I already use CC data in VE2 to control instrument volume, modwheel/cell selection and velocity x-fade. It's so easy to draw in this data in Logic's Hyperdraw, I'd be lost without it.

    Much appreciated.......
  • J
    J

    Hi,

    I just started using VE PRO Beta for Mac yesterday. Except for a few crashes, all is well. I have VE PRO loaded with Stylus and Omnisphere. In Logic 9, I'm successfully triggering them from the multi timbral instruments that I created. My problem is volume automation. When I choose, for example, in the L9 track pulldown Channel 2 volume and draw in some automation, the corresponding Omnisphere track doesn't read the automation. The L9 track is in Read mode. 

    Can anyone suggest how to write automation from L9?

    thanks,

    Judith Gruber-Stitzer

    film composer

    Montreal
  • H
    H

    Hi Judith

    Just to confirm - you realise that these automation parameters control the faders in the VE Pro mixer, not the volume setting for each of the parts within Stylus / Omnisphere? "Ch2Vol" will control the 2nd fader from the left in the VE Pro instance connected to that plugin.

    Regards

    Harry
  • A
    A
    Jusith, Logic's Host automation with CC7 is not the way to go for this. There are 2 good options: automate the individual MIDI channels with CC11 or CC1 or use Logic TBA to automate the auxes that the parts are coming into Logic on from VE Pro.