[Top][All Lists]

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

Re: [fluid-dev] [PATCH] sampledata caching

From: Kjetil Matheussen
Subject: Re: [fluid-dev] [PATCH] sampledata caching
Date: Tue, 09 Oct 2012 20:11:31 +0200
User-agent: Roundcube Webmail/0.6

Thanks for the feedback. I wasn't sure if it was a real problem, or if
I just used fluidsynth the wrong way. Anyway, my patch should solve your
problem too.

On 09.10.2012 19:51, Aere Greenway wrote:

 This same problem is apparent when using Qsynth. I have wished for
what Kjetil has worked-out, but had no idea of how hard (or difficult)
such a fix would be (so I expressed this need only as a wish).

 For my users with less than 1 gigabytes of RAM, I work around the
problem my using the good (150 megabyte) soundfont for the first
Qsynth engine, and use a poorer-quality 8 megabyte font for the 2nd
Qsynth engine.

 - Aere

 On Tue, 2012-10-09 at 11:13 +0200, Kjetil Matheussen wrote:


I'm embedding FluidSynth as an instrument in the Radium music editor


It works fine (thanks for the great work!), but the memory usage was

sometimes shockingly high because fluidsynth reloads
entire soundfonts for every new synth, even if the soundfont was
already used in a different synth.

Maybe I have misunderstood something, but instead of spending
more hours trying to figure out if I had misunderstood
something, I modified fluidsynth to cache already loaded sampledata
from soundfonts.

Here's the patch:

Please let me know if there's anything that's needed to do in order
you to use it.

I also have a question: Can delete_fluid_defsfont and
fluid_defsfont_load_sampledata be called from different threads at
same time?
In so, we also need a lock protecting the global list of cached


fluid-dev mailing list

reply via email to

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