Dewdman42

see this project for an example of how to utilize kontakt ports A-D from logicPro...there are few different things in there, but it comes down inserting CC or PC data into the midi stream and then using a kontakt multi-script to re-route to one of the 4 ports A-D inside kontakt. https://gitlab.com/dewdman42/kprouter

In terms of kontakt alone, there are things you could do. There are not A-D ports as part of the midi spec. Kontakt has the ability to have up to 64 separate listening midi channels on its own set of 4 midi ports, but these ports are generally not exposed to DAW's. However, they are always there. I have in the past made some scripts which basically insert CC's in front of every note, and then once inside kontakt, use the CC to encode which of the 4 A-D ports to send the event to inside kontakt. that makes it possible to have one instrument slot in LogicPro hosting one instance of kontakt and one instance of your plugin (as AUmfx), and theoretically, with the right multi-script in kontakt could have numerous tracks hitting up to 64 separate parts in kontakt. This is definitely possible. Note also that in logicPro this is a distinction between tracks and instruments. Most DAW's on bind track and instrument channel strip into one conceptual thing, and LogicPro attempts to create that kind of illusion, but really you have tracks, and then you have inst channel strips. SO in the case of Kontakt you can potentially have up to 127 separate tracks...all of which send their midi to a single instrument channel where you have your AUmfx and Kontakt hosted. Then in your plugin you would encode midi in such a way to direct to the 64 possible midi channels in kontakt...given that you also use a multi-script in kontakt to direct to the four ports A-D in the case of VePro, there are similar advantages...you can have many tracks which basically feed to a single VePro plugin on a single inst channel...and that can be handing hundreds of midi channels in VePro...so that is going to be a good way for your customers to intonate a larger set of channels hosted in VePro.

First, you will want to implement your plugin for LogicPro as AUmfx, no audio. That's the only way to get midi out of a plugin in logicPro. Secondly, LogicPro itself cannot send the midi output from any plugin to the environment nor to any other track directly. As others have mentioned it's possible to direct to IAC and that will loop back around to the input of LogicPro. Or you could have your plugin send directly to IAC directly.

I don’t have the link handy but I’m sure someone else will provide. In the meantime checkout expert sleepers latency fixer free plugin

And track delay moved the notes when you reopened the project? If so that’s a bug please report it

with the new feature of using midifx pre-record, its possible to do all manner of things like that using midifx plugins, including scripter...as you record it. the sky is the limit. You could, for example, use the midifx that can create LFO cycles, etc..and if neccessarily use a scripter script to convert some CC value into current velocity..to end up with some kind of cycling velocity like what you see in your screen shot. That is just one simple example, the sky is really the limit. You could combine with an arp in some way perhaps... you could use the step sequencer that is built into LogicPro and convert some stepped midi message there into velocity values to use, etc... there are all kinds of ways to manipulate velocity besides purely random.

interesting bug. as a work around, use track delay instead of region. Another thing you can do is use the expert sleepers latency fixer plugin to adjust for legato latency.

thanks. Strange that they added that when IAC is already there. Not sure why they would bother with that, but thanks for the heads up about it

I don't understand what you're saying... but anyway I'll look for it next time I am near my mac

Interesting. And then the midi input ignores it?

it can be done. won't be simple.

Yes it could be done. But... Scripter does not have the ability to do lookahead. sort of. it can't move notes earlier in time, only later in time.... However what you can do is delay everything by a certain look ahead amount, and then you move some notes later then others, which gives you a way to basically move notes earlier, relatively speaking. Then the whole track needs a negative offset to make up for the lookahead.

what is the recently added feature you are talking about, I have not heard about that? honestly MidiFXFreeze is the best way and I would not call it "out dated". But yea if you don't care about sample accuracy, ,then IAC loopback works fine, and honestly, most people won't notice as the delay is probably something like within 1ms or less depending on your buffer size.

not entirely sure i understand your question, but the midi time clock is always running in Mainstage and LogicPro, even when the transport is stopped. But you can use the GetTimingInfo function to obtain the transport info and then look at whether the transport is actually still playing or not. Based on that you can have scripter do things (or not).

Channelizer simply uses the articulationID to offset the midi channel. Please read the channelizer wiki page at gitlab