Quote:
Originally Posted by RefCT
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.
|
I bet the MWC is using a similar system as most conferences are using. This just happened to be the situation that was high profile.
I am not sure they ultimately got this right, but it appears the clock did not start on the touch for some reason. Either way, they followed the system. Again the officials do not create the system.
I think this is just more evidence of over reviewing everything. If these guys count this basket, then someone is going to claim they did not have the clock start properly and we have a different conversation. The problem is ultimately that we are using an impossible standard for most of these situations. We are requiring technology to save every possible play instead of just doing what is obvious to us for the most part.
Peace