On 8/1/2010 11:21 AM, David Henningsson wrote:
2010-08-01 19:00, Elimar Green skrev:
On Sat, Jul 31, 2010 at 2:00 PM, David Henningsson
<launchpad....@epost.diwic.se> wrote:
As a side note, I also added the possibility to have polyphony up to
65535 voices (which should be enough even for jOrgan users!) and that
the polyphony can increase on-the-fly, which did not work before. Having
so many voices might mean some overhead (and memory usage) even if
they're not used though.
I think the way it worked before (or at least should have worked) is
that the initial value for the polyphony set the maximum allowed value
(and the memory requirements), you could then adjust it to be less
than the system maximum.
Actually synth->nvoices was set to synth->polyphony and not 4095 (the
previous maximum).
With this new change, does that mean that the memory allocation is
always for 64k voices? That is probably a significant amount of
memory if so (64k * sizeof (FluidVoice) at least).
The array will be reallocated, and new voices created, when the
polyphony is updated.
There are at least 6 people testing the current version of FluidSynth
using the Miditzer virtual theatre organ on Windows. The Miditzer
doesn't use a wide variety of FluidSynth features but these testers
should at least give the synthesis engine some pretty good exercise. The
Miditzer uses an MSVC build of libfluidsynth.dll. I have discovered that
it needs at least libglib-2.0-0.dll
<http://site.virtualorgan.com/community/download/file.php?id=2008>,
libgthread-2.0-0.dll
<http://site.virtualorgan.com/community/download/file.php?id=2005>, and
msvcr100.dll
<http://site.virtualorgan.com/community/download/file.php?id=2006> as
helpers. <http://site.virtualorgan.com/community/download/file.php?id=2006>
We have also discovered that there is probably something more required
as a helper because when the polyphony is increased it causes a crash
except on my development machine. To me that suggests that I have
something on my machine that is not on the others. Can anyone make a
suggestion of what that might be?
Thanks,
Jim Henry
_______________________________________________
fluid-dev mailing list
fluid-dev@nongnu.org
http://lists.nongnu.org/mailman/listinfo/fluid-dev
