Florida v. Louisville
 

<iframe width="560" height="315" src="https://www.youtube.com/embed/LRYS6Xrp8JA" frameborder="0" allowfullscreen></iframe>

I think it was a good no-call regarding a potential backcourt violation; but it looked more to me like a PC regarding any foul on the play.

No B/C definitely. Couldn't tell watching the game live and didn't have it on DVR.

I'm still iffy on the block but I give Hess the benefit of doubt. But watching the replay, just noticed it was a split second away from a 10-second count.

(thanks apg)

If I were the opposing coach, I'd ask how close it was to a 10-second violation. (As he wasn't counting during the time of this clip.)

The block is the "safe" call. I thought either of the two first ones were closer to a block then the one he actually calls.

No B/C. I wasn't sure if the referee was signaling that it was tapped or that he was dribbling, therefore 2 feet and the ball needed to cross. Either way I didn't like the signal he was using to communicate.

That is a perfect example of the 3-point rule for a dribbler crossing the division line....legal.

I'm going to have to give you the chance to explain exactly what you mean by that because it seems as if you are saying that the right call was a PC, but that the official lacked the courage to make it.

So please tell me what a "safe call" is.

i'm curious too!

Ssssaaaaffffeeeee!!!!!
 

That's the call that I make when the batter/runner touches first base bag before the ball is caught by the first baseman.
OOPS!! Wrong forum - me bad!! ;) :D

Agreed. A good video for training purposes, too.

Thanks for the chance :D

I'm sure we've all had a similar play where we pass on the first one, pass on the second one (thinking, that's marginal, but it's getting closer and closer to illegal) than the third one comes and bam we hit the defender with the foul. In this case, I felt the defender was legal on the third one, but I feel he was penalized as a culmination of the previous ones.

But when I look at the play that was penalized, the defender is legal and the offense extends a forearm. So either it's a No Call or it's Player Control, we can't penalize the defense on that play alone.

That's what I meant by "safe call"

I don't know about his particular courage, but I'm pretty sure you don't make it to that level of being a referee without courage.

Well, the calling official was Karl Hess, so we know he doesn't always play it "safe" :D

Before putting a whistle on it he probably asked himself, "why did he push off?"
Then the contact by the defender that he initially deemed marginal became illegal.
I can see his focus being on the potential b/c play... twice, as opposed to the contact by the defender.

Our eyes only see what our mind tells us we are looking at.

But he happened to push off on the only play, in my view, where the defender was legal. Is this a good time to penalize?

In a perfect world we want to get RSBQ perimiter plays immediately. But when your mind tells your eyes to watch the division line, twice in one transition (uncommon) I can see him not getting it then asking himself "did the defender do something a fraction of a second earlier to make the offense push off?"

Is it much different than getting the foul call a second or two later after the offensive player steps OOB or travels?

Right, I believe that's where having a feel for the game comes into play.

If he called the p/c here, Im sure coach wouldve been like, "call the first foul!"

I think it's different only in the timing. If the defender pushes the offensive player 4 steps ago and then the player goes OOB, that's a little late to penalize.

I think in this play, it was also too late to penalize.

Exactly! and he would have been correct. Which is why I categorized this call as the "safe' call.

Whats with all the "late" stuff?? See the whole play & adjudicate properly.
Late & right trumps quick & wrong, all day, every day.

Under the circumstances (potential b/c twice) I believe this to be a "correct" call instead of a "safe" call.

I agree, but there is such a thing as too late.



I don't agree. But I can see the argument.

Example please...

Place yourself in Hess' shoes, you have a funky misdirection at the timeline... twice. You mean to tell me your mind isnt going to be focused on 2 feet, the ball & the line more than the contact on the offensive guy.

Flirting with the timeline & defensive pressure is always a tough play in real time.

This play :D



I haven't seen the video since last night, so my memory may be a little foggy. But I remember thinking I would have called the first contact as a hand check. But he obviously ruled it incidental no call. Which then lead to the whole series of backcourt non violations.

For the record, he nailed the no call on the possible violations.

But my point remains, if you let the first couple of contacts go, its hard to justify penalizing the defense on the one play he decides to actually not foul.

I guess we'll agree to disagree...

It would be hard to justify if he just blew his whistle like it was a routine call. But did you see his verbal skills & big table presence?

Veteran guys say, we can turn our million dollar call into a cheap call & turn nickle & dimers into a million dollar call, depending on what we do post-whistle.

Take a look at Pitino after the whistle, dude is calling the next play.

Thing is that the first misdirection at the timeline was caused by illegal contact by B1. The next 2 times there is contact it is with A1 warding off a legal B1.

The first contact by B1 is one example of the spotty RSBQ officiating I mentioned in another thread.

Absolutely! Not saying he was correct in missing the first one, but I totally understand how it happened.

Honestly though, the defender with LGP appears to move forward into the dribbler on all 3 instances.