Direkt zum Inhalt

Midi input latency with midi drone and midi import problem

Posted

in summary i cant get midi to transfer to synfire from live via a midi drone set to input without the notes being offset by about a 1/4 bar delay.

i had a problem building a library with the midi import merging some notes (with different pitches) into one note. So I loaded them into live to check them and they loaded without a problem. As a work around i then decided to load the 8 bar sequences all onto one track in live and try transfer them into synfire then from there into a library. This did appear simpler than trying to import 8 8 bar sequences per instrument (8) directly into the library.
I loaded a drone into the track in live, set it up as a plugin drone and checked the box to make it a midi drone. Then I went into the midi ports section and found the drone listed there and made it an input.
I'd also setup the transport rewire thing in live and made sure I had the external sync in synfire set to rewire transport a d tempo.
Pressing record in synfire, started live playing after acknowledging the warning about the count in. The notes were transferred into synfire and when set to static kept the same pattern as in live. However there was a timing issue.
I moved the sequence in live 2 bars to the right and tried again.
There was still an issue with timing. The notes were displaced by about 1/4 bar at 140bpm from where they shoukd have been in bar 3. i tried changing the latency in the instrument, changing the settings in the external sync section, even trying a 1000ms setting. However this made no difference to the positioning of the recorded notes. They were always out by about 1/4 bar.
I have just thought of something I didn't try, turning off the setting to use the engine for midi time stamps (or whatever that is called....it's on)

Any suggestions on how to make this work? Or how to work around it? Shou,d I send the midi file in for you to test importing and work out why it doesn't import correctly?