[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [fluid-dev] Major degradation in sound quality & cpu usage going fro

From: Aere Greenway
Subject: Re: [fluid-dev] Major degradation in sound quality & cpu usage going from Ubuntu 11.04 to 11.10
Date: Mon, 14 Nov 2011 21:17:44 -0700


I installed the version of Fluidsynth in your PPA, and found that it definitely fixes the problem.  Hooraaay! 

I had some difficulty testing it because (I think) this development version uses so much memory, that I couldn't run it on my 1 gigibyte RAM machine without having it the only thing running, and not loading the soundfont into the emu10k1's.  It was also an unpleasant surprise to find that it took out the special configuration necessary for running JACK, but I was able to put that back in manually, after uttering some choice expletives... 

If this high memory usage is not expected, perhaps the fix still has problems. 

But with this version installed, it ran every MIDI sequence that gave it severe problems before, and it didn't get a single under-run in JACK - even though I am running it on the KDE version of Ubuntu (Kubuntu). 

I highly recommend that this particular fix be included in the Ubuntu 11.10 release, due to the severe degradation in performance and sound quality of Fluidsynth that is in that release, without the fix. 

Thank you very much for fixing this!  I now have a way forward for my music education initiative. 

Please let me know if there is anything else you want me to try with your special development level of Fluidsynth.  Otherwise, I will probably install the earlier version to avoid the memory-usage problems. 

Aere Greenway

On Mon, 2011-11-07 at 11:43 +0100, David Henningsson wrote:
On 11/05/2011 09:12 PM, Aere Greenway wrote:
> David, et al:
> I have not heard back since I reported on performing the test you asked
> me to run.
> I noticed on the website that there are "0 new bugs".
> What process do I need to go through to have this problem evaluated as
> to whether it is officially a 'bug' or not?
> To me, this problem kills my future prospects. The music education
> package I am poised to put out depends on FluidSynth (actually Qsynth,
> which uses it).
> I could distribute my package, and people could get all excited about
> it, but when they installed it themselves (instead of using what comes
> with the package), they would find that the installed version won't even
> play the demo-music, even on a fast machine.
> What I had to go through to compile the older version on the current
> level is not something I could expect a new user of Linux to do.
> There is no path forward if this cannot be fixed. But of course, those
> are the chances I take when I attempt to develop something.
> It would be very helpful if I had some indication of whether or not this
> problem will be addressed, or even looked at.
> I am willing to supply MIDI and audio files you could test it with, and
> verify any fixes.
> Please consider the idea that what I have been doing in the past to
> avoid under-runs, by configuring fewer simultaneous voices (setting the
> polyphony parameter to 64, or even 48 on a slower machine), may be a
> more elegant solution than what has apparently been done in the latest
> release (probably to address that same problem of under-runs).
> I think my planned product could make a big difference in the way people
> learn to play (and compose) music, and I am really hoping FluidSynth can
> be a part of it. It certainly has been a rock-solid, dependable
> component up to now.
> Sincerely,
> Aere Greenway

Hi Aere,

I've been on travel with limited time/possibility to help you. In 
addition, the rebuild I asked you to do was harder than I expected.

But now I'm home again, and here's what I've done now:

I've taken the 1.1.5 package, and added the patch I committed as r435. 
This is because you said something earlier about sound working up to the 
polyphony limit.
I then uploaded the source package to a ppa: 

The ppa probably has finished building when you read this, so can you 
download/install the packages from there and see if it resolves your 
problem? Thanks!

// David



reply via email to

[Prev in Thread] Current Thread [Next in Thread]