Indiana game, clock
- Thread starter PSUNATTY2020
- Start date
Yes. I suspect it's because the clock didn't start again after the IU back went out of bounds with about 2:35 left. It should have restarted once the ball was marked for play (if you recall, IU took quite a while to get the kick off, which would have been about 2:17 when the TO was called). Official time is kept on the field and they must have synched the two clocks during the timeout.
Did anyone notice the Indiana screw up at the end of the first half? That may have cost them the game, not the 4th qtr mess.
Indiana is terrible. They are lucky to have a MBB history or they be looked at like a Pitt or Rutgers.
Yes, that was bad. If they had called TO with 8 second left, they could have taken one shot to the endzone then kicked the FG. Instead they spiked it and had to settle for the FG. May have cost them 4 points.
Also the clock in the graphics can get out of sync sometimes, so the technical people on the network end will correct it. You see this sometimes when the clock should be stopped, it is running onscreen, then corrects itself without the refs mentioning it, that is because the clock in the stadium was correct, and always was correct, the interface between it and the graphics overlay got out of sync.
Loved that UT kid making a run that would have put the game away but came up a good foot plus short. Lying on the ground and in full view of everyone (looked like the sea parted and there was nobody blocking refs or TV folks view), the kid just keeps inching the ball forward until it's at the marker. [BTW, I don't blame the kid]
Refs obligingly come in, decide that's a great place to spot it.. chains out, first down.
Prior to IR, that joke ends the contest. Fortunately, IR corrected it.
Then there was the 'here's how we gain a half a yard by moving the ball forward before the snap' trick. To refs credit, they got that one.
Refs obligingly come in, decide that's a great place to spot it.. chains out, first down.
Prior to IR, that joke ends the contest. Fortunately, IR corrected it.
Then there was the 'here's how we gain a half a yard by moving the ball forward before the snap' trick. To refs credit, they got that one.
I noticed the out of bounds at 2:32 and then the tv clock didn't start but the play clock was at 1 when the timeout was called so it should've been way less than 2:17 unless they took forever to mark it and resume the clock running. I suspect there was a screw up and was surprised there wasn't a long delay trying to fix it or maybe those running the clock at bowl games don't know the rules. I feel like there was a PSU game in the last couple years where there would be a first down or out of bounds play and the clock would stop for just 1 or 2 seconds before starting again, clearly not waiting for the ball to be set or the chains to move on a first down. I can't think of the game but felt pretty mad about it. Maybe Kentucky last year??
Better yet what the hell was Ramsey thinking on the last 2 throws? Basically threw them into the ground no where near a receiver - it's your last shot and you don't even try to get the ball at least up for grabs and hope for the best instead you just give up basically - couldn't understand what he was thinking.
I watched this game on tivo this am. What really irritates me is Ramsey looked so ordinary v Tenn. 3rd and long was a joke. He took ridiculous sacks. Threw for 220? He hung 371 on us. WTF secondary DAMN
And lousy execution on the onside kick. They stood there and watched it roll toward them.Tennessee couldn't touch it until it went 10yds and the Indy players just stood and watched.
Indiana's downfall is Tom Allen. He lost at least 2 possibly 3 games for them this season with stupid decisions. But hey he gives great spit flying speeches and kicks over trashcans.
And he’s a weird dude.Indiana's downfall is Tom Allen. He lost at least 2 possibly 3 games for them this season with stupid decisions. But hey he gives great spit flying speeches and kicks over trashcans.
