from the deflated-in-the-locker-room-by-professor-plum dept.
New submitter javakah writes: Controversy has erupted from the February 10th basketball game between Boise State and Colorado State, and speculation is that a timer may have made an incorrect assumption about the number of frames per second the game was recorded in, and ultimately lead to an erroneous result. With the game tied in overtime, Boise State had the ball out-of-bounds with 0.8 seconds left on the game clock. The ball was thrown in-bounds, the shot went in, and the game clock showed that the Boise State player got the shot off with 0.4 seconds left. However there was a problem: the game clock did not start until a fraction of a second after the in-bounds player touched the ball. Referees decided to use video replay to examine whether the player had gotten the shot off within 0.8 seconds or not. To do this, they used a timer embedded in the video replay system. This embedded timer indicated that 1.3 seconds had passed between the time that the in-bounds player touched the ball and when he got the shot off. (Read more, below.)
With the result of the timer, referees ruled that Boise State's shot was invalid, and the game went on to double overtime where Boise State lost. Afterwards, the Mountain West Conference organization, in which both teams play, defended the outcome based upon the embedded timer showing that 1.3 seconds passed and released video of the replay footage. That footage however, clearly displays the game clock. It shows that the game clock, which was counting down from 0.8, counted down to 0.7 seconds 0.7 seconds after the in-bounds player touched the ball. The game clock also shows that there were 0.4 seconds left when the shot was taken. The problem arises however, that the video also reveals that embedded timer counted 1.3 seconds between when the ball was touched and when the shot was taken, meaning that in the time in which .3 seconds passed on the game clock, the embedded timer had counted .6 seconds. Speculation has now arisen that the video footage may have been taken at 60 fps, but that the embedded timer may have calculated the time with an assumption that the video was taken at 30 fps. This closely matches ESPN's own timing, showing that only 0.63 passed.
"Mr. Spock succumbs to a powerful mating urge and nearly kills Captain Kirk."
-- TV Guide, describing the Star Trek episode _Amok_Time_