Daniel James wrote:
> Hi Ralf,
>> QJackCtl's latencies for the "more unstable" (because there was the need
>> for a KDE upgrade) 64 Studio are 26.1ms and for the more stable Suse
>> 11.0 46.4ms at the moment.
> That's a lot of latency for a MIDI instrument, I'm not surprised you
> can hear it. I generally record live audio at about 10ms, but if I was
> doing multitrack MIDI with overdubs, I'd be looking to get the latency
> down to the low single figures (in milliseconds).
> Is there any reason why you can't use the MIDI socket on your EWX
> 24/96? I'd expect better sync performance than when using two
> different interfaces.
maybe I can reduce the latency, because working with Reaper is
impossible and Linux needs less latency, but the trouble isn't made by
the latency. Fluidsynth as a DSSI for Rosegarden is okay. Fluidsynth
used by QSynth and controlled by Rosegarden is a problem, because the
speed isn't fine. Latency for DSSI and Fluidsynth is the same
DSSI has a fluctuation of speed at 120BPM of 1ms, while Qsynth and other
Non-DSSI have a fluctuation of speed at 120BPM of 2ms. 2ms can be heard
as bad timing, e.g. unisono isn't unisono, a groove won't groove, maybe
it's not only the 2ms, it might be possible that there is to add, that
Rosegarden can't sync by delaying the audio tracks for less than 10ms
and that is also needed or Audacities graphic is bad.
Just playing a virtual synth, I can't hear a latency, even if it should
be 46.4ms, that's why I guess the latency displayed by QJackCtl is
wrong. Even the Haas effect is less than 40ms and a 1/48 note at 120BPM
has a length of 41.6ms. The real latency must be shorter.
Again, the problem is that the MIDI timing isn't straight and that it
can be heard, it's not only that I looked at an editor.
64studio-users mailing list