Seconds aren't ticking off at zero, so he had no idea the time from 0-snap. That's what I was saying idiot. But I did say "super" instead of "extremely".
SCORE 1 FOR PLOW
what are you comparing it with/in? In super slow motion is hard to guage a second precisely when you don't know how much it's slowing. If it wasn't that long, we wouldn't have the pre and post games talking so much about it since it's so common.
Just got back from my nephew's b day party, watched game during, fuck yeah ravens, so fucking glad they won, dont have to hear anymore titans banter.
Why are you guys arguing about whether it's half a second or 2 seconds ;o Either way it's past 0 and it should have been a penalty.
When the playclock shows "0" it really means zero. You know why? Because "40" stays on the clock for a full second so it doesn't start at 39.999...
However long it was between 0 and snap, it was the longest I've ever seen in 20+ years of watching football without a call.
It was long, and far too long not to be called. Noone here should be arguing that.
That being said the Titans just didn't get it done in the red zone.
Oh, and my boy Jim Leonard is quickly becoming my favorite player in the NFL (that doesn't play for the Packers)
/boggle...
Watch the clock roll down from 2 seconds to 0. If that takes 4 seconds, it's at 1/2 speed. If that takes 1 second, it's at 2x speed.
Nobody's saying he had a stopwatch, but watching how long it takes a second to roll off gives you a pretty good idea of how long a second in real time translates to in the slow motion.
As far as how slow it is and why people are talking about it, a ref should be staring at the play clock, and the instant it hits 0, look at the ball. If the ball's not being snapped yet, make the call. It really doesn't take the human eye that long to go from one to the other if you're positioned properly to do your job, so even if it's a half second, let alone a full second, the call should clearly be made.
You're looking at such a minute time Plow, it'd be very hard to tell, especially when not compartive to a real-time source. We'll know the answer by the end of the night, as I'm sure SC or someone will tick it away for us on a replay.
I thought it was pretty much just common sense, if the clock dropped to 39 the instant you start it, that would just make it a 39 second clock.
I'm not making any judgement on the play, I was taking a piss at the time and went to smoke during the postgame if they showed it then. Just saying it's not that hard to judge how slow slow-motion is when you're watching a clock tick.
Man if VY had been playing...
lawlzlawlzlawlz
And what I'm saying is that it's much harder than in real-time. Here's a test to exempify what I'm saying. Grab a stop watch and start it without looking at it, when you think you have a second, stop it and see how many milli-seconds you are off. Repeat the same test for 5 seconds. The longer it takes (slowed down), the harder it is to judge. You'll be closer to one second in the first test than 5 seconds in the 2nd.
Amazing catch by Larry Fitzgerald.
Wow what a catch by Fitz
stopping the stop topic...Fitz is God
In the slow motion replay, both the game clock and the the play clock were on the screen. Play clock went to zero when the game clock was XX:X3 and was snapped before it got to XX:X2. Quit arguing about timing the timing of 2-0 and how long after zero it felt like it took when it showed it on the screen.