Vienna Symphonic Library Forum
Forum Statistics

196,728 users have contributed to 43,031 threads and 258,433 posts.

In the past 24 hours, we have 7 new thread(s), 14 new post(s) and 102 new user(s).

  1. Home
  2. Software
  3. Vienna Instruments Pro
  4. Logic AU3 template

  • Logic AU3 template

    lupineL
    lupineL

    Hello,

    I have just downloaded the AU3 Logic template but all of the tracks seem sharing more than they should.
    For example I can't solo one single track only because as soon as I click the solo button in one track, automagically all of the other tracks solo button will activate too!
    Moreover I can't set up a Scripter plugin in one track and a different Scripter plugin in another one, because the latest overwrite the first, so I can't make use of Scripter related software like AG Art Pro or similar.

    Does somebody know how to overcome these issues?

    Thanks in advance

    Mac Studio M1 Ultra macOS Sonoma 14.6.1 Studio One 6.6
  • Dewdman42D
    Dewdman42D

    I reccomend you use this template:

    https://www.logicprohelp.com/forum/viewtopic.php?f=9&t=143416

    The other comments you make about peculiar behavior, however, is related to LogicPro and the way it works with multi-instruments.

    LogicPro is setup so that you can create up to 127 tracks feeding into a single AU3 multi-timbral instrument.  That single multi-timbral instrument is hosted in a single instrument channel.  So..  127 seperate tracks, all feeding a single instrument channel.

    Whenever you hit the SOLO/MUTE buttons on any of those 127 tracks, it effects the same instrument channel, that's why they are all in sync with it.  Hitting solo or mute, effects that single instrument channel they are all funneling through.  The fader on the track header also effects the volume of the one single instrument channel.

    VePro.AU3 is a multi-timbral instrument, sitting in one instrument channel, and servicing up to 127 midi source tracks.

    Likewise, Scripter sits on that one instrument channel.  So that means all 127 source midi tracks have to funnel through that one Scripter script.  If your script is smart enough, it can take that into consideration by handling all processing per channel and port.  A lot of scripts floating around do not make any attempt to distinguish channel and port, so they are just doing it globally to all midi source tracks that are funneling through it.

    So..  That is to be expected, the only solution is make smarter Scripter scripts... if you want to have more then one source track fed into a single multi-timbral instrument.

    And with VePro, the only way to feed those 127 source tracks to a single VePro instance, is to funnel into a single instrument channel, as described above.  

    So yes its solvable, but generally involves more complicated script programming.