That clock stoppage at the end...

[dieterbrock]

the issue is not just if it was okay for them to take a knee and call a timeout that quick...

The clock stopped early...... clock operator killed the clock before he even took a knee.

His knee hit with 2 sec left, I posted it on the previous page

 

[Memento]

Has anybody ever said that anywhere, at any time? I know I haven't.

I'm saying just the opposite. That is far more likely to be human incompetence than it is a conspiracy.

I follow football, soccer, and to a lesser extent, cricket. I have never known a set of fans not to think that they were hard done by officiating. The Derby board that I go on, probably more than this one, is a full-on bitch fest when we lose And it's exactly the same when they go to opposing teams' message boards. They're all claiming they got screwed over by the officiating.

and it's the same with national phone-ins. Fans complaining about referees and in the soccer case, the 4th official and VAR.

It seems weird to me that in 30 years of going on message boards and 50 years of going to competitive sports, all fans think the same way.

Additionally, I wasn't suggesting that there aren't individual officials who are corrupt or accepting bribes. But when you have somebody saying that it was a conspiracy to make the game exciting at the end, and that's why the clock was allowed to run down before the play got off, then that is a whole different matter.

Fair enough. I apologize for coming on a bit strongly. I just feel that Hussey's crew had an all-time bad game against us. There were a lot of missed calls and calls that shouldn't have been made, I'll end with that.

 

[duanevalle22]

Fair enough. I apologize for coming on a bit strongly. I just feel that Hussey's crew had an all-time bad game against us. There were a lot of missed calls and calls that shouldn't have been made, I'll end with that.

I've re-watched the games 3x now and they missed a ton of holding calls.... Our defensive line was held pretty much all day..... but if you can get away with you keep doing it.

 

[El Chapo Jr]

Welp, I know you don't give a shit, but I don't get your argument on this one fucking call.

There is an official standing at the 1st Down yard stick. He is not behind the receiver, but rather at a 30 to 40 degree angle. That offical can see the ball was caught, and that the ball was being cradled with both hands by the receiver; and instantly know it's a catch. The receiver then sits up on his ass looking back (not forward to advance the ball), so the receiver is down and the play is called dead.

I don't buy a person takes forever to process all that info. Like I said, sight only takes 1/10 of 1 second to process into the brain. So, in contrary, yes that process could be performed in 2 seconds.

And, you didn't post anything that I can see with rules stating an official first has to confirm a successful catch. What does that involve? Can the official confirm it in his head, or is it not officially confirmed until making some type of physicall gesture it's a catch. Anyway, I ain't buying that. The official could see the play, see the catch, see him sitting up and see the timeout being called very quickly.

Try counting to two seconds yourself...two seconds is a lot longer than you think when you actually count it out.

I get it, but we won so....

 

[El Chapo Jr]

Try counting to two seconds yourself...two seconds is a lot longer than you think when you actually count it out.

That's not what she said!

 

[younghutch]

Yeah but Seattle never should have had that last time out. The Rams incompletion on 3rd down on the prior possession gave Seattle a break by the stopping the clock.

 

[duanevalle22]

Yeah but Seattle never should have had that last time out. The Rams incompletion on 3rd down on the prior possession gave Seattle a break by the stopping the clock.

For sure that bothered me, but that missed tackle by Forbes really pissed me off.

 

[Memento]

For sure that bothered me, but that missed tackle by Forbes really pissed me off.

Against JSN? You're going to win some and you're going to lose some. And this wasn't man-coverage (if that's the missed tackle I recall, if I'm not mistaken?), but zone. JSN has a full run-way and open space. The receiver is going to win that most times.

 

[LARAMSinFeb.]

I've re-watched the games 3x now and they missed a ton of holding calls.... Our defensive line was held pretty much all day..... but if you can get away with you keep doing it.

Fiske a lot?

 

[Ground Chuck]

The clock stopped when they called time out after Shaheed gave himself up

He went down to catch the ball. He didn't catch the ball, and "give himself up." Huge difference. Clock doesn't stop on a clock operator "hunch" that the offense is giving itself up. Watch the play again. Darn-Old still is HOLDING the ball with 3 seconds left, releases it with 2 seconds left, and it is CAUGHT after the clock ticks to 1.


View: https://youtu.be/S0yqdJlujsw?t=747

Here's the NFL rule for how you can declare yourself down without be contacted by a defensive player or stepping out of bounds...

View attachment 73340


I find it hard to believe that the receiver was actually down long enough for the zebra to consider the receiver DOWN by declaring himself down by clearly giving up and making no move to get up. That process needs to be clear... the ball carrier needs to lay on the ground for a couple of seconds at least before a ref could possibly see that he is clearly not going to make an attempt to advance the ball.

Yesterday, that Seadderall receiver caught the ball while he was going to the ground to catch it. He didn't catch it while standing up and then purposefully drop to the ground to make it clear that he was giving himself up on the play. Like I said, the receiver actually had to make a diving attempt just to catch the pass, so he was on the ground basically when he was in the process of catching the pass. The ref that granted the timeout was actually behind the receiver and did NOT HAVE any clear view as to whether or not the catch was actually made clearly... all he could see from his vantage point was the receiver's back, so that zebra had no way of declaring that a legal catch was made because he could NOT see the ball. In today's NFL, a receiver has to make the catch by having both feet or another body part down on the field of play before touching out od bounds. Then, the receiver has to make some kind of "football move" after that happens and hang on to the ball throughout the entire catch process before the zebra can declare that a successful reception was made. In this case, the zebra had no clear view of the ball... he could not have been able to declare the ball caught successfully if we're being honest. Much less could he have been able to do all of that in the tiny amount of time that he actually did it in yesterday.

That fakkuh (the zebra) declared the ball caught without being able to see the ball while watching the receiver go through the entire catch process, decide that the receiver was CLEARLY giving himself up, and then recognize the timeout request by the receiver in lass than a second. It was like 2 Top Gun fighter pilots maneuvering their jets perfectly while flying through the air without crashing. The level of coordination and timing between the ref who could not see the ball and the receiver diving to the ground in hopes of actually catching the ball was damn near instantaneous.

Go to the 12:23 mark to watch that play yourself. That ref did not have the ability to make the call he made of a completed catch all by himself... much less see that the catch was made and then being able to clearly see that the receiver was giving himself up on the play. That was bullshit.


View: https://youtu.be/S0yqdJlujsw?si=g1Jv-USel3MhhBxt


And just to throw something else out there about this. The receiver could not legally call a timeout until ball was actually declared dead by the zebra. This ref was trying to say all of that happened in basically less than a second of time. Here's the NFL rule for when a timeout can be legally called for by a coach or player.

View attachment 73343

This ^

 

[Ground Chuck]

His knee hit with 2 sec left, I posted it on the previous page

Darnold still has the ball with 2 seconds left. The clock is turning to 1 when the receiver catches the ball ON THE GROUND. He does not give himself up just because he catches it on the ground. Guys get up and run when they are not touched all the time.

Here is the moment after he catches the ball. Nearest defender 3 yards away. Are you saying the refs and clock operator were correct for reading the intentions of the receiver to not attempt to get up and run with the ball? BS.

 

[dieterbrock]

View attachment 73397

Darnold still has the ball with 2 seconds left. The clock is turning to 1 when the receiver catches the ball ON THE GROUND. He does not give himself up just because he catches it on the ground. Guys get up and run when they are not touched all the time.

View attachment 73398

Here is the moment after he catches the ball. Nearest defender 3 yards away. Are you saying the refs and clock operator were correct for reading the intentions of the receiver to not attempt to get up and run with the ball? BS.

I posted screen shot 2 pages back
He was down at 2 seconds
it was a good play and they got it off.
I dont know why people need to believe in conspiracies over the simplest things
You can see him motioning the time out here, and the refs arms waving
the ref was right in front of the coaches who were also calling TO
no clock manipulation, refs just doing their job
if the Rams pulled off the same play we'd be talking about how brilliant it was

 

[Ground Chuck]

I posted screen shot 2 pages back
He was down at 2 seconds
it was a good play and they got it off.
I dont know why people need to believe in conspiracies over the simplest things
You can see him motioning the time out here, and the refs arms waving
the ref was right in front of the coaches who were also calling TO
no clock manipulation, refs just doing their job
if the Rams pulled off the same play we'd be talking about how brilliant it was
View attachment 73399

Well, it is interesting that we both screenshot the same :02 mark. And the same :01 mark. A lot can happen in a second. But as a reminder....

Darnold had the ball still in his hand when the :02 STARTED, so even if the receiver caught the ball technically at :02, the clock ticked, as I stated to :01 a nanosecond later, and his motion to turn his body to "give up" ticks off that second in any real-world situation where operators are acting in a non-partisan manor. Just very curious. This game should have ended here.

There just seemed to be a concerted effort by powers that be to will the timeout prior to the play, whether the execution of the play warranted it or not.

 

[dieterbrock]

Well, it is interesting that we both screenshot the same :02 mark. And the same :01 mark. A lot can happen in a second. But as a reminder....
View attachment 73400

Darnold had the ball still in his hand when the :02 STARTED, so even if the receiver caught the ball technically at :02, the clock ticked, as I stated to :01 a nanosecond later, and his motion to turn his body to "give up" ticks off that second in any real-world situation where operators are acting in a non-partisan manor. Just very curious. This game should have ended here.

There just seemed to be a concerted effort by powers that be to will the timeout prior to the play, whether the execution of the play warranted it or not.

Clearly The secret society of the nfl had a “slow clock” option installed just in case they needed to give the Seahawks an extra half second I guess

 

[Tumak61]

Two things are always ball spotting and clock. For someone like me who's been watching the NFL for decades it's always loosey goosey with regards to both of those things. How many times do the refs just reward 1st downs in hurry up situations when it's not really clear? A LOT. How many times do you hear a ref say " can we set the clock to whatever on my whistle?" It's loossey goosey game management. It is. Fred Dryer said it best about replay. It creates questions that humans try to officiate in real time. Replay just creates beefs.
Don't wring your panties over a second or two. It's subjective. Refs thought they had a sec left.

 

[PARAM]

The clock stoppage at the end? I thought at 0:47 when Charbonnet was driven out of bounds, he wasn't going forward. He caught the ball past the 18 and was driven out at the 18. As a result of the clock stoppage (0:40), they could take their time , whereas if the clock was kept running they wouldn't have snapped that ball until around 0:33. That play was in bounds to JSN and they didn't snap it again for 17 seconds (which would have had the clock at 0:16 with the ball on their 26 . They wouldn't have sniffed a FG attempt. JMHO on watching the game replay.

 

[Steve808]

The clock stoppage at the end? I thought at 0:47 when Charbonnet was driven out of bounds, he wasn't going forward. He caught the ball past the 18 and was driven out at the 18. As a result of the clock stoppage (0:40), they could take their time , whereas if the clock was kept running they wouldn't have snapped that ball until around 0:33. That play was in bounds to JSN and they didn't snap it again for 17 seconds (which would have had the clock at 0:16 with the ball on their 26 . They wouldn't have sniffed a FG attempt. JMHO on watching the game replay.

We just need to be very thankful that the punter killed that ball at the 1 yard line (really should have been the 6 inch line) because the she hawks had a lot farther to go and for whatever reason, they didn't seem to be in a big rush.

 

[Rambitious1]

This is not correct in instances in which the player gives himself up.

True, when he gives himself up. Which he did not do.

 

[Karate61]

Well, it is interesting that we both screenshot the same :02 mark. And the same :01 mark. A lot can happen in a second. But as a reminder....
View attachment 73400

Darnold had the ball still in his hand when the :02 STARTED, so even if the receiver caught the ball technically at :02, the clock ticked, as I stated to :01 a nanosecond later, and his motion to turn his body to "give up" ticks off that second in any real-world situation where operators are acting in a non-partisan manor. Just very curious. This game should have ended here.

There just seemed to be a concerted effort by powers that be to will the timeout prior to the play, whether the execution of the play warranted it or not.

I believe you stopped the video too soon. The receiver was sitting up, with his back turned, calling time-out, with no intention of advancing the ball. And, that was still with one second on the clock. Here's a screenshot showing that. I think that demonstrates the receive gave himself up. What do you think?

 

[LouisvilleRam]

Here's the NFL rule for how you can declare yourself down without be contacted by a defensive player or stepping out of bounds...

View attachment 73340


I find it hard to believe that the receiver was actually down long enough for the zebra to consider the receiver DOWN by declaring himself down by clearly giving up and making no move to get up. That process needs to be clear... the ball carrier needs to lay on the ground for a couple of seconds at least before a ref could possibly see that he is clearly not going to make an attempt to advance the ball.

Yesterday, that Seadderall receiver caught the ball while he was going to the ground to catch it. He didn't catch it while standing up and then purposefully drop to the ground to make it clear that he was giving himself up on the play. Like I said, the receiver actually had to make a diving attempt just to catch the pass, so he was on the ground basically when he was in the process of catching the pass. The ref that granted the timeout was actually behind the receiver and did NOT HAVE any clear view as to whether or not the catch was actually made clearly... all he could see from his vantage point was the receiver's back, so that zebra had no way of declaring that a legal catch was made because he could NOT see the ball. In today's NFL, a receiver has to make the catch by having both feet or another body part down on the field of play before touching out od bounds. Then, the receiver has to make some kind of "football move" after that happens and hang on to the ball throughout the entire catch process before the zebra can declare that a successful reception was made. In this case, the zebra had no clear view of the ball... he could not have been able to declare the ball caught successfully if we're being honest. Much less could he have been able to do all of that in the tiny amount of time that he actually did it in yesterday.

That fakkuh (the zebra) declared the ball caught without being able to see the ball while watching the receiver go through the entire catch process, decide that the receiver was CLEARLY giving himself up, and then recognize the timeout request by the receiver in lass than a second. It was like 2 Top Gun fighter pilots maneuvering their jets perfectly while flying through the air without crashing. The level of coordination and timing between the ref who could not see the ball and the receiver diving to the ground in hopes of actually catching the ball was damn near instantaneous.

Go to the 12:23 mark to watch that play yourself. That ref did not have the ability to make the call he made of a completed catch all by himself... much less see that the catch was made and then being able to clearly see that the receiver was giving himself up on the play. That was bullshit.


View: https://youtu.be/S0yqdJlujsw?si=g1Jv-USel3MhhBxt


And just to throw something else out there about this. The receiver could not legally call a timeout until ball was actually declared dead by the zebra. This ref was trying to say all of that happened in basically less than a second of time. Here's the NFL rule for when a timeout can be legally called for by a coach or player.

View attachment 73343