What causes the green line in the frame before the puck hits the camera?
gifexploder.com
gifexploder.com
In most MPEG-family video codecs video is split between brightness (luma) and color channels (chroma). This looks like error in one of chroma channels.
Image is divided into blocks and average intensity of each block (called DC) is stored as difference from a previous block.
It looks like the first block on that line had invalid, out-of-range DC value stored, and this value has been propagated through entire line.
Still More likely the jostle caused data loss for a while.
The green squares don't look to be 16 pixels tall. Hard to tell with the footage, but DC's are typically 16x16 or 8x8
This looks to be a CCD issue not a compression issue especially since the artifacts don't propagate to the next frame, nor cause variations in the sharpness of things in the next frame which would be common if new image data had to be created in whole rather than as a differential from the perfectly noiseless, "broken" frame before.
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.
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.
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.
Frame 0-26: Puck Flying
Frame 27: Impact g force shorts capacitor (usually rated for ~10g), scanline loses chroma until circuit at proper threshold again.
Frame 28: Frame dims b/c of occlusion from puck, and collision likely turns glass into a negative meniscus lens.
Frame 29->: Officially an inelastic collision. Time to get a new camera