> > The keyboard seem to send raw midi messages in a stream, but Alsa does
> > not translate them in Sequencer events.
>
> Strange. This should happen automatically, especially if the sequencer
> device (port 20) is there.
>
> Does the count in /proc/asound/card1/midi0 increase while aseqdump
> is
Fernando Carello wrote:
> So, I've seen that a working MIDI keyboard "creates" this device:
>
> /dev/snd/-midiC0D0
>
> while my problematic MIDI keyboard has instead:
>
> /dev/snd/-midiC1D0
"C1" means "card 1"; this is because card 0 is already occupied by another
device.
> The keyboard seem to
For temporary purposes and/or a manual workaround, you could
create a symlink:
cd /dev/snd
ln -s ./-midiC0D0 ./-midiC1D0
The "./" prefix is to force the command parser in the 'ln'
executable to interpret the names as arguments rather than
options.
At the very least, that should tell you
Sorry, wrong clue.
The problem is more subtle.
The keyboard seem to send raw midi messages in a stream, but Alsa does
not translate them in Sequencer events.
The softsynth expects Seq midi events (Note On / Note Off and such):
it cannot manage raw MIDI messages directly.
So the question
So, I've seen that a working MIDI keyboard "creates" this device:
/dev/snd/-midiC0D0
while my problematic MIDI keyboard has instead:
/dev/snd/-midiC1D0
see that "C1"?
This has to do with "amidi --dump" requiring "--port hw:1" instead of
the usual "--port hw:0"
Now:
How can I configure ALSA
