Recent content by JSpence

Ooooooh, I like this. They knew he might do something. They were ready. They got his name right!

Seems rude to Spoon. I'm pretty sure we're thankful that Pensacola existed just the way it did!

Haha, yeah, that was wild luck. That's the only frame like that. You're still right to point this out, because the broadcast clock is inconsistent. It's within a frame here and it varies more than that. I'm confident that I could show it being early OR late within the same game. So, now we...

They aren't in "exact to-the-frame" sync, though? I guess I got lucky, but this is me on my first try just clicking pause in my browser. Like I've said, the graphic clock is less out-of-sync than the embedded one, but it's a bit off and varies a bit. In many games, you can occasionally see it...

I wish this were true. Winning two playoff games by 6 or more runs feels doable. Winning a single close or low-scoring playoff game feels almost impossible.

Just sat down to watch the game. Two pitches later, I know I'm bad luck.

Someone else went and did it. I would have also added a view of the delay clock and detailed the blips there, but I understand why they didn't include it. Holy moly, I'm glad I didn't make the effort. The top relies we see are people saying that it doesn't matter because we go by the clock on...

This thread is long, so you probably missed the screenshots in my previous post #288. You can see from the position of WMU's #12 (I said #2 but was describing #12) that the embedded clock was out of sync. We can slice it other ways with other points of reference, too. There was time left...

Yeah, dude, that's the WHOLE discussion. The clocks on the screen were not accurate. I think it was? They might not call it a penalty per se if it's on the defense. Still, a penalty or out of bounds stops the clock and a game can't end on a defensive penalty, yadda yadda.

He went out of bounds without being forced out. He then jumped. He's an out-of-bounds piece of furniture, so the ball is dead as soon as it touches him.

I agree on the deeper issues and I hope that our Gies guys are nerding out to check that our clocks don't have the same vulnerability. I'm not sure that clocks that are kept accurately but only give 14:59 per quarter would count as a clock error in the rule book. And like you imply, do two...

Alright, I'm about wrapped on this. It wasn't a rob by the clock. The clocks in the stadium ticked to 0:00 an eighth of a second (3-4 frames) after the ball was touched. The first movement of the snapped ball is a clean reference. Calling that frame 1, every camera I've checked agrees that...

To confirm for those wondering, the black and white clock in the corner (not the video I'm using) IS footage of a field clock. Aside from its slight jitteriness, we can see physical transition caught in-frame (as in, we can see two numbers at once) from 0:09 to 0:08, as well as to seconds 0:05...

I've looked at the frames. The clock is consistently immediately ticking all game. This is a problem and not how football clocks are supposed to work. For the play in question, the clock was manually reset to 0:09. All video I've used is 30 frames per second. Let's call the very first...

If he were to Michael Vick it 50 rows into the stands, the clock would run until the moment it knocks the phone from the hands of the oblivious trust fund baby is in its path. Also, there are no fractional seconds in football. 15:00 means there are fifteen minutes left or a little less. 0:00...