Connecticut came away with a stunning win on Friday, thanks in large part to this incredible 70-foot shot by Jalen Adams that forced quadruple overtime.
It was an unbelievable shot. Some even argued it was too good to be true, including losing Cincinnati coach Mike Cronin.
"I want to congratulate UConn on their victory," Cronin said via ASAP Sports. "Got nothing but utmost respect for Kevin and the job he does, how hard his kids play. But I felt we won the game and the game was taken away from us, so that's my opinion."
Cronin was asked to expand on those comments, and reiterated that he did not think Adams got the shot off in time.
"In .8 you can't catch the ball, take two steps and then shoot it. You can't catch it, turn, bring it below your waist, and then shoot it with enough force to shoot it 80 feet in .8 seconds. The clock didn't start nearly on time. I've already watched it five times."
He isn't the only person who thinks that, with others on Twitter arguing the clock didn't start in time. They aren't wrong ... if you go by the ESPN ticker.
Here is the moment Adams catches the ball.
Now, here is the moment the clock finally ticks a tenth of a second.
That part seems unquestionably slow. There is no denying that. However, with the slow clock, Adams has released the ball with a full 0.4 seconds left on the clock.
Watching that replay, it doesn't seem right that Adams would be able to get the shot off in 0.4 seconds. Even if Cronin exaggerates a bit in the description of the shot. Adams didn't take two steps, for example. But, when the referees reviewed the play, they didn't use the clock on the ESPN ticker. Instead there was a superimposed clock, and it was much more accurate.
Here is the moment he caught the ball:
And the release:
Let's forget the manually operated clock altogether. Timothy Burke broke it down by just the frames. And the shot is still off in time.
Ball was held for 45 frames at 59.94fps, or 0.75 seconds. Clock read 0.8 upon inbound. Shot was still good https://t.co/IERJkPD0En— Timothy Burke (@bubbaprog) March 12, 2016
No matter how you spin it, the shot was clearly off in time, regardless of an ESPN ticker malfunction.
As for other complaints?
No. Just, no.