Re: [Alsa-user] ALSA MIDI on Raspberry PI: no events from input device (USB keyboard)
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 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@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
Re: [Alsa-user] ALSA MIDI on Raspberry PI: no events from input device (USB keyboard)
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 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 > 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@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
Re: [Alsa-user] ALSA MIDI on Raspberry PI: no events from input device (USB keyboard)
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 whether that is _ALL_ of the problem. HTH Robert > From: Fernando Carello > Date: Sun, 31 Jan 2021 13:20:19 +0100 > To: Clemens Ladisch > Cc: alsa-user@lists.sourceforge.net > > 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 > 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@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/alsa-user ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
Re: [Alsa-user] ALSA MIDI on Raspberry PI: no events from input device (USB keyboard)
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 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 running? Regards, Clemens ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
Re: [Alsa-user] ALSA MIDI on Raspberry PI: no events from input device (USB keyboard)
> > 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 running? No, it stays fixed (this time the keyboard is on port 16): aseqdump --p 16 Waiting for data. Press Ctrl+C to end. Source Event Ch Data 16:0 Active Sensing tail -f midi0 GarageKey mini Output 0 Tx bytes : 0 Input 0 Rx bytes : 10155 Owner PID: 2224 Buffer size : 4096 Avail: 0 Overruns : 0 tail: midi0: file truncated GarageKey mini Output 0 Tx bytes : 0 Input 0 Rx bytes : 10155 Owner PID: 2224 Buffer size : 4096 Avail: 0 Overruns : 0 ___ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
