WEBVTT - Sports Cameras

0:00:00.280 --> 0:00:02.840
<v Speaker 1>Brought to you by the reinvented two thousand twelve camera.

0:00:03.160 --> 0:00:08.920
<v Speaker 1>It's ready. Are you get in touch with technology? With

0:00:09.039 --> 0:00:17.880
<v Speaker 1>tech Stuff from how stuff works dot com. Hello again, everyone,

0:00:17.920 --> 0:00:20.320
<v Speaker 1>Welcome to tech Stuff. My name is Chris Poulette and

0:00:20.360 --> 0:00:22.439
<v Speaker 1>I am an editor at how stuff works dot com.

0:00:22.480 --> 0:00:25.440
<v Speaker 1>Sitting across from me as usual as senior writer Jonathan Strickland.

0:00:25.560 --> 0:00:31.240
<v Speaker 1>Oh and that's a bad miss wice. I like that one. Yeah.

0:00:32.080 --> 0:00:36.720
<v Speaker 1>So today we're going to talk about some interesting technology. Um,

0:00:36.760 --> 0:00:39.640
<v Speaker 1>and this was something that has been requested of us

0:00:39.680 --> 0:00:46.000
<v Speaker 1>from a couple of different people. We're gonna talk about sports, specifically,

0:00:46.159 --> 0:00:50.840
<v Speaker 1>specifically hawkeye, right, but but there are other sports we

0:00:50.840 --> 0:00:53.159
<v Speaker 1>we actually we struggled with what we were going to

0:00:53.240 --> 0:00:59.200
<v Speaker 1>call this podcast because down yep I had said hawkeye

0:00:59.440 --> 0:01:03.360
<v Speaker 1>not an avenger, but was told that that was not

0:01:04.200 --> 0:01:08.360
<v Speaker 1>s c O worthy. Well, I you know, when we

0:01:08.360 --> 0:01:13.760
<v Speaker 1>we started thinking about the technology used in sports officiating

0:01:13.760 --> 0:01:18.080
<v Speaker 1>and sports broadcasting, they're all kinds of technologies that they

0:01:18.160 --> 0:01:21.280
<v Speaker 1>used for for a variety of different things. And um,

0:01:21.360 --> 0:01:25.440
<v Speaker 1>Jonathan and I researched some of the same technologies and

0:01:25.520 --> 0:01:27.640
<v Speaker 1>some of different technologies, and in fact, I'm not sure

0:01:27.640 --> 0:01:29.400
<v Speaker 1>we'll get to everything we looked at. We may have

0:01:29.480 --> 0:01:31.720
<v Speaker 1>to come back to it in the future, write it

0:01:31.760 --> 0:01:33.840
<v Speaker 1>down and and and come back to some of it.

0:01:33.880 --> 0:01:37.720
<v Speaker 1>But specifically, we wanted to talk about the Hawkeye officiating

0:01:37.720 --> 0:01:39.440
<v Speaker 1>system because that's one of the topics that both of

0:01:39.520 --> 0:01:41.040
<v Speaker 1>us worked on. And if you haven't heard of this,

0:01:41.959 --> 0:01:45.880
<v Speaker 1>um it may depend on which sports you follow. Hawkeye

0:01:45.920 --> 0:01:49.760
<v Speaker 1>is used. Americans probably would know what best for tennis.

0:01:50.640 --> 0:01:53.800
<v Speaker 1>If you're a tennis fan, you know that for years

0:01:53.800 --> 0:01:57.760
<v Speaker 1>they've used systems to try to help them officiate whether

0:01:57.840 --> 0:02:01.400
<v Speaker 1>or not the ball hits on the line or next

0:02:01.440 --> 0:02:04.000
<v Speaker 1>to the line, Is it in? Is it out? Uh?

0:02:04.200 --> 0:02:07.600
<v Speaker 1>Is Wacknrow going to throw a complete fit that really

0:02:07.600 --> 0:02:09.800
<v Speaker 1>has almost nothing to do with whether or not the

0:02:09.800 --> 0:02:11.280
<v Speaker 1>ball was in or ound. No, but there's like a

0:02:12.200 --> 0:02:14.560
<v Speaker 1>chance that will happen. Yes, and it's always entertaining when

0:02:14.560 --> 0:02:18.120
<v Speaker 1>he does. It was wonderful anyway, But yeah, and to

0:02:18.520 --> 0:02:21.920
<v Speaker 1>varying degrees, Hawkeye is the newest, I would guess, newest system,

0:02:22.560 --> 0:02:24.320
<v Speaker 1>or at least the newest one I've heard of that's

0:02:24.440 --> 0:02:28.520
<v Speaker 1>used for this purpose. And it's highly highly accurate, and

0:02:28.560 --> 0:02:31.240
<v Speaker 1>I see I see in looking into it in greater depth,

0:02:31.320 --> 0:02:33.760
<v Speaker 1>why people are so interested in it. Yeah, and it's

0:02:33.800 --> 0:02:36.120
<v Speaker 1>not just used in tennis, of course, that's that's what

0:02:36.200 --> 0:02:38.200
<v Speaker 1>Chris was mentioning. That was the one that the American

0:02:38.280 --> 0:02:41.240
<v Speaker 1>folks would probably be most familiar with, but it's also

0:02:41.320 --> 0:02:44.640
<v Speaker 1>been used quite a bit in cricket, which as I

0:02:44.680 --> 0:02:46.920
<v Speaker 1>studied and as I learned more and more about the

0:02:46.919 --> 0:02:51.400
<v Speaker 1>hawkeye system, I realized that compared to cricket, hawkeye is

0:02:51.520 --> 0:02:59.160
<v Speaker 1>really easy to understand. Cricket is impenetrable. I seriously, you

0:03:00.040 --> 0:03:03.440
<v Speaker 1>it's an asseason. All the folks out there playing cricket,

0:03:03.520 --> 0:03:07.400
<v Speaker 1>it's pretty much everybody. How do you even understand what's happening?

0:03:07.520 --> 0:03:09.480
<v Speaker 1>Like do you wake up in the middle of the

0:03:09.520 --> 0:03:12.240
<v Speaker 1>game and say, are you just making the rules up

0:03:12.240 --> 0:03:15.480
<v Speaker 1>as you go along? Seriously, I don't understand. Yeah, you

0:03:15.480 --> 0:03:17.000
<v Speaker 1>know you're gonna get hate mail for that. And we

0:03:17.040 --> 0:03:19.360
<v Speaker 1>need to have a podcast just on cricket so I

0:03:19.360 --> 0:03:22.000
<v Speaker 1>can listen to it, because I sure as heck couldn't

0:03:22.320 --> 0:03:24.639
<v Speaker 1>talk about all right, anyway, that's neither here nor there.

0:03:25.080 --> 0:03:29.360
<v Speaker 1>So well, it's the too share similarities in that you

0:03:29.400 --> 0:03:34.000
<v Speaker 1>have a smallish balls being thrown or hit, and the

0:03:34.000 --> 0:03:36.559
<v Speaker 1>thing is you have to tell whether or not it's

0:03:36.680 --> 0:03:41.440
<v Speaker 1>landing in a certain spot. Um And what hawkeye does

0:03:41.560 --> 0:03:45.400
<v Speaker 1>It can it can tell you, uh, for one thing,

0:03:45.440 --> 0:03:47.360
<v Speaker 1>where the ball is hitting, whether it's in or out

0:03:47.920 --> 0:03:50.960
<v Speaker 1>hits on online. But it also can tell you it

0:03:50.960 --> 0:03:54.960
<v Speaker 1>can give you an idea of the distribution of where

0:03:55.000 --> 0:03:57.800
<v Speaker 1>the ball is landing. And it's a lot easier to tell,

0:03:58.000 --> 0:04:00.360
<v Speaker 1>you know, for example, where a a sock car ball

0:04:00.440 --> 0:04:02.840
<v Speaker 1>or a football or football depending on how you look

0:04:02.840 --> 0:04:05.960
<v Speaker 1>at it, or a basketball, those those balls are are large,

0:04:06.360 --> 0:04:10.200
<v Speaker 1>considerably larger, and they're easier to spot. But yeah, I mean,

0:04:10.560 --> 0:04:13.160
<v Speaker 1>trying to follow something like a hockey puck or a

0:04:13.200 --> 0:04:17.200
<v Speaker 1>cricket ball or a tennis ball is or baseball you

0:04:17.240 --> 0:04:20.000
<v Speaker 1>know there. That's why a lot of these technologies are

0:04:20.000 --> 0:04:24.760
<v Speaker 1>being developed to help augment human ability to see where

0:04:24.800 --> 0:04:27.320
<v Speaker 1>it's going and maybe give us some insight on how

0:04:27.360 --> 0:04:30.000
<v Speaker 1>to play the game a little better. Yeah, So in hawkeye,

0:04:30.040 --> 0:04:33.200
<v Speaker 1>for I mean, it's it's not unusual to think of

0:04:33.440 --> 0:04:36.719
<v Speaker 1>cameras on a sporting event and cameras being used to

0:04:36.760 --> 0:04:40.200
<v Speaker 1>try and determine whether or not a ball has passed

0:04:40.240 --> 0:04:42.640
<v Speaker 1>out of play, and that we've seen that in lots

0:04:42.680 --> 0:04:44.400
<v Speaker 1>of different sports, and you know, you'll see it in

0:04:44.400 --> 0:04:46.839
<v Speaker 1>football even then, where you'll you know, they'll have to

0:04:46.880 --> 0:04:49.400
<v Speaker 1>do a slow motion replay and the referees will be

0:04:49.760 --> 0:04:51.839
<v Speaker 1>looking at to make sure that the call they made

0:04:51.920 --> 0:04:55.360
<v Speaker 1>was an accurate call um if their call has been challenged.

0:04:55.400 --> 0:04:57.520
<v Speaker 1>The same thing in other sports. There are other sports

0:04:57.560 --> 0:05:00.919
<v Speaker 1>where you are allowed to challenge the ruling of a

0:05:00.960 --> 0:05:05.760
<v Speaker 1>referee or umpire and uh, and then you usually have

0:05:05.920 --> 0:05:09.640
<v Speaker 1>either a moment where the referees will talk amongst themselves

0:05:09.760 --> 0:05:13.560
<v Speaker 1>or they will refer to whatever the tape is right right.

0:05:13.680 --> 0:05:15.800
<v Speaker 1>Of course, there is much debate about whether or not

0:05:15.920 --> 0:05:18.880
<v Speaker 1>this is okay or not, and whether, you know, should

0:05:18.960 --> 0:05:23.400
<v Speaker 1>we bring technology into it? Should it just be like

0:05:23.520 --> 0:05:26.680
<v Speaker 1>human error is part of the game, and therefore it's

0:05:26.720 --> 0:05:28.000
<v Speaker 1>part of the game, both on the part of the

0:05:28.000 --> 0:05:31.200
<v Speaker 1>players and the officiates. And other people are saying, can

0:05:31.240 --> 0:05:33.800
<v Speaker 1>we please just take the officiate error out so that

0:05:33.880 --> 0:05:36.279
<v Speaker 1>we just have to worry about the player or well,

0:05:36.320 --> 0:05:41.120
<v Speaker 1>considering how good the technology has gotten, it's understandable that

0:05:41.200 --> 0:05:46.840
<v Speaker 1>this debate has continued because hawkeye itself is at least

0:05:46.839 --> 0:05:51.040
<v Speaker 1>according to my research, accurate within three point six millimeters,

0:05:51.160 --> 0:05:53.800
<v Speaker 1>possibly a little bit better. At least according to the

0:05:53.800 --> 0:05:58.440
<v Speaker 1>person who invented it, Dr Paul Hawkins. Now hawk, Okay,

0:05:58.480 --> 0:06:01.920
<v Speaker 1>you feel like I've heard that Plkins. At any rate.

0:06:02.800 --> 0:06:07.520
<v Speaker 1>The the the interesting thing to me about hawkeye is

0:06:07.560 --> 0:06:13.039
<v Speaker 1>not that it's it's not that it's it's a you know,

0:06:13.480 --> 0:06:17.000
<v Speaker 1>a complex camera system. That part's interesting. But what's really

0:06:17.040 --> 0:06:21.560
<v Speaker 1>interesting to me is that using these cameras and triangulating

0:06:21.680 --> 0:06:26.280
<v Speaker 1>the images captured by these different cameras um and measuring

0:06:26.440 --> 0:06:29.080
<v Speaker 1>the speed of the ball and the path of the ball,

0:06:29.640 --> 0:06:33.080
<v Speaker 1>Hawkeye is able to project where that ball would have

0:06:33.279 --> 0:06:37.640
<v Speaker 1>gone had it not encountered something. All Right, So this

0:06:37.720 --> 0:06:41.080
<v Speaker 1>is not necessarily important in every sport, but in some

0:06:41.120 --> 0:06:43.440
<v Speaker 1>sports it means a great deal. This is where we

0:06:43.440 --> 0:06:45.640
<v Speaker 1>get back to cricket, where I was having a really

0:06:45.640 --> 0:06:47.839
<v Speaker 1>hard time figure out why do you even need this

0:06:47.920 --> 0:06:51.200
<v Speaker 1>for cricket? Um Because for those of you who are

0:06:51.279 --> 0:06:53.960
<v Speaker 1>cricket fans who or perhaps you're not familiar with say

0:06:53.960 --> 0:06:58.520
<v Speaker 1>American baseball, we don't really look at replays for baseball

0:06:58.760 --> 0:07:03.640
<v Speaker 1>that that doesn't really have been well often. Yeah, and

0:07:03.800 --> 0:07:05.960
<v Speaker 1>that's another one of those things that keeps coming up,

0:07:06.279 --> 0:07:09.080
<v Speaker 1>should there be should there be a replay system in baseball?

0:07:09.240 --> 0:07:10.720
<v Speaker 1>So That's why I was wondering, like, why do you

0:07:10.760 --> 0:07:12.880
<v Speaker 1>need it for? Why do you need it for a cricket? Well, cricket,

0:07:12.960 --> 0:07:15.280
<v Speaker 1>you know, they have their elements in cricket that are

0:07:15.280 --> 0:07:18.760
<v Speaker 1>similar to baseball. But that just fools you. It reels

0:07:18.800 --> 0:07:20.720
<v Speaker 1>you in and then think makes you think you understand

0:07:20.720 --> 0:07:22.560
<v Speaker 1>how what's happening, but you really don't. Well, the two

0:07:22.600 --> 0:07:25.760
<v Speaker 1>sports are cousins, they do share some similarity. So the

0:07:26.320 --> 0:07:31.960
<v Speaker 1>batsman in cricket stand in front of the stumps right

0:07:32.000 --> 0:07:34.960
<v Speaker 1>the wicket based based on what I know of cricket. Okay,

0:07:35.040 --> 0:07:39.640
<v Speaker 1>so you have the bowler who lobs the ball, uh,

0:07:40.160 --> 0:07:43.120
<v Speaker 1>and the bowler's aim is to knock over the wicket,

0:07:43.200 --> 0:07:45.840
<v Speaker 1>to knock over the stumps, and the batsman is defending

0:07:45.840 --> 0:07:47.440
<v Speaker 1>the stomps, trying to hit the ball out of the

0:07:47.440 --> 0:07:51.840
<v Speaker 1>way and earn runs. Well, sometimes the ball will hit

0:07:52.040 --> 0:07:59.120
<v Speaker 1>the batsman and there there is a a a term

0:07:59.200 --> 0:08:02.120
<v Speaker 1>called leg for wicket, which is essentially meaning that the

0:08:02.120 --> 0:08:06.160
<v Speaker 1>batsman's body has has encountered the ball and that the

0:08:06.200 --> 0:08:09.600
<v Speaker 1>ball would have continued had the batsman not gotten in

0:08:09.640 --> 0:08:12.520
<v Speaker 1>the way and then knocked the wicket over. Well, clearly

0:08:12.560 --> 0:08:17.040
<v Speaker 1>that would be an unsportsmanlike way to prevent the bowler

0:08:17.160 --> 0:08:21.600
<v Speaker 1>from hitting the wicket. So hawkeye has been used in

0:08:21.640 --> 0:08:25.280
<v Speaker 1>cricket to project where the path of the ball would

0:08:25.280 --> 0:08:28.160
<v Speaker 1>have been had the batter not batsman, not been in

0:08:28.200 --> 0:08:31.320
<v Speaker 1>the way. So the idea is that, well, sometimes the

0:08:31.360 --> 0:08:33.760
<v Speaker 1>ball would have hit the wicket, sometimes it would have

0:08:33.800 --> 0:08:35.680
<v Speaker 1>bounced over the wicket or bounced to the left or

0:08:35.679 --> 0:08:38.479
<v Speaker 1>to the right of the wicket. And yet if you're officiating,

0:08:38.480 --> 0:08:41.080
<v Speaker 1>if you make this call, uh, you know, you're basing

0:08:41.080 --> 0:08:43.880
<v Speaker 1>it on your own perception of what's happening right, your

0:08:43.920 --> 0:08:47.000
<v Speaker 1>own the angle that you're looking at, and um uh

0:08:47.120 --> 0:08:51.360
<v Speaker 1>you know how closely you're paying attention. Hawkeye is supposed

0:08:51.400 --> 0:08:53.679
<v Speaker 1>to try and take some of that guess workout by

0:08:53.720 --> 0:08:57.680
<v Speaker 1>stating by by measuring the path of the ball, the

0:08:57.679 --> 0:09:03.200
<v Speaker 1>speed of the ball, and and essentially guessing or calculating

0:09:03.360 --> 0:09:05.800
<v Speaker 1>where the future path would have been. So that's a

0:09:05.880 --> 0:09:10.800
<v Speaker 1>very useful feature there because it takes theoretically, if it works,

0:09:11.240 --> 0:09:14.760
<v Speaker 1>it takes the human element, the guessing, the estimation out

0:09:14.800 --> 0:09:18.160
<v Speaker 1>of it. Now, what I find interesting about this is

0:09:18.200 --> 0:09:23.280
<v Speaker 1>that humans we tend to really like this kind of prediction, right,

0:09:23.320 --> 0:09:26.320
<v Speaker 1>predicting where something's going to go based upon the angle

0:09:26.360 --> 0:09:30.280
<v Speaker 1>and the speed. Because if we didn't love that, angry

0:09:30.280 --> 0:09:33.719
<v Speaker 1>Birds never would have become a huge hit. But this

0:09:33.800 --> 0:09:35.880
<v Speaker 1>is serious, I'm serious. Think about it. Think of all

0:09:35.920 --> 0:09:41.479
<v Speaker 1>the games that we play that depend upon accurately assessing

0:09:41.760 --> 0:09:44.640
<v Speaker 1>how the path of an object is moving through the air.

0:09:44.679 --> 0:09:47.720
<v Speaker 1>I mean baseball and football, and both depend on it

0:09:47.720 --> 0:09:49.000
<v Speaker 1>because you have to be at the right place at

0:09:49.000 --> 0:09:51.959
<v Speaker 1>the right time to intercept it. Right. Let's let I

0:09:52.040 --> 0:09:55.400
<v Speaker 1>mean get right down to it. Sports. A lot of

0:09:55.400 --> 0:09:59.079
<v Speaker 1>geeks say that they don't like sports, and that may

0:09:59.200 --> 0:10:02.840
<v Speaker 1>necessarily be true. Two, but there is a geeky element

0:10:02.960 --> 0:10:06.400
<v Speaker 1>to sports otherwise, and I don't know of a sport

0:10:06.520 --> 0:10:08.559
<v Speaker 1>for which this is not true. We wouldn't be keeping

0:10:08.600 --> 0:10:12.560
<v Speaker 1>these elaborate statistics about the you know, well, in the

0:10:12.600 --> 0:10:16.680
<v Speaker 1>fourth quarter, the team that is a head is likely

0:10:16.720 --> 0:10:18.839
<v Speaker 1>to win by seventy six percent of the time. And

0:10:19.080 --> 0:10:21.400
<v Speaker 1>you know, he gets on base, he's likely to score

0:10:22.080 --> 0:10:24.600
<v Speaker 1>you know, four d per cent. You know as well,

0:10:25.440 --> 0:10:27.600
<v Speaker 1>you get into them and totally messed that up. But

0:10:27.600 --> 0:10:31.400
<v Speaker 1>I'm basically they keep a lot of the sports statisticians

0:10:31.480 --> 0:10:36.000
<v Speaker 1>keep all kinds of amazingly uh minute statistics about every

0:10:36.000 --> 0:10:39.040
<v Speaker 1>living every little thing you know, on days when it's

0:10:39.040 --> 0:10:43.520
<v Speaker 1>seventy six degrees and you know this kind of right here,

0:10:43.559 --> 0:10:47.199
<v Speaker 1>his name is Paul Revere. That's just going to open

0:10:47.280 --> 0:10:49.360
<v Speaker 1>another door to another world we don't want to go

0:10:49.400 --> 0:10:54.160
<v Speaker 1>to right now. But yeah, I mean, this is another

0:10:54.160 --> 0:10:57.440
<v Speaker 1>one of those examples of adding technology that's going to

0:10:57.520 --> 0:11:02.840
<v Speaker 1>help us track that much more information about the sport

0:11:03.120 --> 0:11:05.199
<v Speaker 1>and gives us something else to argue about, which is

0:11:05.240 --> 0:11:09.000
<v Speaker 1>another sporting tradition, right, but that's sometimes more entertaining than

0:11:09.040 --> 0:11:12.959
<v Speaker 1>whatever is actually going on, depends on the sport. But

0:11:12.960 --> 0:11:15.840
<v Speaker 1>but yeah, I mean, we're interested in what would have

0:11:16.000 --> 0:11:20.240
<v Speaker 1>happened and how likely is this particular outcome versus that

0:11:20.240 --> 0:11:26.920
<v Speaker 1>particular outcome based on history and the ambient temperature and

0:11:26.960 --> 0:11:29.200
<v Speaker 1>all kinds of other things. And hawkeye does take a

0:11:29.200 --> 0:11:31.640
<v Speaker 1>lot of that into account. That's the one of the

0:11:31.679 --> 0:11:35.400
<v Speaker 1>interesting things about hawkeye is, um, there's a battery of cameras.

0:11:35.960 --> 0:11:39.960
<v Speaker 1>They go around the playing surface, whatever sport you're playing.

0:11:40.480 --> 0:11:42.920
<v Speaker 1>And there are people who want hawkeye used for baseball,

0:11:43.120 --> 0:11:49.400
<v Speaker 1>American baseball, cricket. It's the pitch, right or but yeah,

0:11:49.520 --> 0:11:51.760
<v Speaker 1>but but the cameras are only part of the story,

0:11:51.800 --> 0:11:54.600
<v Speaker 1>as Jonathan pointed out earlier, and yes there is there

0:11:54.640 --> 0:11:58.000
<v Speaker 1>are computers on the back end, but what what really

0:11:58.080 --> 0:12:01.800
<v Speaker 1>fascinated me is and the number cameras depends on whatever

0:12:02.080 --> 0:12:04.839
<v Speaker 1>sport is in question. There might be more or fewer

0:12:04.880 --> 0:12:10.079
<v Speaker 1>depending on the area. Ten yea cameras. It is a

0:12:10.120 --> 0:12:13.319
<v Speaker 1>lot of cameras, especially considering the size of a tennis court.

0:12:13.920 --> 0:12:17.520
<v Speaker 1>But the fascinating thing to me is the prep work

0:12:17.559 --> 0:12:19.800
<v Speaker 1>that takes to go in. And the reason that Hawkeye

0:12:19.800 --> 0:12:23.200
<v Speaker 1>isn't used more wide in a more widespread way is

0:12:23.320 --> 0:12:27.360
<v Speaker 1>it's expensive. You might say, why, it's just some cameras. Well, yeah,

0:12:27.480 --> 0:12:31.480
<v Speaker 1>and they're sophisticated cameras, sure, but you also require people

0:12:31.520 --> 0:12:35.280
<v Speaker 1>to run the system. And part of that is it

0:12:35.320 --> 0:12:39.679
<v Speaker 1>takes prep work. The surface of the playing surface, whatever

0:12:39.720 --> 0:12:43.840
<v Speaker 1>it is, is mapped because it's I can't think of

0:12:43.840 --> 0:12:46.200
<v Speaker 1>a playing surface and it seems flat to us when

0:12:46.200 --> 0:12:47.839
<v Speaker 1>we go out to stand on the on the tennis

0:12:47.880 --> 0:12:51.640
<v Speaker 1>court or or the cricket pitch, but it's not. And

0:12:51.760 --> 0:12:55.080
<v Speaker 1>the computer maps. The Hawkeye system needs to map the

0:12:55.160 --> 0:12:58.400
<v Speaker 1>surface of the ground and where the lines are and

0:12:58.440 --> 0:13:00.520
<v Speaker 1>where all the things are on the feet yield so

0:13:00.600 --> 0:13:03.959
<v Speaker 1>that it knows essentially where everything is. It takes into

0:13:04.000 --> 0:13:08.960
<v Speaker 1>account the temperature and other factors because of course, the

0:13:08.480 --> 0:13:12.319
<v Speaker 1>the tennis court could heat up depending on the color

0:13:12.400 --> 0:13:14.560
<v Speaker 1>of the tennis court, that the material the court is

0:13:14.559 --> 0:13:18.559
<v Speaker 1>made of, grass for example, or clay. Um clay is

0:13:18.559 --> 0:13:20.920
<v Speaker 1>a little bit different because you know the clay, you

0:13:20.960 --> 0:13:25.120
<v Speaker 1>can actually see if you've ever watched a clay court match, uh,

0:13:25.240 --> 0:13:27.520
<v Speaker 1>you'll see that it leaves a little dust mark when

0:13:27.559 --> 0:13:29.600
<v Speaker 1>the when the ball hits. That's easier for them to tell.

0:13:29.600 --> 0:13:33.160
<v Speaker 1>But on other surfaces like grass, it's not as easy

0:13:33.200 --> 0:13:35.800
<v Speaker 1>to tell, but it will heat up and that can

0:13:35.840 --> 0:13:39.600
<v Speaker 1>actually change whether or not the the court is expanding

0:13:39.679 --> 0:13:41.839
<v Speaker 1>or contracting depending on the temperature. And Hawkeye has to

0:13:41.880 --> 0:13:45.760
<v Speaker 1>take all of that information into account um so that

0:13:45.840 --> 0:13:49.160
<v Speaker 1>when the cameras do record the trajectory of the ball,

0:13:49.480 --> 0:13:50.920
<v Speaker 1>and it also needs to know how the ball is

0:13:50.960 --> 0:13:53.680
<v Speaker 1>going to act. Right if you're you're looking at a

0:13:53.679 --> 0:13:56.600
<v Speaker 1>tennis ball, how does a tennis ball behave when it

0:13:56.679 --> 0:14:01.480
<v Speaker 1>hits the earth versus cricket ball. Sure, so it takes

0:14:01.480 --> 0:14:03.120
<v Speaker 1>all of this stuff into account, which is why the

0:14:03.120 --> 0:14:08.359
<v Speaker 1>system is so sophisticated and so remarkably accurate. At tracking

0:14:08.480 --> 0:14:11.679
<v Speaker 1>where the ball is going to land based on you know,

0:14:11.720 --> 0:14:14.720
<v Speaker 1>the way the ball is hit or is thrown, and

0:14:14.960 --> 0:14:17.640
<v Speaker 1>the surface it hits in the in the environment that

0:14:17.679 --> 0:14:20.560
<v Speaker 1>it hits. I think that is absolutely amazing how how

0:14:21.160 --> 0:14:24.080
<v Speaker 1>how it works like that, And it does require human

0:14:24.160 --> 0:14:28.240
<v Speaker 1>intervention too, because people have to operate the equipment beforehand

0:14:28.280 --> 0:14:31.560
<v Speaker 1>and during the game or the match to h to

0:14:31.640 --> 0:14:35.800
<v Speaker 1>make it work. And there's definitely some controversy here as well,

0:14:35.840 --> 0:14:38.120
<v Speaker 1>because you're talking about I mean, yes, Christmas pointing out

0:14:38.160 --> 0:14:40.880
<v Speaker 1>it is very precise as a margin of error around

0:14:40.920 --> 0:14:44.800
<v Speaker 1>three point six millimeters, that's pretty tiny. But should you

0:14:44.960 --> 0:14:49.520
<v Speaker 1>have a situation where Hawkeye is essentially telling you that

0:14:49.640 --> 0:14:52.320
<v Speaker 1>let's let's say that it's a tennis match. Okay, let's

0:14:52.320 --> 0:14:57.000
<v Speaker 1>say it's a Test match and the the the the

0:14:57.040 --> 0:15:00.600
<v Speaker 1>referee has said that it is uh that the ball

0:15:00.720 --> 0:15:05.600
<v Speaker 1>was hit out, and then the other the player who

0:15:05.680 --> 0:15:08.320
<v Speaker 1>hit the ball, challenges that call and so they review

0:15:08.360 --> 0:15:11.680
<v Speaker 1>it and Hawkeye says it was in, but it was

0:15:11.800 --> 0:15:15.480
<v Speaker 1>in by one millimeter. Well that's within that range of

0:15:15.600 --> 0:15:18.080
<v Speaker 1>error at every point six. So then you have to

0:15:18.120 --> 0:15:21.200
<v Speaker 1>decide does that does the is the referees call upheld

0:15:21.920 --> 0:15:25.320
<v Speaker 1>or overturned. If it's overturned, how do you justify that

0:15:25.400 --> 0:15:29.920
<v Speaker 1>when the the the the distance that it was you

0:15:29.960 --> 0:15:32.720
<v Speaker 1>know that that it fell within is less than the

0:15:32.760 --> 0:15:35.560
<v Speaker 1>margin of error for the system. See, there's an all

0:15:35.640 --> 0:15:40.400
<v Speaker 1>new uh, all the dimension of arguing about sports to

0:15:40.440 --> 0:15:42.280
<v Speaker 1>be like, no, that's within the margin of error. You

0:15:42.320 --> 0:15:45.080
<v Speaker 1>cannot you cannot overturn a call based upon that. I

0:15:45.120 --> 0:15:47.880
<v Speaker 1>mean that that that could become that could be the

0:15:47.920 --> 0:15:50.960
<v Speaker 1>outcome of that argument. Or they could say, all right,

0:15:51.000 --> 0:15:54.000
<v Speaker 1>well we're gonna trust the machine over the person even

0:15:54.000 --> 0:15:58.040
<v Speaker 1>though the machine gave us a reading that could theoretically

0:15:58.080 --> 0:16:01.600
<v Speaker 1>be wrong. Um. Yeah, that's the sticky thing. And of course,

0:16:01.600 --> 0:16:04.160
<v Speaker 1>when you're talking about one millimeter, you get into a

0:16:04.200 --> 0:16:07.280
<v Speaker 1>point where without the system, you know, you just have

0:16:07.360 --> 0:16:12.560
<v Speaker 1>to go with whatever the the referee or or officiate says.

0:16:12.600 --> 0:16:15.240
<v Speaker 1>I mean, you don't have you don't have the benefit

0:16:15.320 --> 0:16:19.800
<v Speaker 1>of checking back on with another call, and sometimes you

0:16:19.920 --> 0:16:23.000
<v Speaker 1>just you know, you got to accept the fact that

0:16:23.040 --> 0:16:25.640
<v Speaker 1>there is this element of error that's going to happen

0:16:25.680 --> 0:16:28.880
<v Speaker 1>because there's no perfect system to judge it. I think

0:16:29.000 --> 0:16:31.560
<v Speaker 1>if there were a perfect system, would it change the game?

0:16:34.160 --> 0:16:39.280
<v Speaker 1>It can? Um from what I've seen Uh, A lot

0:16:39.320 --> 0:16:43.120
<v Speaker 1>of the tennis players seem to like Hawkeye. They seem

0:16:43.160 --> 0:16:45.960
<v Speaker 1>to feel that it's pretty accurate. And if you're willing,

0:16:47.760 --> 0:16:50.240
<v Speaker 1>if you're willing to agree that the system is accurate

0:16:50.280 --> 0:16:53.440
<v Speaker 1>and to trust it, then that's one thing. But I

0:16:53.480 --> 0:16:57.040
<v Speaker 1>think you're right, Jonathan that if if a call comes

0:16:57.080 --> 0:16:59.640
<v Speaker 1>within that margin of error, even when you said, yes,

0:16:59.720 --> 0:17:03.240
<v Speaker 1>you know what, I trust this computerized system over the

0:17:03.280 --> 0:17:05.840
<v Speaker 1>official when it's a really tight call like that, I

0:17:06.160 --> 0:17:09.440
<v Speaker 1>believe it to be accurate. If they says one millimeter

0:17:09.520 --> 0:17:13.480
<v Speaker 1>and you go, well, yeah, but it's precise to within three,

0:17:15.320 --> 0:17:17.040
<v Speaker 1>it really could have been out. I mean, I think

0:17:17.080 --> 0:17:20.639
<v Speaker 1>that causes even the people who are really behind the

0:17:20.720 --> 0:17:24.800
<v Speaker 1>technology too, you know, because it's an emotional issue, especially

0:17:24.840 --> 0:17:27.159
<v Speaker 1>when you've been playing hard and it's it's you know,

0:17:27.200 --> 0:17:30.560
<v Speaker 1>it's an important match like you know, the Wimbledon final

0:17:30.680 --> 0:17:33.320
<v Speaker 1>for example, or the French Open, one of the Grand

0:17:33.359 --> 0:17:36.720
<v Speaker 1>Slam championships. It's you know, I think even the people

0:17:36.760 --> 0:17:39.040
<v Speaker 1>that are behind it are going to be a little

0:17:39.600 --> 0:17:43.919
<v Speaker 1>reticent to just trust the machine. But that's that you

0:17:43.920 --> 0:17:46.920
<v Speaker 1>have to trust the humans. If you don't trust the machines. Yeah,

0:17:46.960 --> 0:17:49.000
<v Speaker 1>that that does come down. Yeah, exactly. You're like, well,

0:17:49.119 --> 0:17:52.120
<v Speaker 1>does that mean that something we know of that's accurate

0:17:52.200 --> 0:17:56.040
<v Speaker 1>up to three point six millimeters is somehow worse than

0:17:56.240 --> 0:18:00.400
<v Speaker 1>a humans perception? Is the humans perception actually more accurate

0:18:00.400 --> 0:18:02.960
<v Speaker 1>in this case? I mean it's a delicate subject. And

0:18:03.040 --> 0:18:05.680
<v Speaker 1>like like we said before, with the the clay courts,

0:18:06.359 --> 0:18:08.520
<v Speaker 1>that's where you're you start thinking, hey, maybe we just

0:18:08.560 --> 0:18:11.160
<v Speaker 1>need to start playing on clay a lot, because then

0:18:11.200 --> 0:18:13.199
<v Speaker 1>at least we can look at where the mark is

0:18:13.240 --> 0:18:14.960
<v Speaker 1>and say, all right, now, clearly this is where the

0:18:14.960 --> 0:18:17.800
<v Speaker 1>ball hit and you know the ball, Yeah, the ball

0:18:17.840 --> 0:18:21.320
<v Speaker 1>bounced out, but the ball initially hit within the lines.

0:18:21.400 --> 0:18:23.120
<v Speaker 1>Of course, then you're gonna have all the players who

0:18:23.160 --> 0:18:26.240
<v Speaker 1>specialize on all the other courts say no, no, no, no, no,

0:18:26.240 --> 0:18:29.359
<v Speaker 1>no grass courts where it's at. Yeah, And then you

0:18:29.440 --> 0:18:33.960
<v Speaker 1>have the well, how how accurate is the little dust mark? Right?

0:18:34.560 --> 0:18:38.000
<v Speaker 1>Is that within three millimeters Someone's been standing over there

0:18:38.000 --> 0:18:40.520
<v Speaker 1>stomping a lot. So I'm not going to totally entrust

0:18:40.560 --> 0:18:45.280
<v Speaker 1>that either. Yeah, right here, sports is one that's one

0:18:45.280 --> 0:18:49.119
<v Speaker 1>of the that's one of those issues where uh, seemingly

0:18:49.920 --> 0:18:54.639
<v Speaker 1>tiny events can erupt in huge controversy. Yeah, so at

0:18:54.680 --> 0:18:57.960
<v Speaker 1>any rate, I do think this is a pretty cool

0:18:58.320 --> 0:19:01.320
<v Speaker 1>um device. And when Christmas talking about the back end

0:19:01.359 --> 0:19:06.119
<v Speaker 1>with the computers, they're all obviously running algorithms that allow

0:19:06.280 --> 0:19:11.080
<v Speaker 1>the the Hawkeye system to project where the ball either

0:19:11.640 --> 0:19:13.840
<v Speaker 1>was going to go or it can predict where the

0:19:13.880 --> 0:19:19.800
<v Speaker 1>ball actually landed. UM. The usually if you're talking about triangulation,

0:19:19.800 --> 0:19:22.520
<v Speaker 1>you're talking about at least feeds from at least three

0:19:22.600 --> 0:19:28.120
<v Speaker 1>cameras being the triangle right, and then based upon those

0:19:28.160 --> 0:19:32.680
<v Speaker 1>three those three streams of data, that's what the Hawkeye

0:19:32.720 --> 0:19:36.160
<v Speaker 1>system uses to predict where exactly it landed or where

0:19:36.200 --> 0:19:39.680
<v Speaker 1>it was going to go. Uh. It's a pretty interesting

0:19:39.680 --> 0:19:43.399
<v Speaker 1>system and I would be very interested to see it

0:19:43.560 --> 0:19:46.720
<v Speaker 1>applied to other sports as well. UM. I think, for

0:19:46.800 --> 0:19:48.639
<v Speaker 1>one thing, even if you're not using it as a

0:19:48.680 --> 0:19:53.560
<v Speaker 1>way to to back up calls or overturned calls, it

0:19:53.680 --> 0:19:58.080
<v Speaker 1>could in theory be a really useful system just for

0:19:58.119 --> 0:20:01.920
<v Speaker 1>players and teams and to to really kind of see,

0:20:02.320 --> 0:20:07.200
<v Speaker 1>you know, well, I meant to throw this kind of ball,

0:20:07.280 --> 0:20:09.320
<v Speaker 1>you know, the ball this way, but it actually came

0:20:09.359 --> 0:20:13.280
<v Speaker 1>out that way, or you know, uh, how accurate am

0:20:13.359 --> 0:20:20.040
<v Speaker 1>I when I'm trying to hit the wicket in cricket? Um,

0:20:20.119 --> 0:20:22.119
<v Speaker 1>that sort of thing. It could be really useful, although

0:20:22.160 --> 0:20:25.000
<v Speaker 1>again it's very expensive system, so really you only see

0:20:25.040 --> 0:20:28.040
<v Speaker 1>these things trotted it out for actual games as opposed

0:20:28.080 --> 0:20:31.600
<v Speaker 1>to you know, practices and things like that. Yeah, it's uh,

0:20:31.800 --> 0:20:34.520
<v Speaker 1>it's interesting to note to based on on what you

0:20:34.600 --> 0:20:37.480
<v Speaker 1>just said and the numbers I saw. UM. And I

0:20:37.520 --> 0:20:41.119
<v Speaker 1>should say that I did UM most of my or

0:20:41.160 --> 0:20:43.560
<v Speaker 1>a lot of my research from an article uh in

0:20:43.600 --> 0:20:46.040
<v Speaker 1>the New York Times that appeared in two thousand and

0:20:46.080 --> 0:20:50.919
<v Speaker 1>eight by Aaron Pilloffer. UM. He said, the system itself

0:20:50.960 --> 0:20:56.760
<v Speaker 1>actually costs around a hundred thousand dollars or so. UM.

0:20:56.800 --> 0:20:59.840
<v Speaker 1>That probably goes up a little bit or has gone

0:20:59.880 --> 0:21:02.080
<v Speaker 1>up a little bit in the last couple of years.

0:21:02.720 --> 0:21:04.560
<v Speaker 1>And I think it probably depends on the arena and

0:21:04.600 --> 0:21:06.399
<v Speaker 1>the and the type of system, the number of cameras

0:21:06.400 --> 0:21:09.840
<v Speaker 1>you have to have. UM. It also requires again you

0:21:09.880 --> 0:21:12.280
<v Speaker 1>have to pay people to run the equipment, so it

0:21:12.440 --> 0:21:14.960
<v Speaker 1>is not inexpensive, and it's not the kind of thing

0:21:15.680 --> 0:21:18.080
<v Speaker 1>you know, you'd have to set aside a good chunk

0:21:18.080 --> 0:21:21.760
<v Speaker 1>of change to put that on your practice fields. UM.

0:21:21.840 --> 0:21:24.639
<v Speaker 1>But you know, if you want to be really, really good,

0:21:25.520 --> 0:21:28.240
<v Speaker 1>maybe it's worth it. Yeah, I saw that. I saw

0:21:28.280 --> 0:21:35.320
<v Speaker 1>it was also used in UM the snooker Championships. Really yeah, wow,

0:21:35.400 --> 0:21:37.480
<v Speaker 1>I wen't have how many cameras you would need because

0:21:37.520 --> 0:21:41.720
<v Speaker 1>that's a really small playing surface relative to say a

0:21:41.800 --> 0:21:44.480
<v Speaker 1>cricket pitch. Yes, but you know what that that would

0:21:44.520 --> 0:21:49.119
<v Speaker 1>be fascinating though, because you could you could measure. I

0:21:49.119 --> 0:21:52.159
<v Speaker 1>would assume that a surface that small would be easier

0:21:52.160 --> 0:21:56.400
<v Speaker 1>to map with a computer UM, and the temperature would

0:21:56.400 --> 0:22:00.480
<v Speaker 1>be more controlled because it's something that you do indoors mostly.

0:22:02.040 --> 0:22:05.640
<v Speaker 1>I don't think they don't think they play arena. Yeah,

0:22:05.680 --> 0:22:09.320
<v Speaker 1>but but yeah, that would be kind of interesting. And yeah,

0:22:09.600 --> 0:22:12.520
<v Speaker 1>well the idea is that it'll it'll kind of show

0:22:12.560 --> 0:22:16.840
<v Speaker 1>why shots went awry. Yeah, right, like someone when you

0:22:16.880 --> 0:22:20.640
<v Speaker 1>see a championship snooker player. I'm not gonna make any

0:22:20.720 --> 0:22:23.119
<v Speaker 1>jokes about them, but when you see them line up

0:22:23.119 --> 0:22:25.760
<v Speaker 1>a shot, you think, you know, well, why did that

0:22:25.800 --> 0:22:28.720
<v Speaker 1>shot not work out the way it was planned? And

0:22:29.000 --> 0:22:31.600
<v Speaker 1>that's the ideas that with this system you could actually

0:22:31.640 --> 0:22:36.320
<v Speaker 1>review that particular shot and see what exactly went wrong.

0:22:37.200 --> 0:22:40.440
<v Speaker 1>Was there some sort of imperfection in the table surface

0:22:41.200 --> 0:22:44.920
<v Speaker 1>or was it merely the technique the player used that

0:22:45.640 --> 0:22:49.240
<v Speaker 1>you know, it made a wrong judgment and that's why

0:22:49.280 --> 0:22:53.119
<v Speaker 1>it didn't work out. That's kind of interesting. Yeah, it's funny.

0:22:53.119 --> 0:22:56.280
<v Speaker 1>We're we're past the twenty minute mark of our podcast,

0:22:56.320 --> 0:22:58.680
<v Speaker 1>and and I'm thinking I've already thought of a couple

0:22:58.680 --> 0:23:01.119
<v Speaker 1>of things that I didn't do any research on sports

0:23:01.200 --> 0:23:03.880
<v Speaker 1>related technology that we can talk about later. But yeah,

0:23:03.920 --> 0:23:07.359
<v Speaker 1>I think we can definitely do a couple of sports podcasts.

0:23:07.359 --> 0:23:10.560
<v Speaker 1>And it's I do think that it's an illustration of uh,

0:23:10.600 --> 0:23:12.800
<v Speaker 1>you know, it's not sports aren't just for the athletes.

0:23:12.840 --> 0:23:15.480
<v Speaker 1>There's something for the geeks to get into as well. Yeah,

0:23:15.520 --> 0:23:19.359
<v Speaker 1>I have two very simple camera systems I wanted to

0:23:19.400 --> 0:23:22.640
<v Speaker 1>talk about are not These are not Hawkeye systems. This

0:23:22.760 --> 0:23:24.960
<v Speaker 1>is unrelated to that, but I wanted to talk about

0:23:24.960 --> 0:23:29.000
<v Speaker 1>it because it ties into a podcast we did um

0:23:29.200 --> 0:23:32.560
<v Speaker 1>earlier several months ago. And it also I just think

0:23:32.680 --> 0:23:36.359
<v Speaker 1>is it's kind of those cool innovations in technology that

0:23:36.400 --> 0:23:38.359
<v Speaker 1>aren't as you know, we talked about a lot of

0:23:38.359 --> 0:23:42.240
<v Speaker 1>stuff that's really high tech, you know, complex computer systems

0:23:42.280 --> 0:23:45.200
<v Speaker 1>and high speed like these cameras, and that the Hawkeye

0:23:45.240 --> 0:23:49.280
<v Speaker 1>system uses their high definition, high speed cameras so they

0:23:49.280 --> 0:23:52.520
<v Speaker 1>can slow this action down to a crawl. But not

0:23:52.560 --> 0:23:56.480
<v Speaker 1>all systems need to be quite that complex. And a

0:23:56.520 --> 0:23:58.720
<v Speaker 1>good example of this is I don't have to thank

0:23:58.760 --> 0:24:01.959
<v Speaker 1>Tyler Klang for this, our producer, because he he actually

0:24:01.960 --> 0:24:06.640
<v Speaker 1>sent me the information. UM. Some systems designed by Garrett

0:24:06.680 --> 0:24:12.679
<v Speaker 1>Brown are actually deceptively simple and yet they have really

0:24:12.720 --> 0:24:16.320
<v Speaker 1>helped with capturing footage, specifically for events like the Olympics.

0:24:17.200 --> 0:24:19.560
<v Speaker 1>And Garrett Brown, if that name sounds familiar to you,

0:24:19.720 --> 0:24:23.320
<v Speaker 1>he's the guy who invented the steady cam. So we've

0:24:23.320 --> 0:24:25.960
<v Speaker 1>talked about the steady cam in a previous episode, and

0:24:26.000 --> 0:24:30.640
<v Speaker 1>Garrett Brown has continued to innovate camera systems. UM. He's

0:24:30.720 --> 0:24:34.159
<v Speaker 1>retired from shooting films himself, but he still works on

0:24:34.200 --> 0:24:40.639
<v Speaker 1>designing systems to capture footage in unusual situations and for

0:24:40.720 --> 0:24:44.119
<v Speaker 1>some of those he developed systems for to capture footage

0:24:44.160 --> 0:24:48.240
<v Speaker 1>for the Olympics. One of them is called the mob cam. Now,

0:24:48.240 --> 0:24:52.440
<v Speaker 1>the mob cam is designed for swimming events, so if

0:24:52.480 --> 0:24:56.960
<v Speaker 1>you're watching the races, you know, a swimming race. UM,

0:24:56.960 --> 0:24:59.159
<v Speaker 1>this is the camera that's on the bottom of the

0:24:59.200 --> 0:25:03.160
<v Speaker 1>pool that can take footage shot upward, so you get

0:25:03.160 --> 0:25:06.520
<v Speaker 1>to see the swimmers as they swim through the pool.

0:25:07.520 --> 0:25:11.919
<v Speaker 1>It's actually mounted on a track a little thin track

0:25:12.640 --> 0:25:17.920
<v Speaker 1>and it's operated by pulleys manually. So Garrett Brown would

0:25:17.960 --> 0:25:20.440
<v Speaker 1>demonstrate this by you don't have this pulley system where

0:25:20.880 --> 0:25:24.720
<v Speaker 1>he would have a crank that would be attached to

0:25:24.760 --> 0:25:27.600
<v Speaker 1>a spool and then what he could do is turn

0:25:27.760 --> 0:25:32.120
<v Speaker 1>that and it would pull the line which would then

0:25:32.760 --> 0:25:36.440
<v Speaker 1>and pull the the camera on the track under the water,

0:25:36.760 --> 0:25:38.960
<v Speaker 1>so you could follow along with the swimmers, and he

0:25:38.960 --> 0:25:40.800
<v Speaker 1>would watch on a monitor so he could keep the

0:25:40.920 --> 0:25:42.960
<v Speaker 1>right speed, and then when it would get to the

0:25:43.000 --> 0:25:44.520
<v Speaker 1>when the swimmer would get to the end, if they

0:25:44.640 --> 0:25:48.400
<v Speaker 1>it was like a race that had multiple lengths, then

0:25:48.480 --> 0:25:51.280
<v Speaker 1>he would just reverse start turning the crank the other

0:25:51.320 --> 0:25:54.160
<v Speaker 1>way and the camera would move the other way down

0:25:54.480 --> 0:25:57.840
<v Speaker 1>the pool. Um it's all. The reason why I decided

0:25:57.880 --> 0:25:59.960
<v Speaker 1>to go manual was because he was afraid that using

0:26:00.160 --> 0:26:06.080
<v Speaker 1>some sort of motorized or robotic system would um would

0:26:06.520 --> 0:26:10.359
<v Speaker 1>raise ire among judges and athletes because it would it

0:26:10.440 --> 0:26:14.080
<v Speaker 1>could theoretically change the conditions of the pool, and you

0:26:14.080 --> 0:26:15.840
<v Speaker 1>don't want to do that when you're talking about world

0:26:15.840 --> 0:26:21.159
<v Speaker 1>class Olympic athletes where the tiniest detail can affect his

0:26:21.320 --> 0:26:25.360
<v Speaker 1>or her performance, you don't want to create cause for concern.

0:26:25.840 --> 0:26:28.840
<v Speaker 1>So Yeah, it's a neat little camera and you just

0:26:28.960 --> 0:26:30.720
<v Speaker 1>and it just scoots along the bottom. And that one's

0:26:30.760 --> 0:26:33.919
<v Speaker 1>a couple of decades old actually, but a more recent

0:26:33.960 --> 0:26:36.920
<v Speaker 1>one that was introduced in the two thousand Olympics his

0:26:37.040 --> 0:26:42.200
<v Speaker 1>the dive cam. Now the dive cam again deceptively simple.

0:26:42.560 --> 0:26:45.320
<v Speaker 1>Imagine you've got an Olympic sized swimming pool. You've got

0:26:45.359 --> 0:26:49.800
<v Speaker 1>a tube that is uh extends all the way up

0:26:49.840 --> 0:26:54.040
<v Speaker 1>to the height of the um diving board and down

0:26:54.240 --> 0:26:58.520
<v Speaker 1>into the water. The tube is weighted, it's it's got

0:26:58.520 --> 0:27:02.080
<v Speaker 1>air on the inside. It's capped at the top, so

0:27:02.520 --> 0:27:06.119
<v Speaker 1>it's weighted so that it doesn't float away. But the

0:27:06.160 --> 0:27:08.920
<v Speaker 1>tube is set up so that the cameras at the

0:27:09.000 --> 0:27:11.000
<v Speaker 1>very top of the tube when the diver is about

0:27:11.000 --> 0:27:13.960
<v Speaker 1>to begin his or her dive, and there's a release

0:27:14.480 --> 0:27:17.119
<v Speaker 1>another Pulley system, but there's a release where you where

0:27:17.440 --> 0:27:19.960
<v Speaker 1>the operator releases the camera just as the diver starts

0:27:20.000 --> 0:27:24.480
<v Speaker 1>to dive. And because we all obey the law of gravity,

0:27:24.960 --> 0:27:28.040
<v Speaker 1>we all fall at the same speed. So the camera

0:27:28.119 --> 0:27:31.160
<v Speaker 1>falls at the same speed as the diver and goes

0:27:31.200 --> 0:27:33.680
<v Speaker 1>all the way down and even goes down into below

0:27:33.720 --> 0:27:35.760
<v Speaker 1>the water line, right, which you can do because the

0:27:35.800 --> 0:27:39.000
<v Speaker 1>tube exactly the tube extends beneath the water line, so

0:27:39.160 --> 0:27:41.600
<v Speaker 1>the camera continues to go down and capture footage of

0:27:41.640 --> 0:27:44.359
<v Speaker 1>the diver as he or she enters the water. And

0:27:44.400 --> 0:27:47.320
<v Speaker 1>then there's some bungee cords attached to the camera that

0:27:47.359 --> 0:27:49.919
<v Speaker 1>will slow it's descent so it doesn't just crash at

0:27:49.960 --> 0:27:52.840
<v Speaker 1>the bottom. And then you use a pulley system to

0:27:53.040 --> 0:27:55.679
<v Speaker 1>raise the camera back up and you're ready to go

0:27:55.760 --> 0:27:57.919
<v Speaker 1>for the next dive. So it's really kind of a

0:27:57.920 --> 0:28:00.280
<v Speaker 1>neat way to follow a diver all the way down

0:28:00.359 --> 0:28:04.760
<v Speaker 1>the entire uh length of his or her dive. Yes,

0:28:05.760 --> 0:28:08.200
<v Speaker 1>and I'm sorry, no, no, go ahead. You were about

0:28:08.200 --> 0:28:10.840
<v Speaker 1>to say something, it's gonna say. UM, I could talk

0:28:10.880 --> 0:28:15.879
<v Speaker 1>about one other technology that I investigated, UM and UH

0:28:15.920 --> 0:28:20.760
<v Speaker 1>That basically is another camera related technology, and it's very

0:28:20.800 --> 0:28:25.480
<v Speaker 1>similar to Hawkeye in some ways, UM, most notably in

0:28:25.600 --> 0:28:31.000
<v Speaker 1>that it requires UM it requires mapping the field of play,

0:28:31.240 --> 0:28:34.359
<v Speaker 1>and that's UH something we actually have a great article

0:28:34.480 --> 0:28:37.960
<v Speaker 1>on on how stuff works dot com. UM It's something

0:28:38.160 --> 0:28:42.760
<v Speaker 1>originally developed apparently by a company called sport Vision, a

0:28:42.800 --> 0:28:46.840
<v Speaker 1>New York City company that debuted its first and ten

0:28:46.960 --> 0:28:50.360
<v Speaker 1>system on a game between the Cincinnati Bengals and Baltimore

0:28:50.440 --> 0:28:55.120
<v Speaker 1>Ravens on septem So we're talking about American football here,

0:28:56.160 --> 0:28:58.800
<v Speaker 1>and that's if you've ever wondered watched a football game

0:28:58.800 --> 0:29:02.520
<v Speaker 1>and wondered how they it the first down line to appear,

0:29:02.600 --> 0:29:05.160
<v Speaker 1>that yellow line to appear on the field, because you

0:29:05.200 --> 0:29:11.360
<v Speaker 1>know that's not painted on there. UM. In American football, uh,

0:29:11.560 --> 0:29:14.840
<v Speaker 1>you play with a the team has given four downs

0:29:15.000 --> 0:29:16.920
<v Speaker 1>to make a first down. Basically, they have to go

0:29:17.160 --> 0:29:20.520
<v Speaker 1>ten yards UM to get a first down, and they

0:29:20.560 --> 0:29:22.880
<v Speaker 1>have four chances to do that in order to advance

0:29:22.920 --> 0:29:25.719
<v Speaker 1>down the field and hopefully score. That's the objective anyway,

0:29:25.720 --> 0:29:29.240
<v Speaker 1>while the other team tries to prevent that from happening. UM.

0:29:29.520 --> 0:29:32.240
<v Speaker 1>So there is a line of scrimmage, which is the line,

0:29:32.520 --> 0:29:35.760
<v Speaker 1>the imaginary line on on which the ball starts when

0:29:35.800 --> 0:29:38.720
<v Speaker 1>they start to play. And then they have a line

0:29:39.040 --> 0:29:42.920
<v Speaker 1>that is originally at the first down uh ten yards

0:29:42.920 --> 0:29:47.120
<v Speaker 1>away and usually this is marked by a giant piece

0:29:47.160 --> 0:29:51.719
<v Speaker 1>of orange appears to be plastic. I've never actually touched one, UM,

0:29:51.760 --> 0:29:54.640
<v Speaker 1>but it's on the side of the field, and really

0:29:55.440 --> 0:29:57.800
<v Speaker 1>from a televised angle, it's very hard to see because

0:29:57.800 --> 0:30:00.160
<v Speaker 1>they like to zoom in on the players and and

0:30:00.200 --> 0:30:03.040
<v Speaker 1>see what they're doing. So they don't usually zoom out

0:30:03.080 --> 0:30:05.920
<v Speaker 1>to the point where you can actually see that. So somebody,

0:30:06.320 --> 0:30:10.000
<v Speaker 1>apparently Sport Vision, decided to create a system by which

0:30:10.040 --> 0:30:13.720
<v Speaker 1>you could actually show this to the viewer. Now. Um,

0:30:14.000 --> 0:30:18.040
<v Speaker 1>Like uh, tennis courts and and cricket pitches, the football

0:30:18.040 --> 0:30:21.520
<v Speaker 1>field is not flat, not completely flat. Of course, people

0:30:21.840 --> 0:30:26.440
<v Speaker 1>tear it up, especially outdoor arenas where it's been rainy. Uh.

0:30:26.480 --> 0:30:28.920
<v Speaker 1>You know, the cleats tear up the field, It gets

0:30:28.920 --> 0:30:32.360
<v Speaker 1>mashed up. Plus um, the field is raised a little

0:30:32.360 --> 0:30:35.040
<v Speaker 1>bit in the center to help it drain. UM. So

0:30:35.120 --> 0:30:36.800
<v Speaker 1>it has to take the system has to take that

0:30:36.840 --> 0:30:39.280
<v Speaker 1>into account. And I should point out to that there

0:30:39.280 --> 0:30:42.959
<v Speaker 1>are other companies that offer this technology. UM. But in

0:30:43.040 --> 0:30:45.360
<v Speaker 1>order to make this happen, there is a truck full

0:30:45.400 --> 0:30:48.720
<v Speaker 1>of equipment off the field as well, and it requires

0:30:48.720 --> 0:30:51.400
<v Speaker 1>some chroma key the green screen effect that we've talked

0:30:51.440 --> 0:30:55.080
<v Speaker 1>about and UM and other podcasts as well. They have

0:30:55.120 --> 0:30:58.920
<v Speaker 1>to key out the colors of the players uniforms. UM.

0:30:58.960 --> 0:31:03.000
<v Speaker 1>But they showed the imaginary line on the field and

0:31:03.240 --> 0:31:06.360
<v Speaker 1>UM by by using the chroma key technology, they can

0:31:06.400 --> 0:31:08.920
<v Speaker 1>avoid showing the line on top of the players are

0:31:08.920 --> 0:31:13.080
<v Speaker 1>on top of the ball um and uh, they can

0:31:13.120 --> 0:31:15.720
<v Speaker 1>they can show this imaginary line to the viewers. Now,

0:31:15.760 --> 0:31:19.120
<v Speaker 1>of course it's not it's there just to illustrate, So

0:31:19.160 --> 0:31:21.600
<v Speaker 1>it's not supposed to have the same kind of accuracy

0:31:21.640 --> 0:31:23.880
<v Speaker 1>that the Hawkeye system does. It's just to give a

0:31:23.880 --> 0:31:26.240
<v Speaker 1>little frame of reference to the viewer. Yeah, so you

0:31:26.280 --> 0:31:29.800
<v Speaker 1>have an idea, and that's why you know when uh.

0:31:29.880 --> 0:31:32.760
<v Speaker 1>And of course, like most sports, UH, it can be

0:31:32.800 --> 0:31:35.160
<v Speaker 1>a game of very very small I mean we're talking

0:31:35.200 --> 0:31:41.120
<v Speaker 1>to the Hawkeye system millimeters, very small increments of of measurement.

0:31:41.440 --> 0:31:44.200
<v Speaker 1>So when a player appears to get to have earned

0:31:44.200 --> 0:31:48.160
<v Speaker 1>a first down through a running player passing play um,

0:31:48.240 --> 0:31:50.400
<v Speaker 1>and it appears that way to us watching at home,

0:31:50.800 --> 0:31:53.120
<v Speaker 1>it may not actually be the case because that yellow

0:31:53.200 --> 0:31:58.040
<v Speaker 1>line is not accurate. It's a a very good approximation

0:31:58.120 --> 0:32:00.280
<v Speaker 1>of where the line is supposed to be. So that's

0:32:00.280 --> 0:32:02.680
<v Speaker 1>why you will still see the officials use the chains

0:32:02.680 --> 0:32:06.800
<v Speaker 1>to measure um. Although you know that's always kind of

0:32:07.400 --> 0:32:09.160
<v Speaker 1>made me laugh too, because they carry the chain out

0:32:09.200 --> 0:32:11.000
<v Speaker 1>in the middle of the field and I'm going, you

0:32:11.000 --> 0:32:12.680
<v Speaker 1>guys just ran out here with that thing, you know,

0:32:12.800 --> 0:32:17.240
<v Speaker 1>you're going that looks about right, um, But which always

0:32:17.240 --> 0:32:19.640
<v Speaker 1>amuses me. But um, but that's how they do that.

0:32:19.800 --> 0:32:21.680
<v Speaker 1>And I had always wondered that too, and I thought,

0:32:21.760 --> 0:32:25.080
<v Speaker 1>you know, since it does involve cameras, it does involve um,

0:32:25.320 --> 0:32:29.840
<v Speaker 1>a special camera for that purpose. Um. According to our

0:32:29.920 --> 0:32:32.200
<v Speaker 1>our article, it does require quite a bit of computer

0:32:32.200 --> 0:32:34.320
<v Speaker 1>technology as well, because you have to take into account

0:32:34.360 --> 0:32:37.600
<v Speaker 1>the orientation of the camera. UM. You know, they do.

0:32:37.720 --> 0:32:41.120
<v Speaker 1>The producer of the broadcast is also choosing which camera

0:32:41.160 --> 0:32:43.000
<v Speaker 1>to focus on, So it has to the line has

0:32:43.040 --> 0:32:45.880
<v Speaker 1>to appear and roughly the same spot no matter where

0:32:45.920 --> 0:32:47.960
<v Speaker 1>you're you're showing it from. So it has taken to

0:32:48.000 --> 0:32:54.200
<v Speaker 1>account the perspective of the vision angle. UM. But you know,

0:32:54.240 --> 0:32:56.000
<v Speaker 1>and it also has to to be able to show

0:32:56.040 --> 0:32:58.000
<v Speaker 1>the line on the field and not on the top

0:32:58.040 --> 0:33:01.360
<v Speaker 1>of the players and referees in the ball. UM. But

0:33:01.440 --> 0:33:03.960
<v Speaker 1>that's a pretty neat system. And I assume that that's

0:33:04.040 --> 0:33:07.320
<v Speaker 1>pretty close to the system they used to broadcast graphics

0:33:07.360 --> 0:33:11.160
<v Speaker 1>when they show ads or other information about what's going

0:33:11.200 --> 0:33:13.120
<v Speaker 1>on in the field. They you know, they'll show it

0:33:13.160 --> 0:33:16.080
<v Speaker 1>in a place where the players aren't. UM tell you

0:33:16.120 --> 0:33:18.000
<v Speaker 1>what down it is or how many yards they have

0:33:18.080 --> 0:33:21.040
<v Speaker 1>to go. UM. But that's that's pretty neat and it

0:33:21.040 --> 0:33:23.680
<v Speaker 1>does require again, like like the other technologies we've talked

0:33:23.720 --> 0:33:27.640
<v Speaker 1>about today, a special uh special cameras um and it

0:33:27.680 --> 0:33:31.360
<v Speaker 1>does you know, the camera itself has to be communicate

0:33:31.760 --> 0:33:34.680
<v Speaker 1>where it is in regard to the play and the

0:33:34.760 --> 0:33:37.080
<v Speaker 1>line of scrimmage, in the line of where the first

0:33:37.080 --> 0:33:40.440
<v Speaker 1>down is supposed to be earned in order to help

0:33:40.480 --> 0:33:45.200
<v Speaker 1>the camera or help the computers know roughly where to

0:33:45.240 --> 0:33:48.280
<v Speaker 1>put the line. So that's uh, it's fascinating stuff. It's

0:33:48.280 --> 0:33:50.480
<v Speaker 1>something I always wondered about and never really took the

0:33:50.520 --> 0:33:52.000
<v Speaker 1>time to look into until it was time to do

0:33:52.040 --> 0:33:54.080
<v Speaker 1>the research. So I'm glad. I'm glad we did. But

0:33:54.120 --> 0:33:56.400
<v Speaker 1>there are other things that I would like to talk

0:33:56.440 --> 0:33:59.840
<v Speaker 1>about in a future podcast perhaps maybe uh maybe down

0:33:59.880 --> 0:34:02.680
<v Speaker 1>the and we've tackled some other topics first. Yeah, sure,

0:34:02.680 --> 0:34:05.760
<v Speaker 1>I've got I've got a great patent for a a

0:34:05.800 --> 0:34:09.080
<v Speaker 1>pitch speed and strike zone invention that I think would

0:34:09.120 --> 0:34:11.040
<v Speaker 1>never ever ever see the light of day, but I'd

0:34:11.080 --> 0:34:13.400
<v Speaker 1>love to talk about it. Yeah, that's that's definitely one

0:34:13.400 --> 0:34:16.840
<v Speaker 1>of those. And the baseball tracking technology where the baseball

0:34:16.880 --> 0:34:19.759
<v Speaker 1>crosses the plate. Uh, if you're not a baseball fan,

0:34:19.840 --> 0:34:23.239
<v Speaker 1>a lot of times they'll show uh. During the game,

0:34:23.239 --> 0:34:25.719
<v Speaker 1>they'll show an angle camera angle where you see from

0:34:25.760 --> 0:34:28.680
<v Speaker 1>behind the picture where the where the pitch is going

0:34:29.000 --> 0:34:33.799
<v Speaker 1>to the batter, and as they analyze it, the commentators

0:34:33.800 --> 0:34:36.399
<v Speaker 1>will put on a tracker where we'll show you where

0:34:36.400 --> 0:34:39.320
<v Speaker 1>where it was in the strike zone. Right, I'm curious

0:34:39.360 --> 0:34:41.480
<v Speaker 1>to see. I haven't gone enough research on that yet

0:34:41.480 --> 0:34:44.200
<v Speaker 1>to talk about it confidently, but I want to talk

0:34:44.200 --> 0:34:46.680
<v Speaker 1>about that. And possibly even that glow puck they used

0:34:46.719 --> 0:34:51.319
<v Speaker 1>to use in hockey globe. Well, we'll just have to

0:34:51.320 --> 0:34:53.759
<v Speaker 1>save that for a later discussion. We're gonna wrap this

0:34:53.800 --> 0:34:56.320
<v Speaker 1>one up. If you guys have any questions or comments,

0:34:56.360 --> 0:34:58.040
<v Speaker 1>you can let us know. You can let us know

0:34:58.080 --> 0:35:01.160
<v Speaker 1>on Facebook or Twitter. Are handled the is tech Stuff

0:35:01.480 --> 0:35:05.120
<v Speaker 1>hs W, or you can email us. That email address

0:35:05.239 --> 0:35:07.960
<v Speaker 1>is tech stuff at how stuff works dot com and

0:35:08.000 --> 0:35:10.399
<v Speaker 1>Chris and I will talk to you again really soon.

0:35:12.680 --> 0:35:15.560
<v Speaker 1>For moralness and thousands of other topics. Visit how stuff

0:35:15.560 --> 0:35:18.400
<v Speaker 1>works dot com. To learn more about the podcast, click

0:35:18.400 --> 0:35:20.759
<v Speaker 1>on the podcast icon in the upper right corner of

0:35:20.760 --> 0:35:24.840
<v Speaker 1>our homepage. The How Stuff Works iPhone app has arrived.

0:35:24.920 --> 0:35:32.200
<v Speaker 1>Download it today on iTunes. Brought to you by the

0:35:32.239 --> 0:35:35.600
<v Speaker 1>Reinvented two thousand twelve camera. It's ready. Are you