26 Jan
2014
26 Jan
'14
10:55 p.m.
On 2014-01-26 14:56 +0100, Clemens Ladisch wrote:
Andre Majorel wrote:
Tried three combinations of one alsa-midi-latency-test process
writing to one Romio II port and another reading from another
Romio II port :
alsa-midi-latency-test -o 24:0 -i 28:7 &
alsa-midi-latency-test -o 28:7 -i 24:0
alsa-midi-latency-test -o 24:0 -i 28:7 &
alsa-midi-latency-test -o 28:7 -i 24:1
alsa-midi-latency-test -o 24:1 -i 28:7 &
alsa-midi-latency-test -o 28:7 -i 24:1
They all worked without a hitch.
Tried the Romio II with itself again : it failed as before.
Found a large number of "usb_submit_urb: -22" messages in
kern.log for yesterday (but none for today).
--
André Majorel http://www.teaser.fr/~amajorel/
I'm trying to use midi-alsa-latency-test
0.0.3
with an ESI Romio II USB - MIDI interface
and it's not working reliably.
No, it's not a bad connection. Running alsa-midi-latency-test
between one output (or input) of the Romio II and one input (or
output) of another MIDI interface works reliably. What doesn't
work is loopback between the Romio II and itself.
What happens if you try two loopbacks at the same time, from the
Romio to another device, and from another device to the Romio?