Re: [PD] opencv motion tracker external HELP!

2007-05-30 Thread Mike Wozniewski
Yeah, I took the openCV blobtrack code from the examples and modified it just slightly. I didn't document all the changes, because it was never meant to last for more than one project. I simply added the pd netsend stuff, added a few sliders to control parameters, added an automatic background

Re: [PD] opencv motion tracker external HELP!

2007-05-30 Thread martin.peach
Alain wrote: > void window_getframe(t_window *x, t_symbol *sym) > { > char* decode; > char symstr; > x->sym->s_name = decode; > symstr = atol(decode); > frame = symstr; > } Is this the receiving function? I would write it more like: void window_getframe(t_window *x,

Re: [PD] opencv motion tracker external HELP!

2007-05-30 Thread nosehair911
Martin, Thanks for all your help. I have a final question about the sprintf solution. I have managed to get the out going(I think) but I am not quite undestanding the atol()inlet part. I have this. void window_getframe(t_window *x, t_symbol *sym) { char* decode; char symstr;

Re: [PD] opencv motion tracker external HELP!

2007-05-30 Thread Martin Peach
Nose Hair wrote: > I think I figured it out. It looks like I have to use t_symbol *sym > instead of t_symbol sym and the outlet has to be x->outlet_new(x- > >x_outlet0, &*sym). &*sym is the same as sym. > That seemed to work. The weird problem I am > having now it I get an error with the

Re: [PD] opencv motion tracker external HELP!

2007-05-29 Thread Nose Hair
Sorry forgot to ask. Do you have a pd abstraction for this? If not I will see what I can cook up. I think iemmatrix might do the trick. Alain On May 29, 2007, at 8:08 PM, Nose Hair wrote: I see you have the ability to capture from an avi built in already: avi_name = argv[i]; if (avi_name) pCa

Re: [PD] opencv motion tracker external HELP!

2007-05-29 Thread Nose Hair
I see you have the ability to capture from an avi built in already: avi_name = argv[i]; if (avi_name) pCap = cvCaptureFromFile(avi_name); else pCap = cvCaptureFromCAM( 0 ) This is code looks great. I could figure it out from the code but if you have any use instructions let me know. It

Re: [PD] opencv motion tracker external HELP!

2007-05-29 Thread Nose Hair
Thanks Mike, Its awsome how helpful people in this community can be. I will check out you code and modify it if need be, like add the option to use an avi in order to be able to calibrate things and such and I will post it. I will also continue to figure out the external because I think

Re: [PD] opencv motion tracker external HELP!

2007-05-29 Thread Nose Hair
I think I figured it out. It looks like I have to use t_symbol *sym instead of t_symbol sym and the outlet has to be x->outlet_new(x- >x_outlet0, &*sym). That seemed to work. The weird problem I am having now it I get an error with the return(void *)x; I get error: return-statement with a

Re: [PD] opencv motion tracker external HELP!

2007-05-29 Thread martin.peach
Alain wrote: > I am getting a weird error when I try sym = gensym(symstr); I get > no match for 'operator=' in 'sym = gensym(((char*)(& symstr)))' > I dont know what thats all about. I have seen this used before with no > problems. That looks like a c++ error to me, maybe you should be compilin

Re: [PD] opencv motion tracker external HELP!

2007-05-29 Thread Mike Wozniewski
Hi Alain, I've used the OpenCV blobtracker with Pd before, and I simply send blob positions and sizes over UDP using u_pdsend.c I've attached my code and makefile... look in blobtrack.c and search for where I use the pdsend_init() and pdsend_message() functions... it's pretty simple. Then

Re: [PD] opencv motion tracker external HELP!

2007-05-29 Thread nosehair911
)' I dont know what thats all about. I have seen this used before with no problems. Alain > > From: <[EMAIL PROTECTED]> > Date: 2007/05/29 Tue AM 11:51:36 EDT > To: > CC: Tim Boykett <[EMAIL PROTECTED]>, IOhannes m zmoelnig <[EMAIL PROTECTED]>, <[EMA

Re: [PD] opencv motion tracker external HELP!

2007-05-29 Thread martin.peach
> I dont think I quite understood. I tried: > > #define FRAMEOUT frame > > IplImage *frame = 0; > > x->x_outlet = outlet_new(&x->x_obj, &s_anything); > outlet_anything(x->x_outlet, FRAMEOUT); > > with the same results. Maybe someone can dumb it down for me? You can only work with atoms in pd

Re: [PD] opencv motion tracker external HELP!

2007-05-29 Thread nosehair911
TECTED]> > CC: , > [EMAIL PROTECTED] > Subject: Re: [PD] opencv motion tracker external HELP! > > > Hi Alain, > > wouldn't it be a lot easier to take the system that you already have and > use OSC or FIDO to send the values (that you were printing) to PD

Re: [PD] opencv motion tracker external HELP!

2007-05-29 Thread chris clepper
aybe someone can dumb it down for me? > Alain > > > > From: IOhannes m zmoelnig <[EMAIL PROTECTED]> > > Date: 2007/05/29 Tue AM 10:40:29 EDT > > To: [EMAIL PROTECTED] > > CC: Tim Boykett <[EMAIL PROTECTED]>, pd-list@iem.at > > Subject: Re: [PD] open

Re: [PD] opencv motion tracker external HELP!

2007-05-29 Thread nosehair911
t;[EMAIL PROTECTED]>, <[EMAIL PROTECTED]> > Subject: Re: Re: [PD] opencv motion tracker external HELP! > > > I dont think I quite understood. I tried: > > > > #define FRAMEOUT frame > > > > IplImage *frame = 0; > > > > x->x_outlet = outlet_

Re: [PD] opencv motion tracker external HELP!

2007-05-29 Thread Tim Boykett
Hi Alain, wouldn't it be a lot easier to take the system that you already have and use OSC or FIDO to send the values (that you were printing) to PD for further processing? I am greatly in favour of using different systems for different jobs and letting a protocol like OSC or fido (netsend) co

Re: [PD] opencv motion tracker external HELP!

2007-05-29 Thread IOhannes m zmoelnig
[EMAIL PROTECTED] wrote: > I dont think I quite understood. I tried: > > #define FRAMEOUT frame > > IplImage *frame = 0; > > x->x_outlet = outlet_new(&x->x_obj, &s_anything); > outlet_anything(x->x_outlet, FRAMEOUT); > > with the same results. Maybe someone can dumb it down for me? just out

Re: [PD] opencv motion tracker external HELP!

2007-05-29 Thread nosehair911
elnig <[EMAIL PROTECTED]> > Date: 2007/05/29 Tue AM 10:40:29 EDT > To: [EMAIL PROTECTED] > CC: Tim Boykett <[EMAIL PROTECTED]>, pd-list@iem.at > Subject: Re: [PD] opencv motion tracker external HELP! > > [EMAIL PROTECTED] wrote: > > Thanks for helping. Well I

Re: [PD] opencv motion tracker external HELP!

2007-05-29 Thread IOhannes m zmoelnig
[EMAIL PROTECTED] wrote: > Thanks for helping. Well I basically have a rough sketch of all the objects > but I am having a tough > time with the outlet system. In a nutshell opencv uses an image structure > called "typedef struct > _IplImage." Acording to them "The structure IplImage came fr

Re: [PD] opencv motion tracker external HELP!

2007-05-29 Thread nosehair911
Thanks for helping. Well I basically have a rough sketch of all the objects but I am having a tough time with the outlet system. In a nutshell opencv uses an image structure called "typedef struct _IplImage." Acording to them "The structure IplImage came from Intel Image Processing Library

Re: [PD] opencv motion tracker external HELP!

2007-05-27 Thread nosehair911
. BTW the algorithms for pix_multiblob are way, way over my head(seriously)! Alain > > From: "Kyle Klipowicz" <[EMAIL PROTECTED]> > Date: 2007/05/27 Sun PM 10:17:02 EDT > To: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> > CC: pd-list@iem.at, [EMAIL PROTE

Re: [PD] opencv motion tracker external HELP!

2007-05-27 Thread nosehair911
. BTW the algorithms for pix_multiblob are way, way over my head(seriously)! Alain > > From: "Kyle Klipowicz" <[EMAIL PROTECTED]> > Date: 2007/05/27 Sun PM 10:17:02 EDT > To: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> > CC: pd-list@iem.at, [EMAIL PROTE

Re: [PD] opencv motion tracker external HELP!

2007-05-27 Thread Kyle Klipowicz
I haven't looked at this yet, and have no external coding experience. However, I'm wondering if it would be an easier task to port this library to mimic the pix_* objects in Gem? Maybe you could look at the Gem source and figure out how to do this. Or better yet, compare the code you have here wit