Hallo, Eric Van Buggenhaut hat gesagt: // Eric Van Buggenhaut wrote:
On Sat, Jan 03, 2004 at 01:40:54PM +0100, Frank Barknecht wrote:
Disabling LADSPA in libfluidsynth indeed did the trick for fluid~: fluid~ is up and running again now. I do wonder: The fluid-settings I used inside fluid~ explicitly disabled ladspa (as copied over from the fluidsynth source code). Normally it shouldn't go that ladspa path anyway then, not?
<fluidsynth debian package maintainer> At the moment I build libfluidsynth packages with LADSPA enabled. Do you think I should remove LADSPA support ? </fluidsynth debian package maintainer>
That's a hard one. On my machine fluid~ from pd-flext-ext does not work the way libfluidsynth currently is compiled i.e. with ladspa enabled. I cannot try this on another machine. This seems to be a bug not in pd-flext-ext, which Guenther Geiger maintains, but in fluidsynth.
I don't know how many people use LADSPA plugins in fluidsynth or how many people use fluid~ in Pd on Debian...
Maybe just wait a little and see, if Josh finds something?
ciao
On Sunday 04 January 2004 04:05, Frank Barknecht wrote:
Hi Frank - just a note to say I feel your pain - and sorry that I haven't had much time to look into my problem - which who knows, may or may not be related.
Namely, from PD, if I close a fluid~ instance which has a soundfount of say, 250MB on my 512MB machine, it seems to wreak havoc for a long time, until I lose patience and reboot (this is on a Linux machine!)
Larry
-
Frank Barknecht -
Larry Troxler