[PD] pix_motion_sector

[Max]

how come it is irrelevant?

btw i included your shader to the patches
http://web.uni-weimar.de/medien/wiki/Bewegungsmelder

m.

Am 14.05.2010 um 19:27 schrieb Jack:
> Sorry, [pix_info] is irrelevant in your case.
> ++
> 
> Jack
> 
> 
> 
> Le vendredi 14 mai 2010 à 19:05 +0200, Jack a écrit :
>> The seventh outlet of [pix_info] return [1 0( when the pix change
>> (instead of [0 0().
>> ++
>> 
>> Jack
>> 
>> 
>> Le vendredi 14 mai 2010 à 18:40 +0200, IOhannes m zmoelnig a écrit :
>>> On 2010-05-14 18:27, William Brent wrote:
>>>> I'll update the helpfile for [pix_motion_sector] to include a subpatch
>>>> that does the same thing with [pix_crop], [pix_movement], and
>>>> [pix_dump].  I think I might also change the source and try taking the
>>>> distance between current/previous frames using all RGB info instead of
>>>> a greyscale approximation.  The speed issue aside, that may be a
>>>> significant difference from [pix_movement] worth investigating.
>>>> 
>>> 
>>> btw, instead of [pix_dump] (which will kill performance), why not use
>>> [pix_mean_color]?
>>> 
>>> fgmasdr
>>> IOhannes