25 Sep
2009
25 Sep
'09
5:53 p.m.
I ran into a benchmark tool at http://github.com/koppi/alsa-midi-latency-test/
and ran it though my MidiSport 2x2 Anniversary Edition (no firmware upload
required :) ) and Edirol UA-25EX.
Attached are the results on an untuned Debian Testing machine (2.6.30-1-686)
started with 'chrt -f 50 ./src/alsa-midi-latency-test -s 40'
The Edirol sure outperformed the MidiSport - the difference didn't seem huge
though.
(at the time of writing you need to add some symlinks to
/usr/share/automake-1.10/... to make it build right, mailed the author about
that already).
Regards,
Arnout
On Thu, Sep 24, 2009 at 07:56:22AM -0400, Dave Phillips wrote:
I've been experimenting with MIDI control from one
machine to another. I
checked the timing of a single note played simultanesouly by instances
of QSynth on both machines and was surprised to hear a very noticeable
flamming. I then replaced the MidiSport 2x2 with my Edirol UA25 and the
flamming disappeared. Both are USB interfaces, btw. MIDI routing between
the machines is handled by a Yamaha MJC8 and has never been problematic
with that box.
So, my question(s): Is the MidiSport just poorly designed and is there a
further condition or module option that can correct the timing delay
from that unit ?
Best,
dp
_______________________________________________
Linux-audio-dev mailing list
Linux-audio-dev(a)lists.linuxaudio.org
http://lists.linuxaudio.org/mailman/listinfo/linux-audio-dev