3 ms·
There are two impacts. In front of the glass is a light mesh that is used to keep water from kicked up is from showing as droplets on the screen. That mesh is c
by drakaal 13y ago
There are two impacts. In front of the glass is a light mesh that is used to keep water from kicked up is from showing as droplets on the screen. That mesh is coated in a hydrophobic material and works well keeping a camera from needing to have the lens wiped.
The Green Line is when the camera took that part of the impact. Likely the Sensor shook enough to cause an error.
It recovered in the frame before the puck hit the lens so there is a clear frame before that.
The comments about IPB frames and compression might seem logical at first, but B frames are very rarely used in live broadcast because they add so much to the delay, and cause a lot of issues when broadcast over lossy formats.
If this was a broadcast from tape, the impact could have damaged the tape when the tenisioner was jostled by the impact, but typically that would do more than the small ammount of frame loss shown here, and wouldn't have been part of a live broadcast.
- ricardobeat 13y agoIn the frame where the glitch happens the puck still looks quite far from the lens. If the mesh was positioned that far it would probably be visible and mess up autofocus. B frames or buffering would only add <100ms latency, while live transmission already has at least 1s lag, before even considering 'tape delay'. I'm betting on processing delay as the explanation.
- drakaal 13y agoThe mesh is about 3 feet out. B Frames to be of any use require 6 frames at 33ms each, that is 200ms, a quarter of a second, but on play back you need all of the frames in the set from i frame to i frame to get make the reference frames work, this is typically 1-3 seconds. -Brandon Wirtz SMPTE Voting Committee Member for the ratification of H.264 and VC-1 standards.
- drakaal 13y agoA screen in a window only messes up auto focus when the size of the screen is greater than the size of a single pixel.