MXXX: MIDI Settings ---> note data driven parameters in Logic don't compensate for latency

[Annabanna]

Anyone else noticed this? It keeps happening to me in Logic 10.3.3 (hardware restricted), and Melda 14.something.

WHEN THE ISSUE HAPPENS:
Whenever MIDI note data drives a parameter in a module that follows another module that induces latency. For instance, if I attempt to have a freeformphase module (causes latency), then follow it with a volume module being driven by velocity or an EQ module with note pitch driving the EQ frequency.

THE ISSUE:
The MIDI note driven effect does not adjust for the latency in the other module, so it constantly misfires (the EQ or volume in the above examples jumps as if the latency isn't there, so it's never aligned.)

TROUBLESHOOTING:
If I disable the latency inducing plugin, the problem goes away. Alternatively, If I switch the order of the modules so the MIDI note driven module is BEFORE the latency inducing module, the problem goes away as well, but then this wrecks the instrument as, for instance, I need the volume to be the LAST thing in the chain so I can get consistent processing at all velocities, but then vary the output level.

Most of my instruments are complex affairs that have samplers etc that wont' work properly without the associated resources, so if I can locate a simpler one that demonstrates this, I'll upload it. I may have to create a dummy one, but wanted to check in the meantime to see if anyone else has already noticed this and managed to address it somehow.

[MeldaProduction]

Yes, I'm afraid MXXX doesn't compensate for MIDI latency. It's hard to explain, but given the architecture, currently it cannot really be done. Hopefully at some point I'll get to things like this.