16 Dec
2009
16 Dec
'09
6:54 a.m.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Arnold Krille schrieb:
On Tuesday 15 December 2009 22:37:53 Dan S wrote:
In my experience, 10ms roundtrip is the borderline. Anything below that
is safe ground, even for Bluegrass-Banjos at 150 bpm ;-)
at the other hand:
it is also my experience, that a system with a good audio-interface
that cannot run okayish with 10ms will not run okayish with 100ms
either. If normal load (1-2 synths, a sampler, 2 dozen
standard-processors for filters and dynamics plus 3-4 FX like flangers
and the like, ardour project with 40+tracks, 48KHz) produces
significantly more then 2-3 xruns/h at 10ms - then there is something,
that needs tweaking. Often it is a badly programmed processor or really
freaky settings for a synth. Or you have a bottleneck in the
data-transport line like some conflicting SATA-controller or trouble
with ffado etc etc etc
best regs
HZN
If you think 64ms is fine then you're
probably not doing live
beatboxing processing ;). For percussive sounds especially, the
latency is immediately obvious to a live musician - for many
performers a high latency also manifests in a tendency to slow your
tempo down (lagging your performance to keep in sync with the lagged
output)...
So if you know your sound has a (constant) delay before its heard, why don't
you anticipate for that and just make your sound earlier?
It works, for centuries organists have done so.
But to be fair: I use my synths at <20ms. -----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAksovHYACgkQ1Aecwva1SWP7/QCfdiKycCrPT4dGjYmzJMGeoaQ3
zogAnj/QNIdbmx8lLu86rDGBjDw4NGBA
=h5Cj
-----END PGP SIGNATURE-----