I came here to intentionally get myself pissed off by bad calls by arrogant, old obese umps Now I'm pissed at the uploader for posting a video of mostly correct or "close" calls and calling them "awful"
Yup these were very close, hard for anyone to see plays. Many only apparent on ultra slow mo looks. Some calls were actually correct. Kind of click bait with this upload.. Umps were not very awful
Yeah I completely agree....even some of the pitches were only off by a little bit...I would have called those strikes as well..I played for 12 years and I would not have argued those pitches....CLICKBAIT out the ass
@SAVEGE BOI GAMER I totally agree with you these are bad calls and even though they are close, most are noticeable to the umpires. No clickbait whatsoever.
@@action-packedadventures4056 its complete clickbait, half the plays you never even see what the final result is. and the other half the umps were right. i'm thinking the youtube account made some burners to try and make itself not look useless
@@action-packedadventures4056 At 7:14 that call is correct. The pitcher was no longer a fielder once the first baseman got the ball, but still affected the batter/runner's path to the base. That is the definition of obstruction and a dead ball, batter is awarded first, all other runners advance only if forced to by the awarding of first base on the dead ball.
@@mateo0939 The rule is both feet must be in the running lane, EXCEPT for the last step. Had the Runner done that and gotten hit, then he is PROTECTED. Otherwise, this play was called CORRECTLY. Even though it does suck for the Offense.
@@ButchRahman It's a little iffy. His last step has to be made for the "sole purpose" of touching first base. That looked like he did it intentionally to get in the way. It's hard to say, but the umpire made a judgement call. I agree with him on it based on the video.
Just because you don't like or understand the call doesn't mean it's awful umpiring. Several of these are correct calls. 0:29 Infield fly rule. Molina caught the bounce on the foul line. If any part of that ball was fair when he touched it, it counts. Hard to tell from the camera angle. 1:27 A balk, correctly identified by the announcers immediately. 3:03 Clear interference by the batter. 4:05 Interference with the throw by the batter. He has to get out of the way. 4:32 Batter-runner ran into the ball in fair territory. He's out. 4:56 The ball only has to hit the uniform. It doesn't matter if it actually hits the batter's body. 5:30 The runner screened out the fielder in the act of fielding the ball, blocking his view. 6:02 The batter-runner interfered with the fielder in the act of fielding the ball. 6:26 Running lane violation. He needed to run in the running lane in foul territory so as to not interfere with the throw coming in from behind him. 7:13 Obvious obstruction. The pitcher didn't have the ball. The batter-runner shouldn't have to evade him to get to the base. 8:01 Interference by the baserunner on the fielder catching the ball. That ball is dead the second the interference happens, and that runner is out. Almost every one of the "awful" rules interpretations were correct, and of the judgment call plays, many of them were ones that couldn't be seen with the naked eye, like the last one where the knee goes up off the base for a split second.
5:30 The issue wasn't an interference of the SS (it clearly wasn't). It was an obstruction just feet from third, with the umpires only protecting him to that base. And this led to a silly out at home when the runner chose to stop playing and start umpiring himself.
@@daveh1758 It appeared to me that the call made by the umpire at 3B was interference made prior to the obstruction, dead ball, runner out. Since the ball was dead, the obstruction never happened. If that was the case, I think it's a borderline call and an umpire's nightmare. If the call was truly obstruction, then no question, he should have been given home. This is one where you pretty much have to look at the original news coverage or play-by-play of the game. We don't get enough of the play-by-play to find out what the ultimate conclusion was.
@@eauhomme Other compilations include that play and devote more replay time to it. It is indeed the obstruction/non-award of home that's the issue. You're probably looking at 99% of the time this being an easy award of home, but on this particular play, with an extremely shallow left fielder at Fenway quickly getting to the ball, I can see why this could fall into the 1%. With the bad throw, he would have scored anyway, but he was too busy umpiring instead of just traveling the last 90 feet.
@@daveh1758 Thanks for the clarification. As an umpire, I see the obstruction as an obvious send home. The fielder does not have the ball in hand yet and is indeed a couple steps short, and the runner never slowed down rounding the base, so there is no indication he had intended to stay at third. The obstruction happens right on top of the bag, if not even past it a half-step, so it makes no sense that they would hold him at third. If the fielder already had the ball in his glove or hand and the obstruction happened clearly short of the bag or the runner had slowed coming into the bag, then I could see holding him at third. As I said, you ...could... call the interference on the runner for screening the shortstop, but that's a very borderline call if (a) the ball is not contacted--an automatic out--and (b) the runner doesn't make a definite motion to slow down or otherwise screen the fielder.
I would say 7:13 is obstruction if the runner didn't step outside the two lines do make contact with the pitcher. This one, to me, was the worst call, and one of the few "bad" ones in this video.
0:28 This is not an awful call, it's absolutely the correct call. Blue was right on top of it with a great look down the line. It's an infield fly (you hear the umpire call "Infield fly if fair!") - batter is out, ball is live, runners may advance at risk of being put out. The ball hit the ground in fair territory, and was not over foul territory before being touched. It is a fair ball. If he had let it go it would almost certainly have been a foul ball (unless it had some wicked spin on it). And 8:38: "He's clearly off the bag by about a millimeter, which you could only see with the help of this super slo-mo replay. What a terrible call!" 85% of the calls in this video were correct.
@@alanhess9306 Right. Blue was right on top of it and has a much better look than the camera does. I guess it is close enough to warrant coming out of the dugout to talk about it, but I don't think it qualifies as an awful call.
1. A lot of these were either close or the correct call 2. You are just determined to never let us have some kind of final resolution to these calls, are you?
Some of these were bad, but 80% of the calls were the right calls. Even some, I wouldn't call "awful umpiring", just really close to call. It's hard to see a player clearly pop off the bag for a millisecond & make the call.
I mean, most of these were right. There was a few that were missed, but I'd hardly call them awful umpires. The one against the Cardinals in the WS against the Royals was awful, but I'm biased lol
That Tejada deal at 5:31 is ridiculous, yes he was clearly interfered with, but if dude had kept running he would have scored still. Don't assume anything, play hard and don't worry about what the umps do or don't call.
This guy is oblivious of the infield fly rule. “When there are less then two outs, with runners on first and second, or bases loaded and if any infield player makes an attempt to catch, the umpire can call the ball out, even if the ball isn’t caught.”
7:34 "maybe he knows the rules" that was awesome dig on the other broadcaster who doesn't know them and presumably complained that the runner intentionally ran into the pitcher.
I'm very confused by this video. Most of the calls are correct and actually tough technical calls from the umpires (there are exceptions throughout but still). How if this bad umpiring?
1:27 is wrong that is a balk. The pitcher started his motion by moving his hand, but stopped in the middle of his movment. Which should be caled a balk.
I don’t think many of them were wrong and the ones that were wrong didn’t have enough video evidence to overturn the call on the field. Not every controversial call is wrong.
The one call I see that is bad is at 7:13; the pitcher is in fair ground; if the runner runs into him the runner is obviously out of the first base running lane. So runner should be out.
Baserunner interference as it pertains to the running lane only matters on throws in the vicinity of the first base foul line, i.e. from catcher to first base. Now, the fielder has the right of way and that’s where interference could be called but obviously in this case the pitcher doesn’t field the ball and gets in the way of the runner. If Abreu (the fielder) got in the way it would be fine, but that’s not what happened. Pretty clear obstruction by the pitcher.
How is any of this "awful umpiring?" Even if a call is found to be incorrect, it's human error. Now, with replay, the call can be reviewed. The game at full-speed isn't easy to call. Give me a break.
Umpiring can be tough, especially at the little league level because you see things you never see at the pro level. I was calling a game behind the plate with a runner on first, the batter had a 2 ball, 1 strike count. The pitcher threw a ball on the inside half of the plate. The batter swung, but his forearm hit the ball half way to the pitcher. The pitcher threw the ball to first. No call by our base umpire. Runner on first ran to second. What's the call?
The defensive manager claimed the ball was dead because it hit the batter and the runner on second had to return to first. My response was, the bat didn't strike the ball, so it wasn't foul. And since the ball was in the strike zone and the batter swung at it, it was a strike and therefore a live ball. Runner was safe at second and the at bat would resume. He tried to argue I was wrong so I gave him one minute to look at the rules and prove me wrong. After about 45 seconds, he spun around, threw his hands in the air and walked away. Umpiring is one of those thankless jobs.
Dead ball, strike. A ball hitting the batter during a swing is a strike, and if it is strike 3, he's out (it is not a foul ball). I was once working the bases in a Little League game. Runners on first and second, ball hit to left center. Runner on second clearly scoring, and I'm getting into position to make the call at third, positioning myself between the mound and third. All of a sudden, I hear my partner scream "Brian, get down!" I hit the deck. The throw was an absolute laser home, way too late to get the runner, and headed straight for my ear had I not ducked.
@@Deanrite It is always a dead ball when a batter is hit by a pitch, even when he swings. The count should be 2 and 2 and the runner returns to first base. The defensive manager was right, you were wrong.
You’ll notice the managers only argue the calls that don’t benefit them. Nobody ever got kicked out of a game for arguing a horrible call that helped them.
A lot of these are questionable but I can see why they would be called because there is a hidden rule. Mostly if the ball touches the player even not in the glove they are out from what I got out of watching baseball. I think the rule is inconsistent tho but I believe it is there.
I was wondering about that. I'm not a pitcher and I don't know all the bauk rules. Thought it was only a bauk if he did that after he came set but wasn't sure.
The umpire didn't call it a HBP because it was too close. He called it a HBP because he saw it hit the uniform. You call it as you see it. You don't wait and think about it.
From the MLB Rules, Definition of Terms: If a declared Infield Fly is allowed to fall untouched to the ground, and bounces foul before passing first or third base, it is a foul ball. If a declared Infield Fly falls untouched to the ground outside the baseline, and bounces fair before passing first or third base, it is an Infield Fly.
@@CastlegarGlenn The catcher grabbed the ball through before the ball went foul. That would make it not a foul would it not? It hit fair and bounced up and was headed foul. If the catcher had let it go foul then it would not have been a correct call but he caught it before it actually went foul I belive
@@truffleshuffle009 Yes, you are correct. The Orioles were contending that the catcher touched it after it crossed over into foul territory, which would have been good for them. Too close to call from the angle we saw, so just as likely a correct call.
There may be some mistakes made but I don't believe these calls rise to awful umpiring. The game has always been played and decided by humans and to their credit have included replay as a way to get the most egregious of plays reversed.
Illegal move by the pitcher, often to deceive the runner. In this case, his move of the glove could be seen as starting to get into the pitching position, leading the runner to take his lead. Balks are called very tightly at the major league level, and it can be maddening to see small moves like that called. But some pitchers would do that, then immediately snap a throw to first to catch the guy leaning, and that's what the rule is there to prevent.
Oh I think I get it myself. If it is foul tipped, it only would count, if the Ball would have bounced. If it is foul tipped right in his glove, like in this video, it should've counted as a strike and so as a strikeout, right?
The first one was sooo bad the runner took his foot on the bag then again I have seen worse in my own games lol
4 года назад
watched the Sox lose to the A's, the home plate umpires in the 3 games were horrendous for both teams, called balls 6 inches off the plate strikes, called strikes , balls...HORRENDOUS
He moved his mitt in a way that suggested he was going to get into pitching position, then failed to do so. This could be seen as deceptive to the runner, so a balk is called. If he needed to signal the catcher, he needed to step off the pitching rubber first.
The one where the 3rd baseman and catcher don't catch it and it bounces foul doesn't matter, it was ruled an infield fly, so what happens afterward is meaningless. The infield fly call supercedes it bouncing foul and you can't overturn it just because of that.
If it bounces foul, it is a foul ball. But in this case, I think the catcher picked it up right at, or just inside the foul line, making it a fair ball. Hard to tell for certain from the camera angle.
it’s the way the rule is written. the issue isn’t the umpiring, it’s the rule. the batter technically has to stay between the two white lines, despite that not being a straight line to the base.
A lot of these are either correct or too close to where they review it and it's overturned Edit: You see that last one like an umpire can see the centimeter gap to where I could have watched it 100 times with out slow motion and not see that
The only call I can say was awful was the Wright tag call. Most the rest of the video is correct calls besides maybe a literal handful of other calls. Majority of the video were correct calls. By like 70-80%...
Obvious that the poster has never umpired nor actually knows baseball rules Most were correct. Several were correct by rule, but the announcers had no idea what the right rules were. A couple were bang bang plays where there's no way without video an umpire could have seen the call correctly and a couple that were clear misses. Maybe next time, post a video of all the right calls umpires make. Or better, post one of you umpiring one game so can pick you apart.
Let’s be honest. This video is not bad umpiring. The only way most of these calls were “bad” was because of slow motion replay. The ball call was 100% on and I would have called that as a high school umpire.
The call, as you can clearly hear in the video, is "Infield Fly if Fair." That, and the umpire pointing at the sky (as you can clearly see in the video) is the correct mechanic for calling it. The call has to be made early so that the runners know to hold their bases--they're not going to get doubled up because they didn't run and the ball wasn't caught. So the only question is where the catcher got that ball after the bounce. It looks to me to be right on the foul line, which would make it a fair ball.
I came here to intentionally get myself pissed off by bad calls by arrogant, old obese umps
Now I'm pissed at the uploader for posting a video of mostly correct or "close" calls and calling them "awful"
Like the very last clip how the hell is the ump supposed to see that.
Yup these were very close, hard for anyone to see plays. Many only apparent on ultra slow mo looks. Some calls were actually correct. Kind of click bait with this upload.. Umps were not very awful
Agree 100%. At least we got to see interesting plays, but the video title is absolutely clickbait.
Seriously 😭
Totally agree! There are FAR more examples of terrible umpiring, why pick these?
A lot of these are correct, and a lot of the wrong ones are VERY close, bang-bang plays, so even if they're wrong, they're not AWFUL.
Agreed. Such clickbait!!
Yeah I completely agree....even some of the pitches were only off by a little bit...I would have called those strikes as well..I played for 12 years and I would not have argued those pitches....CLICKBAIT out the ass
@SAVEGE BOI GAMER I totally agree with you these are bad calls and even though they are close, most are noticeable to the umpires. No clickbait whatsoever.
@@action-packedadventures4056 its complete clickbait, half the plays you never even see what the final result is. and the other half the umps were right. i'm thinking the youtube account made some burners to try and make itself not look useless
@@action-packedadventures4056 At 7:14 that call is correct. The pitcher was no longer a fielder once the first baseman got the ball, but still affected the batter/runner's path to the base. That is the definition of obstruction and a dead ball, batter is awarded first, all other runners advance only if forced to by the awarding of first base on the dead ball.
The majority were correct, almost all of the rest were bang-bang plays that anyone could have missed.
Agree. Badly titled.
i think the channel owner didn’t want to create a joe west/angel hernandez lowlight reel
Yeah I understand why umps are hated on because it’s easy to blame them these don’t look incredibly obvious. However fuck Angel Hernandez
@@bigboy-cz3nv Joe West sucks behind the plate, but he’s a pretty solid base umpire.
Yea, creator doesnt know much about baseball
Most of these are genuinely confusing and tough calls lol, props to the umpires for being the ones who have to make the decision
A ton of these are the CORRECT call.
Not true
Traci Tuerke yes true. Dont comment on baseball you clearly dont know shit
Well except at 6:42 like how is he supposed to avoid getting hit by the ball it was clearly the pitchers error.
@@mateo0939 The rule is both feet must be in the running lane, EXCEPT for the last step. Had the Runner done that and gotten hit, then he is PROTECTED. Otherwise, this play was called CORRECTLY. Even though it does suck for the Offense.
@@ButchRahman It's a little iffy. His last step has to be made for the "sole purpose" of touching first base. That looked like he did it intentionally to get in the way. It's hard to say, but the umpire made a judgement call. I agree with him on it based on the video.
Almost all of these are the correct call
I agree
I will forever have the upmost respect for David Wright for how he handled that call...
Utmost
He handled it well but I am still not sure he over-slid the bag honestly.
A lot of these are the correct call....
?
@@frank_da_tank_05 like.....it's called awful umpiring, but the umpires on most of these made the correct calls
"Obi wan voice'
FROM A CERTAIN POINT OF VIEW
Who is Obi Wan?
Just because you don't like or understand the call doesn't mean it's awful umpiring. Several of these are correct calls.
0:29 Infield fly rule. Molina caught the bounce on the foul line. If any part of that ball was fair when he touched it, it counts. Hard to tell from the camera angle.
1:27 A balk, correctly identified by the announcers immediately.
3:03 Clear interference by the batter.
4:05 Interference with the throw by the batter. He has to get out of the way.
4:32 Batter-runner ran into the ball in fair territory. He's out.
4:56 The ball only has to hit the uniform. It doesn't matter if it actually hits the batter's body.
5:30 The runner screened out the fielder in the act of fielding the ball, blocking his view.
6:02 The batter-runner interfered with the fielder in the act of fielding the ball.
6:26 Running lane violation. He needed to run in the running lane in foul territory so as to not interfere with the throw coming in from behind him.
7:13 Obvious obstruction. The pitcher didn't have the ball. The batter-runner shouldn't have to evade him to get to the base.
8:01 Interference by the baserunner on the fielder catching the ball. That ball is dead the second the interference happens, and that runner is out.
Almost every one of the "awful" rules interpretations were correct, and of the judgment call plays, many of them were ones that couldn't be seen with the naked eye, like the last one where the knee goes up off the base for a split second.
5:30 The issue wasn't an interference of the SS (it clearly wasn't).
It was an obstruction just feet from third, with the umpires only protecting him to that base. And this led to a silly out at home when the runner chose to stop playing and start umpiring himself.
@@daveh1758 It appeared to me that the call made by the umpire at 3B was interference made prior to the obstruction, dead ball, runner out. Since the ball was dead, the obstruction never happened. If that was the case, I think it's a borderline call and an umpire's nightmare. If the call was truly obstruction, then no question, he should have been given home. This is one where you pretty much have to look at the original news coverage or play-by-play of the game. We don't get enough of the play-by-play to find out what the ultimate conclusion was.
@@eauhomme Other compilations include that play and devote more replay time to it. It is indeed the obstruction/non-award of home that's the issue.
You're probably looking at 99% of the time this being an easy award of home, but on this particular play, with an extremely shallow left fielder at Fenway quickly getting to the ball, I can see why this could fall into the 1%.
With the bad throw, he would have scored anyway, but he was too busy umpiring instead of just traveling the last 90 feet.
@@daveh1758 Thanks for the clarification. As an umpire, I see the obstruction as an obvious send home. The fielder does not have the ball in hand yet and is indeed a couple steps short, and the runner never slowed down rounding the base, so there is no indication he had intended to stay at third. The obstruction happens right on top of the bag, if not even past it a half-step, so it makes no sense that they would hold him at third. If the fielder already had the ball in his glove or hand and the obstruction happened clearly short of the bag or the runner had slowed coming into the bag, then I could see holding him at third.
As I said, you ...could... call the interference on the runner for screening the shortstop, but that's a very borderline call if (a) the ball is not contacted--an automatic out--and (b) the runner doesn't make a definite motion to slow down or otherwise screen the fielder.
I would say 7:13 is obstruction if the runner didn't step outside the two lines do make contact with the pitcher. This one, to me, was the worst call, and one of the few "bad" ones in this video.
0:28 This is not an awful call, it's absolutely the correct call. Blue was right on top of it with a great look down the line. It's an infield fly (you hear the umpire call "Infield fly if fair!") - batter is out, ball is live, runners may advance at risk of being put out. The ball hit the ground in fair territory, and was not over foul territory before being touched. It is a fair ball. If he had let it go it would almost certainly have been a foul ball (unless it had some wicked spin on it).
And 8:38: "He's clearly off the bag by about a millimeter, which you could only see with the help of this super slo-mo replay. What a terrible call!"
85% of the calls in this video were correct.
you are correct
The question on the infield fly is whether or not the ball was touched while it was over fair or foul territory.
@@alanhess9306 Right. Blue was right on top of it and has a much better look than the camera does. I guess it is close enough to warrant coming out of the dugout to talk about it, but I don't think it qualifies as an awful call.
@@XXelpollodiabloXX Agreed, I can't tell from this angle where the ball was when it was touched. the umpire was looking right down the line.
The strike box on TV has scrutinized umpiring so much that a borderline strike is considered an “awful” mistake. I hope they remove it.
Lmao just cuz someone argues doesn’t make it “awful umpiring”
1. A lot of these were either close or the correct call
2. You are just determined to never let us have some kind of final resolution to these calls, are you?
Some of these were bad, but 80% of the calls were the right calls. Even some, I wouldn't call "awful umpiring", just really close to call. It's hard to see a player clearly pop off the bag for a millisecond & make the call.
@SAVEGE BOI GAMER you are wrong every time you post this, but keep trying. maybe learn about what baseball is first
I mean, most of these were right. There was a few that were missed, but I'd hardly call them awful umpires. The one against the Cardinals in the WS against the Royals was awful, but I'm biased lol
That Tejada deal at 5:31 is ridiculous, yes he was clearly interfered with, but if dude had kept running he would have scored still. Don't assume anything, play hard and don't worry about what the umps do or don't call.
Some of these calls are absolutely correct.
This guy is oblivious of the infield fly rule. “When there are less then two outs, with runners on first and second, or bases loaded and if any infield player makes an attempt to catch, the umpire can call the ball out, even if the ball isn’t caught.”
Greg Gibson calls, infield fly rule, the announcers missed that…47 seconds
You know it’s an awful call when David Wright is arguing
Baseballer24 so true 😂
7:34 "maybe he knows the rules" that was awesome dig on the other broadcaster who doesn't know them and presumably complained that the runner intentionally ran into the pitcher.
I'm very confused by this video. Most of the calls are correct and actually tough technical calls from the umpires (there are exceptions throughout but still). How if this bad umpiring?
1:27 is wrong that is a balk. The pitcher started his motion by moving his hand, but stopped in the middle of his movment. Which should be caled a balk.
I don’t think many of them were wrong and the ones that were wrong didn’t have enough video evidence to overturn the call on the field. Not every controversial call is wrong.
00:28 the most ridiculous thing about that play is that the batter didn't even _consider_ running.
infield fly rule
The one call I see that is bad is at 7:13; the pitcher is in fair ground; if the runner runs into him the runner is obviously out of the first base running lane. So runner should be out.
The runner would have had to alter his path to avoid the pitcher who did not have the ball. That is clearly obstruction. Correct call.
Baserunner interference as it pertains to the running lane only matters on throws in the vicinity of the first base foul line, i.e. from catcher to first base. Now, the fielder has the right of way and that’s where interference could be called but obviously in this case the pitcher doesn’t field the ball and gets in the way of the runner. If Abreu (the fielder) got in the way it would be fine, but that’s not what happened. Pretty clear obstruction by the pitcher.
How is any of this "awful umpiring?"
Even if a call is found to be incorrect, it's human error. Now, with replay, the call can be reviewed. The game at full-speed isn't easy to call.
Give me a break.
I see David wright yelling at ump, I click
"Just call them all out and let God sort it out"
Umpiring can be tough, especially at the little league level because you see things you never see at the pro level. I was calling a game behind the plate with a runner on first, the batter had a 2 ball, 1 strike count. The pitcher threw a ball on the inside half of the plate. The batter swung, but his forearm hit the ball half way to the pitcher. The pitcher threw the ball to first. No call by our base umpire. Runner on first ran to second. What's the call?
The defensive manager claimed the ball was dead because it hit the batter and the runner on second had to return to first. My response was, the bat didn't strike the ball, so it wasn't foul. And since the ball was in the strike zone and the batter swung at it, it was a strike and therefore a live ball. Runner was safe at second and the at bat would resume. He tried to argue I was wrong so I gave him one minute to look at the rules and prove me wrong. After about 45 seconds, he spun around, threw his hands in the air and walked away. Umpiring is one of those thankless jobs.
Dead ball, strike. A ball hitting the batter during a swing is a strike, and if it is strike 3, he's out (it is not a foul ball).
I was once working the bases in a Little League game. Runners on first and second, ball hit to left center. Runner on second clearly scoring, and I'm getting into position to make the call at third, positioning myself between the mound and third. All of a sudden, I hear my partner scream "Brian, get down!" I hit the deck. The throw was an absolute laser home, way too late to get the runner, and headed straight for my ear had I not ducked.
@@Deanrite It is always a dead ball when a batter is hit by a pitch, even when he swings. The count should be 2 and 2 and the runner returns to first base. The defensive manager was right, you were wrong.
This is a really funny video because almost all of these calls were correct
You’ll notice the managers only argue the calls that don’t benefit them. Nobody ever got kicked out of a game for arguing a horrible call that helped them.
A lot of these are questionable but I can see why they would be called because there is a hidden rule. Mostly if the ball touches the player even not in the glove they are out from what I got out of watching baseball. I think the rule is inconsistent tho but I believe it is there.
Uhh the balk call at 1:50 is 100% correct
I was wondering about that. I'm not a pitcher and I don't know all the bauk rules. Thought it was only a bauk if he did that after he came set but wasn't sure.
I hate replay. Baseball has lost it's luster. The umpire making bad calls is part of what made Baseball great back in the..
Most of umpires are too old to see MLB's speed
The infield fly is a rule: if a ball is a pop fly and lands infield it is automatically out
It would not be an infield fly if the ball lands in the infield but bounces foul.
How about awful labeling! Most of the calls were spot on!
The first play. That was a nice slide
2:14 No intent"...yeah, we know which team he is calling the game for.
If a HBP is too close to call, call it a ball.
The umpire didn't call it a HBP because it was too close. He called it a HBP because he saw it hit the uniform. You call it as you see it. You don't wait and think about it.
The fact there is 9 mins of bad calls says something
Many of these calls were correct or so close it is understandable why they were missed. There were not 9 minutes of bad calls.
The second was an infield fly. Hardly an awful call. Doesn't matter if it's going to bounce foul, it's out.
From the MLB Rules, Definition of Terms: If a declared Infield Fly is allowed to fall untouched to the
ground, and bounces foul before passing first or third base, it is a foul
ball. If a declared Infield Fly falls untouched to the ground outside the
baseline, and bounces fair before passing first or third base, it is an
Infield Fly.
@@CastlegarGlenn The catcher grabbed the ball through before the ball went foul. That would make it not a foul would it not? It hit fair and bounced up and was headed foul. If the catcher had let it go foul then it would not have been a correct call but he caught it before it actually went foul I belive
@@truffleshuffle009 Yes, you are correct. The Orioles were contending that the catcher touched it after it crossed over into foul territory, which would have been good for them. Too close to call from the angle we saw, so just as likely a correct call.
The second one was the infield fly rule.
Why was the fly ball to the catcher a bad call? That's an infield-fly rule which requires the batter to be "out."
The question was whether the ball was fair or foul.
Who else wishes David Wright never got hurt
Umpires are gonna miss calls. It’s okay.
How in the world can you have a brick about awful calls by umpires and not include the call that cost Armando Gallaraga his perfect game? So stupid.
Good♥
Every home announcer is gonna agree with the call if its bad or good
There may be some mistakes made but I don't believe these calls rise to awful umpiring. The game has always been played and decided by humans and to their credit have included replay as a way to get the most egregious of plays reversed.
Title correction: incredible umpiring because these guys make the correct calls that we’d never think to make
I never really understood the more advanced rules of baseball. Can someone explain to me what a "Balk" is and what happened @ 4:35 clip?
Illegal move by the pitcher, often to deceive the runner. In this case, his move of the glove could be seen as starting to get into the pitching position, leading the runner to take his lead. Balks are called very tightly at the major league level, and it can be maddening to see small moves like that called. But some pitchers would do that, then immediately snap a throw to first to catch the guy leaning, and that's what the rule is there to prevent.
By 2025 every sport is going to be judged by artificial intelligence more then anything else
1st one was the right call
I miss baseball
player to ump... I dont like your shoes. Ump.... YOURE OUT OF HERE!
Pretty good
Tejada would have been safe had he continued running.
4:25, the throw also should have been better!!
Most of these are not be “upping”, you just don’t know what you’re looking at.
It's not awful umpiring if you can't see every detail of a baseball flying 93mph. It's human error and totally reasonable.
Can somebody explain to me the rule at 2:30. What changes if the ball would have hit the ground? I'm not so much into Baseball.
Oh I think I get it myself. If it is foul tipped, it only would count, if the Ball would have bounced. If it is foul tipped right in his glove, like in this video, it should've counted as a strike and so as a strikeout, right?
I wouldn’t say this is “awful” umpiring I’d say this is “micromanaging” which is worse
Those for the most part were good calls
The first one was sooo bad the runner took his foot on the bag then again I have seen worse in my own games lol
watched the Sox lose to the A's, the home plate umpires in the 3 games were horrendous for both teams, called balls 6 inches off the plate strikes, called strikes , balls...HORRENDOUS
Does this channel even watch baseball? A ton of these are the correct calls... I don't think this channel even knows the rules
Agreed
Are you serious??? You must be an umpire
@@seanbonella Maybe he is an umpire. If he is, he knows more than 90% of those commenting here.
I'm not super familiar with the finer rules of baseball. What was wrong at 1:30? The pitcher signaled something to the catcher, what?
He moved his mitt in a way that suggested he was going to get into pitching position, then failed to do so. This could be seen as deceptive to the runner, so a balk is called. If he needed to signal the catcher, he needed to step off the pitching rubber first.
I umpire pony games and I called a balk on a kid who wiped his nose when set and the coaches flipped out
I'm so confused by the title, most of these are the correct calls.
Watches frame-by-frame replay where there are fractions of an inch in it and that somehow equals bad umpiring!?!?
Should be called awful video package
I don’t understand why because of tough plays umpires are considered “awful” for not getting them right 😠 respect them, there job is so tough!
i’m confused most of these were there right calls. how are they “awful umpires”?
The one where the 3rd baseman and catcher don't catch it and it bounces foul doesn't matter, it was ruled an infield fly, so what happens afterward is meaningless. The infield fly call supercedes it bouncing foul and you can't overturn it just because of that.
If it bounces foul, it is a foul ball. But in this case, I think the catcher picked it up right at, or just inside the foul line, making it a fair ball. Hard to tell for certain from the camera angle.
It must end up fair in order to be called an infield fly. It absolutely matters what happens after it bounces.
In many of these, a player is partly or mostly to blame.
You should do throwing the game
If he’s running in a STRAIGHT line why and it hits him why does the thought of calling him out even go into your head.
it’s the way the rule is written. the issue isn’t the umpiring, it’s the rule. the batter technically has to stay between the two white lines, despite that not being a straight line to the base.
The first one was safe
A lot of these are either correct or too close to where they review it and it's overturned
Edit: You see that last one like an umpire can see the centimeter gap to where I could have watched it 100 times with out slow motion and not see that
Can someone explain to me how tejada was out? It looks like the third baseman interfered to me
99.9999999% of these calls are from angel hernandez
We know it's popular to bash Hernandez, but save it for when he does something wrong. Angel wasn't in any of these clips.
On the second one what happened, I was confused on what was happening there
This guy obviously just picked random clips. The only decent one was David Wright and that was an awful call. Does this guy know baseball rules?
The only call I can say was awful was the Wright tag call. Most the rest of the video is correct calls besides maybe a literal handful of other calls. Majority of the video were correct calls. By like 70-80%...
Obvious that the poster has never umpired nor actually knows baseball rules
Most were correct. Several were correct by rule, but the announcers had no idea what the right rules were. A couple were bang bang plays where there's no way without video an umpire could have seen the call correctly and a couple that were clear misses.
Maybe next time, post a video of all the right calls umpires make. Or better, post one of you umpiring one game so can pick you apart.
A lot of them were the right call😅😅😅
Strike 3 you are out 🤭👌🔥
Does this person know what is a bad call or what because most of them where right waste of are time.
Let’s be honest. This video is not bad umpiring. The only way most of these calls were “bad” was because of slow motion replay. The ball call was 100% on and I would have called that as a high school umpire.
If you don’t run out a pop fly, you should get sent to the minors immediately.
The infield fly call was borderline. I think the problem is it was called too early. It could've been a foul ball.
You like most cubs fans have no idea how infield fly rule works.
The call, as you can clearly hear in the video, is "Infield Fly if Fair." That, and the umpire pointing at the sky (as you can clearly see in the video) is the correct mechanic for calling it. The call has to be made early so that the runners know to hold their bases--they're not going to get doubled up because they didn't run and the ball wasn't caught. So the only question is where the catcher got that ball after the bounce. It looks to me to be right on the foul line, which would make it a fair ball.
How is 1:27 awful that was a balk
Was it a balk because of the glove movement? sorry if it's a dumb question I just don't know .
Totally disagree with the title. Most of these calls are spot on
This is the BEST umpiring I have ever seen, is this click bait? lol
Some of the ones that could be considered wrong is because the ump was not in a position to see what you saw.
You are underrated
These are some tough calls.
The second clip is an In-field Fly. It is a correct call.