8000 Intervalometer, long exposure, and dark frame at set intervals · Issue #248 · 400plus/400plus · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Intervalometer, long exposure, and dark frame at set intervals #248

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.

Sign up for GitHub

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

Jump to bottom
Open
GoogleCodeExporter opened this issue Mar 14, 2015 · 0 comments
Open

Intervalometer, long exposure, and dark frame at set intervals #248

GoogleCodeExporter opened this issue Mar 14, 2015 · 0 comments
Labels
auto-migrated Priority-Medium Type-Enhancement

Comments

@GoogleCodeExporter
Copy link 
The 400D has a dark frame subtraction long exposure option. In this mode, a 
dark frame is taken after each exposure, the noise from the dark frame is 
examined, and then subtracted from the exposed frame. In long exposure 
astrophotography, taking a dark frame (which is of the same duration as the 
exposure) after each shot can be cumbersome if we are taking multiple images of 
an object at set intervals. For this reason, astrophotographers disable the 
option and manually take a dark frame after a number of exposures (by covering 
the front lens element). The dark frame subtraction is done in post processing.

It would be useful if there was an option to take a dark frame after x number 
of long exposures (of the same duration of one shot), so that the process can 
be done unattended.

However, to accomplish this task, we would need access to the dark frame 
routine (the portion that flips the mirror down during the dark frame 
exposure). Otherwise, we must be able to keep the mirror down during the dark 
frame (after the shutter opens).

Are either of the above options feasible today?

Original issue reported on code.google.com by colinban...@gmail.com on 10 May 2012 at 10:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
auto-migrated Priority-Medium Type-Enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@GoogleCodeExporter
0