Paul W. Rogers

Did anyone figure out why can't use MMALISPResizer, getting same error as reported initially... ispresizer has too many output ports using picamera in just mmal style. shame because I think...

Yeah spent some time messing around, YUV is cool, the Y channel is better than taking the green channel of RGB, and the picamera trick described in docs of only...

Setting MMAL_PARAMETER_ENCODING_T to 63 slots works OK tested using dummy buffers and one output captured, against the basic resizer and actually basic resizer is faster. being as how can use...

well, I forked it, and if I'm just using a splitter, ispresizer and two encoders it does work, 10fps solid, producing 2 jpeg files on disk or memory buffer and...

isn't it time ls and rsync did not fail on a simple wildcard like `*small*` LOL no transfer speed problems, but.... fipping ls and rsync fail... no problem with data...

Funny, regarding how good the manual is, I was messing with trying to set "sports" etc. mode and just used the mmal brightness parameter example and at 3 fps at...

in my motion detect prog based on my blitbuffer example in my fork determinate-wise it is the rsync causing some dropouts... running rsync daemon may help I guess indeterminate (as-yet)...

last addition to the rant... perhaps... motion detection is very scene specific... always trade-offs... the blitbuffer seems stable, reckon its when come to write the buffers to file, especially writing...