I am sending this mail again because the list seems to have gotten another (later) mail from me but not this one. Sorry if you get double postings...

Nicola

Nicola Bernardini E-mail: nicb@axnet.it

Re graphics: A picture is worth 10K words -- but only those to describe the picture. Hardly any sets of 10K words can be adequately described with pictures.

---------- Forwarded message ---------- Date: Thu, 5 Feb 1998 10:25:19 +0100 (MET) From: Nicola Bernardini nicb@axnet.it To: pd list pd-list@iem.mhsg.ac.at Subject: problems running pd-0.20 under linux

Hello everybody!

I am running pd on a linux laptop and a linux box both of which run a 2.0.33 kernel. They have different audio setups but I always get a few warnings, like "failed to open audio read port" and "could not open MIDI ports" (even though, at least on the linux box, MIDI is up and running on a SB16). Also, pd must be set suid if running as user because otherwise there are a number of operations (like setting scheduler priorities, etc.) which are not permitted. Anyway, no big problems there (at least for the moment).

One thing that is not clear is the two environment variables TCL_LIBRARY and TK_LIBRARY that are set upon exec'ing pd-gui. Are they for some future purpose? (Actually, I noticed that pd runs also if these variables are not set or are set to incorrect paths, so are they of any use at all?) I made a little trivial patch so that TCL_LIBRARY and TK_LIBRARY can be set externally and applied upon calling pd-gui. I am appending it at the bottom of this mail, if somebody finds it useful, she/he can apply it with patch. Also, on the same idea, some call or some library like, I believe, kpathsea or something like that could be used to infer the path where pd is being run from so to apply it to sys_progdir.

Aside from that, there are a few things I am not able to solve:

1. If, for example, I call up pd, set the audio to ON, THEN open a patch like "cos~.pd" and run the oscillator, no audio happens; if I open the patch THEN turn the audio ON the audio works (this used to happen to 0.18 too)

2. on 0.20 when I edit the patch and audio is ON, after *any* edit operation (like delete a cord, change a patch name, etc.) the program sigsevs and collapses; I cannot run gdb on pd because it says it cannot ptrace (I am using 4.14), but I managed to look into pd-gui and that's not the process doing the segmentation violation: it's pd, but since sigsev does not dump core there is little that I can do there to help...

At any rate, let's go on! Looks like we have a bright future to look up to...

ciao Nicola

Nicola Bernardini E-mail: nicb@axnet.it

Re graphics: A picture is worth 10K words -- but only those to describe the picture. Hardly any sets of 10K words can be adequately described with pictures.