I'd like to help, but I am not going to have time. I'll be on tour
starting Sat. for two months. Any flext people want to try to get
flext builds in Pd-extended?
There could also be a Pd-devel-extended without too much work. Jamie
had talked about it in the past.
.hc
On Apr 11, 2006, at 5:24 AM, Thomas Grill wrote:
Am 11.04.2006 um 00:52 schrieb Hans-Christoph Steiner:
All are fresh downloads of the binaries from your site. This
happens with Pd-0.38.4-extended, Pd-0.39.2-extended-test1, and the
new build with fresh downloads.The binaries are not up to date and i'm sure that the relevant
fixes have been afterwards. Please try the cvs versions. Building
the stuff is a cinch.Have you tried with Pd-extented and that org.puredata.pd.plist
file? I have reproduced this on 3 or 4 Mac OS X machines by
installing Pd-extended, installing the included
org.puredata.pd.list, starting Pd and loading a [py] or [pool]
object.Yes, I tried and i will do once again when i find the time. Please
note that I don't use the Pd-extended build (because i'm rather
using Pd-devel) so i can't follow the problems associated with that.Mac OS X doesn't catch the crash, so it doesn't pop up the crash
dump. Any other way to get it?What about the proposals Jamie made?
greetings, Thomas
Thomas Grill http://grrrr.org
¡El pueblo unido jamás será vencido!
Hans-Christoph Steiner schrieb:
I'd like to help, but I am not going to have time. I'll be on tour starting Sat. for two months. Any flext people want to try to get flext builds in Pd-extended?
Hi Christoph, you could also try to use the binaries in http://grrrr.org/ext/beta/pd/osx . The disadvantage is that those are bloated static builds but they should work at least. greetings, Thomas
hi all, i just noticed that the detach method of pyext can cause pd to crash. i had a patch with gem, pdp and pdp2gem and as soon as i tried to display video from pdp into gem display, pd crashed. spent quite a hard time (not too long though) to find out why this happened. the solution is the following : comment out the self._detach(1) in pyext files. best, vincent
Hi Vincent, thanks for the report, although commenting out self._detach(1) is no solution. I could try to find the reason, if you can provide a simple crashing patch with as few external objects as possible.
greetings, Thomas
vincent rioux schrieb:
hi all, i just noticed that the detach method of pyext can cause pd to crash. i had a patch with gem, pdp and pdp2gem and as soon as i tried to display video from pdp into gem display, pd crashed. spent quite a hard time (not too long though) to find out why this happened. the solution is the following : comment out the self._detach(1) in pyext files. best, vincent
hi Thomas,
sorry i should definetely have said "quick and dirty solution".
i send you two files - you need the externals : py, Gem, pdp and pdp2gem.
when detach is commented out in detach_crash.py, pd crashes on my linux box (pd 39.2, pyext, Gem and pdp compiled from cvs, ubuntu 5.10).
thanks for your fast reply! best, vincent
Thomas Grill a écrit :
Hi Vincent, thanks for the report, although commenting out self._detach(1) is no solution. I could try to find the reason, if you can provide a simple crashing patch with as few external objects as possible.
greetings, Thomas
vincent rioux schrieb:
hi all, i just noticed that the detach method of pyext can cause pd to crash. i had a patch with gem, pdp and pdp2gem and as soon as i tried to display video from pdp into gem display, pd crashed. spent quite a hard time (not too long though) to find out why this happened. the solution is the following : comment out the self._detach(1) in pyext files. best, vincent
#N canvas 393 166 575 346 10; #X obj 15 56 pyx detach_crash creation; #X obj 16 110 gemwin; #X obj 16 86 r gemwin; #X msg 15 26 reload; #X msg 185 23 on; #X obj 390 109 pdp_v4l; #X msg 442 18 stop; #X msg 390 18 bang; #X obj 390 57 metro 40; #X obj 292 139 pdp2gem; #X obj 290 165 pix_rgba; #X obj 290 199 pix_texture; #X obj 289 228 rectangle 4 3; #X obj 265 100 gemhead; #X connect 2 0 1 0; #X connect 3 0 0 0; #X connect 4 0 0 1; #X connect 5 0 9 0; #X connect 6 0 8 0; #X connect 7 0 8 0; #X connect 8 0 5 0; #X connect 9 0 10 0; #X connect 10 0 11 0; #X connect 11 0 12 0; #X connect 13 0 9 0;
import pyext import glob, os import random import time
class creation(pyext._class): _inlets=1 _outlets=0
def __init__(self):
#self._detach(1)
pass
def on_1(self):
self._send('gemwin', 'border', (1,))
self._send('gemwin', 'offset', (0, 0))
self._send('gemwin', 'create', ())
self._send('gemwin', (1,))
Hi Vincent, sorry, i won't be able to debug a setup involving pdp, since i don't use it and i don't have the time to set up all the stuff on linux. You could send me a gdb backtrace, although that's probably not very meaningful or try to provoke a crash without using pdp.
greetings, Thomas
vincent rioux schrieb:
hi Thomas,
sorry i should definetely have said "quick and dirty solution".
i send you two files - you need the externals : py, Gem, pdp and pdp2gem.
- open detach_crash.pd
- press 'bang' for pdp acquisition start
- press 'on' for gem window creation
when detach is commented out in detach_crash.py, pd crashes on my linux box (pd 39.2, pyext, Gem and pdp compiled from cvs, ubuntu 5.10).
thanks for your fast reply! best, vincent
Thomas Grill a écrit :
Hi Vincent, thanks for the report, although commenting out self._detach(1) is no solution. I could try to find the reason, if you can provide a simple crashing patch with as few external objects as possible.
greetings, Thomas
vincent rioux schrieb:
hi all, i just noticed that the detach method of pyext can cause pd to crash. i had a patch with gem, pdp and pdp2gem and as soon as i tried to display video from pdp into gem display, pd crashed. spent quite a hard time (not too long though) to find out why this happened. the solution is the following : comment out the self._detach(1) in pyext files. best, vincent
#N canvas 393 166 575 346 10; #X obj 15 56 pyx detach_crash creation; #X obj 16 110 gemwin; #X obj 16 86 r gemwin; #X msg 15 26 reload; #X msg 185 23 on; #X obj 390 109 pdp_v4l; #X msg 442 18 stop; #X msg 390 18 bang; #X obj 390 57 metro 40; #X obj 292 139 pdp2gem; #X obj 290 165 pix_rgba; #X obj 290 199 pix_texture; #X obj 289 228 rectangle 4 3; #X obj 265 100 gemhead; #X connect 2 0 1 0; #X connect 3 0 0 0; #X connect 4 0 0 1; #X connect 5 0 9 0; #X connect 6 0 8 0; #X connect 7 0 8 0; #X connect 8 0 5 0; #X connect 9 0 10 0; #X connect 10 0 11 0; #X connect 11 0 12 0; #X connect 13 0 9 0;
import pyext import glob, os import random import time
class creation(pyext._class): _inlets=1 _outlets=0
def __init__(self): #self._detach(1) pass def on_1(self): self._send('gemwin', 'border', (1,)) self._send('gemwin', 'offset', (0, 0)) self._send('gemwin', 'create', ()) self._send('gemwin', (1,))
ola,
mm, looks like it has to do with the threads, and dod you use pdp in threaded mode ( change the option with pdp_control ) ? does it make any difference?
saludos, sevy
vincent rioux wrote:
hi Thomas,
sorry i should definetely have said "quick and dirty solution".
i send you two files - you need the externals : py, Gem, pdp and pdp2gem.
- open detach_crash.pd
- press 'bang' for pdp acquisition start
- press 'on' for gem window creation
when detach is commented out in detach_crash.py, pd crashes on my linux box (pd 39.2, pyext, Gem and pdp compiled from cvs, ubuntu 5.10).
thanks for your fast reply! best, vincent
Thomas Grill a écrit :
Hi Vincent, thanks for the report, although commenting out self._detach(1) is no solution. I could try to find the reason, if you can provide a simple crashing patch with as few external objects as possible.
greetings, Thomas
vincent rioux schrieb:
hi all, i just noticed that the detach method of pyext can cause pd to crash. i had a patch with gem, pdp and pdp2gem and as soon as i tried to display video from pdp into gem display, pd crashed. spent quite a hard time (not too long though) to find out why this happened. the solution is the following : comment out the self._detach(1) in pyext files. best, vincent
#N canvas 393 166 575 346 10; #X obj 15 56 pyx detach_crash creation; #X obj 16 110 gemwin; #X obj 16 86 r gemwin; #X msg 15 26 reload; #X msg 185 23 on; #X obj 390 109 pdp_v4l; #X msg 442 18 stop; #X msg 390 18 bang; #X obj 390 57 metro 40; #X obj 292 139 pdp2gem; #X obj 290 165 pix_rgba; #X obj 290 199 pix_texture; #X obj 289 228 rectangle 4 3; #X obj 265 100 gemhead; #X connect 2 0 1 0; #X connect 3 0 0 0; #X connect 4 0 0 1; #X connect 5 0 9 0; #X connect 6 0 8 0; #X connect 7 0 8 0; #X connect 8 0 5 0; #X connect 9 0 10 0; #X connect 10 0 11 0; #X connect 11 0 12 0; #X connect 13 0 9 0;
import pyext import glob, os import random import time
class creation(pyext._class): _inlets=1 _outlets=0
def __init__(self): #self._detach(1) pass
def on_1(self): self._send('gemwin', 'border', (1,)) self._send('gemwin', 'offset', (0, 0)) self._send('gemwin', 'create', ()) self._send('gemwin', (1,))
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Thomas Grill a écrit :
Hi Vincent, sorry, i won't be able to debug a setup involving pdp, since i don't use it and i don't have the time to set up all the stuff on linux. You could send me a gdb backtrace, although that's probably not very meaningful or try to provoke a crash without using pdp.
i understand that. but i found pdp quite useful so i'll try not to use the detach method for the python script i use to control the gem window - do you think that not using a thread (that's what detach is meant for isn't it? might make things unstable?
best regards, vincent
vincent rioux schrieb:
Thomas Grill a écrit :
Hi Vincent, sorry, i won't be able to debug a setup involving pdp, since i don't use it and i don't have the time to set up all the stuff on linux. You could send me a gdb backtrace, although that's probably not very meaningful or try to provoke a crash without using pdp.
i understand that. but i found pdp quite useful so i'll try not to use the detach method for the python script i use to control the gem window - do you think that not using a thread (that's what detach is meant for isn't it? might make things unstable?
It depends on what you are trying to do, but this solution will surely not help to fix any bug.
greetings, Thomas
Yves Degoyon a écrit :
ola,
mm, looks like it has to do with the threads, and dod you use pdp in threaded mode ( change the option with pdp_control ) ? does it make any difference?
ola, it does not make a difference.
thanks thomas and yves for your help.
this is not a big problem anyway - just for initialization purposes and which can be avoided. so...
greetings, vincent
saludos, sevy
dear list, i know this has already been adressed but i still wonder how can one build a receiver with two or more initialization arguments.
nb | [s 0-1-test]
and in abstraction [pd test 0 1] [r $1-$2-test] does not work.
i solved this pb with a simple and uncomplete pyext script (r.py, attached): to be used like that:
nb | [s 0-1-test]
and in abstraction [pd test 0 1] [pyx r r $1 $2 test]
but i wish i could get a genuine pd solution. vincent
import pyext class r(pyext._class): _inlets=0 _outlets=1
def __init__(self, *args):
r = ''
for arg in args:
r += str(arg)+'-'
self._bind(r[0:-1], self.recv)
def recv(self, *args):
if len(args)==2:
self._outlet(1, str(args[0]), (str(args[1]),))
elif len(args)==1:
self._outlet(1, args)
else:
self._outlet(1, args)
something like that should work
[nb] | [2 $1( | [s 1-test]
and in the abstraciton [test 1 2]
[r $1-test] | [route $2]
and in abstraction [pd test 0 1] [r $1-$2-test] does not work.
note that does _not_ work in a subpatch like [pd test 0 1]
regards
eni
On Apr 13, 2006, at 11:49 AM, vincent rioux wrote:
dear list, i know this has already been adressed but i still wonder how can one build a receiver with two or more initialization arguments.
nb | [s 0-1-test]
and in abstraction [pd test 0 1] [r $1-$2-test] does not work.
i solved this pb with a simple and uncomplete pyext script (r.py, attached): to be used like that:
nb | [s 0-1-test]
and in abstraction [pd test 0 1] [pyx r r $1 $2 test]
but i wish i could get a genuine pd solution. vincent
import pyext class r(pyext._class): _inlets=0 _outlets=1
def __init__(self, *args): r = '' for arg in args: r += str(arg)+'-' self._bind(r[0:-1], self.recv) def recv(self, *args): if len(args)==2: self._outlet(1, str(args[0]), (str(args[1]),)) elif len(args)==1: self._outlet(1, args) else: self._outlet(1, args)
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
with a abstracion in an abstraction you could make a [r 1-2-test] but it's a rather ugly solution.
main patch:
[nb
|
[s 1-2-test]
[firstabstraction 1]
firstabstraction:
[secondabstraction $1-2]
secondabstraction:
[r $1-test]
On Apr 13, 2006, at 11:49 AM, vincent rioux wrote:
dear list, i know this has already been adressed but i still wonder how can one build a receiver with two or more initialization arguments.
nb | [s 0-1-test]
and in abstraction [pd test 0 1] [r $1-$2-test] does not work.
i solved this pb with a simple and uncomplete pyext script (r.py, attached): to be used like that:
nb | [s 0-1-test]
and in abstraction [pd test 0 1] [pyx r r $1 $2 test]
but i wish i could get a genuine pd solution. vincent
import pyext class r(pyext._class): _inlets=0 _outlets=1
def __init__(self, *args): r = '' for arg in args: r += str(arg)+'-' self._bind(r[0:-1], self.recv) def recv(self, *args): if len(args)==2: self._outlet(1, str(args[0]), (str(args[1]),)) elif len(args)==1: self._outlet(1, args) else: self._outlet(1, args)
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
sorry to send this again but i am still stuck with this pb any news around this?
best, v
vincent rioux a écrit :
dear list, i know this has already been adressed but i still wonder how can one build a receiver with two or more initialization arguments.
nb | [s 0-1-test]
and in abstraction [pd test 0 1] [r $1-$2-test] does not work.
IOhannes m zmoelnig a écrit :
Vincent Rioux wrote:
sorry to send this again but i am still stuck with this pb any news around this?
no news, just olds: upgrade to pd>=0.40
oups! cool, thanks a lot - i did not even tried it again - should probably be more optimistic ;-) v
fgmasrd IOhannes
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list