Journeyman said:How many times have we seen a catcher pretend he caught the third out and run off the field?
t3a said:Catchers tag guys out all the time even though they have caught 3rd strikes it is something you do just to avoid things like this. 9th inning of a tie playoff game you make sure its an out you don't roll the ball away
Replays did look like he caught it though
t3a said:so doesn't that contradict trusting what the catcher does?
Chuck Sims said:The arrogance of these umpires is frightening. These chumps are saying after seeing the slo-mo replay, "its inconclusive" whether he caught it or the ball bounced. He obviously caught it. The replay showed that.
The obvious call was that he caught it. But, like someone said earlier, on the live broadcast on Fox, they showed a closer replay than the one on ESPN, and it did appear that it changed directions. That would indicate that it hit the ground. It should have obviously been called a catch, but if replay came into play, and they showed the Fox close-up, it would not have been overturned.Chuck Sims said:The arrogance of these umpires is frightening. These chumps are saying after seeing the slo-mo replay, "its inconclusive" whether he caught it or the ball bounced. He obviously caught it. The replay showed that.
What you don't realize is that there are a lot of calls to make on one play. A strike/ball on the pitch, whether or not he swung, and whether the catcher caught it. And what if it was a check swing? The plate umpire could call it a ball, but then be overruled on an appeal. The bottom line is that his signal was not "out," but rather "strike three." He probably did not need to signal strike three, because it was obvious that it was swung at, and was not a check swing. His first call was "no catch," before he signaled strike. So a delayed call after reading the situation is what should have been made. But his quick call actually caused all the problems.t3a said:It might be nice if MLB could get all these umps on the same page though and get rid of all the variations with how balls and strikes and outs are signalled and called. They need uniform signals and get rid of the guys who make the delayed calls
His first signal was like a "safe" signal. It means no catch. Watch it again, and you will see that it was his first call, before he called a strike on the swing.Chuck Sims said:Illinois, I think you made a typo on "no catch" signal. It was "no contact" signal.
The HP umpire uses a terrible hand gesture to signal a strike. It looks like he is signaling "you're out".
As I've stated previously, a "no catch" signal is the same as "safe." He does that first before calling the strike. Watch closely and you'll see it. That is where he got into trouble, by calling the no catch too quick.quantumleap said:Regardless of whether an ump uses a strike signal or an out signal the ump would use the same signal whether the ball hit the ground or not. Is there no signal that the ball hit the ground and that the runner can advance to first base? If not, then it's left up to the whim of the umpire without the knowledge of either the catcher or the batter.
Illini said:As I've stated previously, a "no catch" signal is the same as "safe." He does that first before calling the strike. Watch closely and you'll see it. That is where he got into trouble, by calling the no catch too quick.
He called "no catch," and then he called a strike. The strike call was not necessary in this case, because it was obvious that it was a swing. But you are so used to signaling strikes on swings that it just comes naturally. You have to train yourself to not signal it on plays like this. Not signaling was never really taught anyway, just something that I, and other umpires, find the most convenient and pain-free way to call a play like this. But it cannot be like this all the time, because if it's a check swing, you may have to emphatically signal "strike" on a bounced ball, even though that strike 3 is not yet an out. It's just a fucked up situation.quantumleap said:Then he called the "out/strike" call. Would that have negated the "no catch" call? If so, is the runner out?