Hi Enrike, please, for PD-related questions, always write to the list. Some questions appear again and again and others should be able to look them up in the archives.
I am testing on mac a patch that uses xsample and py. This sample was working fine in the computer i was using previously but now it does crash PD. I try to describe the situation to see if you have any idea of the problem.
Creating xplay~ or xgroove~ is ok but then if i move click on the xplay or xgroove or any pd subpatch, crashes pure data after a couple of secs being frozen. Note that clicking or modifying pd objects like
- or atoms doesnt cause the crash.
If I run PD from terminal i get this when crashes Pd : signal 4 closing audio ... closing MIDI ... ... done. pd_gui: pd process exited
however i did some other tests and i found out that: The xsample examples work ok, even if i try to move pd subpatches etc.. Creating an empty canvas and creating there xsample, xgroove or xplay is ok
What is the difference between what you describe in the last sentence and the situation above?
do you have any ideas why this is happening? i talked to Hans and he pointed into the externals. I tested this in different versions of PD, basically in the extended versions with same results. Initially i was using exactly the same version i was using in previous computer, i think it was 0.39.4-extended-RC7, now i am on RC4. Millers ditro does not crash but i get a very strange error, it doesnt load xsample, so i foused on my tests on 0.39.4-extended-RC8
When you say, Miller's distro doesn't load xsample, which error message (with -verbose) do you get? Above all, which xsample version are you running?
best greetings, Thomas
Thomas Grill(e)k dio:
Hi Enrike, please, for PD-related questions, always write to the list. Some questions appear again and again and others should be able to look them up in the archives.
sorry. I thought this might be just something i set up wrong on my system and maybe not very interesting for everybody.
I am testing on mac a patch that uses xsample and py. This sample was working fine in the computer i was using previously but now it does crash PD. I try to describe the situation to see if you have any idea of the problem.
Creating xplay~ or xgroove~ is ok but then if i move click on the xplay or xgroove or any pd subpatch, crashes pure data after a couple of secs being frozen. Note that clicking or modifying pd objects like
- or atoms doesnt cause the crash.
If I run PD from terminal i get this when crashes Pd : signal 4 closing audio ... closing MIDI ... ... done. pd_gui: pd process exited
however i did some other tests and i found out that: The xsample examples work ok, even if i try to move pd subpatches etc.. Creating an empty canvas and creating there xsample, xgroove or xplay is ok
What is the difference between what you describe in the last sentence and the situation above?
. Sorry not to be clear. The difference is that the second is with an empty patch with no other patch open on pd. The first is on my patch or in a new patch while my patch is open. So this is the sequence of events in both tests:
1 test - Open my patch on PD / create xsample / create xgroove~ / click or try to move xgroove~ or some pd subpatch in the same patch : Pd crashes
2 test - open pd / create xsample / create xgroove~ / click and move xgroove or any other object or atom on the same patch: No crash
do you have any ideas why this is happening? i talked to Hans and he pointed into the externals. I tested this in different versions of PD, basically in the extended versions with same results. Initially i was using exactly the same version i was using in previous computer, i think it was 0.39.4-extended-RC7, now i am on RC4. Millers ditro does not crash but i get a very strange error, it doesnt load xsample, so i foused on my tests on 0.39.4-extended-RC8
When you say, Miller's distro doesn't load xsample, which error message (with -verbose) do you get? Above all, which xsample version are you running?
I was using the version that comes with Hans distro 0.39.2-extended-RC8 Now i downloaded the version on your page. I get the same behavior.
The error i get with millers 0.39-2 is that if py is loaded xample wont load and the other way around. I load them by creating py and xsample objects, i mean i am not passing the path on startup.
best greetings, Thomas
many thanks thomas
Hi Enrike,
1 test - Open my patch on PD / create xsample / create xgroove~ / click or try to move xgroove~ or some pd subpatch in the same patch : Pd crashes
2 test - open pd / create xsample / create xgroove~ / click and move xgroove or any other object or atom on the same patch: No crash
i haven't been able to reproduce this yet... would be great to have comments from other users.
The error i get with millers 0.39-2 is that if py is loaded xample wont load and the other way around. I load them by creating py and xsample objects, i mean i am not passing the path on startup.
This sounds very much like http://sourceforge.net/tracker/index.php?func=detail&aid=1378927&gro... which obviously has been fixed by Miller and should propagate into the pd-extended distro soon, if it hasn't yet.
best greetings, Thomas
On Feb 21, 2006, at 7:49 AM, Thomas Grill wrote:
Hi Enrike,
1 test - Open my patch on PD / create xsample / create xgroove~ /
click or try to move xgroove~ or some pd subpatch in the same
patch : Pd crashes2 test - open pd / create xsample / create xgroove~ / click and
move xgroove or any other object or atom on the same patch: No crashi haven't been able to reproduce this yet... would be great to have
comments from other users.
...both of these work fine with me using pd-0.38.4-extended and osx
10.4.5...
james
Thomas Grill(e)k dio:
Hi Enrike,
1 test - Open my patch on PD / create xsample / create xgroove~ / click or try to move xgroove~ or some pd subpatch in the same patch : Pd crashes
2 test - open pd / create xsample / create xgroove~ / click and move xgroove or any other object or atom on the same patch: No crash
i haven't been able to reproduce this yet... would be great to have comments from other users.
I decided to do some step by step tests as this looks pretty weird problem. I guess somebody should have reported something similar at some point.
I downloaded the latest versions of the externals and different versions of PD again, and tested it on my previous laptop that has the same OS, this is 10.3.9 . It runs fine there (powerbook G4, 1.2) but not on the current one (iBook G3, 500mhz)
Then i went and installed the latest externals on my current setup. Using han's pd 0.38.4-extended-RC8 I decided to copying parts of my patch int a new patch to see if there was some problem in some part of the patch.
I found out that the problem was coming from a pd dsp 1 message
So, basically I get the crash by doing this: load PD create xsample object (or load it on startup) start dsp create xgroove click somewhere in the patch click on the xgroove object or other object on the patch release mouse click somewhere else -- here is the crash after couple of secs not responding to mouse clicks Note that in this case after creating the xgroove object, i can still create more objects like + or osc~, messages, numbers. It is only when i click in one of them that the crash happens. Funnyly enough clicking on the + object does not crash pd. So i am really puzzled.
I can also do it the other way around, launch pd, load xgroove then start dsp, here PD crashes. In this case the crash happens straight away.
I am going over it over and over again to see if i can find out what it is different on the previous computer set up and this one, but the only thing i can think of is the hardware and the apple's developer cd.
The error i get with millers 0.39-2 is that if py is loaded xample wont load and the other way around. I load them by creating py and xsample objects, i mean i am not passing the path on startup.
This sounds very much like http://sourceforge.net/tracker/index.php?func=detail&aid=1378927&gro...
which obviously has been fixed by Miller and should propagate into the pd-extended distro soon, if it hasn't yet.
ok, thanks
best greetings, Thomas
Hi Enrike,
I downloaded the latest versions of the externals and different versions of PD again, and tested it on my previous laptop that has the same OS, this is 10.3.9 . It runs fine there (powerbook G4, 1.2) but not on the current one (iBook G3, 500mhz)
Oh well. Please note that y binaries are compiled for Altivec which is not available on the G3. When i got the time i'll try to build a special version and put it on the website.
best greetings, Thomas
hi again
I downloaded the latest versions of the externals and different versions of PD again, and tested it on my previous laptop that has the same OS, this is 10.3.9 . It runs fine there (powerbook G4, 1.2) but not on the current one (iBook G3, 500mhz)
Oh well. Please note that y binaries are compiled for Altivec which is not available on the G3. When i got the time i'll try to build a special version and put it on the website.
mmm... thats really bad news for me. How about compiling it myself on my laptop? do you think it is feasible? please bear in mind that i am not experienced on compiling and less under OSX, and i dont have the developers cd installed I probably need it to get the gcc compiler and libraries required, maybe i would need to install it ... Lot of compiling this days actually :)
best greetings, Thomas
Hi Enrike,
to build externals under OSX you'll need the developer packages. Then you'll have to build flext and xsample using the flext build system. The process is described in flext/build.txt In buildsys/config-mac-pd-gcc.txt be sure to remove -faltivec and change -mcpu=G4 to G3.
greetings, Thomas
On Feb 24, 2006, at 9:43 AM, altern wrote:
hi again
I downloaded the latest versions of the externals and different
versions of PD again, and tested it on my previous laptop that
has the same OS, this is 10.3.9 . It runs fine there (powerbook
G4, 1.2) but not on the current one (iBook G3, 500mhz)Oh well. Please note that y binaries are compiled for Altivec
which is not available on the G3. When i got the time i'll try to
build a special version and put it on the website.mmm... thats really bad news for me. How about compiling it myself
on my laptop? do you think it is feasible? please bear in mind that
i am not experienced on compiling and less under OSX, and i dont
have the developers cd installed I probably need it to get the gcc
compiler and libraries required, maybe i would need to install
it ... Lot of compiling this days actually :)
Well, its not horrible news. Part of the Pd-extended build system
has support for setting CPU targets in one location. Gem and flext-
based stuff isn't part of this yet, but it shouldn't be too hard to
include it. Then we plan to make a range of binary releases, like
generic-PowerPC, G4, G5, MacIntel. Then you'll be in luck again.
.hc
"[W]e have invented the technology to eliminate scarcity, but we are
deliberately throwing it away to benefit those who profit from
scarcity."
-John Gilmore