The only constant this season has been inconsistency. If you watched the last four games out of context — Ohio State, Purdue, Michigan State, Oregon — you’d think you just watched four different teams. At least that’s better than being consistently bad, and the last two, a clear upward...
If we can watch Clayton ball out and develop and stumble backwards until a bowl, I’d consider that a success from this point forward considering how we got here.
A loss so catastrophically bad you fear it’s the beginning of another long dark decade-long era in hell. The worst feeling you can have as a sports fan.
If that’s our team, we have six or seven more wins ahead of us on the schedule. None of those teams have Jeremiah Smith on their roster. Nor will any of those teams have the officials that deep in their pockets.
it’s impressive we could maintain that drive at all considering we have to overcome a bad call or missed call from the refs at least once per each set of downs
I wouldn’t say there is blatant DPI every time we attempt a pass. But there is borderline DPI every time we attempt a pass, and sometimes it’s actually pretty blatant.
Having witnessed the referee war crimes from Michigan-Illinois in 2000 (the fumble game) and again from Michigan-Illinois in 2022 (the “what OPI?” OPI) my first instinct is always to believe the conspiracy angle. But ironically in this instance the reversal did college football no favor at all...
That’s not right though. If the clock is set to 9 seconds, it should display 0:09 for one full second after it is started before dropping to 0:08.
Clock set at 0:09
Ball snapped, clock starts
0.00 to 0.09 seconds elapsed —> clock displays “0:09”
1.00 to 1.09 seconds elapsed —> clock displays...
12+ hours later and after the dust has settled, this is my read of the situation. Both the NBC production team and the B1G officials apparently synchronize the game footage with a fixed shot of the game clock on the scoreboard in the stadium. Somehow their respective syncs were different by...