this not the first time that i encounter this kind of behaviour, but first time that i take time to report it >
i’ve been trying GA se as a midi pattern player, the set up is extremely simple :
GA playing midi files / pattern ( 1 to 3 bars ) only one pitch ( rhythmic part )
i have a hi hat sample in GA to check in audio that it is playing OK
than another plugin ( retrologue ) receiving midi from GA midi out ( midi in from GA, midi monitor ON )
Retrologue is playing, but the timing is so messed up you can’t even recognise the original rhythm
( i mean it is not just a tiny groove or delay problem )
i first tried that in my big work template.
than make an empty project ( only 2 tracks ), same problem.
i tried two ways :
transport = stop
playing GA, retrologue monitoring on
record a midi part on GA track ( just notes triggering the patterns )
Retrologue monitoring on
both ways are total chaos… unusable.
i have to say i have short and fast notes ( think trap hi hat kind of part / in fact more flamenco guitar strum rhythm type of pattern )
but nothing that a human hand can’t do, i could play this kind of patterns on a pad.
Other test >>
if i drag the pattern from GA to the retrologue track ( mini monitor = off ), it plays fine
it seems like midi between two vst is badly buffered / got no timing reference ?
if it is not a bug, how can we overcome this behaviour…
this an absolute nonsense to me and a total workflow breaker on the project i’m writing music for actually…
i use a rme fireface
multi process active
asio guard = low
audio priority = boost
steinberg power scheme = on
disk preload 4 sec
adjust for record latency = on
record shift = 0
system timestamp for windows midi input = off
use device direct music = off