Vienna Symphonic Library Forum
Forum Statistics

194,397 users have contributed to 42,918 threads and 257,959 posts.

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

  • Using Logic's Articulation ID + Scripting with MIDI tracks

    I have a very large Logic template which has a custom Environment build with hundreds of MIDI tracks feeding several VEPro instances, which drives an external PC renderer.

    I would like to make use of Logic's Articulation ID's and MIDIFX Scripting function to control Synchron libraries.  However, on MIDI tracks there is no Scripting function, and External MIDI tracks don't pass the output of the MIDIFX Scripter to the Environment.

    How are you working around this limitation in your template?


  • last edited
    last edited

    @oldskool said:

    I have a very large Logic template which has a custom Environment build with hundreds of MIDI tracks feeding several VEPro instances, which drives an external PC renderer.

    I would like to make use of Logic's Articulation ID's and MIDIFX Scripting function to control Synchron libraries.  However, on MIDI tracks there is no Scripting function, and External MIDI tracks don't pass the output of the MIDIFX Scripter to the Environment.

    How are you working around this limitation in your template?

    In this case you are funneling all your midi through several VePro plugins (which connect to the VePro instances).  Those VePro plugins are on a couple of instrument channels.  That is where you have to do the MIDIFX processing, on those instrument channels.  That means if you have say, 16 instruments in one VePro instance on 16 midi channels....all 16 of those midi tracks are merging and funneling through the one instrument channel hosting the VePro Plugin for that instance.  So you put an instance of Scripter on that channel, and it does mean you have to process all those 16 parts in one script...which can make things more complicated, but that's how it is...no way around that...LogicPro is architected that way.  You will have to make your scripts smart enough to process more than one midi channel independently...if you are using AU3 and multiports, etc..then it can get even more complicated.  its all doable though.  Just use a seperate function to handle each midi channel.  The script could get quite large, but whatever.


  • last edited
    last edited

    @Dewdman42 said:

    its all doable though.  Just use a seperate function to handle each midi channel.  The script could get quite large, but whatever.

    Hey THANK YOU for this insight Dewdman42!  It's actually your script that I got from GitLab that I am modifying for this task.  This information enables me to continue along my path.  I'll let you know how it goes.

    Thanks for sharing your work!


  • last edited
    last edited

    @Dewdman42 said:

    its all doable though.  Just use a seperate function to handle each midi channel.  The script could get quite large, but whatever.

    Hey THANK YOU for this insight Dewdman42!  It's actually your script that I got from GitLab that I am modifying for this task.  This information enables me to continue along my path.  I'll let you know how it goes.

    Thanks for sharing your work!

    sure thing.  If you have more detailed questions, post it on the LogicPro forum in the scripting section, I can answer better there they have better formatting options on the forum.