100% False!Ever see someone scoop the cue ball on a soft draw shot? The shooter is squeezing the cue trying to keep the cue speed slow.
As it was NOT possible for the ref to do the same fifteen feet away from the carom.... wouldn't you agree.
Anyone 15' away telling me it didn't hit the rail when looking at the back side of the ball doesn't know what they are doing.Generally speaking (i.e., not just with pool), I tend to distinguish between a bad call and an incorrect calls. Bad calls are typically incorrect, but not every incorrect call is bad. An incorrect call is one that appears reasonable in real time from the viewing perspective of the official making the call, but replay shows that things didn't happen quite as they appeared to happen from the official's angle. A bad call is a call (or non-call) that is noticeably incorrect in real time from most any viewing angle.
An example of an incorrect call that was not a bad call would be the facemask foul called against the Detroit Lions at the end of regulation when Detroit hosted the Packers during the 2015 NFL season, a game known as the Miracle in Motown. Replay showed that contact with the facemask was minimal and incidental, not justifying a foul being called. However, in real time, it looked like an egregious facemask foul. An example of a bad (no-) call would be Rams at Saints in 2018. There was simply no excuse for the ref missing that clear and obvious foul.
In the Filler vs. Bijsterbosch match, it's tough to say if the cue ball did or did not hit the rail when watching in real time. It might have been an incorrect call, but it wasn't a bad call.
Did 'I' ever use the words, 'Soft or Slow'?You cant hit the cue ball fast but soft or slow but hard. A short stroke doesn't mean you hit the ball soft but muscled it. If all strokes are accelerating at impact the cue ball only knows tip speed and location. Show me these different hits while lagging, the distance the cue ball travels will tell the story.
The ball had enough spin. It shoulda chirped if it touched the cushion.Generally speaking (i.e., not just with pool), I tend to distinguish between a bad call and an incorrect calls. Bad calls are typically incorrect, but not every incorrect call is bad. An incorrect call is one that appears reasonable in real time from the viewing perspective of the official making the call, but replay shows that things didn't happen quite as they appeared to happen from the official's angle. A bad call is a call (or non-call) that is noticeably incorrect in real time from most any viewing angle.
An example of an incorrect call that was not a bad call would be the facemask foul called against the Detroit Lions at the end of regulation when Detroit hosted the Packers during the 2015 NFL season, a game known as the Miracle in Motown. Replay showed that contact with the facemask was minimal and incidental, not justifying a foul being called. However, in real time, it looked like an egregious facemask foul. An example of a bad (no-) call would be Rams at Saints in 2018. There was simply no excuse for the ref missing that clear and obvious foul.
In the Filler vs. Bijsterbosch match, it's tough to say if the cue ball did or did not hit the rail when watching in real time. It might have been an incorrect call, but it wasn't a bad call.
Don't know for sureDoesn't he play at Blue Grass on a regular basis?
You use varying amounts of speed, the more speed the harder you hit, the less speed the softer you hit, its actually quite simple.So, from the first 3 videos I provided You can't ascertain if I'm hitting the CB 'Hard/Force' or not?