I still have no access to Pi and Pi camera, will be home tomorrow evening.
I just found 320x340@180fps tool for v1 camera:
https://github.com/Hermann-SW/fork-rasp ... ls/320x240
It has vinc 1F, while 640x480 tool has vinc 17 -- therefore that v1 320x240 tool has full FOV.
I just did recursive search in my Raspberry folder to find a 320x240 v2 tool -- there is none yet.
Perhaps I did not build one because v2 camera allows to get 640x480@180fps with raspivid and that looks much better.
I started raspivid high framerate work (in the beginning 90fps was max fps for v1, 120fps was max fps for v2 camera even with raspiraw, now it is 750fps/1007fps) because I intercepted raspiraw for frame analysis and robot control. What I have achieved already with that is automatic camera tilt calibration:
Recently I did reverse engineer Wifi protocol between Eachine E52 drone and android control app:
https://github.com/Hermann-SW/wireless- ... -E52-drone
I was able to tell the drone to send its camera h264 video stream to Raspberry and process there further.
At least for letting the the onboard Pi Zero W flying the drone autonomously I will have to learn how to process single frames from h264 stream:
Back to your v2 camera FOV problem -- couldn't you cover the same FOV with reduced 640x480FOV by moving v2 camera a bit further away from the area you want to record?
> Main goal, capture a fast moving item passing past the camera with as little blur as possible
In addition to high framerate you will want to set shutter time to less than what would be possible for a given framerate to avoid the blur.
I once went down to 200us(!) shutter time for capturing 20140rpm RC airplane propeller for minimizing rolling shutter effect:
https://lb.raspberrypi.org/forums/viewt ... 4#p1319597
This is from 640x75@1007fps v2 camera video, animation plays at 1fps:
This is 640x150_s tool 1007fps recording of same scene