A few thoughts from my side...
> I have the suspicion that your MIDI keyboard is not yet fully registered as a
> MIDI device when fluidsynth starts.
This shouldn't matter. As soon as a new MIDI port is made available in
alsa_seq, fluidsynth receives an event about a new port becoming
available a
Hi Jean-Jacques.
I have tried what you suggested by updating /root/.profile like this:
aplay /usr/share/sounds/alsa/Front_Left.wav
/home/george/startfs
sleep 2
aplay /usr/share/sounds/alsa/Front_Right.wav
killall fluidsynth
sleep 2
/home/george/startfs
aplay /usr/share/sounds/alsa/Front_L
Hello Georges,
After reading your issue about no Alsa audio when starting FluidSynth from root
.profile.
This sounds like if Alsa hadn't started (or not yet finished its
initialization) before FluidSynth starts.
May be could you validate this supposing trying to start Alsa player (aplay)
@Marcus - many thanks for your help.
I tried directing the output from fluidsynth to a file but it was too brief
to reveal anything.
I also used 'aconnect -l' to determine whether it was the midi connection
from my keyboard that was not being made correctly but everything was as
expected;
Next I t
