Hello,
maybe another way to do it is to use [pix_crop] object in GEM as in this
example (motion checked by a color approach, it can also be done with
[pix_movement])
http://yamatierea.org/papatchs/#detc-mvt
or pidip object [pdp_mgrid] (see example in pdextended)
of course, opencv objects are also really efficient for some kinds of
motion detection
best++
Benjamin
James Harkins a écrit :
At Sun, 11 Sep 2011 13:05:31 -0300,
palmieri, ricardo wrote:
and this?
http://www.hangar.org/wikis/lab/doku.php?id=start:puredata_opencv
Oh, interesting. Thanks (and thanks to Marko for the other suggestions).
I got another idea this morning -- instead of slicing the frame and running a
bunch of motion detectors, run one motion_detection object on the whole frame
and slice that result. The problem was that motion detection is stateful
(depends on previous frames) so I would have to have a separate object for each
slice, but the [#moment] calculation is not. That should simplify the patch a
lot.
James
--
James Harkins /// dewdrop world
[email protected]
http://www.dewdrop-world.net
"Come said the Muse,
Sing me a song no poet has yet chanted,
Sing me the universal." -- Whitman
blog: http://www.dewdrop-world.net/words
audio clips: http://www.dewdrop-world.net/audio
more audio: http://soundcloud.com/dewdrop_world/tracks
---
[email protected]
http://identi.ca/group/puredyne
irc://irc.goto10.org/puredyne
---
[email protected]
http://identi.ca/group/puredyne
irc://irc.goto10.org/puredyne
