Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project!

## Re: [Rosegarden-user] MIDI Latencies vs. Human Latencies

 Re: [Rosegarden-user] MIDI Latencies vs. Human Latencies From: Richard Cooper - 2007-08-28 16:11:42 On Tue, 28 Aug 2007 10:09:51 -0400, Abrolag = wrote: > Interesting you come up wit 25mS. I seem to remember (dimly) reading > that auditory response time was approximately 20mS Response time is something else, and much slower. Here's a script I mad= e = to test response time. It plays a drum after a random delay, and you = respond by playing any note, and after ten times it displays your averag= e. #!/usr/bin/perl use Time::HiRes qw( gettimeofday ); sub militime { (\$seconds, \$microseconds) =3D gettimeofday; return \$seconds + \$microseconds / 1000000; }; open MIDI, "+ 0)); \$bucket =3D int(100 * \$latency + 0.5 * (\$latency <=3D> 0)); \$bucket =3D +12 if \$bucket > +12; \$bucket =3D -12 if \$bucket < -12; exit if ++\$buckets[\$bucket+12] > 60; print "\e[d\e[2J"; for (\$i =3D 0; \$i <=3D 24; \$i++) { \$v =3D 10 * (\$i - 12); \$v =3D substr(' ' . \$v, -4); print "\$v " . '=3D' x \$buckets[\$i] . "\n"; }; if (abs(\$msecs) <=3D 16) { print "\e[1;33mLatency: \$msecs miliseconds\e[0m\n"; } else { print "Latency: \$msecs miliseconds\n"; }; }; \$data =3D substr(\$data, -2) if length(\$data) > 2; goto SELECT; }; close MIDI; I've noticed my scripts don't work while other MIDI applications are = running. I suppose my scripts also won't work if anyone's keyboard does= = "running status."