Originally posted by Man_Called_Horse:
Originally posted by Mousie:
Originally posted by Man_Called_Horse:
I don't use the video function of my camera, however, why specialize with just still imagery when video is widely used from many people with their gear.
Open up your market share and include Frames Per Second to calculate proper exposure.
Just a thought. |
This sounds interesting! Do you have a pointer where I could look at how to calculate to compensate for frames per second? Is there some standard math people use? I haven't seen this before, but heck, if I could make it work for video too that would be great! |
just like still photography, moving images have their own dynamic trade offs. Everything is on the 'depends' status.
24 fpm, ISO 100, 50 mm lens with no filter the lighting can be a 4.8f to as much as a 5.6f. ANY of the parameters that change, changes your math. The more fpm increases you lighting needs, and visa versa when slowing your fpm.
The math changes with the type of lens, the sensitivity of the sensor, if your using filters, blah, blah.
Sounds like you have a handle on the still side, take the time to do some experiments...it's easy enough. |
None of the calculations in Expositor 'depend' on the situation/lens/camera. The three variable parameters, ISO, F-Stop, and speed effect each other predictably... doubling the ISO corresponds to doubling the aperture or halving the shutter speed. it's that simple. No experimentation is needed! Perhaps you mean something different when you say the math changes... like the inputs change? :)
My assumption is that shutter speed vs. ISO vs. aperture works exactly the same for motion pictures as it does still... perhaps with a conversion factor for motion-specific gear... and if that's the case my app can ALREADY do the calculations for you... just look for a shutter speed of 1/24 (or 1/30) for the scene/ISO/aperture you're shooting. Done? :)
|
