-
Posts
9,539 -
Joined
-
Days Won
370
Content Type
Profiles
Forums
Store
Articles
Reviews
Everything posted by maven
-
Why yes, yes he is. Boring meetings and forum sometimes don't mix....Let this be a lesson.
- 11 replies
-
- 5
-
- steal home
- walk
-
(and 2 more)
Tagged with:
-
Your inference is incorrect. Batter 6 is (also) batting out of order, and the umpire should rectify the error (without penalty to the offense, due to the timing of the notification).
- 11 replies
-
- steal home
- walk
-
(and 2 more)
Tagged with:
-
A batted ball can be fair, foul, or a foul tip. The batter does not have to be holding onto the bat for the entire swing in order for him to have batted the ball. Indeed, the batter need not swing at all to have a batted ball. If the pitch goes toward the batter, who ducks, and the ball hits the bat, we play it as a batted ball (fair or foul, usually not a foul tip in that case).
-
File that under "wouldn't that be nice/funny/cool," and never think of it again. Now, coach is responsible for his players' behavior, so if we replace "start with your clean-up hitter" with "start with you," then I have no objection.
-
That's an NBA rule. In HS and NCAA, the non-scoring team gets possession under their opponent's basket and they may run the end line on the throw in. I don't know Olympic/Int'l hoops rules, but would wager it's not the NBA rule. I expect that noumpere's rationale for the NBA rule is at least part of why NBA is different.
-
2 man Double play coverage suggestion. (thought)
maven replied to Richvee's topic in Umpire Mechanics
Not arguing, Rich, just a possible explanation for why a sensible mechanic never caught on. -
2 man Double play coverage suggestion. (thought)
maven replied to Richvee's topic in Umpire Mechanics
I agree that it makes sense, but only for a single situation: R1 only. Downside? One of the virtues of a set of mechanics is simplicity: having multiple mechanics for BU depending on the number of runners, outs, etc. complicates mechanics. Any set of mechanics is a series of compromises, and this one never caught on (for long) at any level, AFAIK. -
Sounds like a question for the league. It's not a baseball game-play rule.
-
A fielder can tag 1B to retire the BR before he touches the base by holding the ball securely in hand or glove and touching 1B with any part of his body. Some codes explicitly state, and others accept, that "secure possession" will survive contact with the base. When the ball pops out during the tag as a result of the fielder tagging the base, that's not secure possession, and thus no tag. I agree with the umpire's ruling.
-
Pitcher stumbles after catching cleat, delivers the ball. Balk?
maven replied to Tog Gee's question in Ask the Umpire
Too many of us use this provision to claim that F1's delivery must be the same every time. That's not what the provision means: as noumpere hints at, the rule specifies an additional (FED) constraint on time of pitch, so that F1 cannot pick after starting his delivery with a habitual motion. -
Pitcher stumbles after catching cleat, delivers the ball. Balk?
maven replied to Tog Gee's question in Ask the Umpire
Maybe. F1 clearly may not walk 5 steps toward HP before delivering the pitch. I'd like to be able to articulate it in fewer than 5 words: too many steps? -
Pitcher stumbles after catching cleat, delivers the ball. Balk?
maven replied to Tog Gee's question in Ask the Umpire
Is the delivery in the video a balk? What provision of the pitching restrictions did he violate? He paused, didn't stop and start, delivered the pitch after stepping toward HP, ball crossed the plate (ish)... what did he violate? Maybe my brain is not grokking this, but I can't see it. As ever, I will counsel against using pro rulings in actual games as a definitive guide for officiating amateur contests. Pro ball has its own rhythm and flow, and everyone on that field expected a balk there. So they got one—maybe this wasn't "smooth and continuous" enough for pro ball, or maybe they ruled that he dropped it rather than throwing it. But we have to be able to explain what F1 did wrong. Catching a cleat isn't illegal, nor a violation of the pitching restrictions. Ugly is not illegal. Different from his other pitches isn't a balk. If we can't explain it, we shouldn't be calling it. Oh, that's my answer to the OP, too. 😎 -
I guess I don't understand who's getting the "benefit" here. If you rule this a foul tip, the offense gets the benefit, because R1 gets to keep his stolen base. If I were the defense, I'd expect this to be ruled a foul ball. Baseball is a game of defense: had you ruled that way, nobody would have said a word—the defense certainly doesn't want R1 on 2B. And the batter fouled off the pitch, so R1 has to return. Play on.
-
Excellent. This will get a lot of play going forward.
-
Agree. At that level, my approach is to call time when the batter takes off. Then I don't have to send anyone back. If the coach becomes angry and complains that I shouldn't have killed it, I ask — loudly — "Coach, you didn't create a scheme to cheat and get yourself a cheap run in a 10U game did you? Is that what you're teaching these kids?" That usually shuts them up. If he's stupid enough to admit it, dump him.
-
First inning? That's early to be so hot. Anyway, I agree with discouraging, "what did you say?" As grayhawk points out, daddy ball coaches don't know what they're allowed to say, so this question won't get processed as a warning. Instead, please consider the following: First, address the first thing, storming out on the field. Put up the stop sign and yell "Stop!" If he runs through that, dump him. If he stops, then say, "Coach, you will not run out here shouting. You may first request time, then come out to ask your question in a normal tone of voice." If he doesn't comply, dump him. If he complies, then have him come out to you. Before his question, say, "Coach, you said 'That's two you've cost us!' Are you accusing me of cheating?" If yes, dump him. If no, then say, "Then we're not having any more of that. Now, you had a question?" And answer his question, preferably in 5 words or fewer. If it's not a question, but a veiled argument, say so. When he thinks he gets to argue with you, say, "Coach, I've answered your question, we're going to resume the game now." If he doesn't return to the dugout immediately, tell him to go there. If he doesn't dump him. Please note that except for step 1, all of this should be conducted in a normal tone of voice with non-confrontational body language.
-
The video is from a pro game, and is not necessarily scalable to amateur or youth baseball. You'll have to use your judgment. A swing is a swing, so if you need a strike you have cover. But I tend not to reward shenanigans or jackassery, and will frustrate efforts in that direction. The call will depend on context. Sometimes, you just gotta umpire.
-
Definition of a strike. It's an "offer" at a pitch, which entails intent to hit it (however fleeting the intention might be on, for instance, a check swing). Other (spurious, gaming the game) reasons for swinging are not offers.
-
Offensive interference at 2nd with bases loaded
maven replied to Arr Gee's question in Ask the Umpire
I think ousafe's question concerned FPSR, which does not apply in OBR. For codes with FPSR, I agree with SHO102's initial response. Without FPSR, in straight OBR, this would violate the "bona fide slide" rule, 6.01(j). R1 is out on the play, BR is out for R1's INT (assuming that's the runner the defense would have played on next). Other runners return to their TOI bases, and I'm pretty sure R2 and R3 had not attained their advance bases at TOI. -
The appeal would be granted only if it is an advantageous fourth out, that is, a situation where granting the appeal nullifies the run. An appeal of another runner missing a base that does not nullify a run is pointless and not ruled on. An advantageous 4th out is (briefly) apparent, as it supersedes and replaces the third out. At that point, it's an actual out (and the formerly third out is merely apparent).
-
No INT (of the kind you mean, resulting in an out) is possible. So drop that. I've already addressed the scenario in which we would not award bases. The ball is dead when it enters dead ball territory, so kill it then. Runners might keep running, but it doesn't count. Sometimes, you just gotta umpire.
-
"Coach, we award bases for the defense putting the ball out of play. That's not what happened, so no award. But the ball's dead, so the runners have to stop at their last legally touched bases." Can be delivered to both coaches (at the same time—they like to know that the other guy is getting the same ruling and info).
-
If the player out of the dugout is allowed to be there, then his team is on offense. When the ball is kicked out of play, kill it and put the runner(s) back. Those runners were going to be able to advance. Now, due to the actions of his team mate, they're going back. That's sufficient penalty (although others are available in the MSU rule book). No, we don't award bases when a thrown ball that was not going out of play is sent out of play by the offense. Remember, that penalty is for the defense putting the ball out of play, not merely for the ball going out of play. If the offense puts the ball out of play, we don't penalize the defense for that.