Dewdman42

you create the IAC port in an external editor, and I don't know of any way you can create it and export it to them through your product unfortunately. Once an IAC port is created on the system, it stays there until explicitly deleted, after reboot, etc..it's always available after that. So your instructions for LogicPro users would be to install your product and then manually go into AudioMidi editor and create an IAC port. However, it MIGHT be possible for your plugin to actually create IAC ports on the fly and expose them in a way that all apps on the system including LogicPro would then see as available midi input, but not permanently, only when the plugin is running. I leave that to you to figure out, I have no direct experience in this. It also might not be possible

you can get logicPro for older mac's with older OS. You cannot get the latest version of LogicPro however 10.8 I am confident you can get something working in LogicPro using IAC.

yes. when you create an IAC port...it will show up as one of the available input midi and output midi ports throughout logicPro. In cubase, for example, when you put a vst instrument into an instrument track, if that instrument has output midi, it will suddenly show up in cubase as an available midi input port on other tracks. so then you create another midi or inst track and use that internal virtual midi port as the input to the new tracks. That's how midi plugins are handled in cubase, DP and some others. LogicPro simply does not automatically create that available midi port for you...you have to create it using Apple Audio Midi Editor....and then it will show up...and if your plugin doesn't send to it directly....then you'll need to use the external instrument to send it. I suggest you should probably get a copy of LogicPro if you intend to sell and support use of the product on LogicPro. That was my understanding, years ago. But its possible not all DAW's are compliant with that. I thought JUCE added that support also long ago...but anyway... that is just my understanding...you will have to find out if its true for sure and if some DAW's don't support it then its moot point. And it doesn't really matter here either, that was related to kontakt four A-D ports and some workaround to use those if you wanted to do that. You don't have to use CC, you could use key switches or other means as well.

In general midi plugin handling is not great in any of the DAW's in my opinion. LogicPro is actually just about the only one that even provided dedicated midi fx plugin slots to handle AUmfx plugins..the other daw's don't have this. The other DAW's require you to chain up the output of one instrument track to the input of another midi or inst track...with the the first track holding your VST midi plugin in it. That is fine, but note that when they do that they are basically doing the same thing as what we are talking about when you use IAC... IAC is just an external bus to chain up one track to another...the other daw's such as Cubase and DP can do it internally, LogicPro requires you to setup the IAC port externally and use it. But otherwise it functions exactly the same way with the sam pros and cons...loss of sample accuracy is part of that...in all of the daw's. so if you want a consistent way to handle it across various DAW's I would use that approach in LogicPro, use IAC. then in your instructions you just explain how to set it up in LogicPro. functionally it will be the same as chaining tracks in Cubase or DP. Not sure about S1.

JUCE can send CC, certainly from AUmfx. If the code has to be exactly the same as for the VST3 version of your plugin...then still VST3 was updated by steinberg with extensions to allow it to send CC. FWIW I'm sure you will figure something out. You have lots of options.

An IAC port is kind of like a midi port. Except that it's not really input or output..it's both. whatever you send to an IAC midi port will be received by any apps on your system that are at that moment listening to that same IAC port. That includes LogicPro itself. By default LogicPro is always listening to all current IAC busses. The way you can send midi from an instrument channel to IAC is to use the external instrument AUinst and configure it to send to an IAC port. At that moment, any midi being sent to that IAC port by this external inst plugin will then show up as new input at the front end of LogicPro. At that point you can route it to other tracks or instrument channels by various means in LogicPro.

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