Umpire 'distraught' over no-ball call

[AirWolf]

Cape Town - Umpire Richard Illingworth was apparently 'distraught' after realising that his match-changing no-ball call in the first Test between New Zealand and Australia was incorrect, according to match referee Chris Broad.

The incident happened when Australia batsman Adam Voges was on seven in his side's one and only innings. Doug Bracewell bowled Voges, but Illingworth called a no-ball. Bracewell's heel was well behind the line, and Voges went on to score a double century.

http://www.sport24.co.za/Cricket/Proteas/umpire-distraught-over-no-ball-call-20160216

Sidenote: WTF is the point of starting with the place where the article was regurgitate i.e. Cape Town and not where the incident took place i.e. Wellington?

 

[satanboy]

erm....

sob

 

[StellenboschStudent]

How difficult can it be to have some sort of 'touch' technology built into the crease... when the bowler touches the line, it pings in the umpires ear... or something like that.
Or just do all no-ball calls with the 3rd umpire, only takes a second.

 

[bwana]

Sidenote: WTF is the point of starting with the place where the article was regurgitate i.e. Cape Town and not where the incident took place i.e. Wellington?

It's called a dateline and it's usually the place where the article was filed.

 

[BigAl-sa]

http://www.sport24.co.za/Cricket/Proteas/umpire-distraught-over-no-ball-call-20160216

Sidenote: WTF is the point of starting with the place where the article was regurgitate i.e. Cape Town and not where the incident took place i.e. Wellington?

The person who filed the report (in SA) was in CT? Std practice...

 

[AirWolf]

It's called a dateline and it's usually the place where the article was filed.

The person who filed the report (in SA) was in CT? Std practice...

I just find that a bit dumb.

 

[muazzamb]

I have never heard an umpire or ref say they need help. However it is clear that they do need technology to help them make the right decisions and the above scenario should be a wake up call to those dragging their feet in introducing technology to the game.

 

[Nerfherder]

http://www.sport24.co.za/Cricket/Proteas/umpire-distraught-over-no-ball-call-20160216

Sidenote: WTF is the point of starting with the place where the article was regurgitate i.e. Cape Town and not where the incident took place i.e. Wellington?

Its because it came out of the Cape Town news desk. Bloody annoying, they should either leave it out or put the location of the news its self.

 

[Baxteen]

At least with Cricket implementing Technology to help in making calls is something that happens.

we have 3rd umpire reviews on LBW, caught behind, run outs, stumping.
and most of those start with checking for a no ball.

we have the light up bails to help in speeding up the process.

the question is, how would you implement a technology based solution to the no ball call problem, that will not slow down the game?
Maybe RFID tags on the line, and in the tip of the bat and the shoes of the fielding team?

Small, no need to be powered, tan send signals to a reciever in the base of middle stump that send the data back via the mic wire to a computer sitting with 3rd umpire, that can process the data, and pick up if the front foot crossed the line before it made contact.
it will take a bit of mat and a few interesting processes to to get this working, but a small beep in the umpire's ear when the foot has made contact and is not behind the line, leaving the call whit the umpire still, and additionally will give the third umpire a way to go hold up, review the no ball.


and Why do I want an RFID tag in the bottom of the bat? to help more with run out decisions.

 

[AirWolf]

Pressure sensors at the line area - no pressure behind the line = no-ball.

 

[pinball wizard]

Meh. With all the cheating in cricket who cares?

 

[Kelerei]

Pressure sensors at the line area - no pressure behind the line = no-ball.

The problem with this approach is: how does one install pressure sensors in the pitch without affecting the behaviour of said pitch?

 

[stefan9]

The problem with this approach is: how does one install pressure sensors in the pitch without affecting the behaviour of said pitch?

Stump mics and wires for it are already installed in a similar area to where you would install these sensors.

Ball very rarely will be pitched at the crease line so hardly affects it.

 

[AirWolf]

No-balls are a big problem, and whatever they decide, cricket definitely needs a new standard that involves technology.

 

[Kelerei]

Stump mics and wires for it are already installed in a similar area to where you would install these sensors.

Ball very rarely will be pitched at the crease line so hardly affects it.

Close to, but that makes the difference. The stump mic and wires are placed behind the stumps and therefore will not impede on the pitch of the ball (unless something like this happens). Forward of the bowling crease and it's a different story entirely -- in fact, the area you describe is often aimed at by spinners in the latter stages of a first-class fixture.

One also has to consider the effects on the bowler's run-up. A few weeks ago, I was scoring a club fixture, and there was a significant hump on the pitch, behind the bowler's crease, but at the point where the fast bowlers would enter their delivery stride. After the first 5 overs, 9 no-balls had been bowled; the hump was affecting the bowlers that much.

I'm all for technology to improve the game, but I firmly believe that anything intruding on the pitch between the two bowling creases should not be considered, not now, not ever. I believe that some RFID/Hawkeye type solution would be the least intrusive, and still achieve the desired results.