Is there a way to have more control over latency when we use Max native internal virtual midi interfaces ?
I never really needed a very accurate timing from Max to Live (always needed the opposite) as I was playing more with M4L. My current project requires to have an external max patch (for global control and live patching reasons) that fires triggers to Live. and I just noticed very bad accuracy and I'm sure it can't be possible and I miss something.
Basically, I have my external patch running, everything fine, accurate.
I fire these midi notes through "from max 1" virtual midi bus and .. OMG... timing are not accurate. If I hear the sound only, it "sounds" correct. If I record the midi flows, we can see a lot of jittering.
Before splitting everything into M4L patches, and also because splitting this would change the project, I'm asking: can we reduce this latency ? or working around it ?
I even was thinking about using network stack (I mean udp osc stuff) from Max to Live (max packing things, live unpacking things and generating midi notes to synth).
Any ideas for pointing what I miss here would be appreciated.