lets end this whole evf lag now

  • Thread starter Thread starter Donald B
  • Start date Start date
Average them out...that sounds like 20ms or so - about the same as my test where I had to reduce focal length by a factor of three (600mm to 200mm) because of 25ms of lag, measured exactly this way.
Your one-off "test" using the LCD on your DSLR that you were unable to use effectively?
No, that was a separate test, and I was using the LCD as an eye-level EVF. And, yes, I was unable to use it effectively because of EVF lag, as I clearly demonstrated.
 
Average them out...that sounds like 20ms or so - about the same as my test where I had to reduce focal length by a factor of three (600mm to 200mm) because of 25ms of lag, measured exactly this way.
show us the math on an excell spread sheet for all us to see and ad some of our own numbers in :-)
Okay, shoot video this time, use a millisecond timer, and give me the video and I'll process it.
shot this afternoon a 2sec sequence of a car traveling at 80klm per hour with a 120mm lens (ff eq) car was 40 meters away shot 20 images with the car filling half the frame and perfectly in the center, how many rpm was i panning at ? and how fast would the car have to be traveling to exit the vf ? and what would be the rpm of my body panning :-)
And how am I going to make a spreadsheet from that useless information?
your kidding arnt you ;-) i can write a celestial navigation program on excel with no references needed , this is a simple task i have asked.
Do you have dementia or something?

The question is "how much lag does your EVF have", and I tried to estimate that from the lousy pictures you provided. You asked for the math so I asked for you to shoot a video of a millisecond timer so I could calculate it. Now you're talking about a car. What the heck are you talking about?
read the next post

Don
 
Average them out...that sounds like 20ms or so - about the same as my test where I had to reduce focal length by a factor of three (600mm to 200mm) because of 25ms of lag, measured exactly this way.
show us the math on an excell spread sheet for all us to see and ad some of our own numbers in :-)
Okay, shoot video this time, use a millisecond timer, and give me the video and I'll process it.
shot this afternoon a 2sec sequence of a car traveling at 80klm per hour with a 120mm lens (ff eq) car was 40 meters away shot 20 images with the car filling half the frame and perfectly in the center, how many rpm was i panning at ? and how fast would the car have to be traveling to exit the vf ? and what would be the rpm of my body panning :-)
And how am I going to make a spreadsheet from that useless information?
your kidding arnt you ;-) i can write a celestial navigation program on excel with no references needed , this is a simple task i have asked.
Do you have dementia or something?

The question is "how much lag does your EVF have", and I tried to estimate that from the lousy pictures you provided. You asked for the math so I asked for you to shoot a video of a millisecond timer so I could calculate it. Now you're talking about a car. What the heck are you talking about?
read the next post
Its on another topic, and you're still mixing in human reaction time, which is irrelevant. According to that, this video I took couldn't have been taken. That plane was 40 feet from me at closest approach going about 200mph.

Oh...I got plenty of good stills of that same plane going the same speed, pretty tightly framed, using an OVF:



Lightning%20shots.jpg




--
Lee Jay
 
A nice example of how not to do an EVF timing test.

Things to fix:

1) Need to have a high resolution clock. This one clearly isn't with both .x2 and .x7 being displayed in some frames.

2) Camera display and main screen have to be at the same vertical position in the recording sensor, otherwise there is an unknown delay between the two in the readout rate of the recording sensor. At least mention whether the recording camera was in electronic or mechanical shutter.
none of that matters.
It all matters. You should learn to listen.
 
Very close, but this isn't quite the right way. The best thing would be to take a high speed camera that is capable of around 240fps. This will give you a measurement to the nearest ~4ms, which should be sufficient.

Then point your camera at a screen where something is changing, just as you did, and take a video. Then look at the video frame by frame and measure how long it took for a change in the source to be reflected as a change in the target.

I can tell you right now that this is almost certainly not going to be faster than about four frames (16ms). That's one frame at 60fps. I doubt it will be slower than 50ms. Either way, it's not enough to materially effect panning except for objects that are extremely close to the camera moving extremely fast. (100 km/h * 50ms = ~1 meter).
 
The problem is Lea is your shots are composition aly not good as they should be flying into the frame not out of it. So the small delay would have enhanced your images

Don
 
High res clock would be pointless in this context because the screen will only display updates once per 16ms. (Unless it's a 144hz screen or something.)
 
Very close, but this isn't quite the right way. The best thing would be to take a high speed camera that is capable of around 240fps. This will give you a measurement to the nearest ~4ms, which should be sufficient.

Then point your camera at a screen where something is changing, just as you did, and take a video. Then look at the video frame by frame and measure how long it took for a change in the source to be reflected as a change in the target.

I can tell you right now that this is almost certainly not going to be faster than about four frames (16ms). That's one frame at 60fps. I doubt it will be slower than 50ms. Either way, it's not enough to materially effect panning except for objects that are extremely close to the camera moving extremely fast. (100 km/h * 50ms = ~1 meter).
thank you very much for the reply, i knew someone with math skill would chim in soon.

Don
 
High res clock would be pointless in this context because the screen will only display updates once per 16ms. (Unless it's a 144hz screen or something.)
thanks for the technical answer, now we are getting somewere.

Don
 
You're not going to get an EVF lag by measuring lag of the back screen.

I have no proof for the statement that follows, but I'd bet my E-M1 II that the lag on the back screen is a lot higher than that of EVF.

Heck, the input lag on that back screen LCD panel by itself is probably higher than the lag of the whole data pipeline for the EVF (ie. from sensor readout to all the way to the displayed image).

I also don't know how you could reliably measure this stuff by yourself without some elaborate setup. Even just taking a photo like you did here means you need to account for a rolling shutter effect (and yes, even with mechanical one).
 
I also don't know how you could reliably measure this stuff by yourself without some elaborate setup. Even just taking a photo like you did here means you need to account for a rolling shutter effect (and yes, even with mechanical one).
Actually, maybe it would not be as complex as I initially thought. Super slo-mo modes on moderns smartphones should make the problem of rolling shutter minimal (and it could be eliminated completely by setting up the scene in a specific way). And you could take a video of an RGB LED alternating through different states. It would be quite simple to create a setup where you could capture both the EVF and the LED itself. And you could control the frequency of LED changes to get the best possible measurement.

Something like that.
 
A nice example of how not to do an EVF timing test.

Things to fix:

1) Need to have a high resolution clock. This one clearly isn't with both .x2 and .x7 being displayed in some frames.

2) Camera display and main screen have to be at the same vertical position in the recording sensor, otherwise there is an unknown delay between the two in the readout rate of the recording sensor. At least mention whether the recording camera was in electronic or mechanical shutter.
none of that matters. a photo is a photo is a photo.

Don
If you are doing timing tests, then the fact that the bottom of a photo is taken a variable amount of time after the top of the photo absolutely matters (depending on camera and settings).
 
You're not going to get an EVF lag by measuring lag of the back screen.

I have no proof for the statement that follows, but I'd bet my E-M1 II that the lag on the back screen is a lot higher than that of EVF.

Heck, the input lag on that back screen LCD panel by itself is probably higher than the lag of the whole data pipeline for the EVF (ie. from sensor readout to all the way to the displayed image).

I also don't know how you could reliably measure this stuff by yourself without some elaborate setup. Even just taking a photo like you did here means you need to account for a rolling shutter effect (and yes, even with mechanical one).
 
He has argued this across multiple threads about EVFs, complaining about how dreadful EVF lag is, without disclosing until caught out that he was actually talking about the LCD screen on his 7D.
Seriously??!! This whole storm in a teacup is based on the fact that he is not familiar with the generally accepted photographic colloquial distinction between an EVF and an LCD? Could you point me at a post where this is made public please?

Over and above anything else: attempting to track anything while holding a camera at arm's length to see the rear screen is a complete and utter waste of time. This is a far, far greater issue than simple display lag.

Holy cow, talk about absurd....
 
He has argued this across multiple threads about EVFs, complaining about how dreadful EVF lag is, without disclosing until caught out that he was actually talking about the LCD screen on his 7D.
Seriously??!! This whole storm in a teacup is based on the fact that he is not familiar with the generally accepted photographic colloquial distinction between an EVF and an LCD? Could you point me at a post where this is made public please?

Over and above anything else: attempting to track anything while holding a camera at arm's length to see the rear screen is a complete and utter waste of time. This is a far, far greater issue than simple display lag.

Holy cow, talk about absurd....
Since when should all those happy with EVFs need to convince DSLR shooters to move? I am happy if they stay with the DSLRs and they have every right to prefer it.
 
He has argued this across multiple threads about EVFs, complaining about how dreadful EVF lag is, without disclosing until caught out that he was actually talking about the LCD screen on his 7D.
Seriously??!!
Sad but true.
whole storm in a teacup is based on the fact that he is not familiar with the generally accepted photographic colloquial distinction between an EVF and an LCD? Could you point me at a post where this is made public please?
Here you are.

Over and above anything else: attempting to track anything while holding a camera at arm's length to see the rear screen is a complete and utter waste of time. This is a far, far greater issue than simple display lag.

Holy cow, talk about absurd....

--
Cheers
Alwyn
 
It could be an order of magnitude longer than the EVF I bet
 
It could be an order of magnitude longer than the EVF I bet
It is included in the shutter lag measurements in the performance tests results posed in the DSLR camera reviews in the Imaging Resources web site.
 
Last edited:
Also, if you don't like 25ms˜50ms lag, get a DSLR. Maybe mirroless are not for you. Nothing can beat the speed of light, literally.

Literally the best post. Mirrorless EVF will ALWAYS have a lag, because of the laws of physics. We may decrease that lag to extremely small amounts in the years to come but it will never ever be zero. Just want to clarify that.
 
Also, if you don't like 25ms˜50ms lag, get a DSLR. Maybe mirroless are not for you. Nothing can beat the speed of light, literally.
Literally the best post. Mirrorless EVF will ALWAYS have a lag, because of the laws of physics. We may decrease that lag to extremely small amounts in the years to come but it will never ever be zero. Just want to clarify that.
Neither will an OVF lag ever be zero, literally. :-D

They both may become inconsequential in the future, however.
 

Keyboard shortcuts

Back
Top