On 10/13/2012 10:50 AM, BCA wrote:
Hello David,
as I'm a newbie to this - is the current "snapshot" of the sourcecode
containing the new patch now? I just managed compiling the source and I'm eager to test
the new RAM handling...
Many thanks and regards
Bernd.
Yes, if you checkout the lates
Absender: David Henningsson
Empfänger: FluidSynth mailing list
Zeit: 2012-10-12, 10:54:08
Betreff: Re: [fluid-dev] [PATCH] sampledata caching
...
>
>I've committed your patch now, after fixing a compiler warning and an
>unprotected read of all_cached_sample
On 12.10.2012 10:54, David Henningsson wrote:
On 10/10/2012 10:29 AM, Kjetil Matheussen wrote:
On 10.10.2012 09:51, Kjetil Matheussen wrote:
Another thing we need to verify is that the sampledata is
read-only
once it's been bigendian converted. If it is not, chances are that
two
threads would
On 10/10/2012 10:29 AM, Kjetil Matheussen wrote:
On 10.10.2012 09:51, Kjetil Matheussen wrote:
Another thing we need to verify is that the sampledata is read-only
once it's been bigendian converted. If it is not, chances are that two
threads would both modify the sampledata, causing problems.
On 10.10.2012 08:05, David Henningsson wrote:
On 10/09/2012 11:13 AM, 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 shoc
On 10.10.2012 09:51, Kjetil Matheussen wrote:
Another thing we need to verify is that the sampledata is read-only
once it's been bigendian converted. If it is not, chances are that
two
threads would both modify the sampledata, causing problems.
Okay. I'll see if there's any trouble changing
On 10.10.2012 08:05, David Henningsson wrote:
On 10/09/2012 11:13 AM, 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 shoc
On Tue, Oct 9, 2012 at 11:05 PM, David Henningsson wrote:
> On 10/09/2012 11:13 AM, 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
On 10/09/2012 11:13 AM, 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 s
Once upon a time I has a patch for Qsynth which attempted to accomplish the
same thing. It was not tested sufficiently at that time. I'm delighted that
you've put the remedy at the source.
On Tue, 09 Oct 2012 20:11:31 +0200
Kjetil Matheussen wrote:
> Thanks for the feedback. I wasn't sure if i
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:
All:
This same problem is apparent when using Qsynth. I have wished for
what Kjetil has work
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 g
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 soun
13 matches
Mail list logo
