|
Gents,
let me notice here, as a side information, my practical experience with FS
working real-time, that usage of more than one FS instances raises the
performance of all test systems intensely. On my AMD DualCore 2x3 GHz system
(organ console) I was able to reduce the CPU usage to around 5-10% using a
full organ by using around 4-7 instances of FS, instead of around 60% CPU usage
while using only one instance of FS for the same instrument.
Regards
Bernd.
-----
Folgende Nachricht wurde empfangen -----
Zeit:
2010-08-06, 19:08:57
Betreff:
Re: [fluid-dev] New voice overflow code committed
<snip>
One thought concerning a dynamic voice overflow
algorithm is to
utilize the cpu_load calculation. At least in regards to
timing the
synthesis loop and comparing it to realtime. A running average
could
be performed and if the value starts to approach realtime, then
voices
should be killed. I think that might work regardless of how
many
instances of FluidSynth are running or what other applications
are
using CPU, since its based on how much CPU is being given
to
FluidSynth by the OS.
Elimar
<snap>
|