Sounds like pretty good arguments/information to me. I think it might
be better to implement streaming support though, which has been on the
wish list for a while. I agree it is a bit overkill to lock all sample
data, as it currently is, when possibly only a few are being actually
used for the ac
I've been having an enlightening offline discussion with P. Millar about
memory usage within fluidsynth, particularly the 'mlocking' of soundfont
sample data areas. I've done some cursory exploration of the source code
and come to the conclusion that the hypothetical average user (of which there
a
Hi all,
I've written (what I hope is) a minimal, functioning test code for running
fluidsynth, linking against libfluidsynth. Its available from:
http://ppewww.physics.gla.ac.uk/~paul/fluidsynth/simple-fluidsynth-test.c
Running this test test through valgrind's memcheck tool is quite interesti
Hello Paul,
I wouldn't be surprised if there are some leaks. Doesn't mean it
shouldn't be fixed of course though! The valgrind output would be more
useful if FluidSynth had debugging support enabled, but I could get this
output myself too, which I will probably do when I get around to axing
the
On Tue, 21 Nov 2006 19:45:57 +
Paul Millar <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> I've written (what I hope is) a minimal, functioning test code for running
> fluidsynth, linking against libfluidsynth. Its available from:
>
> http://ppewww.physics.gla.ac.uk/~paul/fluidsynth/simple-fluids
