|
It was said earlier and I will say it again, what it comes down to (from my view) is that the officials followed protocol but the protocol was flawed. You can't blame them, blame the software package and protocol. Based on the Deadspin article, the fact the virtual stopwatch was set to time at 30 fps, but the video was 60 fps, likely led to the time being double what it should have been.
The bigger problem here is the MWC needs to recognize that mistake and work with the vendor to fix it, or change the protocol and allow officials to use something like a traditional stopwatch instead of the faulty software package.
With hyper analysis by all outside sources (including us) due to everything in HD, mistakes like this need to be responded to and adjusted and/or fixed quickly.
|