F11: alsa sequencer error

[Philippe Carriere]

> > Hi,
> > 
> > since the two or three last releases, I have the following errors:
> > 
> >     Qjackctl messages
> > 
> >         21:27:05.799 Patchbay deactivated.
> >         21:27:05.851 Statistics reset.
> >         21:27:05.853 Could not open ALSA sequencer as a client. ALSA
> > MIDI patchbay will be not available.
> >         ALSA lib seq_hw.c:457:(snd_seq_hw_open) open /dev/snd/seq
> > failed: Aucun fichier ou dossier de ce type
> > 
> >     Qsynth messages
> > 
> >         21:30:56.500 Qsynth1: Creating synthesizer engine...
> >         21:30:56.517 Qsynth1: Creating audio driver (jack)...
> >         21:30:56.638 Qsynth1: Creating MIDI router (alsa_seq)...
> >         21:30:56.638 Qsynth1: Creating MIDI driver (alsa_seq)...
> >         21:30:56.640 Qsynth1: Failed to create the MIDI driver
> > (alsa_seq). No MIDI input will be available.
> >         ALSA lib seq_hw.c:457:(snd_seq_hw_open) open /dev/snd/seq
> > failed: Aucun fichier ou dossier de ce type
> >         fluidsynth: error: Error opening ALSA sequencer
> > 
> > Finally, even simply using aplaymidi doesn't work:
> > 
> >         $ aplaymidi file.midi 
> >         ALSA lib seq_hw.c:457:(snd_seq_hw_open) open /dev/snd/seq
> > failed: No such file or directory
> >         Cannot open sequencer - No such file or directory
> > 
> > Present configuration is:
> >     $ uname -a
> >     Linux localhost.localdomain 2.6.29.1-37.rc1.fc11.x86_64 #1 SMP Wed
> > Apr 1 08:56:57 EDT 2009 x86_64 x86_64 x86_64 GNU/Linux
> > 
> > Has something changed or is it a bug ?
> > 
> > Phil.
> > 
> > 

> If your sound hardware does not support MIDI, you need to run a software
> sequencer, e.g. timidity++.
> 
> For JACK output, use this:
> timidity -iADq -Oj --sequencer-ports=1
> 
> This one will use PulseAudio (through libao) for output instead:
> timidity -iADq -OO --sequencer-ports=1
> 
>         Kevin Kofler
> 

Well, rather than timidity I use Fluidsynth (the reason for which I
mentionned the Qsynth GUI). The problem is that Qjackctl fails before
any invocation of midi input or output, just starting (note that pure
audio works) while it was working up to approximately one week ago; the
situation changed with the latest releases of rawhide. 

Effectively, aplaymidi does not enable sound with no hardware
synthetizer but does not lead to an error: typically

   $  aplaymidi file.midi -p14:0

runs (of course without sounding) on the same hardware and standart F10.

I'm thus rather inclined to think that something is going wrong
somewhere (possibly incompatible changes between alsa standart and
jack).

Phil.