Yes this is what I felt in my hands, lesser shock. This is clearly not EFCS
Then what is the first curtain doing when it says "This type starts exposure electronically", why is it still going up and down? For what purpose?
L-MOUNT Forum
Register a free account now!
If you are registered, you get access to the members only section, can participate in the buy & sell second hand forum and last but not least you can reserve your preferred username before someone else takes it.
S5ii Electronic First Curtain Shutter
- Thread starter Oíche
- Start date
JohnnyMauser
Member
I understand only half, but have experieces with this kind of tests, and if splitscreen would work than two devices next to each other should also work. Or do you need screen recording? If so a 2nd cam with highest speed video could help.
Last edited:
pdk42
Moderator
I set up a test like this:
- I used the Lumix Tether app on my Mac to control the camera (via USB cable). This allows a click on a button to fire the shutter.
- I arranged the screen to have the Mac Clock in stopwatch mode and Lumix Tether showing at the same time.
- I used the Automator App to create a macro script to click the "Reset" and "Start" buttons on the Clock app then the shutter button on the Lumix Tether app.
- I pointed the camera at the screen so that it took a shot of the timer. In other words, the resulting photo shows the total time from reseting the clock to taking the shot.
- The camera was set to 1/200 shutter speed - approx the maximum flash speed so that the shutter did a full open/close cycle.
This is a little video to show it:
The total time recorded includes the mouse movement and clicking actions, but that part of the sequence is fixed, no matter how the camera's shutter is configured. In other words, if there is variation in the delay time to take a shot within the camera, it should be measurable in this test (assuming enough precision and consistency). Here are ten recorded results in full mech, EFCS, and ES modes:
Full mech: 0.54, 0.55, 0.54, 0.55, 0.55, 0.53, 0.54, 0.54, 0.58, 0.54 - average = 0.546, std dev = 0.013
EFCS: 0.55, 0.54, 0.56, 0.55, 0.56, 0.53, 0.54, 0.54, 0.55, 0.56 - average = 0.548, std dev = 0.009
Electronic: 0.56, 0.56, 0.58, 0.54, 0.55, 0.53, 0.54, 0.55, 0.56, 0.55 - average = 0.552, srd dev = 0.013
Unfortunately, I don't think I can conclude much from this since the standard deviation is around 10ms or more. Also, the resolution of the timer is only 10ms. Both those could easily mask any differences at the scale I'm looking for (ca 20ms). I'll try again later with a more precise clock - it looks like there are some available in the App Store.
- I used the Lumix Tether app on my Mac to control the camera (via USB cable). This allows a click on a button to fire the shutter.
- I arranged the screen to have the Mac Clock in stopwatch mode and Lumix Tether showing at the same time.
- I used the Automator App to create a macro script to click the "Reset" and "Start" buttons on the Clock app then the shutter button on the Lumix Tether app.
- I pointed the camera at the screen so that it took a shot of the timer. In other words, the resulting photo shows the total time from reseting the clock to taking the shot.
- The camera was set to 1/200 shutter speed - approx the maximum flash speed so that the shutter did a full open/close cycle.
This is a little video to show it:
The total time recorded includes the mouse movement and clicking actions, but that part of the sequence is fixed, no matter how the camera's shutter is configured. In other words, if there is variation in the delay time to take a shot within the camera, it should be measurable in this test (assuming enough precision and consistency). Here are ten recorded results in full mech, EFCS, and ES modes:
Full mech: 0.54, 0.55, 0.54, 0.55, 0.55, 0.53, 0.54, 0.54, 0.58, 0.54 - average = 0.546, std dev = 0.013
EFCS: 0.55, 0.54, 0.56, 0.55, 0.56, 0.53, 0.54, 0.54, 0.55, 0.56 - average = 0.548, std dev = 0.009
Electronic: 0.56, 0.56, 0.58, 0.54, 0.55, 0.53, 0.54, 0.55, 0.56, 0.55 - average = 0.552, srd dev = 0.013
Unfortunately, I don't think I can conclude much from this since the standard deviation is around 10ms or more. Also, the resolution of the timer is only 10ms. Both those could easily mask any differences at the scale I'm looking for (ca 20ms). I'll try again later with a more precise clock - it looks like there are some available in the App Store.
Last edited: