[Top][All Lists]

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

Re: [fluid-dev] Qsynth broken with FluidSynth 1.1.0

From: Rui Nuno Capela
Subject: Re: [fluid-dev] Qsynth broken with FluidSynth 1.1.0
Date: Tue, 03 Nov 2009 16:45:09 +0000
User-agent: RoundCube Webmail/0.3-stable

On Tue, 03 Nov 2009 17:04:59 +0100, David Henningsson wrote:
> Rui Nuno Capela wrote:
>> i am sorry to chime in this late, but qsynth won't support this
>> fluidsynth release.
> :-(
>> first of all build fails due to (const char *) api change.
> Right, I'll let Josh answer to this, I thought he only changed the input

> API, not the callbacks. But that is easily fixed in QSynth, I can supply

> a patch against qsynth if you like.

no need for that, thanks. i can do that too. problem is that it now needs
conditional compilation flags (#ifdef's) to compile against conflicting
apis. if you fix it to 1.1.0 you'll break it to < 1.1.0, and vice versa.
not a good thing, not at all. it's a tiny change but one big trouble for
source distribution by packagers and users at large. a complete disgrace
and i would even commit the capital sin to suggest for immediate
regression, if not too late.

>> second, qsynth behaves very badly, inconsistently and troublesome
>> 1.1.0. everything just feels broken.
> Can you explain this a bit?
> I haven't used QSynth much, but I fixed the const char* stuff (in qsynth

> 0.3.4, ubuntu version) and built it against current svn. And I got 
> Fluidsynth up and working in qsynth and it seemed quite responsive when 
> I played on my piano, and that was actually even without a real-time 
> kernel or rtprio. I tried changing the reverb and it worked fine.

well, you can make it play soundfonts just barely, but using qsynth gui
elements on most if not all aspects is now a nightmare, nothing is liable,
nothing stays put, all feels broken, what can i say?

just try to use qsynth against libfluidsynth 1.1.0, tweak some reverb or
chorus parameters, even master gain if you like and look at the channel
presets for instance. you'll see the trouble in no time. all the advantage
you had by using a gui like qsynth has just gone astray. inconsistent,
unreliable, what a piece of junk it has become :(

sorry for the rant, if you were not a qsynth user before i'm sure you'll
never be one from now.

>> it's a pity :( 1.1.0 seemed a good step forward but i'm afraid i will
>> avoid it for quite some time, at least until i have some and rewrite
>> qsynth from the ground up. or else, let qsynth simply rot to oblivion
> Do you think you need do do more than change the const char* stuff?

yes. note that changing the const char * stuff will only solve the build
process. it is the runtime gui behavior that is at stake.

rncbc aka Rui Nuno Capela

reply via email to

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