Vienna Symphonic Library Forum
Forum Statistics

181,978 users have contributed to 42,198 threads and 254,643 posts.

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

  • Logic X / VEPro6 / Multiport legato issue

    last edited
    last edited

    Hello,

     

    I’m in the middle of a VEPro6 template using the Multiport Template for Logic Pro X. The routing works very well, I can play any instrument in Logic, every track sounds, etc. (I’ve been using Logic/VEPro for a few years now). The ONLY issue occurs with unisson legatos.

     

    Let’s see how I did it :

     

    Master MacBook Pro :

    - an Instrument track with VEPro6 (hidden in the picture attached)

    - MIDI tracks routed to the Instrument track using the VSL Multiport Template in the Environment

     

    Slave PC, in VE Pro 6 :

    - 1st Kontakt plugin with MIDI Port > 1 VE PRO Plugin MIDI In 1 (default name) and MIDI Channel > All

    - 2nd Kontakt plugin with MIDI Port > 1 VE PRO Plugin MIDI In 2 and MIDI Channel > All

     

    In each Kontakt, I load multiple patches with increasing MIDI Channel numbers. Let’s say in the 1st Kontakt :

    - Violin1 legato > Midi Ch. : [A] 1

    - Vln1 staccato > Midi Ch. : [A] 2

    - Vln1 pizz > Midi Ch. : [A] 3

    - etc.

    And in the same in the 2nd Kontakt with Violin2 legato, stacc, pizz, etc.

     

    As I said, every patch works when I play it in Logic. The problem occurs when playing a unisson (with the legato patch) with all the violins and the 1st start an new note (a legato note) while the 2nd stay on the same note : the 2nd violins suddenly stop playing.

     

    Given that all the patches are routed via a single Instrument in Logic, it seems that the 2nd violins also receive the new-legato-note information, leading to a stop-note.

     

    So, my questions are :

    - What did I do wrong ? I'm sure, it's so easy I could find it 😉

    - Instead of having a Multi-Instrument per section (i.e. Violins 1, Violins 2, Violas, etc.) in Logic’s Environment, I could have one per articulation (legato, long notes, short, etc.) to avoid having legatos in the same MIDI Channels of the same Instrument track but with different MIDI Ports. But, isn’t there a solution to have one per section ? Because I remember youtube video where people did this (but it was in Cubase) and I never heard about this issue.

     

    Best regards,

     

    Clément

     

     

    PS :

    - it already occurred with older versions of Logic X and VEPro5, I just didn’t take time to post a thread

    - I used Kontakt in this example but it behaves the same with VI Pro 2 (I assume it wouldn’t occur with polyphonic legato but it’s not the point)

    - I know that MIDI Channels start at 2 in the Logic picture I attached, but I did it the same in VEPro6. It was just to try something. Of course, it doesn’t work either starting at 1 


  • Hi Groctave, 

    That's indeed a glitch in Logic's environment, thanks for your posting.  

    As soon as you trigger the same note on the same MIDI Channel on two different ports, they interrupt each other. 
    Did you try to switch the MIDI Channels for your second instance yet?

    E.g.:
    MIDI Channel 1: pizz
    MIDI Channel 2: stac
    MIDI Channel 3: leg

    I don't know any other way around this, and we're all really hoping for AUv3 Multiport to be available in the near future. 

    Best, 
    Paul


    Paul Kopf Product Manager VSL
  • Thanks for your quick reply Paul !

     

    A Logic glitch ! That's what I was starting to think. Great you pointed it out.

    Yes, the "switching solution" was the other idea I had in mind to keep a Kontakt/VIPro per section.

     

    Best,

    Clément


  • I have solved this issue on my system by replacing the cc99 transformers in the 2015 Multiport Layer with the old encrypted macros from the 2013 Multiport Layer.

    In the newer Multiport Layer note-on commands are sent to only the correct port, but note-off commands are echoed to the same MIDI channel on all ports.   Thus it seems like the template is working, but upon closer inspection one notices the cut off notes.

    Substituting the old macros fixes this across all ports.  This fix is really good news for me, because I didn't want to have to wait until the AU3 implementation to have a fully operational template.


  • Hi, 

    That's good news indeed. Do you want to send me your new song, so I can take a look? support@vsl.co.at

    We're hoping that we can support AUv3 in the next months. Yay!

    Thanks,
    Paul


    Paul Kopf Product Manager VSL
  • Wonderful !

     

    But where can I find the 2013 version ? Or how can I fix it on the 2015 ?


  • last edited
    last edited

    ok, I am going to attempt to attach a Logic project containing very little aside from my VE Pro layer. There are VE Pro's for VSL, Kontakt and GIGA in this project, although the fix is only applied to the VSL instance as you can see.

    You can simply import the "VEPro Multiport" layer into your template and copy the encrypted macros over to your project.

    VEProU0020MultiportU0020LayerU0020example.logicx.zip-1696294419871-o3zo6.zip

  • last edited
    last edited

    I think something similar is happening to me.

    I have some sustain info on a celeste part that is crossing over to a clarinet in a different port forcing the note to hang.  When I click on a different part of the session with no midi data from any channel, the note stops.  When I restart from the top it plays correctly except for when I stop the playback in the middle of the phrase... then the note hangs.

    "I have solved this issue on my system by replacing the cc99 transformers in the 2015 Multiport Layer with the old encrypted macros from the 2013 Multiport Layer."

    Is this the solution?  I'm having trouble translating 😶


  • As a Logic Certified Trainer and a guy who helps some fairly famous musicians build Logic/VE Pro templates, I sinply cannot recommend the Multiport layer. It is building a foundation on quicksand in my  view.


  • last edited
    last edited

    @Another User said:

    As a Logic Certified Trainer and a guy who helps some fairly famous musicians build Logic/VE Pro templates, I sinply cannot recommend the Multiport layer. It is building a foundation on quicksand in my  view.

    Yes, I've read that singles instances with 16 MIDI channels show better performance. But I don't want (don't have time) to recreate my VEP6 server. Moreover, I plan on leaving Logic-Mac-master/PC-slave for good and go to PCs with Cubase quite soon.


  • https://forum.vsl.co.at/topic/48669/VEP Multi Port Bug In Logic/271416

  • But hopefully VSL will get the AU plugin updated to AU3 soon so we can stop all this shenanegans