[PlanetCCRMA] Re: Starting fluidsynth

[Rui Nuno Capela]

Timo Sivula wrote:
>
> Fluidsynth works nicely by starting first qjackctl and then fluidsynth.
> Using the "connect" window I then connect the audio output from fluidsynth
> to alsa_pcm and the output from the soundcard midi to fluidsynth input.
> (Nando's command line above does not yet work for me) So far so good.
>
> 1) I would like to automate the setup above with a script. Can the above
> connecting and starting up be done on the command line? If it can, could
> someone send an example of how to do it? I would like to make a script
> that I can activate by clicking it to bring the whole thing up in one go.
>

Use qjackctl's visual patchbay, that's what its for :)

After you have all wired up as you want, open the patchbay window and
click "New". Answer yes to the snapshot question. This will populate a new
patchbay definition with a snapshot of all the current active connections
(audio and midi).

However, you'd better now edit the fluidsynth midi input client name as it
includes the PID suffix and that will certainly change in the future. On
the fluidsynth midi input socket edit dialog, replace the PID number with
a regular expression like "[0-9]+". Example:

    "FLUID Synth (31625)" becomes "FLUID Synth \([0-9]+\)"

Note the backslashes to escape both parentesis, otherwise they will be
parsed as regular expression meta-characters.

Just save and activate the new patchbay definition and from then on,
qjackctl will check and try to maintain the jack and alsa_seq midi
connections as they are defined by the active patchbay.

Hope you get it right.
-- 
rncbc aka Rui Nuno Capela
rncbc@rncbc.org