i was testing some PD patches and I found some problems with xsample
external. When I load the external and start audio the PD CPU usage
raises to 98% or so.The PD GUI gets kind of frozen, i cannot open any
dialogue and I have to force PD to quit. I have compiled Flext and
xsample from source and now it works fine. I was just wondering if
this is happening only to me or it is a bug with the xsample package

There seems to be a general problem with the way Flext and Flext
externals are packaged at the moment, see this bug and its duplicates
(in short, you are not alone):

https://bugs.launchpad.net/puredyne-live/+bug/505247

later i remember i already had this few months ago. I had to compile it myself and change some compilation flags. This time i did not have to change anything.

Probably the packages are missing some important subtle configuration
details - which settings did you use to compile your working Flext and
xsample? Does it still work if you load other Flext externals (that you
compiled) into Pd in the same session? Does it make a difference if you
use -lib or instantiate the objects one at a time?

I have not compiled any other flext external so I cannot test that. But it does not make a difference to use -lib or instantiate xsample, as soon as it loads it freezes PD

I used the default settings in the latest svn versions of flext and xsample, I think this is all

UFLAGS=-msse -mfpmath=sse -ffast-math
OFLAGS=-O3
OFLAGS+=-march=pentium4

thanks!


---
[email protected]
http://identi.ca/group/puredyne
irc://irc.goto10.org/puredyne

Reply via email to