Slashdot Mirror
Did a Timer Error Change the Outcome of a Division I College Basketball Game?
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.
It's kind of a silly discussion because the clock is started and stopped by humans throughout the game. So even if an error was made here by some fraction of a second, there have to be numerous other errors throughout the rest of the game which aren't being considered with equal scrutiny. So yeah a timing error probably did cost one team the game but unless you go back across the entire game you'll never know which team got screwed by the timer.
It's like in football where the referee rather arbitrarily places the ball but then they measure it to the inch to see if they got a first down. The problem is with the spot, not with the measurement.
Didn't I just post that you should get a good night's sleep timothy? You're on a roll with dodgy posts today.
Maybe slashdot should implement a "preview" button for editors too!
If you don't want to the outcome of the game to be determined by referees and shot clocks, then you need to put enough points on board so that there's no doubt that you've won.
I coach a wrestling team and that is more or less exactly what I tell my team. If you don't put enough points on the board then you risk having the referee decided the match in a way not favorable to you. If that happens you have no one to blame but yourself. We insist on accountability and no whining. If it doesn't go our way we own it and figure out how to make sure we do better next time. If a bad call is made it is my job as the coach to try to get things set right but at the end of the day the goal is to leave no doubt as to the outcome even in the fact of bad calls.
We, the people who work on the technical back-end to create the HD broadcasts you watch, are fighting a never-ending battle with crappy, hastily-written software that can't tell the difference between 30fps and 60fps.
Professional video gear that costs tens of thousands of dollars per unit still have software settings that assume the video coming into them is 29.97fps in both the settings and math calculations, which hasn't been used in broadcasting since the days of standard def. Even frame syncronizers - the workhorse devices that cross-convert and conform video feeds into whatever standards we need - still push out software that claims an output of 29.97fps when it's really pumping out 59.94fps. Not to mention, when the marketing staff puts together an on-air read to tell you how super-duper-awesome their new super-slow-mo cam-du-jour is, I can't tell you how many times I hear on-air talent still use the "regular cameras shoot in 30 frames a second but ours shoots 1,000!!@!" technical explanation, which just flat out isn't true anymore and hasn't been for nearly a decade.
If it's HD, you're more than likely staring at 59.94fps. In fact, any time you see an HD picture that is in 29.97fps, people immediately ask "Hey, why is that picture strobing?" This was a huge problem back when GoPros could only do 1080p at 30fps. Anyone who wasn't smart enough to set the cameras to 720p and upconvert them was met with very substandard results.
The only reason this hasn't come to a head sooner than this, is most of the time this poorly-written software and it's completely inaccurate timing isn't used as an official timing device to determine the outcome of a game. It was only a matter of time, pun not intended.
Baloney. The vast majority of sport programs are a net loss for the University. ESPN did a story on this. Even the powerhouses like Alabama (Football) lose massive amounts of money. People think the Universities are making massive money off of these teams, but reality it is just the coaches and Athletic Directors getting rich.