u all for your help. And for a great software ;-)
> Nikolay Shaplov schrieb am Mo., 14. Feb. 2022, 10:58:
> > Though I should say it is totally counterintuitive. No user would guess
> > how
> > to solve "open /dev/snd/midiC0D0 failed" problem. No wonder google does
>
В письме от понедельник, 14 февраля 2022 г. 12:46:19 MSK пользователь Nikolay
Shaplov написал:
> > > that parameter ist for the alsa_sequencer backend to name the
> > > _fluidsynth_
> > > input port.
> >
> > That is correct. The --portname parameter sets
dsynth -a pulseaudio -m alsa_raw -g 10 -r 48000 -O
"midi.alsa.device=hw:1,0,0" /usr/share/sounds/sf3/default-GM.sf3
[.]
ALSA lib rawmidi_hw.c:235:(snd_rawmidi_hw_open) open /dev/snd/midiC0D0 failed:
No such file or directory
--
Nikolay Shaplov aka Nataraj
Fuzzing Engin
can also look into the code, and try
to get what is happening...
--
Nikolay Shaplov aka Nataraj
Fuzzing Engineer at Postgres Professional
Matrix IM: @dhyan:nataraj.su
___
fluid-dev mailing list
fluid-dev@nongnu.org
https://lists.nongnu.org/mailman/listinfo/fluid-dev
port of your second sound card) and use the ones, which
> are created in your fluidsynth command. If you don't find any "MIDI*"
> in /dev/snd, the driver isn't loaded (and you can load it with the
> "modprobe" command in case you know the right driver for the
midiC1D0
I trued to pass device name via -p: midiC1D0, /dev/snd/midiC1D0 and so on, but
did not success.
creating symlink from midiC1D0 to midiC0D0 solves the problem though.
This issue is not discussed anywhere I can found. So, are there any way to
make it work without creating a symlink? I am
chosen alsa_seq in my
case).
Isn't MIDI devices are somehow a standard thing? This driver "converts" what
into what?
Hope it's OK to ask this question here. If I got an answer I will manage to
write better and clearer documentation.
--
Nikolay Shaplov aka Nataraj
Fuzzing
