Mathieu Bouchard a écrit :
Seriously, it's not really a problem to have any amount of latency
(even one million year) when there is a single musician.
If the musician can concentrate on the fingers rather than what is
heard, fine (but that needs to be a good player).
The musician don't have
On Tue, 19 Dec 2006, Patco wrote:
Mathieu Bouchard a écrit :
When the latency is changed, the musician has to retrain to a different
compensation delay, and that's more tiresome than not having to retrain.
Seriously, it's not really a problem to have any amount of latency (even one
million y
Mathieu Bouchard a écrit :
When the latency is changed, the musician has to retrain to a
different compensation delay, and that's more tiresome than not having
to retrain.
Hello?
Seriously, it's not really a problem to have any amount of latency
(even one million year) when there is a single m
Hans-Christoph Steiner a écrit :
Honestly, I doubt you could tell the difference between 4ms and 14ms
in a blind test. There have been many studies on this. If you can
detect such tiny differences in onset time, you would be superhuman.
Normal humans start to detect a modulation above a diff
On Dec 16, 2006, at 8:38 PM, Mathieu Bouchard wrote:
On Sun, 17 Dec 2006, Patco wrote:
aws a écrit :
A general method for latency measurement of any system is
described in this paper: Matthew Wright, Ryan Cassidy, Michael
Zbyszynski, Audio and Gesture Latency Measurements on Linux and
OS
I use the cc~ external. The time domain function is not so efficient
for large sizes, since it's an O(N^2) algorithm. The freq domain
version uses a fourier algorithm, so it uses only O(N*log(N)).
use [cc~ 1024] for time-domain where +/- 1024 is the bounds of the cc~
use [cc~ f] for one-block at
On Sat, 2006-12-16 at 20:38 -0500, Mathieu Bouchard wrote:
> On Sun, 17 Dec 2006, Patco wrote:
> > aws a écrit :
> >> A general method for latency measurement of any system is described in
> >> this paper: Matthew Wright, Ryan Cassidy, Michael Zbyszynski, Audio and
> >> Gesture Latency Measuremen
Mathieu Bouchard a écrit :
Do you have any ideas on how to make it more precise?
maybe with measuring the phase difference between a periodic signal sent
to DAC and the same received in the ADC instead of timing clicks?
Or guessing the frequency of differencial waves between both signals,
and
On Sun, 17 Dec 2006, Patco wrote:
aws a écrit :
A general method for latency measurement of any system is described in
this paper: Matthew Wright, Ryan Cassidy, Michael Zbyszynski, Audio and
Gesture Latency Measurements on Linux and OSX, Proceedings of ICMC
2004, Miami
or just connect ãudio
Bryan Jurish a écrit :
since i'm just plain not good enough to compensate before the
glitches become painfully audible...
marmosets,
Bryan
It becomes really difficult if you add the latency caused by the the
sound in air.
I've experience this once I was playing guitar at the control table
aws a écrit :
I have measured such things precisely when the application required
it. Its also fairly trivial to "hear" the latency by clapping into a
microphone and monitoring it over headphones after it passes through
the system. A 10msec difference is quite audible.
A general method for
On Sat, 2006-12-16 at 16:21 +0100, Patco wrote:
> IOhannes m zmoelnig a écrit :
> > Hans-Christoph Steiner wrote:
> >
> >> Apple puts good audio hardware in their laptops. I can get 14ms of
> >> latency on Mac OS X with Pd without really trying (I just set it to
> >> 14ms). I can get down to 1
IOhannes m zmoelnig a écrit :
Hans-Christoph Steiner wrote:
Apple puts good audio hardware in their laptops. I can get 14ms of
latency on Mac OS X with Pd without really trying (I just set it to
14ms). I can get down to 11ms if I don't mind clicks when I operate the
menus and switch to othe
13 matches
Mail list logo
