Hi everybody,
I'm struggling to get the plugin~ external working (to get LADSPA plugins in pd). Whenever I instanciate it in pd, I get an empty box with several inputs and outputs and an error message in the console about "bad screen distance". It also corrupts every single other node I create after that (all of them appear blank and output similar error messages). I quickly searched the archive and have seen that several users have had the same problem, and that for some, unsetting the LANG environment variable fixed the problem, but not for everybody. Unfortunately, I belong to the latter category. Has anybody found since another workaround ?
Btw this happens using pd 0.40.2 under Linux with plugin~ from some pd-extended 0.40 release (I think 0.40.0 but I'm not 100% sure).
Cheers
Have you tried using Jamie's [dssi~] ; I haven't used it but it sounds like it's good. It works for ladspa and dssi plugins
On 4/30/07, Cyrille.Damez@laposte.net Cyrille.Damez@laposte.net wrote:
Hi everybody,
I'm struggling to get the plugin~ external working (to get LADSPA plugins in pd). Whenever I instanciate it in pd, I get an empty box with several inputs and outputs and an error message in the console about "bad screen distance". It also corrupts every single other node I create after that (all of them appear blank and output similar error messages). I quickly searched the archive and have seen that several users have had the same problem, and that for some, unsetting the LANG environment variable fixed the problem, but not for everybody. Unfortunately, I belong to the latter category. Has anybody found since another workaround ?
Btw this happens using pd 0.40.2 under Linux with plugin~ from some pd-extended 0.40 release (I think 0.40.0 but I'm not 100% sure).
Cheers
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Le Lundi 30 Avril 2007 16:37, Kevin McCoy a écrit :
Have you tried using Jamie's [dssi~] ; I haven't used it but it sounds like it's good. It works for ladspa and dssi plugins
I didn't know that. I downloaded it and compiled it, but it crashes pd everytime I try to launch it, be it with a ladspa plugin or a dssi plugin (I tried with hexter). In the first case, the pd window closes instantly, whereas in the second it stays open (but doesn't do anything if I try to launch something from the menu) and the console tells me that pd segfaulted. I have to kill the plugin process(es) to close the pd window.
Hi Cyrille,
On Mon, 2007-04-30 at 20:43 +0200, Cyrille.Damez@laposte.net wrote:
Le Lundi 30 Avril 2007 16:37, Kevin McCoy a écrit :
Have you tried using Jamie's [dssi~] ; I haven't used it but it sounds like it's good. It works for ladspa and dssi plugins
I didn't know that. I downloaded it and compiled it, but it crashes pd everytime I try to launch it, be it with a ladspa plugin or a dssi plugin (I tried with hexter). In the first case, the pd window closes instantly, whereas in the second it stays open (but doesn't do anything if I try to launch something from the menu) and the console tells me that pd segfaulted. I have to kill the plugin process(es) to close the pd window.
Could you answer the following questions to help solve the problem.
- Do either of the above result in any output in the PD console? e.g.
'dssi: DSSI/LADSPA host -version 0.96'?
If so which version of dssi~ do you have?
Could you give me the output of the following commands: uname -r pd -version gcc -v
finally it would be very helpful if you could install gdb (if you
don't already have it), and do the following:
gdb pd
(then try to instantiate [dssi~] and cause a crash) then in gdb:
(gdb) bt
And send me the results of the backtrace.
Thanks,
Jamie
Since this only appears to happen with non-English language systems, is it possible to set LANG to English?
d.
Cyrille.Damez@laposte.net wrote:
Hi everybody,
I'm struggling to get the plugin~ external working (to get LADSPA plugins in pd). Whenever I instanciate it in pd, I get an empty box with several inputs and outputs and an error message in the console about "bad screen distance". It also corrupts every single other node I create after that (all of them appear blank and output similar error messages). I quickly searched the archive and have seen that several users have had the same problem, and that for some, unsetting the LANG environment variable fixed the problem, but not for everybody. Unfortunately, I belong to the latter category. Has anybody found since another workaround ?
Btw this happens using pd 0.40.2 under Linux with plugin~ from some pd-extended 0.40 release (I think 0.40.0 but I'm not 100% sure).
Cheers
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Could you describe how you set the variable... i.e. locally in the terminal with "export", or globally in some conf file and "env update", etc etc? Maybe there was an error there...
best, d.
Cyrille.Damez@laposte.net wrote:
Le Lundi 30 Avril 2007 17:15, Derek Holzer a écrit :
Since this only appears to happen with non-English language systems, is it possible to set LANG to English?
I tried with LANG set to fr_FR, en_EN, C and not set at all, none of them worked.
Le Lundi 30 Avril 2007 19:07, Derek Holzer a écrit :
Could you describe how you set the variable... i.e. locally in the terminal with "export", or globally in some conf file and "env update", etc etc? Maybe there was an error there...
Using "setenv LANG <whatever>" since I'm using tcsh instead of bash. I echo'ed the variable to doublecheck that it was correctly set before lauching.
Derek Holzer schreef:
Could you describe how you set the variable... i.e. locally in the terminal with "export", or globally in some conf file and "env update", etc etc? Maybe there was an error there...
best, d.
Cyrille.Damez@laposte.net wrote:
Le Lundi 30 Avril 2007 17:15, Derek Holzer a écrit :
Since this only appears to happen with non-English language systems, is it possible to set LANG to English?
I tried with LANG set to fr_FR, en_EN, C and not set at all, none of them worked.
i just do "unset LANG" in a terminal and then start pd, which works for me.
m
Le Lundi 30 Avril 2007 16:00, Cyrille.Damez@laposte.net a écrit :
I'm struggling to get the plugin~ external working (to get LADSPA plugins in pd). Whenever I instanciate it in pd, I get an empty box with several inputs and outputs and an error message in the console about "bad screen distance". It also corrupts every single other node I create after that (all of them appear blank and output similar error messages). I quickly searched the archive and have seen that several users have had the same problem, and that for some, unsetting the LANG environment variable fixed the problem, but not for everybody. Unfortunately, I belong to the latter category. Has anybody found since another workaround ?
It turned out to be a tcltk problem, not pd one. It affects plugin~ as well as dssi~ (when loading dssi plugins) and probably other externals as well (Jamie saw reports in the archives about similar issues with arrays). I was using TclTk 8.4.9, installing version 8.4.14 fixed it.
Thanks everybody for the help.
-
Cyrille.Damez＠laposte.net -
Derek Holzer -
Jamie Bullock -
Kevin McCoy -
mik