[SOLVED] VEP Multi Port workaround in Logic

[Dewdman42]

I believe I have figured out why Vienna Multi port mode will not function correctly with Logic Pro.  There is a bug in the environment layer of LPX.  Specfically, the transformer object will not insert CC99 with the fixed value for the port number.  It does for NoteOn's and other event types, but for NoteOff, it always inserts zero for the second byte even when VSL have provided an environment layer that is supposed to be setting that byte to the port#.  This is clearly a bug in the transformer object of Logic Pro.  its also creating duplicate NoteOff's, all of which is confusing the VEP plugin.

Good luck getting Apple to address that bug, as its in very old code from the old Logic days...but anyway, that is the problem.

SOLVED:  I have come up with a work around, See this link for explanation and free downloads:

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

[Dewdman42]

alright I figured out a work around to make the logic multiport templates to work.  

Need to add another transformer after each one in the template, that looks for CC99=0 and forces it to the port# needed...  Kind of redundant due to the bug, but it works...

VSL should update their templates accordingly...

[Dewdman42]

-

[Dewdman42]

-

[Cyril Blanc]

We do not need al those tracks with Logic 10.4 as you can define a few articulation changes on the same track

[Dewdman42]

I don't really disagree with you, was just meaning, at this junction to point out the problem with LogicPro, the reason the existing VSL multi-port templates are broken due to that LogicPro bug...  and demonstrate a workaround using the ginormous multi-port template approach similar as what VSL did with them originally..

Here is a smaller way to work that may be preferable to you.  Basically I packed up the multi-port functionality into a LogicPro macro, so the environment looks much less cluttered and you can easily copy and paste a couple of objects and wire up to VEP inst channel to add more ports as needed.

In this simple example, there is one VEP instance with 4 ports, 64 total midi channels feeding it.

By the way, even though you can define many articulation id's on a single track in LogicPro, you often will still need to put differnet articulations onto different slots in the instrument.  So yes you want less tracks, but ultimately you still may need to get to more than 16 midi channels if you have more than 16 articulations for a particular instrument track.

Also if you simply want to keep your VEP instance-count down to less instances, then using multi-ports will be needed to do that.

(see downloads below)

[Dewdman42]

Also, if you're not needing a lot of tracks, but rather needing a way to send one track to many channels in VEP...more than 16...channelizing by articulation id, this script, this may help you also....  It includes support for VEP multi port mode for handling more than 16 articulations from a single track in LogicPro...

https://www.logicprohelp.com/forum/viewtopic.php?f=45&t=136801

[Cyril Blanc]

You can define 127 articulations per tracks with Logic 10.4

The X Y problem is solved by a the Environment,  (see screen copy)

 

I think we will never have the AU3 implantation. VSL does not care, they prefer to issue new products.

[Dewdman42]

Not sure what the X/Y problem is, could you elaborate on that?  I'm curious.  I don't have any VSL instruments yet other then the stuff that came with VEP.  I'm assuming you're dealing with something related to the VSL xy matrix.

So anyway Logic pro can support up to 254 articulations per articulation set...meaning you could have as many as 254 articulation id's on a single track.  Where are you getting the limitation of 127?

I agree with you that Logic may never adopt AU3.  Well maybe someday, but probably years away.

[Cyril Blanc]

The X/Y problem is that Logic only allow to send one parameter to VSL, so you use the velocity of the articulation to define the Y value.

You are right it is not 127, it is 254 articulations per instrument

 

With Levell II patch you have less than 50 articulations per type of instrument.

i.e. Violin, Viola and cello have the same articulations, Double bass have it's own set

 

You say : "I agree with you that Logic may never adopt AU3".  this is false 

Since the 4 march 2017 : "The announcement says that Logic 10.3.1 supports AU3 and multi port midi "

This mean that VSL need to change there code 

[Dewdman42]

Yes right. Well in fairness to VSL, I haven’t yet seen any other AU3 plugins show up in logic. I know they announced compatibility but the existing GUI doesn’t have any way to specify the up to 256 midi output ports that I know of. Maybe it would show up magically if and when an AU3 is inserted.

[Dewdman42]

-

[Dewdman42]

 

SOLVED

Well I figured out a solution.  Attached are three templates.  They should work around the LogicPro glitches.  

Essentially, two work arounds are required beyond the templates provided by VSL in order for it to work:

1. An extra transformer is needed to make sure all generated CC99 events have the correct port#, including NoteOff messages
2. Other transformers in the environment are needed to avoid duplicate NoteOff messages.

With the above, it appears to be working properly with smaller projects.  So I will be interested to hear positive results.  There are still a few potential issues with larger projects being ironed out

See this link or top of this thread for a link to free template downloads and a more complete explanation of the Logic bug and what the work around is: https://www.logicprohelp.com/forum/viewtopic.php?f=9&t=137085

I very much hope this is tempoary and VSL will get AU3 plugin ready Asap so that we can stop stressing about this.

[Cyril Blanc]

Did you add this :

[Dewdman42]

No I didn't add that.  What is that supposed to do?

[Cyril Blanc]

When you send a note on you have to send a note off

This send the note off

[Dewdman42]

How does that send a NoteOff can you please explain?

In any case, that is not really related to the problem.  

[Cyril Blanc]

I dont know what is in your Macro

if you do a replace xxx by a note, you need to add the note off transformer

[Dewdman42]

I don't do a replace of Note Off.  Maybe you should check out what I did before confusing the issue with unrelated stuff.

I have it working now completely in an environment macro, no need for a Scripter script.  Check it out.. v1.1

[Cyril Blanc]

Dont take it like that, I just wanted to help in case off

I dont know what you do in you Macro

It might help other Environement designer 

I have design my own enveironnement and that is using program changes to change articulation ;)

Now I am going to use the new Articulation handling of 10.4. I dont need more than 125 midi channel, one by instruments