good point. The VST could be compiled as AU-MFX pretty easily if he's doing AU anyway. I'm not sure whether PDC is handled through those midi plugin slots though, quite possibly not.
Hmm I have another alternative rather than a VST I'm working on at the moment. I'm starting to think a VST won't work for other DAWs which is a pity because of the delay compensation.Logic doesn't support putting a VST or AU before Kontakt, only MIDI FX scripts.
How? Some kind of "is a note already being held down" detector?
Yeah no worries. Thanks, I didn't think of that!I'll do that, if you don't mind me borrowing your idea. Here's an idea for you, if you haven't thought of it already, you should exclude keyswitch notes (below the playable range) from this counter. I've seen many people drag out KS notes below the entire relevant phrase for clarity.
Great that's good to know. Looks like there are several possible solutions, I'm also investigating the possibility of a Kontakt multiscript but then we lose the auto latency delay compensation. Not sure whether it will be possible but checking it out.Just did a test. AU-MFX plugins can report latency and LPX appears to recognize it. So...I think it could be compiled as AU-MFX for use in LPX and PDC should be handled properly.
The cross-DAW part makes this tricky, because to do it properly it needs to be articulation-aware, because within a given library, different articulations require different delay compensations.collaborated on a cross-DAW vst solution with a flexible framework to conform the latency and dynamic discrepancies between all the different libraries out there
I've given up on that. I messed around with Logic's articulationID briefly but it's just not worth it. Seems like a design dead end IMO. One track per articulation, or at least, per group of articulations that have the same delay compensation needs, seems inevitable if people want a cross DAW capable solution. The real dynamite features here, that might have broad appeal, areto do it properly it needs to be articulation-aware, because within a different library, different articulations require different delay compensations.
I do think that this is possible if we track keyswitches + CC values. But this would be something I think we should target after getting base functionality down.The cross-DAW part makes this tricky, because to do it properly it needs to be articulation-aware, because within a given library, different articulations require different delay compensations.
This is wonderful news! Would love to test in Cubase if you need more volunteers!We've made some progress and have an AU-MIDIFX version detected by Logic and available to use before any instrument FX. NoamL is going to do some more testing in Logic to see how well it functions.
So it looks like we'll be proceeding with this
I would love to know your authoring process to get MIDI inserts in Cubase. My impression was that the inserts available could not be changed, but that is mainly based on a lack of information on adding MIDI plugins. Exciting!I now have a version successfully working in Cubase as a MIDI insert rather than a VST. Sadly we don't get automatic PDC but it is working with the different delays for legato types with that. End product is exactly the same as the previous video except you have to apply a -400ms track delay.