OT: Did Cincinnati Get Screwed?
This is a picture of the Cincinnati dunk before the shot clock expires. What you will notice is that the shot clock is showing 0.0, but the game clock shows 0.2 seconds left.
The red light around the backboard is on because the shot clock has expired. But the shot clock and game clock inexplicably are not in sync.
Cincinnati got the ball back with less than 30 seconds left on the game clock. So the shot clock should have been turned off regardless.
You can see that the ball goes through the basket with .2 seconds left. But the referees were fooled by seeing the red light on because the non-synced shot clock showed 0.0, but the game clock was at .2 seconds.
[url=http://imgur.com/M0P3a4J][img]http://i.imgur.com/M0P3a4Jl.jpg[/img][/url]
Sent from MGoBlog HD for iPhone & iPad
haha, sorry.
Not sure why my pic won't show, I thought I followed the rules.
If someone could tell me which pic link to post I would appreciate it. I think it's worth showing.
Sorry to bring back the pain, but I think the refs blew this call.
head of officials explained it - in order of importance, it's clock above the actual basket, then the red light, then the horn.
Clock above basket was at all zeros, red light was on, ball was still in hand.
Ball can even be through the cylinder, if you haven't let go, you haven't released a shot.
As to the various clocks, you seem to be referring to something that isn't one of the official timekeeping elements (see above).
Ok, so the clock above the backboard was the actual game clock and not the shot clock? Man, that's an absolute clusterfuck. My buddy and I were sure they had it wrong. Not sure why the clocks are not synced up properly.
Wish I could figure out how to embed a pic that would explain the confusion.
The 0.0 above the basket is the official game clock. The empty black space beneath that 0.0 is where the shot clock time is located, but it is off because Cincinnati got possesion w/ less than 30 seconds remaining. The 0.2 seconds is the unofficial TV score bug display that is there for the benefit of the viewers at home.
But they're in Ohio, so they can suffer like we are.
True, good point.
Go Blue, Good Night
It was the correct call.
Sent from MGoBlog HD for iPhone & iPad
seriously laughed out loud on that one.
March 19th, 2016 at 11:20 AM ^
The board above the basket is showing the actual game clock only at that point. During the entire game that board shows both the game clock (on top) and the shot clock (on bottom in larger font) unless the time remaining in the game is less than 30 seconds. For the reasoning behind the 0.2 left on the broadcast clock, I'm not sure how accurate that can be considered, but I think it's pretty obvious you go with the clock in the arena before that. While it was an extremely close call, it definitely looked like he was touching the ball as the clock hit zero.
I guess then the game clock in the bottom right of the screen shouldn't be different than the clock above the basket. Because as a neutral observor it looks like there is still time left on the clock.
I assume the Bearcat fans would agree with me that there was .2 seconds left per the picture I posted.
How the two clocks are not in sync is beyond me.
March 19th, 2016 at 10:02 AM ^
I mean, sure it'd be great if they were both synced up perfectly, but if there's two different people in control of both then of course it won't be perfect. Sometimes broadcasts just show a feed of the actual clock in place of the broadcast version (I've seen this in football, as well). I noticed they were doing that during the MSU game, but not for the entire game. I'm guessing they only do that when there's some type of issue, but maybe they should just do something like that for the entire game.
Sent from MGoBlog HD for iPhone & iPad
Sent from MGoBlog HD for iPhone & iPad
ABC News just ran the last offensive sequence with closeups on their morning news (because the first weekend of the Tournament has angered America's amateur bracketologists) and yeah, the ball is still about an inch or two from the hoop as time expires and still clearly in that player's hands. Not even a second too late, which blows because there's another bracket down for me but also because it would have been a great finish to send it to OT.
Sent from MGoBlog HD for iPhone & iPad
March 19th, 2016 at 10:07 AM ^
Sent from MGoBlog HD for iPhone & iPad
March 19th, 2016 at 10:33 AM ^
March 19th, 2016 at 10:37 AM ^
last night? i figure the game ending by 5 probably saved the whole city from being reduced to an ash pile.
March 19th, 2016 at 12:27 PM ^
Sent from MGoBlog HD for iPhone & iPad
Sent from MGoBlog HD for iPhone & iPad
March 19th, 2016 at 10:04 AM ^
Sent from MGoBlog HD for iPhone & iPad
March 19th, 2016 at 11:19 AM ^
Sent from MGoBlog HD for iPhone & iPad