make camera_trigger_canon_eos_capture "synchronous" #1027
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This is a draft of a change along the lines of the discussion in gphoto#968 (comment) meant to be able to discuss something like that further. After realizing that there is no event sent from the camera to reliably detect the moment the camera is ready again, I went back to the approach that I successfully used for the last 10 years in production. This allows me to execute the following command on my R8 to capture a total of 4 images in under 2s. gphoto2 --set-config capturetarget=1 --set-config aeb="+/- 3" --set-config-index drivemode=1 --set-config shutterspeed=1/500 --set-config ownername=400 --trigger-capture --set-config aeb=off --set-config-index drivemode=0 --set-config ownername=1 --trigger-capture The use of "ownername" is obviously not meant to stay, it was just a quick hack to enable me to pass an sleep_ms parameter into camera_trigger_capture from the command line.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a draft of a change along the lines of the discussion in #968 (comment) meant to support further discussion of the subject.
After realizing that there is no event sent from the camera to reliably detect the moment the camera is ready again, I went back to the approach that I successfully used for the last 10 years in production.
This allows me to execute the following command on my R8 to capture a total of 4 images in under 2s.
The use of "ownername" is obviously not meant to stay, it was just a quick hack to enable me to pass the
int full_press_wait(in ms) parameter intocamera_trigger_capturefrom the command line.