Josh, Garett,
Thank guys for the quick reply.
Yes, the work-around worked fine: when setting "audio.alsa.device" to "hw:0"
I see the CPU usage drops to far more modest values.
Setting "audio.alsa.device" to "default" (fluidsynth's default value, I
believe) recreates the problem. [as an asid
It is indeed known about, but should have been fixed a while ago.. I'll
do my best to fix this issue and get a release out soon. Best regards,
Josh
On Thu, 2006-11-16 at 11:50 -0700, Garett Shulman wrote:
> I believe that this is a known glitch between fluidsynth and alsa plug.
> Check
Thanks for the links, I have a better understanding of dithering now :)
FluidSynth really needs a new release, I'll make it a priority. Best
regards,
Josh Green
On Wed, 2006-11-15 at 03:23 +0200, Zenkov Mihail wrote:
> > Thank you for your patch submission. I haven't yet given it a try.
I believe that this is a known glitch between fluidsynth and alsa plug.
Check out:
http://www.mail-archive.com/fluid-dev@nongnu.org/msg00183.html
Paul Millar wrote:
Hi all,
Inspired by Nathan Harrington's article on monitoring computers with
FluidSynth (recently linked to from Slashdot), I've
Hi all,
Inspired by Nathan Harrington's article on monitoring computers with
FluidSynth (recently linked to from Slashdot), I've started coding against
FluidSynth's C-library: libfluidsynth.
I'd like to say first how easy it was: libfluidsynth is a very nice library!
The main reason for writin
