New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Investigate "burst mode" for faster stills capture #115

Closed
waveform80 opened this Issue Jun 25, 2014 · 2 comments

Comments

Projects
None yet
1 participant
@waveform80
Owner

waveform80 commented Jun 25, 2014

Investigate the MMAL_PARAMETER_CAMERA_BURST_CAPTURE parameter mentioned by 6x9 in this post. Check out the mentioned caveat as well (that exposure and awb might have to be set?).

Possible implementation: add this to PiMultiImageEncoder._create_encoder so create_sequence gets to take advantage of it automatically (find out what happens if it gets set on the video port - if that's an error have the capture_sequence caller calculate a burst_mode parameter based on the camera port in use).

What about capture_continuous (which always uses PiOneImageEncoder)? Tempting to leave it out for now (as it'll be merged into capture_sequence in 2.0), but that does remove a potential use-case until then...

@waveform80 waveform80 added this to the 1.6 milestone Jun 25, 2014

@waveform80 waveform80 added the task label Jun 25, 2014

@waveform80 waveform80 self-assigned this Jun 25, 2014

@waveform80

This comment has been minimized.

Owner

waveform80 commented Jun 30, 2014

Good news and bad news on this one. The good news: I've tested it and it works. With burst mode in place, I've achieved 4.2fps with consecutive still port image captures - in other words, pretty much exactly what we used to get with picamera before fixing #22 with the hidden preview.

The bad news: some of the issues we got with consecutive still port captures prior to fixing #22 are back with burst mode. Unless an artificial pause is inserted between captures, some (but not all) frames come back completely black. Currently testing whether the fade-to-black issue comes back with burst mode too...

@waveform80

This comment has been minimized.

Owner

waveform80 commented Jul 1, 2014

Yup, looks like the fade-to-black issue is back as well. I'm tempted to implement this still, given that the fade-to-black issue takes a long time to manifest so burst-mode still has utility for performing reasonably short bursts of captures from the still port but obviously we should clearly document that the mode has issues (in particular with the frames that come back almost entirely black).

@waveform80 waveform80 closed this in ea68961 Jul 8, 2014

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment