On Sat, 19 Dec 2009, robert lazarski wrote:
> /root> jackd -d alsa &
For now, don't use JACK unless you have to (e.g. to use
QSynth or something).
Also, don't do this stuff as root.
> /root> arecordmidi -l
> Port Client name Port name
> 14:0 Midi Through Midi Through Port-0
> 16:0 M Audio Audiophile 24/96 M Audio Audiophile 24/96 MIDI
> 24:0 MidiSport 2x2 MidiSport 2x2 MIDI 1
> 24:1 MidiSport 2x2 MidiSport 2x2 MIDI 2
> [dhcppc0(root)]
Connect the Oasys to the IN on one of the midisport ports
and start your sequence. Meanwhile, do:
$ aseqdump --port=24:0
(or 24:1) and see if anything registers. If you see
anything, then the MIDI port is working and the problem is
something else. If you're not getting /anything/ -- then
the problem is between the keyboard and ALSA. Otherwise,
it's probably a problem with using arecordmidi.
> /root> arecordmidi --port 24:0 oasys.mid
I wonder if the tempo settings (man arecordmidi) have
anything to do with this?
-gabriel
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user@email-addr-hidden
http://lists.linuxaudio.org/mailman/listinfo/linux-audio-user
Received on Sun Dec 20 00:15:02 2009
This archive was generated by hypermail 2.1.8 : Sun Dec 20 2009 - 00:15:02 EET