[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [fluid-dev] Multiple fluidsynth instances or all-in-one?

From: Josh Green
Subject: Re: [fluid-dev] Multiple fluidsynth instances or all-in-one?
Date: Wed, 17 Jan 2007 20:21:35 +0000

Each FluidSynth audio driver is only one thread, and thus all synthesis
processing is done in a single thread.  There are separate threads for
MIDI input though.  FluidSynth isn't really doing anything special
currently to utilize SMP systems.  If you are running a couple separate
FluidSynth processes it may or may not be more efficient.  Not really
sure.  It would be nice to allow FluidSynth to at least be able to share
settings/instruments etc between instances.  This has been suggested
before, but so far no progress in that area.

Best regards,

On Tue, 2007-01-16 at 22:51 -0800, Ken Restivo wrote:
> Hash: SHA1
> On an SMP system (Intel Core Duo), does fluidsynth spawn off child 
> threads/processes for each midi channel active?
> Right now I have multiple fluidsynth instances, one for each MIDI instrument, 
> and I patch them using qjackctl. I suppose I could also have only one 
> fluidsynth instance, with all my soundfonts loaded, and use fluidsynth's 
> routing and different MIDI channels to send the various signals to the 
> correct instrument.
> Which approach would make the most sense on an SMP machine?
> - -ken
> Version: GnuPG v1.4.1 (GNU/Linux)
> iD8DBQFFrcdre8HF+6xeOIcRAsw7AJ0Ukz9nGE4IHwV4qQQsZFgQ1HA68gCfYcQ1
> WlY5rDuVfSLN53/GOzFxisE=
> =ciY8
> _______________________________________________
> fluid-dev mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/fluid-dev

reply via email to

[Prev in Thread] Current Thread [Next in Thread]