Working on understanding motion_detect.c and adapting to Digic 6.
Perhaps there's a better thread to post about motion detect Digic 6 than here?
It seems fairly straightforward so far but I find some questionable code ( existing) that might mess up modes other than luminance (Y) mode especially.
I'll probably start a thread...playing with this, I can get well behaved trigger in Y mode (using modified code), BUT..after a random number of triggers (1-8 shots) it stops responding.I checked with modified chdkptp liveview, and it confirms that at this point, the active buffer is changed. Live view uses the same logic to get the view, and it just shows a totally dark screen when motion_detect stops triggering so we are processing the wrong buffer at this point and it seems to stay that way for quite awhile (since the camera isn't doing anything much).
It would appear that cycling to a new viewport buffer doesn't happen on a schedule but rather when necessary.