<HTML><BODY style="word-wrap: break-word; -khtml-nbsp-mode: space; -khtml-line-break: after-white-space; ">I tried running it with a low res 400x300 clip and it still did the same thing. I am trying to get a game going using an FTIR setup. Here is a reference:<DIV><A href="http://cs.nyu.edu/~jhan/ftirsense/">http://cs.nyu.edu/~jhan/ftirsense/</A></DIV><DIV>pix_mutiblob is way to slow, I cant get gridflow compiled, and pidip is not working currently on the extended version. Is there another option to do functional multitracking on a mac with pure data? I really cant fork over the dough for max/msp/jitter, but there is a free jitter plugin called cv.jit that looks great:</DIV><DIV><A href="http://www.iamas.ac.jp/~jovan02/cv/">http://www.iamas.ac.jp/~jovan02/cv/</A></DIV><DIV>Is there a posibility that anyone will port this over to PD I wonder?</DIV><DIV>Alain</DIV><DIV><BR><DIV><DIV>On May 14, 2007, at 12:49 PM, chris clepper wrote:</DIV><BR class="Apple-interchange-newline"><BLOCKQUOTE type="cite">I ran the pix_multiblob example on the same 640x480 clip on CoreDuo, G5 and Xeon CPUs at 2 Ghz and it destroys all of those processors. I guess it was designed to work on really low resolutions since none of the current CPUs can handle full sized standard def video as the code is written. <BR><BR>If the code could be written without the numerous function calls and int to float to int conversions in the processing loop it would be much faster.<BR><BR><DIV><SPAN class="gmail_quote">On 5/14/07, <B class="gmail_sendername"> <A href="mailto:nosehair911@bellsouth.net">nosehair911@bellsouth.net</A></B> <<A href="mailto:nosehair911@bellsouth.net">nosehair911@bellsouth.net</A>> wrote:</SPAN><BLOCKQUOTE class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> I tried to use the Gem from the latest pd extended autobuilds and I have also compiled my own from<BR>CVS with the same results. If you can point me in the right direction on how to get this going I would<BR>apreciate it. BTW I dont know any C or C+ but I am willing to give it a go. <BR>Thanks,<BR>Alain<BR>><BR>> From: "chris clepper" <<A href="mailto:cgclepper@gmail.com">cgclepper@gmail.com</A>><BR>> Date: 2007/05/14 Mon AM 10:56:03 EDT<BR>> To: "<A href="mailto:nosehair911@bellsouth.net"> nosehair911@bellsouth.net</A>" <<A href="mailto:nosehair911@bellsouth.net">nosehair911@bellsouth.net</A>><BR>> CC: <A href="mailto:pd-list@iem.at">pd-list@iem.at</A><BR>> Subject: Re: [PD] pix_multiblob cpu usage <BR>><BR>> pix_multiblob is not the most efficient code but it should run at that low<BR>> resolution. Where did you get the GEM binary? It could be built without<BR>> optimization.<BR>><BR>> On 5/11/07, <A href="mailto:nosehair911@bellsouth.net">nosehair911@bellsouth.net</A> <<A href="mailto:nosehair911@bellsouth.net">nosehair911@bellsouth.net</A>> wrote:<BR>> ><BR>> > I made a 400x300 motion JPEG-a movie 15 fps with 5 solid blue circles <BR>> > moving on a black background<BR>> > to test pix_mutiblob. I open it up with pix_film, flip it with pix_flip<BR>> > and send it to pix_multiblob. I suddenly<BR>> > notices PD getting very, very slow. When I look at the cpu usage in <BR>> > activity monitor (if you can believe<BR>> > activity monitor) I get 100-104% cpu usage. I cant do anything else in PD<BR>> > because PD gets so slow. I<BR>> > am using a dual 2Ghz G5 with ATI Radeon 9800 XT and 3GB of internal <BR>> > memory. Is this normal? What<BR>> > can I do to lower cpu usage? What else can I use within Gem to get the<BR>> > same results? I eventually want<BR>> > to be able to track 20-30 objects but It looks like it would be imposible <BR>> > at this rate.<BR>> > Thanks,<BR>> > Alain<BR>> ><BR>> ><BR>> > _______________________________________________<BR>> > <A href="mailto:PD-list@iem.at">PD-list@iem.at</A> mailing list <BR>> > UNSUBSCRIBE and account-management -><BR>> > <A href="http://lists.puredata.info/listinfo/pd-list">http://lists.puredata.info/listinfo/pd-list</A><BR>> ><BR>><BR>><BR><BR></BLOCKQUOTE></DIV> <BR></BLOCKQUOTE></DIV><BR></DIV></BODY></HTML>