> The video frame is tiled by 16x16 macroblocks left to right and then from top to down > row by row with the extra column spilling out of the right side. Yes, that assumption helped me too. Unfortunately I don't know about the spill-over logic, so out of caution, I'm currently using only frame size...

Update: unfortunately, the SAD values of vectors passing through my filter and getting dropped by the filter, are too close to each other. Their ranges overlap and I would be unable to separate them manually, so I can't find an efficient algorithm to do that. I guess the next stop for me is consolid...

P.S. And here's a frame with real motion - first unfiltered and then filtered.

A side note about 50Hz (especially LED, since LEDs respond fast) lamps and featureless single-color surfaces... that's a recipe for confusion. This is likely due to the cyclic nature of ceiling lights. They brighten and dim with AC current in the electrical grid, and the brightening and dimming cycl...

P.S. As for the camera cable length, I have tested it up to 75 cm. Longer ones were not sold, and the 75 cm ones worked in the conditions I had.

If you do put the Pi in the ROV, beware of using WiFi, as water absorbs 2.4 GHz signals especially well. To my knowledge, Raspberry Pi only has 2.4 GHz WiFi (and most likely, 5 GHz would not fare much better - real submarines use VLF (Wikipedia says 3-30 KHz) and there's no hope of homebrewing anyth...

I cannot contribute to the memory-related discussion as I don't know Python, but my 2 cents: my system refused to behave at all when I tried to reduce GPU memory below 128 MB. So I left it at exactly that value. I don't know if Python has anything like garbage collection in Java... for me the greate...

So I realized that I cannot measure the speed improvement gained from the -f option without other onboard sensors - I'd be measuring my own network latency. Unfortunately, other onboard sensors are not ready yet (well, there is a Scanse Sweep here too, and a mirror system for conical scanning is bei...

Thanks for reminding, I will definitely try the -f option for comparison! :) Until now, I have lacked a framework for measuring latency properly, but I just rediscovered the old trick of filming my laptop's screen while it's displaying a running stopwatch. That should help figure out how much effect...

Hello everyone (first post). :D And thanks for writing about your work - it has been helpful to read. :D I first read Gordon's post with the juggling GIF, then later found Hove's blog about drones and finally stumbled here. I've got a somewhat different (yet similar) situation, which I've solved (we...