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

[Aere Greenway]

All:

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:
> Hi,
>
> I'm embedding FluidSynth as an instrument in the Radium music editor 
> (http://users.notam02.no/~kjetism/radium).
>
> 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 several 
> 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: 
> http://users.notam02.no/~kjetism/fluid_defsfont_patch.diff
>
> Please let me know if there's anything that's needed to do in order for 
> you to use it.
>
> I also have a question: Can delete_fluid_defsfont and 
> fluid_defsfont_load_sampledata be called from different threads at the 
> same time?
> In so, we also need a lock protecting the global list of cached 
> sampledata.
>
> -Kjetil
>
>
> _______________________________________________
> fluid-dev mailing list
> address@hidden
> https://lists.nongnu.org/mailman/listinfo/fluid-dev

-- 

Sincerely,
Aere