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 becomes: why Alsa does not correctly translates the raw MIDI messages (as in "amidi --dump", which works) in MIDI sequencer events (as in "aseqdump", which does not work)? amidi --dump --port hw:1 90 42 17 80 42 00 90 3D 19 90 3F 0C aseqdump -p 20 Waiting for data. Press Ctrl+C to end. Source Event Ch Data (nothing happens as I play notes on the keyboard) Thanks! Il giorno dom 31 gen 2021 alle ore 13:20 Fernando Carello <fcarello@xxxxxxxxx> ha scritto: > > 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 (.asoundrc?) in order to correctly "map" that > "port hw:1", so it can be used by a MIDI softsynth, which expects > "hw:0"? > > Thanks! > > > Il giorno sab 30 gen 2021 alle ore 18:54 Fernando Carello > <fcarello@xxxxxxxxx> ha scritto: > > > > > > No events with asqedump: :-( > > > > > > Try with "amidi --dump --port hw:1". > > > > This works! > > > > amidi --dump --port hw:1 > > > > 90 42 17 > > 80 42 00 > > 90 3D 19 > > 90 3F 0C > > > > Thanks a lot! > > > > Now, how should I configure ALSA in order for my softsynth > > (ZynAddSubFx) to "see" this keyboard? > > > > > Do other USB MIDI devices (or USB devices) work? > > > > Yes, other MIDI USB keyboards (for example Akai LPK25) work fine; > > "aseqdump" shows MIDI messages and the softsynth plays without issues. _______________________________________________ Alsa-user mailing list Alsa-user@xxxxxxxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/alsa-user
