Vienna Symphonic Library Forum
Forum Statistics

182,188 users have contributed to 42,209 threads and 254,695 posts.

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

  1. Home
  2. Sample Libraries
  3. Vienna Instruments Libraries
  4. VE3 Routing - I am puzzled

  • VE3 Routing - I am puzzled

    S
    S

    In the Video about about VE3 there is a screenshot of Play Back which is presumably using using several instances of VE3 each providing 16 stereo outputs.

    I notice that each Track in Logic is behaving as one would expect in that the Track Meters are independent.

    My Puzzlement is this:

    If I create a Multi-Timbral Software Instrument and Insert a Vienna Ensemble Multi Out Plug-In, my slave creates a "Project" capable of holding 16 instruments each of which can access any one of 16 stereo outs.

    But

    HW Out 1-2 go to the first Instance of the Multi Timbral Software Instrument. Now at the moment that a Multi Timbral Instrument is created the equivalent number of Auxilary Objects are also (or may be) created. It is only within the inputs of those Auxilary objects that you see a reference to the Multi outs of VE3 (except HW output 1-2) and HW 3-4 through to HW 31-32 are correctly assigned to those Auxilary Objects.

    As a consequence if you create the 16 tracks of a Multi Timbral Sofware Instrument with their different MIDI channels, the Track Automation for Audio Volume will only control the output of the first Multi Timbral Software Instrument component. Also all tracks of the Multi Timbral Software Instrument will show the Audio Activity of the VE3 instrument assigned to Midi channel 1 in their Track Meters.

    So, quite simply, how do you have 16 Tracks of Midi Data feeding the VE3 source and then return their audio in such a way that those tracks can be controlled by track automation that is INDEPENDENT for each track.

    The only way I can think of doing it is the same as I have for my 2 Mac Mini which host the plugins in Plogue and use MOL together with FW Audio interfaces.

    I have a midi track for each Vienna Instrument on the Mac Minis and an Audio Track to receive the Audio back which can then be controlled by Track Automation.

    Thus if I attach a midi Instrument to each component of the Multi Timbral Software Instrument I can see Independent Meter activity for MIDI data and If I set up tracks of the Auxilaries being fed from VE3 I have control over Track Automation.

    But am I missing some settings or techniques since the Video tracks seem to be the components of the Software Instrument (if you look at the inspector) and have independent track meters.

    I am running Logic 8.01 on a Mac Pro 8 core (January 2008) OS is 10.5.2. Slave for VE3 is a G5 running OS 10.4.11
  • T
    T
    This is the only way I've managed to do it which is as you suggest, creating multiple AUX tracks and wiring them to the outputs from VE3 and then automating the AUX tracks rather than the VE MIDI tracks.

    It will be nice when we can send MIDI data into VE3 to automate it....

    Tim
  • D
    D
    [quote=timkiel]This is the only way I've managed to do it which is as you suggest, creating multiple AUX tracks and wiring them to the outputs from VE3 and then automating the AUX tracks rather than the VE MIDI tracks.

    We can already automate the MIDI data. It's the faders and panning that we can't, and this, strictly speaking is not MIDI data.

    DG
  • O
    O
    Hi Vienne-Team, hi guys. this canĀ“t be true, is it. IĀ“m loosing my hair on this one too. This means we have to create 2 tracks per Instrument in LogicĀ“s Arrange, one for playing midi, one for automating aux data? On my VE2 slave (G5) it works with just one Midichannel sending MOL. On my VE3 Slave (on my local host-slave) i cantĀ“t automate midi volume to VE3!!!??? Even when I create a multitimbral midiinstrument and route it to the discrete aux channels, VE3 wonĀ“t automate separate midi volume channels!!! Is it a bug in logic- or in VE3? This canĀ“t be true, is it? Am I just to dull to understand? VSL-Team please help!!!! Best Oliver
  • T
    T
    Oliver

    I think it is (unfortunately) true. You have some other options, you can draw (or record) expression MIDI data onto each part, this works fine, or even draw MIDI Volume data on each part. I'm not in my studio today but have you tried to see what other automation is possible of VE3 other than the default Volume parameter? What I mean here is (looking at Stylus RMX which I do have on my laptop) is that there is a default Volume automation control (which controls the whole instance of RMX) and also separate Level automations for each of the 8 parts? Perhaps VE3 has something similar?

    Tim
  • D
    D
    last edited
    last edited

    @oliverheuss said:

    Hi Vienne-Team, hi guys. this canĀ“t be true, is it. IĀ“m loosing my hair on this one too. This means we have to create 2 tracks per Instrument in LogicĀ“s Arrange, one for playing midi, one for automating aux data? On my VE2 slave (G5) it works with just one Midichannel sending MOL. On my VE3 Slave (on my local host-slave) i cantĀ“t automate midi volume to VE3!!!??? Even when I create a multitimbral midiinstrument and route it to the discrete aux channels, VE3 wonĀ“t automate separate midi volume channels!!! Is it a bug in logic- or in VE3? This canĀ“t be true, is it? Am I just to dull to understand? VSL-Team please help!!!! Best Oliver

    Yes, it's a Logic bug. The best you can do is use C11 instead, as this should be recognised by individual MIDI channels.

    DG
  • S
    S
    last edited
    last edited

    @DG said:

    Yes, it's a Logic bug. The best you can do is use C11 instead, as this should be recognised by individual MIDI channels.

    DG

     

    I should have mentioned that a lot of my Mac Mini WW and Brass tracks use C11 to Control Velocity Xfade and of course that is built into the Midi data going from my DAW to the Mac Mini Slaves. 

  • D
    D
    last edited
    last edited

    @DG said:

    Yes, it's a Logic bug. The best you can do is use C11 instead, as this should be recognised by individual MIDI channels.

    DG

     

    I should have mentioned that a lot of my Mac Mini WW and Brass tracks use C11 to Control Velocity Xfade and of course that is built into the Midi data going from my DAW to the Mac Mini Slaves. 

    In which case you'll just have to wait until Apple fixes this bug, I'm afraid.

    DG
  • S
    S

    Referring back to my orginal post I would state that I think the VE3 manual needs beefing up in this department ie for the Logic Setup. OK I now have some answers after the various replies but new users may be stumped easily.

    Although I have used Logic for years it is the first time I have really used a MultiTimbral Software Instrument in that way.
  • C
    C

    Hi,

    Yes this is a Logic behaviour (or maybe really a bug). CC 7 in Logic always controlls the volumen of the Instrument/Audio Track. Even if there is a Multi Instrument connected to a AudioInstrument Track with an inserted Multitimbral Instrument. As you have to set the Midi channel of the Instrument Track to "ALL" and the Midi-Multi Instrument is wired to this AudioInstrument channel, all CC 7 data from all 16 channels just change the Volumen of the Instrument Channel were the Multitimbral Instrument is inserted.

    My workaround for this is: In the Environment Page were you made the Multi-Instrument object, cable the out of this object to a Transformer object which transforms all incomming CC7 data from this Multi- Instrument to any other controller not used yet.

    Then go to the inserted VIĀ“s in your VE. Open the  Map Control Page on the Perform Page and change the controller for Volume manually to the controller converted by the Transformer object.

    There you go, now you still can send CC7 from your prefered masterkeyboard/controller and can automate all VIĀ“s in one VE via  CC7 (converted in the VIĀ“s to whatever).

    best

    christian 
  • O
    O
    timkiel, DG, and christan, Thanxalot for this workaround! I will try it next week and let you know if it works for me.... Best regards (from a DEADline-hell) Oliver