I filed this into the bug tracker:
http://sourceforge.net/tracker/index.php?func=detail&aid=3202613&gro...
As I mention in the bug tracker, you can get around the problem by adding symbolic links: /usr/lib/bin -> /usr/lib/pd-extended/bin /usr/lib/extra -> /usr/lib/pd-extended/extra /usr/lib/docs -> /usr/lib/pd-extended/docs
Anyway, after all that I seem to get better performance with the old model of running separate Pd instances. I'm not communicating audio between the instances so running separate instances and using sockets to communicate between them continues to be a fine solution for me.
-John
On Mon, Mar 7, 2011 at 8:05 AM, Husk 00 husk00@gmail.com wrote:
On Mon, Mar 7, 2011 at 2:04 PM, John Harrison johnharrisonwsu@gmail.com wrote:
When I send [start( to [pd~] I get "tcl: /usr/lib/bin/pd.tk: can't open script" in the command window.
Hi John, first try pddir flag to set the pd path. It could works. But if it doesn't, as for me, you can try to use pd-vanila (for [pd~]) in conjunction with pd-extended libraries/externals (the extra dir). After a night of pd Chat and testing (different machines, different platforms) was the only way to get it working on linux. Seems to remember pd~ works correctly on MacOS X. I know it's not elegant but it's worked for me. I'm curious to know if someone get it working. husk
since /usr/lib/bin/pd.tk didn't exist I tried ln -s /usr/lib/pd-extended/bin/pd.tk /usr/lib/bin/pd.tk
still no go. I had also been getting other variations of file not found
for
watchdog and pd-gui but symbolic links appeared to fix those: ln -s /usr/lib/pd-extended/bin/pd-watchdog /usr/lib/bin/. ln -s /usr/lib/pd-extended/bin/pd-gui /usr/lib/bin/pd-gui
pd 0.42.5-extended downloaded as a binary from the pd site, running on ubuntu Maverick
workaround?
John
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
-- when Art become pratical we call it technology.
When Technology become useless we call it Art
www.estereotips.net