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 <fcarello@xxxxxxxxx>
> Date: Sun, 31 Jan 2021 13:20:19 +0100
> To: Clemens Ladisch <cladisch@xxxxxxxxxxxxxx>
> Cc: alsa-user@xxxxxxxxxxxxxxxxxxxxx
>
> 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
_______________________________________________
Alsa-user mailing list
Alsa-user@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/alsa-user
