The below email was sent just to me but I would like to share it
with the list.
That is a really good idea, but a better idea might be to have a
"startfluid" script that is provided either by the distribution or is
part of the fluid synth team that works like the startx script. ie it
starts up fliud in the best manor with a GM sound set. I think it
would be best to have _one_ script that could be run by all the
different midi apps that want fluid started. PB could then call
start_fluid which would just start fluid with the best possible config
for that distribution. in an ideal world there would be no
distribution differences.
Just an idea any way. what do think about a startfluid script?
Louis
On Thu, May 21, 2009 at 11:38 PM, Joan Quintana <> wrote:
If QSynth crashes, I think that the problem is that, in setup, jack
audio driver is selected. When you start QSynth it starts without
-l option: doesn't try to start jack. So, if jack is not running,
it crashes. Solution: first start jack; or use alsa audio driver
directly.
In your case, a possible solution is: PB is launched by a script.
This script first attempts to start fluidsynth, and later start PB.
This script could be these two lines long, or 10ths lines: for
instance, detect soundcards available... this script can also read
a configuration file... PB could be great, but bash scripting and
programming coud make it better.
_______________________________________________
fluid-dev mailing list
address@hidden
http://lists.nongnu.org/mailman/listinfo/fluid-dev