Hi!
On Fri, Apr 19, 2019 at 09:27:35AM +0200, Tom M. wrote:
> > Another question I have is related to threading. I'd like to use two
> > fluid_synth_t* instances in two different threads with two different
> > soundfonts to render two different midi tracks. I'm assuming that I can
> > call f
Hi Tom.
On 19.04.19 09:27, Tom M. wrote:
>> Another question I have is related to threading. I'd like to use two
>> fluid_synth_t* instances in two different threads with two different
>> soundfonts to render two different midi tracks. I'm assuming that I can call
>> fluid_synth_process() indep
> > Another question I have is related to threading. I'd like to use two
> > fluid_synth_t* instances in two different threads with two different
> > soundfonts to render two different midi tracks.
As explained by Tom, you don't need to create two fluid_synth_t* instances in
two different th
> All right, I didn't even know that there is a sample cache so far. Suppose I
> load the same huge soundfont into two different fluid_synth_t objects. Will
> that double my memory usage?
No. Only the structural information of a soundfont is allocated for every
synth, e.g. preset zones, instrumen
A maintenance release for fluidsynth has been released.
Details can be found in the release notes:
Download: https://github.com/FluidSynth/fluidsynth/releases/tag/v2.0.5
API: http://www.fluidsynth.org/api/
Website: http://www.fluidsynth.org
FluidSynth is a real-time software synthesizer based on
Hi Stefan,
pls. also send a copy to our mailing list the next time.
> I've seen that my fixes should be in 2.0.5. Do you have an approximate idea
> when this fluidsynth release will be available?
Today.
> Another question I have is related to threading. I'd like to use two
> fluid_synth_t* in
