The Official Forum  

Go Back   The Official Forum > Basketball
Register FAQ Community Calendar Today's Posts Search

Reply
 
LinkBack Thread Tools Rate Thread Display Modes
  #1 (permalink)  
Old Tue Nov 17, 2015, 12:56am
Official Forum Member
 
Join Date: Nov 2015
Posts: 127
Just seemed like the logical: clock was 26.2 and now the clock says 15.9?
BTW: with my remote in-hand I had the "touch" at 16.9.
I'm more interested in why neither official said: the clock went from 26 to 15 and we had no violation... Crap, either my count was off or the clock didn't stop in time.
Q. If they go to the monitor to review clock stoppage... Is the ten second violation "not reviewable"?
My intent is not to be disparaging or negative, just seeking clarification.
Reply With Quote
  #2 (permalink)  
Old Tue Nov 17, 2015, 01:22am
Do not give a damn!!
 
Join Date: Jun 2000
Location: On the border
Posts: 30,558
You cannot use replay for that violation, it is that simple.

Peace
__________________
Let us get into "Good Trouble."
-----------------------------------------------------------
Charles Michael “Mick” Chambers (1947-2010)
Reply With Quote
  #3 (permalink)  
Old Tue Nov 17, 2015, 02:01am
Official Forum Member
 
Join Date: Jan 2012
Location: West Orange, NJ
Posts: 2,583
Quote:
Originally Posted by Refhoop View Post
Just seemed like the logical: clock was 26.2 and now the clock says 15.9?
BTW: with my remote in-hand I had the "touch" at 16.9.
I'm more interested in why neither official said: the clock went from 26 to 15 and we had no violation... Crap, either my count was off or the clock didn't stop in time.
Q. If they go to the monitor to review clock stoppage... Is the ten second violation "not reviewable"?
My intent is not to be disparaging or negative, just seeking clarification.
To follow up on Jeff's comment - as well as my previous post - the only way this can be reviewed is to correct a clock error. You can't go back and call the violation (if there is a violation). Think of it this way: If officials miss a travel - or another violation or a common foul - they can't go back and call it using video review. The same theory applies here.
__________________
"Everyone has a purpose in life, even if it's only to serve as a bad example."
"If Opportunity knocks and he's not home, Opportunity waits..."
"Don't you have to be stupid somewhere else?" "Not until 4."
"The NCAA created this mess, so let them live with it." (JRutledge)
Reply With Quote
  #4 (permalink)  
Old Tue Nov 17, 2015, 08:31am
Courageous When Prudent
 
Join Date: Jan 2006
Location: Hampton Roads, VA
Posts: 14,950
Quote:
Originally Posted by Refhoop View Post
Just seemed like the logical: clock was 26.2 and now the clock says 15.9?
BTW: with my remote in-hand I had the "touch" at 16.9.
I'm more interested in why neither official said: the clock went from 26 to 15 and we had no violation... Crap, either my count was off or the clock didn't stop in time.
Q. If they go to the monitor to review clock stoppage... Is the ten second violation "not reviewable"?
My intent is not to be disparaging or negative, just seeking clarification.
The clock went to 16.9 according to you, so that right there tells you why there was no 10-second violation.

You're only question should be is why didn't they put the 1 second back on the clock, not why wasn't there a violation.

Also, as already pointed out, once the shot clock gets turned off, a visible count is used, not the game clock for 10-second violations.
__________________
A-hole formerly known as BNR
Reply With Quote
  #5 (permalink)  
Old Tue Nov 17, 2015, 09:52am
AremRed
Guest
 
Posts: n/a
I saw the game, it was weird that there was a delay in the clock stopping because they were using PTS. Perhaps 15.9 was when their whistle went off. It probably would have been the best idea and review the exact time of the foul so everyone could be assured the foul happened inside the 10 second window but they were using PTS and probably thought it was pointless.
Reply With Quote
  #6 (permalink)  
Old Tue Nov 17, 2015, 11:20am
Official Forum Member
 
Join Date: Jan 2012
Location: West Orange, NJ
Posts: 2,583
Quote:
Originally Posted by AremRed View Post
I saw the game, it was weird that there was a delay in the clock stopping because they were using PTS. Perhaps 15.9 was when their whistle went off. It probably would have been the best idea and review the exact time of the foul so everyone could be assured the foul happened inside the 10 second window but they were using PTS and probably thought it was pointless.
Nothing would have changed with the foul regardless of whether it was inside the 10-second window. The violation wasn't called. It's done.

Regarding PTS: It ain't foolproof. I had a chance to use it in a scrimmage earlier this month. The game clock operator told me he always starts/stops the clock at the console because in his building PTS has been known to be cranky. He's the backup so it makes sense the clock will start/stop a bit late.
__________________
"Everyone has a purpose in life, even if it's only to serve as a bad example."
"If Opportunity knocks and he's not home, Opportunity waits..."
"Don't you have to be stupid somewhere else?" "Not until 4."
"The NCAA created this mess, so let them live with it." (JRutledge)
Reply With Quote
Reply

Bookmarks


Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is On
Trackbacks are On
Pingbacks are On
Refbacks are On


Similar Threads
Thread Thread Starter Forum Replies Last Post
Possible BI no-call: San Diego State/Cincinnati bballref3966 Basketball 5 Thu Dec 18, 2014 01:34pm
BYU Utah state breakaway foul followed by scrum vid request Sharpshooternes Basketball 7 Fri Dec 12, 2014 11:26am
BYU and San Diego State (Video) Sharpshooternes Basketball 18 Thu Nov 27, 2014 12:43am
Utah County, Utah Refs rotationslim Basketball 7 Wed Oct 22, 2008 12:44pm
New to San Diego James Neil Baseball 26 Sun Mar 11, 2007 09:32pm


All times are GMT -5. The time now is 02:19am.



Search Engine Friendly URLs by vBSEO 3.3.0 RC1