ABLETON SIMPLE DELAY ONLY 300 MS SOFTWARE
Now, if I were to take the previous setup, and instead of using software instrument, I were to use the same chain to control that external hardware synthesizer using the recommended External Instrument device method, it would add yet another 'pass' of both audio and MIDI latency of 100 ms, resulting in a 300 ms of monitoring latency. With a buffer size of 256, this means around 30 ms of 'performance offset', which starts to make me late in my timing when perfoming in practice meaning in a 1/16th based sequence always missing the first note etc. So, for the note from MIDI keyboard to land on musical time in the external sequencer it needs to be anticipated 200 ms instead of the 100 ms roundtrip latency. But when I press a note on the keyboard, it's also susceptible for another 100 ms of MIDI latency when routed via Live. Because when I hear the sequencer controlling the software instrument in sync with Live click, the sequencer is actually running 100 ms 'before', because of the offset. This makes sense.īut if I where to perform with this setup, instead of just adjusting myself for the 100 ms latency, I would actually have to double that in the anticipation of playing the MIDI keyboard. Now, for the external MIDI sequencer to be more accurately in sync with the Live internal sequencer, I need to set a MIDI sync offset of around -100 ms for the external sequencer, which is roughly the negative of the total roundtrip latency. The external sequencer takes MIDI sync from Live, and the resulting MIDI output from external sequencer is routed back to Live and is used to play a software instrument on another track. I route it to an external hardware MIDI sequencer, to control it's note transposition/key changes or something similar. I setup one MIDI track taking input from a MIDI keyboard as in the previous example. But let's assume the 100 ms roundtrip for an example. But I guess that's how Ableton meant it to be.īut if I setup a more complex project, issues arise even with low buffer sizes. Allright, if were using buffer size of 256, the latency would be about 15 ms, which would be tolerable in most cases.Įven if I disable all audio inputs and outputs from the global preferences, and am routing MIDI from one USB device to another, the audio interface total roundtrip latency seems to be the reference for passing through the MIDI data. I press a MIDI note, and instead of hearing the sound in near realtime, I hear the sound after 100 ms, even though the Ableton Live audio engine plays no part in this from my perspective.
One MIDI track taking input from a USB MIDI keyboard and routing the MIDI output to an external hardware desktop synthesizer, which is also connected with USB and monitored directly. With my audio interface, this results in a total roundtrip latency of around 100 ms.
Even at the nowdays greatly reduced risk of jitter.Īn atomic example with overly large buffer size of 2048 at 44k sample rate.
I think this would greatly improve the experience when performing, well, live with Live. And how some audio processing plugins introduce additional latency, and how the Delay Compension and Reduced Latency When Monitoring functions work in these situations.īut I would love to see some kind of 'near realtime' MIDI Performance mode in Live. I also understand the inevitable latency when monitoring audio through software/DAW. Because latency is consistent and predictable, it can be dealt with much more easily by both computers and people. In all cases, latency is preferable to jitter. 'Ableton‘s approach to MIDI timing is based on two key assumptions:ġ. I've read the and understand(?) that Ableton Live introduces some 'extra' midi latency/buffer to eliminate jitter and to maintain sync better.
0 kommentar(er)
