Ah, I presume you have never made a mistake in your own code. Must be great to be perfect. How do you manage to get your head through the door?towolf wrote:This option was highly appreciated. We had a lot of talk months ago about what the maximum milliseconds are that fit into a 32-bit unsigned integer.
Then finally someone came to send a pull request (actually more than one person did) to make -t 0 indefinite operation. Now it's clobbered again.
Wasn't there something about a slow motion train wreck?
OK, have fixed the code and seems to work OK now.SnowLeopard wrote:raspivid --timeout 0 -o test.h264 no longer records indefinitely, but rather creates a 19 byte file and exists immediately.
Code: Select all
raspistill -t 60000 -tl 1000 -w 250 -h 250 -ss 345000 -ISO 800 -o img/test%d.jpg mmal: Skipping frame 3 to restart at frame 4 mmal: Skipping frame 5 to restart at frame 6 mmal: Skipping frame 8 to restart at frame 9 mmal: Skipping frame 10 to restart at frame 11 mmal: Skipping frame 12 to restart at frame 13 mmal: Skipping frame 14 to restart at frame 15 mmal: Skipping frame 16 to restart at frame 17 mmal: Skipping frame 18 to restart at frame 19
I've been getting these skipping frame messages since playing with the shutter speed option. If you check "vcdbg msg log" (or with -f) you'll get matching ca_process_frame_frames: metadata_image NULL messages appearing.poing wrote:In the past I never got the frame skipping IIRC, even with full res and also -tl 1000.
TryKLL wrote:hallo, a beginner question:
also for raspistill i tried the t 0 / run forever / option and -k and -l
and they not work as described in the github manual.
pls. help, what are the steps to get the new version?