WEBVTT - Using Computer Vision to See What Coaches Can’t

0:00:08.320 --> 0:00:08.800
<v Speaker 1>Pushkin.

0:00:16.160 --> 0:00:19.079
<v Speaker 2>Because I didn't know that sports biomechanics could be a career.

0:00:20.280 --> 0:00:22.880
<v Speaker 2>I decided to go to grad school and initially start

0:00:22.960 --> 0:00:25.960
<v Speaker 2>working on prosthetic limbs. So that was the first two

0:00:26.000 --> 0:00:30.920
<v Speaker 2>years of grad school. Then about two years in I

0:00:31.040 --> 0:00:36.640
<v Speaker 2>discovered baseball pitching biomechanics research. The funny thing that happened

0:00:36.640 --> 0:00:40.360
<v Speaker 2>there was I gave a PhD committee meeting where I

0:00:40.400 --> 0:00:44.440
<v Speaker 2>spent most of the time talking about prosthetic limbs, and

0:00:44.479 --> 0:00:46.920
<v Speaker 2>then I spent the last few minutes as an aside

0:00:47.360 --> 0:00:50.520
<v Speaker 2>on the baseball pitching research I found. And my committee

0:00:50.600 --> 0:00:53.760
<v Speaker 2>was like, Jimmy, the last few minutes were way better

0:00:53.800 --> 0:00:55.000
<v Speaker 2>than the first forty fives.

0:00:55.400 --> 0:00:57.040
<v Speaker 3>So I was like, all right.

0:00:57.240 --> 0:01:00.800
<v Speaker 2>So then they were like, we'll let you do baseball

0:01:00.840 --> 0:01:04.080
<v Speaker 2>pitching biomechanics as your PhD work, but just so you know,

0:01:04.319 --> 0:01:06.480
<v Speaker 2>it might be really hard to have a career doing that.

0:01:08.040 --> 0:01:09.480
<v Speaker 2>But you know, they were like, if you want to

0:01:09.520 --> 0:01:10.760
<v Speaker 2>go for it, you can go for it. And so

0:01:10.840 --> 0:01:13.319
<v Speaker 2>I was like, you know what, Sure, I'll go for it.

0:01:19.200 --> 0:01:22.200
<v Speaker 1>I'm Jacob Goldstein, and this is what's your problem. Today

0:01:22.280 --> 0:01:25.639
<v Speaker 1>we have the second episode in our series about people

0:01:25.880 --> 0:01:29.039
<v Speaker 1>who are working at the frontiers of technology to help

0:01:29.080 --> 0:01:33.640
<v Speaker 1>a lead athletes perform better. My guest today is Jimmy Buffy,

0:01:33.959 --> 0:01:36.639
<v Speaker 1>and as it happened, the concerns of his grad school

0:01:36.680 --> 0:01:40.800
<v Speaker 1>advisors were unfounded. Jimmy has in fact made a career

0:01:40.920 --> 0:01:44.920
<v Speaker 1>out of the biomechanics of pitching in baseball and sports

0:01:44.920 --> 0:01:48.560
<v Speaker 1>biomechanics more broadly. When he finished grad school, he got

0:01:48.560 --> 0:01:51.120
<v Speaker 1>a job with the Los Angeles Dodgers, and he went

0:01:51.160 --> 0:01:54.160
<v Speaker 1>on to co found a company called Reboot Motion that

0:01:54.280 --> 0:01:57.360
<v Speaker 1>works with teams in Major League Baseball and the NBA.

0:01:57.840 --> 0:02:01.360
<v Speaker 1>Jimmy's problem is this, how do you take massive amounts

0:02:01.360 --> 0:02:05.400
<v Speaker 1>of data about how professional athletes move and turn all

0:02:05.440 --> 0:02:10.600
<v Speaker 1>that data into information that actually helps those athletes perform better.

0:02:12.240 --> 0:02:15.160
<v Speaker 1>You end up doing your dissertation research on the on

0:02:15.240 --> 0:02:19.480
<v Speaker 1>the biomechanics of pitching, Yes, of baseball, pitching and baseball. Yeah,

0:02:19.560 --> 0:02:22.639
<v Speaker 1>and and then you get hired by the Dodgers.

0:02:23.080 --> 0:02:23.800
<v Speaker 3>Yeah.

0:02:23.960 --> 0:02:27.520
<v Speaker 2>Yeah, that was That was awesome because I originally didn't again,

0:02:27.560 --> 0:02:30.320
<v Speaker 2>didn't realize that that could be a thing that could happen.

0:02:30.800 --> 0:02:33.840
<v Speaker 1>Well, and it kind of wasn't right, Like, you're kind

0:02:33.880 --> 0:02:36.640
<v Speaker 1>of just coming into this field as it's becoming a

0:02:36.680 --> 0:02:38.799
<v Speaker 1>field where you can get a job where it's a.

0:02:38.720 --> 0:02:40.280
<v Speaker 3>Field, right exactly. Yeah, there.

0:02:40.360 --> 0:02:42.280
<v Speaker 2>I mean the challenge then was there wasn't a lot

0:02:42.320 --> 0:02:45.400
<v Speaker 2>of options for actually even getting the data that you

0:02:45.560 --> 0:02:47.079
<v Speaker 2>need to analyze.

0:02:47.800 --> 0:02:51.120
<v Speaker 1>So ten years ago, like what is the state of

0:02:51.160 --> 0:02:54.160
<v Speaker 1>play in this sort of nasson field that you're in

0:02:54.400 --> 0:02:55.200
<v Speaker 1>helping to create?

0:02:56.639 --> 0:03:00.000
<v Speaker 2>So the field is, I would say, is like sports biomechanic,

0:03:00.200 --> 0:03:03.600
<v Speaker 2>and what that is is being able to analyze the

0:03:03.760 --> 0:03:07.519
<v Speaker 2>movement of athletes for lots of purposes, help them reduce

0:03:07.560 --> 0:03:10.720
<v Speaker 2>injury risk, help them improve performance.

0:03:10.680 --> 0:03:14.440
<v Speaker 1>And to be clear, like folk, sports biomechanics has been

0:03:14.480 --> 0:03:16.720
<v Speaker 1>around forever, right, that's what coaches do. They stay out

0:03:16.720 --> 0:03:18.480
<v Speaker 1>there and they watch it. Yeah, And so it's kind

0:03:18.480 --> 0:03:21.519
<v Speaker 1>of becoming it's becoming more technical, right, the field is

0:03:21.560 --> 0:03:22.480
<v Speaker 1>becoming more technical.

0:03:22.600 --> 0:03:22.919
<v Speaker 3>Yeah.

0:03:22.960 --> 0:03:26.799
<v Speaker 2>So the state of the art relied on what is

0:03:26.840 --> 0:03:31.760
<v Speaker 2>called marker based motion capture, which is where you literally

0:03:31.800 --> 0:03:36.080
<v Speaker 2>put reflective markers like little balls, you stick them all

0:03:36.120 --> 0:03:39.440
<v Speaker 2>over somebody's body. Usually the person has to like strip

0:03:39.480 --> 0:03:41.760
<v Speaker 2>their clothes off because you want the markers like literally

0:03:41.840 --> 0:03:45.040
<v Speaker 2>like on the skin, on the joints, and then you

0:03:45.120 --> 0:03:48.400
<v Speaker 2>have these special cameras that track those markers.

0:03:48.760 --> 0:03:50.920
<v Speaker 1>So you've got like a picture in his underwear with

0:03:50.960 --> 0:03:54.000
<v Speaker 1>a bunch of little metal balls, takes them and they're like,

0:03:54.160 --> 0:03:55.800
<v Speaker 1>just pitch like you always pitch.

0:03:55.720 --> 0:03:57.000
<v Speaker 3>Right, And that's the challenge.

0:03:57.160 --> 0:03:59.760
<v Speaker 2>That's why that wasn't That's why it wasn't very wide

0:03:59.800 --> 0:04:02.040
<v Speaker 2>SPA is a thing people did because it was so

0:04:02.240 --> 0:04:04.800
<v Speaker 2>hard to collect the data because ultimately, what you would

0:04:04.840 --> 0:04:08.000
<v Speaker 2>need is you need the data on how someone is moving.

0:04:08.360 --> 0:04:09.280
<v Speaker 3>You need to track.

0:04:09.040 --> 0:04:11.000
<v Speaker 2>Where their elbow is, where their wrist is, where their

0:04:11.080 --> 0:04:13.800
<v Speaker 2>knees are so that you can analyze it. And the

0:04:13.840 --> 0:04:15.960
<v Speaker 2>state of the art for tracking it was an awful

0:04:16.000 --> 0:04:18.240
<v Speaker 2>experience for the people you were trying to track.

0:04:18.720 --> 0:04:22.479
<v Speaker 1>That presumably would mean they didn't pitch like they usually exactly,

0:04:22.480 --> 0:04:25.040
<v Speaker 1>because they don't usually stand there in their underwear with

0:04:25.440 --> 0:04:27.200
<v Speaker 1>met Were they really in their underwear by the way,

0:04:27.240 --> 0:04:28.840
<v Speaker 1>I'm saying it because it sounds absurd, but is that

0:04:28.839 --> 0:04:29.680
<v Speaker 1>actually what they were doing.

0:04:29.760 --> 0:04:32.680
<v Speaker 2>That's actually you strip down to your your boxers, your

0:04:32.680 --> 0:04:34.800
<v Speaker 2>boxer briefs, and that's it, that's all you're wearing.

0:04:35.640 --> 0:04:38.080
<v Speaker 1>So it basically didn't work, and it basically wasn't very

0:04:38.080 --> 0:04:39.560
<v Speaker 1>widely used as a result.

0:04:39.360 --> 0:04:43.320
<v Speaker 2>Right exactly, Yeah, you yeah, you look at studies in

0:04:43.360 --> 0:04:47.279
<v Speaker 2>that field, and people would be throwing like several miles

0:04:47.279 --> 0:04:49.600
<v Speaker 2>an hour slower than they would be throwing when they

0:04:49.640 --> 0:04:55.279
<v Speaker 2>weren't wearing all that stuff. So what changes computer vision?

0:04:56.440 --> 0:05:00.360
<v Speaker 2>That was the big That was the big inflection point. Now,

0:05:00.360 --> 0:05:04.480
<v Speaker 2>to be fair, like, even when I was finishing my PhD,

0:05:04.960 --> 0:05:06.440
<v Speaker 2>and I'll give them, I'll give them a shout out,

0:05:06.480 --> 0:05:10.240
<v Speaker 2>there was a company that was already like working really

0:05:10.279 --> 0:05:13.240
<v Speaker 2>hard to solve this problem for baseball teams that I

0:05:13.480 --> 0:05:16.440
<v Speaker 2>was getting that I got to be familiar with, called Kinnetrax.

0:05:18.279 --> 0:05:21.840
<v Speaker 2>But yeah, the big inflection point was computer vision, basically

0:05:21.960 --> 0:05:26.960
<v Speaker 2>using artificial intelligence to identify where those joints are in

0:05:26.960 --> 0:05:31.760
<v Speaker 2>a camera image rather than needing to paste those reflective markers.

0:05:32.279 --> 0:05:35.320
<v Speaker 1>So computer vision takes off. You're working at the Dodgers,

0:05:35.560 --> 0:05:39.080
<v Speaker 1>and then eventually in twenty nineteen, right, you leave the

0:05:39.120 --> 0:05:43.840
<v Speaker 1>Dodgers and you start your company a reboot motion, what

0:05:43.880 --> 0:05:44.640
<v Speaker 1>does your company do?

0:05:45.240 --> 0:05:49.360
<v Speaker 2>We do what we call biomechanics as a service, So

0:05:49.680 --> 0:05:52.840
<v Speaker 2>we try to analyze this computer vision data at a

0:05:52.960 --> 0:05:56.800
<v Speaker 2>very large scale to help teams and coaches make use

0:05:56.800 --> 0:06:03.200
<v Speaker 2>of it to help athletes get better. Bas Yeah, that says.

0:06:03.040 --> 0:06:06.720
<v Speaker 1>But bess Yah and and who are your customers?

0:06:06.920 --> 0:06:14.239
<v Speaker 2>Our customers are Major League Baseball teams actually NBA teams,

0:06:14.279 --> 0:06:19.520
<v Speaker 2>so we've gotten into basketball also sort of like league

0:06:19.560 --> 0:06:23.839
<v Speaker 2>wide data providers. So yeah, leagues teams is basically our

0:06:23.880 --> 0:06:24.440
<v Speaker 2>sweet spot.

0:06:24.720 --> 0:06:27.760
<v Speaker 1>So let's talk. Let's talk in like a little more

0:06:27.760 --> 0:06:30.839
<v Speaker 1>detail about about what you actually do, right, tell me

0:06:30.880 --> 0:06:32.360
<v Speaker 1>the story of what you do.

0:06:33.600 --> 0:06:37.520
<v Speaker 2>So, Evan, my co founder, Evan Demchik, he likes to

0:06:37.520 --> 0:06:41.920
<v Speaker 2>call this the biomechanics Trainkay.

0:06:41.080 --> 0:06:43.080
<v Speaker 1>Let's take a ride on the biomechanics trend.

0:06:43.720 --> 0:06:45.800
<v Speaker 2>And we call it that because with the way our

0:06:45.839 --> 0:06:49.320
<v Speaker 2>product works is we let people get on the train

0:06:49.760 --> 0:06:51.800
<v Speaker 2>at whatever stop works for them, and get off the

0:06:51.839 --> 0:06:53.640
<v Speaker 2>train at whatever stop works for them.

0:06:53.720 --> 0:06:55.360
<v Speaker 1>How far are we going to go with this metaphor

0:06:55.600 --> 0:06:57.360
<v Speaker 1>of a little o'b nervous about it?

0:06:57.760 --> 0:06:59.160
<v Speaker 3>That might be as far as we go.

0:06:59.320 --> 0:07:03.960
<v Speaker 1>Okay, good, good, So just tell it to me. Start

0:07:04.000 --> 0:07:06.279
<v Speaker 1>at whatever seems like the beginning of a you know,

0:07:07.040 --> 0:07:10.120
<v Speaker 1>a of an encounter, and so I'd like to understand

0:07:10.160 --> 0:07:12.600
<v Speaker 1>how that works. That's really kind of a way to

0:07:12.600 --> 0:07:15.640
<v Speaker 1>think about it. So let's start with the data, right,

0:07:16.040 --> 0:07:19.080
<v Speaker 1>what is a basic what is the basic thing that's.

0:07:18.920 --> 0:07:22.440
<v Speaker 2>Happening So the very first thing that happens is you

0:07:22.520 --> 0:07:27.920
<v Speaker 2>record videos of the athlete doing the athletic motion. So

0:07:27.920 --> 0:07:30.880
<v Speaker 2>we'll talk about pitching, So you record videos of a

0:07:30.920 --> 0:07:34.840
<v Speaker 2>pitcher pitching. Our product, we actually have implemented our own

0:07:34.840 --> 0:07:38.560
<v Speaker 2>computer vision models, so we can do that if people want.

0:07:38.640 --> 0:07:43.480
<v Speaker 2>But generally speaking, people have systems like Kinetrax is one

0:07:43.520 --> 0:07:47.120
<v Speaker 2>I've mentioned that, Hawkeye is another popular one where there

0:07:47.200 --> 0:07:49.600
<v Speaker 2>is a system in place that has the cameras that

0:07:49.680 --> 0:07:52.960
<v Speaker 2>record the videos and then runs those computer vision models.

0:07:53.240 --> 0:07:56.840
<v Speaker 2>What those computer vision models do is they extract the

0:07:56.920 --> 0:08:00.880
<v Speaker 2>locations in three dimensional space of all of like the

0:08:00.960 --> 0:08:03.640
<v Speaker 2>joint centers. So where's my elbow, where's my wrist, where's

0:08:03.640 --> 0:08:07.040
<v Speaker 2>my knee? In three dimensional space? That's what comes out

0:08:07.040 --> 0:08:08.400
<v Speaker 2>of these computer vision systems.

0:08:08.920 --> 0:08:12.080
<v Speaker 1>Okay, so pretty much everybody has that at this point,

0:08:12.120 --> 0:08:16.280
<v Speaker 1>Like every professional baseball team has that for every pitch

0:08:16.320 --> 0:08:17.480
<v Speaker 1>in every game at this point.

0:08:17.600 --> 0:08:18.320
<v Speaker 3>Yes, exactly.

0:08:18.640 --> 0:08:21.520
<v Speaker 2>Okay, So it's a ton a ton of data. So

0:08:21.560 --> 0:08:24.360
<v Speaker 2>that's another challenge that we've solved, is not only how

0:08:24.360 --> 0:08:25.640
<v Speaker 2>do you do this, but how do you do this

0:08:25.680 --> 0:08:27.040
<v Speaker 2>at a very large scale?

0:08:27.280 --> 0:08:30.920
<v Speaker 1>Okay, so this data, everybody's got it now, and you're not.

0:08:31.360 --> 0:08:33.760
<v Speaker 1>You can sort of process the data, but that's not

0:08:33.880 --> 0:08:36.559
<v Speaker 1>your special sauce. That's not your secret sauce, right, So

0:08:36.600 --> 0:08:39.800
<v Speaker 1>typically they'll send you that that data of like, here's

0:08:39.800 --> 0:08:41.360
<v Speaker 1>all the body points. Here is how they're moving in

0:08:41.520 --> 0:08:44.000
<v Speaker 1>physical space. Then what do you do with it?

0:08:44.360 --> 0:08:46.600
<v Speaker 2>So, yeah, this is where the special sauce comes in.

0:08:47.120 --> 0:08:49.320
<v Speaker 2>So the first step to that is how do you

0:08:49.400 --> 0:08:53.160
<v Speaker 2>turn those key points into a human skeleton. So you've

0:08:53.160 --> 0:08:55.439
<v Speaker 2>got to figure out, like where do the bones connect,

0:08:55.520 --> 0:08:58.200
<v Speaker 2>what sort of degrees of freedom do those bones have,

0:08:58.760 --> 0:09:01.840
<v Speaker 2>So then you can figure out how do those key

0:09:01.880 --> 0:09:04.640
<v Speaker 2>points animate a human skeleton.

0:09:05.120 --> 0:09:07.160
<v Speaker 1>So you're sort of rebuilding it. It's like you start

0:09:07.200 --> 0:09:08.880
<v Speaker 1>with the picture of a person and then you turn

0:09:08.880 --> 0:09:10.839
<v Speaker 1>it into a bunch of data points, and now you've

0:09:10.840 --> 0:09:13.160
<v Speaker 1>got to kind of build the person back up again from.

0:09:13.000 --> 0:09:17.120
<v Speaker 2>The day exactly exactly. So now you have an actual

0:09:17.280 --> 0:09:21.240
<v Speaker 2>human skeleton where the shoulder is rotating, the elbow is flexing,

0:09:21.280 --> 0:09:24.240
<v Speaker 2>the knee is flexing, the hips are rotating. And now

0:09:24.280 --> 0:09:27.120
<v Speaker 2>once you do that, now you can understand that data

0:09:27.160 --> 0:09:30.160
<v Speaker 2>in the context of how the body works. Okay, so

0:09:30.240 --> 0:09:34.000
<v Speaker 2>once we've done that, then we calculate how energy flows

0:09:34.040 --> 0:09:37.240
<v Speaker 2>through the body, we calculate how momentum flows through the body,

0:09:37.520 --> 0:09:40.359
<v Speaker 2>and once we've done that, we can analyze how efficiently

0:09:40.360 --> 0:09:43.840
<v Speaker 2>the athlete is moving. Are they generating energy and momentum

0:09:44.080 --> 0:09:47.000
<v Speaker 2>in the direction that they want to generate in? What

0:09:47.160 --> 0:09:50.199
<v Speaker 2>is that desired direction? So we then we calculate all

0:09:50.240 --> 0:09:54.640
<v Speaker 2>sorts of metrics around movement efficiency and direction. Then once

0:09:54.679 --> 0:09:58.319
<v Speaker 2>we calculate all those metrics, now we can understand how

0:09:58.320 --> 0:10:00.720
<v Speaker 2>those relate to what you're trying to do. Throw the

0:10:00.720 --> 0:10:01.960
<v Speaker 2>ball as hard as possible.

0:10:02.040 --> 0:10:05.200
<v Speaker 1>So so presumably with the picture, what you want to

0:10:05.240 --> 0:10:08.640
<v Speaker 1>optimize for is is having as much of the picture's

0:10:09.520 --> 0:10:13.199
<v Speaker 1>energy of their body go toward making the ball go

0:10:13.280 --> 0:10:15.760
<v Speaker 1>toward home plate. Exactly right, I mean that is that? Yeah,

0:10:15.800 --> 0:10:17.800
<v Speaker 1>they mail optimization problem mail it.

0:10:17.840 --> 0:10:20.120
<v Speaker 2>Yeah, Yeah, that's exactly it. And that's the problem that

0:10:20.160 --> 0:10:22.840
<v Speaker 2>we try to understand. So when we build our sort

0:10:22.840 --> 0:10:25.679
<v Speaker 2>of models regarding like how does a pitcher create efficient

0:10:25.679 --> 0:10:28.640
<v Speaker 2>fastball velocity, one of the most important things that comes

0:10:28.679 --> 0:10:31.600
<v Speaker 2>out of those models is lining up the direction of

0:10:31.600 --> 0:10:33.960
<v Speaker 2>your torsore rotation with the direction of your arm rotation.

0:10:34.400 --> 0:10:37.439
<v Speaker 1>The pitching bution is crazy complex, right, Like they're they

0:10:37.520 --> 0:10:39.640
<v Speaker 1>kick their leg up and they got their front arms

0:10:39.679 --> 0:10:42.200
<v Speaker 1>doing something and their back arms going back like a

0:10:42.280 --> 0:10:46.040
<v Speaker 1>lot is happening. Yeah, the sort of platonic ideal is

0:10:46.120 --> 0:10:50.160
<v Speaker 1>every little millimeter of every motion is going toward maximizing

0:10:50.160 --> 0:10:52.000
<v Speaker 1>the energy of the ball going toward home plate.

0:10:52.160 --> 0:10:56.000
<v Speaker 2>Yes, and not just not just maximizing like in a vacuum,

0:10:56.160 --> 0:10:59.640
<v Speaker 2>but doing it in the most efficient way, because if

0:10:59.640 --> 0:11:02.560
<v Speaker 2>you just sort of maximize in a vacuum, maybe you're

0:11:02.559 --> 0:11:04.680
<v Speaker 2>transferring that energy in a way that hurts your elbow.

0:11:04.840 --> 0:11:07.040
<v Speaker 2>You're transferring that energy in a way that hurts your shoulder.

0:11:07.520 --> 0:11:09.280
<v Speaker 2>So not only do we figure out how can a

0:11:09.280 --> 0:11:11.880
<v Speaker 2>pitcher maximize it, but we try to figure out how

0:11:11.920 --> 0:11:14.360
<v Speaker 2>they can have that energy and momentum go in a

0:11:14.440 --> 0:11:18.800
<v Speaker 2>direction that doesn't hurt their joints, So try to have

0:11:18.920 --> 0:11:21.960
<v Speaker 2>them throw the ball a little harder while also reducing

0:11:21.960 --> 0:11:23.160
<v Speaker 2>their injury risk a little bit.

0:11:23.559 --> 0:11:30.640
<v Speaker 1>So you're whatever doing the math at reboot HQ, and

0:11:30.679 --> 0:11:33.319
<v Speaker 1>then what are you sending back to the.

0:11:33.320 --> 0:11:38.199
<v Speaker 2>Team, So some teams so it sort of so again,

0:11:38.440 --> 0:11:39.760
<v Speaker 2>all right, I told you that was the end of

0:11:39.760 --> 0:11:41.160
<v Speaker 2>the biomechanics train analogy.

0:11:41.720 --> 0:11:43.320
<v Speaker 3>I'm going to bring it back for a brief second.

0:11:43.840 --> 0:11:44.679
<v Speaker 1>Okay, I'm ready.

0:11:45.800 --> 0:11:48.160
<v Speaker 2>So we go all the way to building a report

0:11:48.240 --> 0:11:51.200
<v Speaker 2>that has a bunch of suggestions. So there's a report

0:11:51.240 --> 0:11:53.719
<v Speaker 2>that's like, this is how efficient you are. You can

0:11:53.840 --> 0:11:55.599
<v Speaker 2>like tilt your torso a little bit to be a

0:11:55.640 --> 0:11:57.439
<v Speaker 2>little bit more efficient. You can tilt your arm a

0:11:57.440 --> 0:11:59.280
<v Speaker 2>little bit to be a little bit more efficient. So

0:11:59.320 --> 0:12:02.440
<v Speaker 2>we go all the way to generating a report that's

0:12:02.480 --> 0:12:03.840
<v Speaker 2>like the final stop on the train.

0:12:04.480 --> 0:12:06.400
<v Speaker 1>And that's a report for for one pitcher.

0:12:06.679 --> 0:12:09.120
<v Speaker 3>Yeah, that's a report on a pitcher for whatever.

0:12:09.480 --> 0:12:13.200
<v Speaker 1>And and in a way that's like the nerdiest it's

0:12:13.280 --> 0:12:15.360
<v Speaker 1>what a pitching coach does, but just in a way

0:12:15.440 --> 0:12:16.120
<v Speaker 1>nerdier way.

0:12:16.360 --> 0:12:16.600
<v Speaker 3>Yeah.

0:12:16.640 --> 0:12:20.120
<v Speaker 2>Well, so we try to sort of like give the

0:12:20.160 --> 0:12:23.320
<v Speaker 2>coaches superpowers, you know, even though that you know, the

0:12:23.360 --> 0:12:25.800
<v Speaker 2>coaches like can look at an athlete and understand a

0:12:25.840 --> 0:12:29.120
<v Speaker 2>lot about the athlete just by looking at them. We

0:12:29.160 --> 0:12:32.920
<v Speaker 2>try to make a report that can really amplify what

0:12:33.000 --> 0:12:36.160
<v Speaker 2>the coach is already doing, maybe help them discover some

0:12:36.240 --> 0:12:39.560
<v Speaker 2>things they weren't thinking about, or measure some things that

0:12:39.600 --> 0:12:41.600
<v Speaker 2>they were thinking about, but now they can track those

0:12:41.640 --> 0:12:44.040
<v Speaker 2>a little bit easier. So that's you know, that's the

0:12:44.160 --> 0:12:47.880
<v Speaker 2>ultimate thing that we produces a report that can sort

0:12:47.880 --> 0:12:49.719
<v Speaker 2>of like we say, give a coach superpowers.

0:12:51.760 --> 0:12:53.960
<v Speaker 1>Where was the trained metaphor doing that? Is there an

0:12:53.960 --> 0:12:57.000
<v Speaker 1>earlier station of disembarkation exactly?

0:12:57.760 --> 0:13:01.600
<v Speaker 2>So a lot of teams now are hiring people with

0:13:01.679 --> 0:13:06.080
<v Speaker 2>biomechanics and analytics backgrounds, so rather than just use our

0:13:06.200 --> 0:13:09.000
<v Speaker 2>reports out of the box, they want to build their

0:13:09.040 --> 0:13:11.440
<v Speaker 2>own reports and their own statistical models and their own

0:13:11.480 --> 0:13:14.559
<v Speaker 2>AI models. So we also get let people get off

0:13:14.600 --> 0:13:17.040
<v Speaker 2>the train a little bit earlier and build whatever they

0:13:17.120 --> 0:13:19.120
<v Speaker 2>want on top of the data that we're generating.

0:13:19.360 --> 0:13:22.880
<v Speaker 1>Are they not going to disintermediate you once those people

0:13:22.880 --> 0:13:25.400
<v Speaker 1>are there? Does that reduce the value you provide to

0:13:25.440 --> 0:13:26.439
<v Speaker 1>the team.

0:13:26.120 --> 0:13:28.880
<v Speaker 2>Now because we still have to process all that data.

0:13:29.520 --> 0:13:32.720
<v Speaker 1>Do you have some like IP or like why can't

0:13:32.920 --> 0:13:35.400
<v Speaker 1>somebody like you who works for a team just do

0:13:35.480 --> 0:13:36.040
<v Speaker 1>that without you?

0:13:36.160 --> 0:13:39.720
<v Speaker 2>That is a great question. We answered this question all

0:13:39.760 --> 0:13:44.920
<v Speaker 2>the time. Is because it's a very complex engineering problem.

0:13:44.960 --> 0:13:47.440
<v Speaker 2>Not only to do all the math that the physics

0:13:47.440 --> 0:13:50.520
<v Speaker 2>based math, to calculate the energy, calculate the momentum, like

0:13:50.600 --> 0:13:54.000
<v Speaker 2>all of that math is really hard, but also to

0:13:54.080 --> 0:13:57.959
<v Speaker 2>do it at a very large scale. So someone like

0:13:58.040 --> 0:14:00.760
<v Speaker 2>me in grad school learned how to do that on

0:14:00.800 --> 0:14:03.880
<v Speaker 2>a sample size. You know, my PhD was actually really

0:14:03.920 --> 0:14:06.439
<v Speaker 2>just one pitch, but lots of people do it on

0:14:06.520 --> 0:14:10.040
<v Speaker 2>like ten pitches or maybe one hundred pitches, So we

0:14:10.200 --> 0:14:16.760
<v Speaker 2>do it on several thousand pitches like and swings like

0:14:16.880 --> 0:14:17.520
<v Speaker 2>every morning.

0:14:18.240 --> 0:14:18.480
<v Speaker 3>You know.

0:14:18.559 --> 0:14:23.600
<v Speaker 2>There's just every team has like seven affiliates, so there's

0:14:23.920 --> 0:14:26.120
<v Speaker 2>you know, one hundred and fifty games every day that

0:14:26.160 --> 0:14:26.560
<v Speaker 2>need to be.

0:14:26.680 --> 0:14:28.640
<v Speaker 1>So you're doing this on farm teams as well.

0:14:28.720 --> 0:14:29.600
<v Speaker 3>Yeah, exactly.

0:14:29.960 --> 0:14:32.000
<v Speaker 2>So not only did we solve the problem of doing

0:14:32.000 --> 0:14:34.960
<v Speaker 2>it for like one pitcher in a way that's really actionable,

0:14:35.320 --> 0:14:38.240
<v Speaker 2>but we solved the problem doing it for every game

0:14:38.560 --> 0:14:41.840
<v Speaker 2>every day, you know, so that you have the data

0:14:41.880 --> 0:14:42.720
<v Speaker 2>when you wake up.

0:14:44.720 --> 0:14:46.920
<v Speaker 1>So you guys are doing it at scale. The answer

0:14:46.920 --> 0:14:48.760
<v Speaker 1>to why it is that that there is in fact

0:14:48.800 --> 0:14:51.680
<v Speaker 1>an economy of scale, a benefit of scale.

0:14:51.480 --> 0:14:53.640
<v Speaker 3>Yes, which you have, Yes, exactly, Yeah. Yeah.

0:14:54.600 --> 0:14:57.960
<v Speaker 1>What's what's a specific example of a thing that a

0:14:58.040 --> 0:15:01.200
<v Speaker 1>coach might tell a pitcher in response to your report

0:15:01.240 --> 0:15:04.040
<v Speaker 1>to try and get them to throw whatever differently?

0:15:05.440 --> 0:15:06.400
<v Speaker 3>A really.

0:15:08.080 --> 0:15:12.720
<v Speaker 2>Common low hanging fruit type of piece of feedback that

0:15:12.840 --> 0:15:16.120
<v Speaker 2>often comes out of the reports is how a pitcher

0:15:16.400 --> 0:15:21.040
<v Speaker 2>is using their lead arm in a typical pitching motion,

0:15:21.320 --> 0:15:23.720
<v Speaker 2>the pitcher will reach forward with their lead arm.

0:15:24.160 --> 0:15:25.600
<v Speaker 1>So, just to be clear, the lead arm is the

0:15:25.680 --> 0:15:27.520
<v Speaker 1>arm that is not holding the ball.

0:15:27.400 --> 0:15:29.080
<v Speaker 3>Right right, yeah, the arm in front of you.

0:15:29.200 --> 0:15:29.480
<v Speaker 1>Yeah.

0:15:29.680 --> 0:15:30.440
<v Speaker 3>Yeah.

0:15:30.480 --> 0:15:32.720
<v Speaker 2>A pitcher will reach forward with that lead arm while

0:15:32.760 --> 0:15:35.600
<v Speaker 2>the rear arm is holding the baseball, and they'll rotate

0:15:35.800 --> 0:15:38.960
<v Speaker 2>that lead arm really hard, and that's the thing that

0:15:39.040 --> 0:15:43.640
<v Speaker 2>kind of initiates the torso rotation. So a very common

0:15:43.720 --> 0:15:47.040
<v Speaker 2>flaw that we see is if a pitcher has a

0:15:47.200 --> 0:15:51.400
<v Speaker 2>very vertical pitching arm, they're pitching the ball way over

0:15:51.440 --> 0:15:54.520
<v Speaker 2>the top of their head, but their lead arm when

0:15:54.560 --> 0:15:56.760
<v Speaker 2>they pull it through, when they swing it through, they

0:15:56.800 --> 0:15:58.400
<v Speaker 2>swing it in a very flat.

0:15:58.160 --> 0:16:02.040
<v Speaker 1>Plane as horizontal.

0:16:01.480 --> 0:16:05.520
<v Speaker 2>Horizontal, right, yeah, That is not a very efficient plane

0:16:05.560 --> 0:16:07.320
<v Speaker 2>to use when you're throwing the ball on a very

0:16:07.400 --> 0:16:10.560
<v Speaker 2>vertical plane. So a very common low hang piece of

0:16:10.560 --> 0:16:15.280
<v Speaker 2>fruit feedback that comes out of the reports is having

0:16:15.320 --> 0:16:18.960
<v Speaker 2>pitchers just try to rotate their lead arm pull with

0:16:19.000 --> 0:16:21.840
<v Speaker 2>their lead arm in a more vertical plane to better

0:16:21.920 --> 0:16:24.200
<v Speaker 2>match what their torso is doing, a better match with

0:16:24.280 --> 0:16:25.240
<v Speaker 2>their pitching arm is doing.

0:16:26.320 --> 0:16:28.160
<v Speaker 1>That's a good one. I feel like that one's so

0:16:28.240 --> 0:16:30.360
<v Speaker 1>simple that you don't want it to get out that

0:16:30.480 --> 0:16:31.840
<v Speaker 1>everybody ell to start looking at it.

0:16:31.920 --> 0:16:34.440
<v Speaker 2>No, I mean really, I mean like it's this has

0:16:34.480 --> 0:16:37.080
<v Speaker 2>happened when I went to talk to a team and

0:16:37.120 --> 0:16:40.080
<v Speaker 2>we talked about some pieces, you know, some low hanging fruit,

0:16:40.120 --> 0:16:43.120
<v Speaker 2>and they're like, okay, great, we'll take the lead arm thing,

0:16:43.160 --> 0:16:45.800
<v Speaker 2>will implement it everywhere. And I'm like, well, what about

0:16:45.840 --> 0:16:48.160
<v Speaker 2>like the other ten pages of the report.

0:16:49.800 --> 0:16:50.760
<v Speaker 3>Good with the lead arm thing.

0:16:52.200 --> 0:16:56.240
<v Speaker 1>Thanks by so for you. The end of the train

0:16:56.600 --> 0:16:59.840
<v Speaker 1>is the report. But that report goes to the coach, right,

0:17:00.000 --> 0:17:03.680
<v Speaker 1>and so presumably the meaningful change hasn't happened yet, right,

0:17:03.680 --> 0:17:06.040
<v Speaker 1>It has to somehow get from the coach to the picture.

0:17:06.720 --> 0:17:08.840
<v Speaker 1>And like, I know that piece of it is not

0:17:09.640 --> 0:17:11.679
<v Speaker 1>your business now, but it was kind of your business

0:17:11.680 --> 0:17:13.959
<v Speaker 1>when you were at the Dodgers. Presumably you're familiar with

0:17:14.000 --> 0:17:16.240
<v Speaker 1>it now, Like, how does that piece of it work?

0:17:16.320 --> 0:17:18.120
<v Speaker 1>Is it like the pitching coach is like reading from

0:17:18.160 --> 0:17:20.320
<v Speaker 1>the report to the picture. I imagine not, but I

0:17:20.359 --> 0:17:20.679
<v Speaker 1>don't know.

0:17:20.960 --> 0:17:27.480
<v Speaker 2>No, definitely, definite, definitely not. Even at the Dodgers, my

0:17:27.680 --> 0:17:32.000
<v Speaker 2>role was not being the one to coach the players.

0:17:32.200 --> 0:17:34.800
<v Speaker 1>It's like, whatever you do, don't talk to the pictures. Man,

0:17:34.960 --> 0:17:35.879
<v Speaker 1>go back to your computer.

0:17:36.960 --> 0:17:39.760
<v Speaker 2>Yeah no, no, I mean thankfully I got to be

0:17:40.400 --> 0:17:43.280
<v Speaker 2>in the in the room as you know, dark Walld,

0:17:43.320 --> 0:17:47.439
<v Speaker 2>the interaction is happening. But I think that is the

0:17:47.440 --> 0:17:52.439
<v Speaker 2>the art of coaching that is so important is understanding

0:17:52.960 --> 0:17:55.960
<v Speaker 2>the picture and how the pitcher thinks about themselves and

0:17:56.080 --> 0:18:00.080
<v Speaker 2>giving the right feedback to have the picture do the

0:18:00.119 --> 0:18:02.240
<v Speaker 2>thing that you that you want them to do.

0:18:02.800 --> 0:18:06.000
<v Speaker 1>Uh huh. Knowing how to talk to a player in

0:18:06.040 --> 0:18:09.360
<v Speaker 1>a way that is not generic. Presumably different pitchers need

0:18:09.400 --> 0:18:12.680
<v Speaker 1>to hear different things, even if the outcome is the same, right.

0:18:12.760 --> 0:18:15.399
<v Speaker 2>I mean, there's a there's a classic like debate in

0:18:15.520 --> 0:18:19.200
<v Speaker 2>baseball of like do you swing down on the ball

0:18:19.320 --> 0:18:22.280
<v Speaker 2>or do you swing with an uppercut? And in reality,

0:18:22.440 --> 0:18:25.760
<v Speaker 2>like the batpath is an arc, the path goes down

0:18:25.800 --> 0:18:28.440
<v Speaker 2>and then the path goes up. But some coach, some

0:18:28.480 --> 0:18:32.120
<v Speaker 2>players respond better when a coach will say swing down

0:18:32.160 --> 0:18:34.960
<v Speaker 2>on the ball, and some players spawn better when a

0:18:35.000 --> 0:18:37.040
<v Speaker 2>coach will say, you know, have get a little bit

0:18:37.040 --> 0:18:39.640
<v Speaker 2>more uppercut, do your swing. But in reality, you know,

0:18:39.960 --> 0:18:41.760
<v Speaker 2>the bat goes down and the bat goes up. So

0:18:41.800 --> 0:18:44.639
<v Speaker 2>it's like really understanding what is the player what helps

0:18:44.640 --> 0:18:45.520
<v Speaker 2>the player the most?

0:18:45.960 --> 0:18:48.320
<v Speaker 1>So I heard you use this phrase in another interview

0:18:48.680 --> 0:18:50.600
<v Speaker 1>that I think is kind of what you're talking about here,

0:18:50.600 --> 0:18:54.159
<v Speaker 1>And it's feel versus real? What is that? What is

0:18:54.160 --> 0:18:55.080
<v Speaker 1>feel versus real?

0:18:55.320 --> 0:18:59.480
<v Speaker 2>So it's exactly what we're talking about. Is sometimes with

0:18:59.560 --> 0:19:03.080
<v Speaker 2>the apt let feels like they're doing is not.

0:19:03.359 --> 0:19:05.000
<v Speaker 3>What's actually happening.

0:19:05.200 --> 0:19:08.480
<v Speaker 2>But if you understand what the athlete feels like they're doing,

0:19:08.920 --> 0:19:12.720
<v Speaker 2>you can give feedback that interacts with how they're feeling.

0:19:12.960 --> 0:19:16.000
<v Speaker 2>So if they feel like they're swinging down on the

0:19:16.040 --> 0:19:18.880
<v Speaker 2>ball and you give them feedback related to that, even

0:19:18.880 --> 0:19:21.560
<v Speaker 2>if they're actually swinging with an uppercut, you know, the

0:19:21.640 --> 0:19:24.119
<v Speaker 2>important thing is like how do they feel and how

0:19:24.160 --> 0:19:26.520
<v Speaker 2>do you give them feedback related to how they feel,

0:19:26.760 --> 0:19:30.400
<v Speaker 2>which then impacts is real. But it's understanding the interplay

0:19:30.400 --> 0:19:31.600
<v Speaker 2>between the feel and the real.

0:19:32.920 --> 0:19:36.840
<v Speaker 1>Yeah, it's wild that, like there is there is a

0:19:36.920 --> 0:19:39.800
<v Speaker 1>human being doing a thing, and then there's this huge

0:19:39.920 --> 0:19:44.560
<v Speaker 1>industrial machinery of your company and the team and all

0:19:44.600 --> 0:19:47.639
<v Speaker 1>of these scientists and all these cameras and computers that

0:19:47.680 --> 0:19:50.640
<v Speaker 1>are trying to get this human being to change their

0:19:50.640 --> 0:19:52.320
<v Speaker 1>behavior in a very subtle way.

0:19:52.440 --> 0:19:52.960
<v Speaker 3>Yeah, exactly.

0:19:53.000 --> 0:19:57.560
<v Speaker 1>It's a behavior that is in many ways intuitive right,

0:19:57.600 --> 0:20:00.520
<v Speaker 1>it's sort of partly conscious but partly intuitive him like

0:20:00.560 --> 0:20:05.480
<v Speaker 1>there's a really interesting human being at the center.

0:20:05.200 --> 0:20:05.840
<v Speaker 3>Of all of this.

0:20:06.160 --> 0:20:09.080
<v Speaker 2>Yeah, And I think that's also why it's so important

0:20:09.600 --> 0:20:12.720
<v Speaker 2>to have the coach in the loop, because they understand

0:20:13.160 --> 0:20:15.800
<v Speaker 2>the human being even beyond just like the feel versus

0:20:15.800 --> 0:20:19.240
<v Speaker 2>real aspect of like did the athlete not get a

0:20:19.240 --> 0:20:21.560
<v Speaker 2>good night's sleep last night, then maybe today is not

0:20:21.760 --> 0:20:24.000
<v Speaker 2>a good day to give them feedback. Are they going

0:20:24.040 --> 0:20:27.040
<v Speaker 2>through challenges, you know, with a significant other, are they

0:20:27.080 --> 0:20:30.040
<v Speaker 2>going through challenges in other ways? Or today are they

0:20:30.080 --> 0:20:31.920
<v Speaker 2>really fired up? So today is a really good day

0:20:31.920 --> 0:20:34.879
<v Speaker 2>to give them feedback. It's like understanding the human being.

0:20:34.920 --> 0:20:38.000
<v Speaker 2>I'll give him a shout out. Connor McGuinness is the

0:20:38.000 --> 0:20:41.439
<v Speaker 2>assistant pitching coach right now for the Dodgers, and he

0:20:41.640 --> 0:20:44.280
<v Speaker 2>was so good at this. He would always talk about

0:20:45.040 --> 0:20:49.919
<v Speaker 2>he never felt comfortable truly coaching a player until the

0:20:49.960 --> 0:20:52.159
<v Speaker 2>player trusted him, until he felt like he had a

0:20:52.160 --> 0:20:54.760
<v Speaker 2>good enough relationship with the player with the player would

0:20:54.880 --> 0:20:57.239
<v Speaker 2>feel comfortable taking his feedback.

0:20:57.280 --> 0:20:59.560
<v Speaker 1>Like start with the player as a human beings, Start

0:20:59.600 --> 0:21:01.760
<v Speaker 1>with the player and get to get to.

0:21:02.400 --> 0:21:04.119
<v Speaker 2>And this is why I think it's going to be

0:21:04.200 --> 0:21:09.920
<v Speaker 2>really really difficult to have a product that goes direct

0:21:10.080 --> 0:21:12.919
<v Speaker 2>to a player. We've dabbled with that, you know, and

0:21:13.000 --> 0:21:15.679
<v Speaker 2>lots of companies have dabbled with film yourself with your

0:21:15.680 --> 0:21:19.680
<v Speaker 2>iPhone and you get some feedback, you know, on your movement.

0:21:20.280 --> 0:21:23.800
<v Speaker 2>But I think there's so much subjective stuff that goes

0:21:23.800 --> 0:21:26.600
<v Speaker 2>into what we're talking about, how does the athlete move

0:21:26.720 --> 0:21:29.280
<v Speaker 2>and how do they feel like they're moving, that I

0:21:29.280 --> 0:21:31.000
<v Speaker 2>think it's going to be really hard to solve the

0:21:31.119 --> 0:21:34.080
<v Speaker 2>challenge of giving an athlete feedback without a coach.

0:21:36.800 --> 0:21:40.120
<v Speaker 1>In a minute, Jimmy's work in the NBA and why

0:21:40.160 --> 0:21:43.480
<v Speaker 1>figuring out how to help NBA players shoot better is

0:21:43.520 --> 0:21:55.159
<v Speaker 1>actually a really hard problem. What are you doing in basketball?

0:21:55.960 --> 0:21:59.280
<v Speaker 2>Basketball is very very cool because it's a slightly different

0:21:59.760 --> 0:22:05.120
<v Speaker 2>channe In baseball, like we've been talking about, the challenge

0:22:05.119 --> 0:22:10.200
<v Speaker 2>for a pitcher is mostly just maximizing efficiency, or even

0:22:10.240 --> 0:22:12.600
<v Speaker 2>for a hitter, you know, they're reacting to the pitcher,

0:22:13.040 --> 0:22:15.399
<v Speaker 2>but they're still trying to swing as hard as they

0:22:15.440 --> 0:22:17.880
<v Speaker 2>can and hit the ball as far as they can.

0:22:18.359 --> 0:22:20.760
<v Speaker 2>So basketball is very different because you got a target.

0:22:22.280 --> 0:22:24.479
<v Speaker 2>You're not trying to do this thing as hard as

0:22:24.560 --> 0:22:25.520
<v Speaker 2>humanly possible.

0:22:25.880 --> 0:22:28.280
<v Speaker 1>The target is the hoop. The targets to be clear, the.

0:22:28.200 --> 0:22:29.160
<v Speaker 3>Target is the hoop.

0:22:29.359 --> 0:22:33.880
<v Speaker 2>So that's a really interesting kind of like motor control

0:22:34.080 --> 0:22:37.679
<v Speaker 2>problem of no matter where you are on the court,

0:22:38.240 --> 0:22:41.040
<v Speaker 2>how good are you at getting the ball to do

0:22:41.080 --> 0:22:44.120
<v Speaker 2>what you want it to do. We've been finding that

0:22:44.160 --> 0:22:49.600
<v Speaker 2>there seems to be lots of trade offs that good

0:22:49.600 --> 0:22:53.000
<v Speaker 2>shooters are making regarding like when do they release the

0:22:53.000 --> 0:22:55.879
<v Speaker 2>ball in the course of their jump, how high of

0:22:55.920 --> 0:22:58.600
<v Speaker 2>an arc do they use when they release the ball,

0:22:59.080 --> 0:23:01.639
<v Speaker 2>how high they have their release point when they.

0:23:01.520 --> 0:23:02.160
<v Speaker 3>Release the ball.

0:23:02.400 --> 0:23:05.360
<v Speaker 2>So there's all sorts of trade offs that these shooters

0:23:05.400 --> 0:23:09.240
<v Speaker 2>seem to be making related to how good they are

0:23:09.440 --> 0:23:13.360
<v Speaker 2>at controlling their own jump, controlling their own velocity, where

0:23:13.359 --> 0:23:15.520
<v Speaker 2>they are on the court, how close the nearest defender is.

0:23:16.040 --> 0:23:17.880
<v Speaker 2>It's it's a very different problem.

0:23:18.240 --> 0:23:21.440
<v Speaker 1>Sounds way harder, sounds way way harder, is that right

0:23:22.040 --> 0:23:25.000
<v Speaker 1>for you? Harder for you to sort of solve to

0:23:25.600 --> 0:23:27.800
<v Speaker 1>write a report that says, do this different thing and

0:23:27.840 --> 0:23:30.120
<v Speaker 1>you'll hit a higher percentage of your shots.

0:23:29.840 --> 0:23:33.320
<v Speaker 2>Right exactly? Yeah, And which makes it which makes it fun.

0:23:33.400 --> 0:23:34.960
<v Speaker 2>I love solving hard podcasts.

0:23:35.640 --> 0:23:37.840
<v Speaker 1>What have you solved in basketball so far?

0:23:38.280 --> 0:23:40.480
<v Speaker 2>The big the first challenge that we had to solve

0:23:40.600 --> 0:23:44.399
<v Speaker 2>was the scale challenge in basketball. There isn't quite as

0:23:44.520 --> 0:23:48.720
<v Speaker 2>much there aren't quite as many games in basketball, but

0:23:49.119 --> 0:23:52.920
<v Speaker 2>the data is a lot harder to parse because the

0:23:53.359 --> 0:23:57.000
<v Speaker 2>events aren't as distinct. It's not like it's not like

0:23:57.280 --> 0:23:59.479
<v Speaker 2>this is a shot, I mean only for free throws.

0:23:59.560 --> 0:24:01.400
<v Speaker 1>It's a more continuous.

0:24:00.880 --> 0:24:03.760
<v Speaker 2>Continuous motion. So the first big challenge was how do

0:24:03.800 --> 0:24:06.840
<v Speaker 2>we even just isolate the events that we care about.

0:24:06.800 --> 0:24:09.200
<v Speaker 1>Like what is time? When does a shot begin? When

0:24:09.240 --> 0:24:10.840
<v Speaker 1>does a time equals zero for shot?

0:24:11.000 --> 0:24:15.520
<v Speaker 2>But kind of debatable, right exactly. So that, yeah, that

0:24:15.600 --> 0:24:17.120
<v Speaker 2>was the first big challenge that we had to solve.

0:24:17.240 --> 0:24:21.160
<v Speaker 2>Was just sort of like the data engineering challenge. And now,

0:24:21.240 --> 0:24:26.880
<v Speaker 2>like I said, our reports are more than telling you,

0:24:26.880 --> 0:24:29.240
<v Speaker 2>you know, how to be more or less efficient. It's

0:24:29.240 --> 0:24:32.280
<v Speaker 2>trying to surface the trade offs that you're making. Where

0:24:32.280 --> 0:24:34.639
<v Speaker 2>in your jump are you are you releasing the ball,

0:24:34.920 --> 0:24:37.480
<v Speaker 2>how high is your release point? What kind of arc

0:24:37.600 --> 0:24:40.160
<v Speaker 2>are you using? And how does that compare to other

0:24:40.320 --> 0:24:41.320
<v Speaker 2>arcs you could be using?

0:24:41.600 --> 0:24:43.280
<v Speaker 1>What like what what are the trade offs?

0:24:44.560 --> 0:24:50.120
<v Speaker 2>A really really interesting trade off to me is how

0:24:50.200 --> 0:24:53.119
<v Speaker 2>much arc are you putting on the basketball? Not just

0:24:53.200 --> 0:24:57.000
<v Speaker 2>to like evade a defender. But there's a trade off

0:24:57.040 --> 0:25:00.800
<v Speaker 2>where if you shoot the ball at a highhigher arc,

0:25:01.680 --> 0:25:04.560
<v Speaker 2>you have to use more velocity to get the ball

0:25:04.560 --> 0:25:06.520
<v Speaker 2>to go all the way to the rim.

0:25:07.119 --> 0:25:10.640
<v Speaker 1>Right, because it's going to travel farther in total in space.

0:25:10.600 --> 0:25:15.480
<v Speaker 2>Right, And if you are not the most coordinated human,

0:25:16.080 --> 0:25:18.919
<v Speaker 2>it might be harder for you to add more velocity

0:25:19.840 --> 0:25:22.399
<v Speaker 2>in a really in a really precise way. So the

0:25:22.440 --> 0:25:25.440
<v Speaker 2>more arc you have, the more prone you can be

0:25:25.600 --> 0:25:29.480
<v Speaker 2>to what we would call like velocity errors overshooting undershooting.

0:25:29.880 --> 0:25:33.240
<v Speaker 2>The advantage you get when you create more arc is

0:25:33.240 --> 0:25:35.760
<v Speaker 2>if you if you imagine the ball coming down from

0:25:35.760 --> 0:25:38.119
<v Speaker 2>that arc and the angle the angle with which it

0:25:38.160 --> 0:25:41.200
<v Speaker 2>approaches the rim, it approaches at a steeper angle, which

0:25:41.240 --> 0:25:44.199
<v Speaker 2>means you literally have more rim to aim at.

0:25:44.560 --> 0:25:46.440
<v Speaker 3>So if you're hot, so if you shoot.

0:25:46.160 --> 0:25:49.000
<v Speaker 2>Higher, you know this is a steph Curry thing. He

0:25:49.040 --> 0:25:52.760
<v Speaker 2>has a really high arc. Presumably this is the hypothesis,

0:25:52.800 --> 0:25:55.120
<v Speaker 2>because he's one of the most coordinated humans on the.

0:25:55.040 --> 0:25:59.480
<v Speaker 1>Planet, so he sea.

0:25:59.359 --> 0:26:01.680
<v Speaker 2>So he can use a really high arc because he's

0:26:01.760 --> 0:26:05.000
<v Speaker 2>really good at controlling his velocity output. Oh huh, so

0:26:05.040 --> 0:26:07.680
<v Speaker 2>he can really dial in how hard he releases the ball,

0:26:07.960 --> 0:26:10.160
<v Speaker 2>which means he gets the advantage of having more rimmed

0:26:10.160 --> 0:26:13.240
<v Speaker 2>to aim at, where as somebody who's bad at controlling

0:26:13.280 --> 0:26:16.040
<v Speaker 2>their velocity output when they try to aim higher, they'll

0:26:16.080 --> 0:26:17.399
<v Speaker 2>just overshoot an undershoot.

0:26:17.720 --> 0:26:20.880
<v Speaker 1>So is the notion, and this is something of an oversimplification,

0:26:21.040 --> 0:26:26.080
<v Speaker 1>but that for any given level of coordination, there is

0:26:26.119 --> 0:26:29.199
<v Speaker 1>some optimal arc, and the more coordinated you are, the

0:26:29.280 --> 0:26:33.280
<v Speaker 1>higher the optimal arc would be for you setting aside defense.

0:26:33.760 --> 0:26:35.280
<v Speaker 3>Maybe that's the hypothesis.

0:26:35.800 --> 0:26:38.879
<v Speaker 1>Yeah, I mean that seems like where what you were

0:26:38.920 --> 0:26:40.200
<v Speaker 1>saying goes exactly.

0:26:40.280 --> 0:26:42.680
<v Speaker 2>Yeah, that's the hypothesis. So that's what we're trying to

0:26:42.720 --> 0:26:43.160
<v Speaker 2>look into.

0:26:43.840 --> 0:26:46.960
<v Speaker 1>Okay, I'll be curious to see what you figure out.

0:26:47.600 --> 0:26:50.080
<v Speaker 1>Are free throws easier? Did you think of starting with

0:26:50.119 --> 0:26:50.679
<v Speaker 1>free throws?

0:26:51.200 --> 0:26:52.320
<v Speaker 3>Yeah?

0:26:52.520 --> 0:26:56.080
<v Speaker 2>Right, right now. Honestly, the phase we're at in basketball

0:26:57.960 --> 0:27:01.480
<v Speaker 2>is mostly just collecting a lot of data. So you know,

0:27:01.520 --> 0:27:04.159
<v Speaker 2>a starting pitcher will you know, throw ninety pitches in

0:27:04.200 --> 0:27:05.639
<v Speaker 2>a game, and now you have a sample size of

0:27:05.960 --> 0:27:08.840
<v Speaker 2>ninety pitches that are all the same, whereas a basketball

0:27:08.840 --> 0:27:11.320
<v Speaker 2>shooter only has a couple of free throws in a game.

0:27:12.160 --> 0:27:15.280
<v Speaker 2>You know, we're working on ways with teams of collecting

0:27:15.400 --> 0:27:18.320
<v Speaker 2>data in a practice setting, so getting a lot of

0:27:18.320 --> 0:27:22.320
<v Speaker 2>this data in a bigger chunks. But really at this

0:27:22.359 --> 0:27:24.520
<v Speaker 2>point it's collecting a lot of data so we can

0:27:24.600 --> 0:27:27.320
<v Speaker 2>do some of this research to explore some of these hypotheses.

0:27:27.640 --> 0:27:31.240
<v Speaker 1>Huh. So it seems like in basketball you're where you

0:27:31.280 --> 0:27:33.120
<v Speaker 1>were ten years ago or something in.

0:27:33.040 --> 0:27:34.840
<v Speaker 3>Baseball, right exactly.

0:27:35.440 --> 0:27:40.520
<v Speaker 1>So basketball is sort of one kind of frontier. It

0:27:40.560 --> 0:27:42.480
<v Speaker 1>seems like one thing you're trying to figure out and

0:27:42.520 --> 0:27:44.800
<v Speaker 1>haven't really cracked yet. What are some of the other

0:27:45.800 --> 0:27:48.359
<v Speaker 1>frontiers the other things you're figuring out, whether it's in

0:27:48.440 --> 0:27:51.520
<v Speaker 1>baseball or in the fundamental technology or whatever. What are

0:27:51.560 --> 0:27:52.000
<v Speaker 1>you working on?

0:27:54.000 --> 0:27:59.159
<v Speaker 2>We want to try to have a computer vision be

0:27:59.400 --> 0:28:04.639
<v Speaker 2>even more accessible. You know, there's been a lot and

0:28:04.680 --> 0:28:07.240
<v Speaker 2>a lot, a lot a lot of improvements over the

0:28:07.320 --> 0:28:11.080
<v Speaker 2>last ten years in computer vision where you can do

0:28:11.200 --> 0:28:17.520
<v Speaker 2>really good motion capture with just your iPhone, but still

0:28:17.560 --> 0:28:25.320
<v Speaker 2>for certain specialized movements, pitching, shooting, things like that, there's

0:28:25.320 --> 0:28:27.640
<v Speaker 2>still have little ways to go to get really really

0:28:27.640 --> 0:28:30.720
<v Speaker 2>good data straight from your iPhone. So that's one of

0:28:30.760 --> 0:28:35.160
<v Speaker 2>the frontiers, is like continuing to try to help understand

0:28:35.160 --> 0:28:39.640
<v Speaker 2>how to make computer vision more accessible. Another one is

0:28:40.640 --> 0:28:46.160
<v Speaker 2>more fitness based analysis. You know, it's interesting to think

0:28:46.200 --> 0:28:50.040
<v Speaker 2>about companies like Mirror and companies that have tried to

0:28:50.080 --> 0:28:55.080
<v Speaker 2>give people feedback and like a fitness environment, But how

0:28:55.120 --> 0:28:58.080
<v Speaker 2>do you give someone or how do you give like

0:28:58.120 --> 0:29:00.840
<v Speaker 2>a strength and conditioning coach good feedback that can be

0:29:00.960 --> 0:29:03.920
<v Speaker 2>used in a weight room setting. Yeah, and then continue

0:29:03.960 --> 0:29:07.680
<v Speaker 2>to explore other emotions and other sports, Like football is

0:29:07.680 --> 0:29:12.080
<v Speaker 2>a really interesting one because a lot of football is

0:29:12.360 --> 0:29:17.080
<v Speaker 2>interacting with other humans. Indeed, yeah, I mean that's obvious,

0:29:17.800 --> 0:29:21.680
<v Speaker 2>but like, how do you get a takeaway from like

0:29:21.760 --> 0:29:23.120
<v Speaker 2>two linemen interacting?

0:29:24.000 --> 0:29:26.440
<v Speaker 1>Ye, things, but that one I wonder. I mean, it

0:29:26.760 --> 0:29:29.560
<v Speaker 1>seems like if you think of the line, you know,

0:29:29.920 --> 0:29:33.400
<v Speaker 1>in football, it's so they're so on top of each other,

0:29:33.480 --> 0:29:35.360
<v Speaker 1>the defensive line, of the defensive line, that I feel

0:29:35.360 --> 0:29:37.320
<v Speaker 1>like vision might not be what you want. You might

0:29:37.360 --> 0:29:40.720
<v Speaker 1>want sensors, right, you might want pressure sensors in the

0:29:40.840 --> 0:29:43.040
<v Speaker 1>lineman's clothes or something. I don't know, I'm just making

0:29:43.080 --> 0:29:45.080
<v Speaker 1>that up, but like it seems like that might be

0:29:45.120 --> 0:29:47.000
<v Speaker 1>more useful, just because it's hard to see what's going

0:29:47.000 --> 0:29:47.680
<v Speaker 1>on in the line.

0:29:47.760 --> 0:29:48.040
<v Speaker 3>Yeah.

0:29:48.160 --> 0:29:52.920
<v Speaker 2>Yeah, yeah, except professional athletes don't like wearing random.

0:29:52.640 --> 0:29:57.120
<v Speaker 1>Things, well are aren't people trying to make sensors like

0:29:57.400 --> 0:29:59.400
<v Speaker 1>woven into the clothes. I mean, I feel like there

0:29:59.400 --> 0:30:02.080
<v Speaker 1>are ways you would just be putting on your jersey

0:30:02.160 --> 0:30:03.960
<v Speaker 1>or putting on your paths or whatever and they would

0:30:03.960 --> 0:30:04.920
<v Speaker 1>have the sensors built in.

0:30:05.040 --> 0:30:06.160
<v Speaker 3>Yeah. Yeah, one hundred percent.

0:30:06.200 --> 0:30:09.840
<v Speaker 2>There's lots of really cool technology of that is you know,

0:30:10.600 --> 0:30:13.760
<v Speaker 2>you know, microscopic sensors that are just woven, woven into

0:30:13.760 --> 0:30:15.480
<v Speaker 2>clothing for sure.

0:30:16.440 --> 0:30:20.040
<v Speaker 1>So so let's talk for a second more about the

0:30:20.080 --> 0:30:23.080
<v Speaker 1>consumer side. You sort of touched on it and moved on.

0:30:23.160 --> 0:30:25.960
<v Speaker 1>I mean, is that are you actively working on that

0:30:26.120 --> 0:30:28.320
<v Speaker 1>or is that just like yeah, it kind of seems interesting,

0:30:28.360 --> 0:30:30.640
<v Speaker 1>but not for now. We're too busy, like what's what's

0:30:30.640 --> 0:30:32.120
<v Speaker 1>happening on the consumer side.

0:30:33.120 --> 0:30:37.640
<v Speaker 2>We're not actively tackling in the consumer side right now.

0:30:37.720 --> 0:30:40.560
<v Speaker 2>And that the reason why we started with professional sports

0:30:40.640 --> 0:30:42.920
<v Speaker 2>is one it's because like it's what I know, you know,

0:30:42.960 --> 0:30:47.600
<v Speaker 2>I work for the Dodgers, but also because the value

0:30:47.680 --> 0:30:52.920
<v Speaker 2>proposition of what we're doing is so impactful. You know, yeah,

0:30:53.000 --> 0:30:54.920
<v Speaker 2>you know, you understand, you try to understand, like the

0:30:54.960 --> 0:30:58.120
<v Speaker 2>relationship between people have tried to put numbers on this,

0:30:58.280 --> 0:31:01.040
<v Speaker 2>it's the people have estimated, it's in the millions of dollars.

0:31:01.080 --> 0:31:03.920
<v Speaker 2>But the value of adding one mile an hour of

0:31:04.240 --> 0:31:08.080
<v Speaker 2>fastball velocity to a picture, you know, people have valued that,

0:31:08.360 --> 0:31:10.360
<v Speaker 2>We have valued that in millions of dollars.

0:31:10.880 --> 0:31:13.160
<v Speaker 1>Well, sure you will tell you millions of dollars, But

0:31:13.560 --> 0:31:16.800
<v Speaker 1>what is the like, I don't know what's a what's

0:31:16.800 --> 0:31:18.960
<v Speaker 1>a what's a top picture make? These days? I don't

0:31:18.960 --> 0:31:19.680
<v Speaker 1>even know anymore.

0:31:20.640 --> 0:31:21.960
<v Speaker 3>I mean, you want to talk about show.

0:31:23.680 --> 0:31:28.320
<v Speaker 1>Half a billion, hundreds of millions, half a billion? Yeah,

0:31:28.360 --> 0:31:32.480
<v Speaker 1>so so right, so so the marginal benefit has a

0:31:32.600 --> 0:31:35.480
<v Speaker 1>very large value. Yah a million dollars against one hundred

0:31:35.520 --> 0:31:37.800
<v Speaker 1>million dollars, like one percent better. If they're making a

0:31:37.880 --> 0:31:40.240
<v Speaker 1>hundred million dollars, it's worth a million dollars presumably.

0:31:40.400 --> 0:31:43.200
<v Speaker 2>Yeah, And we start to get the pro sports teams

0:31:43.200 --> 0:31:44.200
<v Speaker 2>to believe.

0:31:43.840 --> 0:31:48.120
<v Speaker 1>That, well, how many how many pro sports teams are

0:31:48.200 --> 0:31:50.360
<v Speaker 1>paying you at this point, about uh.

0:31:51.320 --> 0:31:54.480
<v Speaker 2>Close to ten in Major League Baseball and a couple

0:31:54.520 --> 0:31:55.040
<v Speaker 2>in the NBA.

0:31:55.120 --> 0:31:56.080
<v Speaker 3>The NBA is a lot newer.

0:31:57.240 --> 0:31:59.520
<v Speaker 1>And how big is the field? Like, what's sort of

0:31:59.560 --> 0:32:03.360
<v Speaker 1>the state of play in the field of I don't

0:32:03.360 --> 0:32:06.360
<v Speaker 1>even know what to say. Biomechanics as a service seems

0:32:06.360 --> 0:32:09.160
<v Speaker 1>like a niche construction of it. But what would you

0:32:09.200 --> 0:32:12.680
<v Speaker 1>say sports analytics? I mean, I guess that's not quite right.

0:32:12.720 --> 0:32:14.640
<v Speaker 1>What how do you construct the broader field?

0:32:15.840 --> 0:32:18.920
<v Speaker 2>Sports analytics is definitely a part of it. The data

0:32:18.920 --> 0:32:25.080
<v Speaker 2>that we provide is novel or is different than like

0:32:25.200 --> 0:32:28.400
<v Speaker 2>traditional sports analytics. So we don't really have a lot

0:32:28.440 --> 0:32:37.480
<v Speaker 2>of companies as competitors. Honestly, our biggest competitors are teams

0:32:38.280 --> 0:32:40.440
<v Speaker 2>wanting to try to do this type of thing internally.

0:32:40.760 --> 0:32:42.880
<v Speaker 2>How you know, hire a bunch of data engineers, hire

0:32:42.880 --> 0:32:46.560
<v Speaker 2>a bunch of software engineers, hire people with biomechanics backgrounds,

0:32:46.600 --> 0:32:49.320
<v Speaker 2>and try to build out these pipeline processing pipelines themselves.

0:32:50.080 --> 0:32:53.760
<v Speaker 1>Does every team have like a somebody with a PhD

0:32:53.880 --> 0:32:55.720
<v Speaker 1>in biomechanics working for them now?

0:32:55.760 --> 0:32:57.240
<v Speaker 3>In baseball? Yeah?

0:32:57.440 --> 0:32:57.800
<v Speaker 1>Wow?

0:32:58.440 --> 0:33:01.600
<v Speaker 2>In basketball and not Yeah, but they're starting to.

0:33:02.320 --> 0:33:06.120
<v Speaker 1>So I know people, I mean, I think in general

0:33:06.160 --> 0:33:08.440
<v Speaker 1>baseball fans like to complain, but so one of the

0:33:08.440 --> 0:33:11.880
<v Speaker 1>things they've complained about lately is the way analytics more

0:33:11.920 --> 0:33:15.520
<v Speaker 1>broadly made the game more boring, right, like the shift

0:33:16.800 --> 0:33:21.120
<v Speaker 1>and changing pictures more frequently and whatever else people complain about.

0:33:21.720 --> 0:33:27.520
<v Speaker 1>Are you do you fit into that at all? Uh?

0:33:28.400 --> 0:33:35.440
<v Speaker 3>That's a good that's a good question. Some people.

0:33:35.680 --> 0:33:38.680
<v Speaker 2>Some people complain about how hard pictures are throwing these

0:33:38.760 --> 0:33:43.000
<v Speaker 2>days because it creates more strikeouts, and people think strikeouts

0:33:43.000 --> 0:33:43.440
<v Speaker 2>are boring.

0:33:45.360 --> 0:33:47.200
<v Speaker 3>So maybe, yeah, so.

0:33:47.200 --> 0:33:50.600
<v Speaker 1>Maybe you need to get better at helping hitters. Really

0:33:50.680 --> 0:33:53.240
<v Speaker 1>you're out that way, you can even at back up, all.

0:33:53.200 --> 0:33:55.560
<v Speaker 2>Right, And that's what we talked about takeaways four Hitters

0:33:55.640 --> 0:33:58.160
<v Speaker 2>are harder because they're reacting to the picture.

0:33:59.000 --> 0:34:02.640
<v Speaker 1>So if you think about the field, what your company

0:34:02.720 --> 0:34:05.600
<v Speaker 1>say in five years, yeah, whatever is your kind of

0:34:05.680 --> 0:34:09.640
<v Speaker 1>medium term future that you think about, what is the

0:34:09.680 --> 0:34:12.680
<v Speaker 1>company in the sort of the world, the sports world

0:34:12.680 --> 0:34:15.560
<v Speaker 1>that you're interacting with look like at that time and

0:34:15.640 --> 0:34:17.359
<v Speaker 1>say whatever, five years, ten years.

0:34:18.800 --> 0:34:23.799
<v Speaker 2>What I hope is that what we are trying to

0:34:23.880 --> 0:34:32.680
<v Speaker 2>foster is an environment where coaches have really incredible tools

0:34:32.680 --> 0:34:35.920
<v Speaker 2>at their disposal to understand how an athlete moves. So,

0:34:35.960 --> 0:34:38.359
<v Speaker 2>you know, we talk about the very beginning where sort

0:34:38.400 --> 0:34:40.840
<v Speaker 2>of the still more or less the state of the

0:34:40.960 --> 0:34:43.560
<v Speaker 2>art is a coach just looks at an athlete, watches

0:34:43.680 --> 0:34:46.200
<v Speaker 2>video of an athlete, and tries to give the athlete

0:34:46.239 --> 0:34:48.840
<v Speaker 2>feedback regarding what they see on the video, what they

0:34:48.880 --> 0:34:52.880
<v Speaker 2>see with their eyes. We hope that the standard becomes

0:34:54.040 --> 0:34:59.399
<v Speaker 2>you use an analytical tool to help you understand how

0:34:59.440 --> 0:35:02.920
<v Speaker 2>the athlete is moving and to really like level up

0:35:02.960 --> 0:35:06.480
<v Speaker 2>your coaching because now you have this objective information about

0:35:06.480 --> 0:35:09.120
<v Speaker 2>how the athlete is moving. I kind of I kind

0:35:09.120 --> 0:35:13.960
<v Speaker 2>of make the analogy related to just radar guns. Before

0:35:14.080 --> 0:35:17.040
<v Speaker 2>radar guns were a thing, a coach would just like

0:35:17.160 --> 0:35:18.919
<v Speaker 2>look at a picture and be like, oh, that looks

0:35:18.920 --> 0:35:22.600
<v Speaker 2>pretty fast, you know, make an adjustment, and I think

0:35:22.640 --> 0:35:27.239
<v Speaker 2>that looks a little faster. But then radar guns came out,

0:35:27.239 --> 0:35:30.120
<v Speaker 2>and you could actually measure how fast the picture was throwing,

0:35:30.400 --> 0:35:33.040
<v Speaker 2>and you could actually measure if the picture is getting

0:35:33.440 --> 0:35:35.280
<v Speaker 2>throwing the ball harder based on your feedback.

0:35:35.800 --> 0:35:39.160
<v Speaker 1>Yeah, and now you're you're doing that but in a

0:35:40.560 --> 0:35:41.920
<v Speaker 1>in a way more complex way.

0:35:41.960 --> 0:35:42.360
<v Speaker 3>Exactly.

0:35:42.520 --> 0:35:50.000
<v Speaker 1>Yeah, we'll be back in a minute with the lightning round.

0:36:01.640 --> 0:36:03.319
<v Speaker 1>Let's do the lightning rounds. Let's start with a few

0:36:03.320 --> 0:36:07.840
<v Speaker 1>baseball questions. Who's the most underrated picture of all time?

0:36:08.800 --> 0:36:16.840
<v Speaker 2>Whoa underrated picture of all time? Oh my goodness, I

0:36:16.840 --> 0:36:19.640
<v Speaker 2>don't know if I can give you one that's like

0:36:20.280 --> 0:36:22.600
<v Speaker 2>all time, because I don't know if that's fair. I'm

0:36:22.640 --> 0:36:24.959
<v Speaker 2>sure I'm not thinking of everybody of.

0:36:24.880 --> 0:36:26.440
<v Speaker 1>Your lifetime, of your lifetime.

0:36:26.440 --> 0:36:29.880
<v Speaker 3>I grew up a hardcore Red Sox fan.

0:36:29.960 --> 0:36:33.520
<v Speaker 2>I grew up in Rhode Island, and the first one

0:36:33.520 --> 0:36:37.120
<v Speaker 2>that comes to mind mostly in the Red Sox atmosphere,

0:36:37.160 --> 0:36:39.280
<v Speaker 2>but I wonder if you could make a broader argument

0:36:39.400 --> 0:36:43.759
<v Speaker 2>was Tim Wakefield, who was a knuckleball pitcher for the

0:36:43.800 --> 0:36:48.600
<v Speaker 2>Red Sox and what made amazing physics amazing physics and aerodynamics,

0:36:49.160 --> 0:36:53.400
<v Speaker 2>And the reason being is he just did so many

0:36:53.400 --> 0:36:55.840
<v Speaker 2>things for the Red Sox, ate up so many innings

0:36:56.120 --> 0:37:00.959
<v Speaker 2>and was so effective closing, starting, whatever, But he never

0:37:01.200 --> 0:37:05.120
<v Speaker 2>got incredible recognition because it was a knuckleball that was going,

0:37:05.160 --> 0:37:06.719
<v Speaker 2>you know, fifty five sixty miles an hour.

0:37:07.280 --> 0:37:09.239
<v Speaker 1>What's one thing you would change about baseball to make

0:37:09.280 --> 0:37:10.080
<v Speaker 1>it more popular?

0:37:13.000 --> 0:37:17.240
<v Speaker 2>I do feel like actually the changes that are being

0:37:17.280 --> 0:37:22.239
<v Speaker 2>made are good ones, in like reducing the amount of downtime.

0:37:23.080 --> 0:37:25.719
<v Speaker 1>A pitch clock, it's one, is that the way you're

0:37:25.719 --> 0:37:26.120
<v Speaker 1>thinking of?

0:37:26.239 --> 0:37:29.000
<v Speaker 2>Or yeah, yeah, yeah, exactly, yeah, a pitch clock. The

0:37:29.080 --> 0:37:32.160
<v Speaker 2>thing that's challenging for me as a biomechanist is when

0:37:32.160 --> 0:37:34.680
<v Speaker 2>you reduced the amount of time that a pitcher has

0:37:35.160 --> 0:37:39.840
<v Speaker 2>to throw, you theoretically could introduce more fatigue, which theoretically

0:37:39.880 --> 0:37:42.480
<v Speaker 2>also introduces more injury risk. So this is something that

0:37:42.520 --> 0:37:46.839
<v Speaker 2>we've been thinking about. Is like, So for me, while

0:37:46.840 --> 0:37:50.160
<v Speaker 2>I like that change that baseball is making to make

0:37:50.200 --> 0:37:53.279
<v Speaker 2>the game, to speed the game up, I think the

0:37:53.320 --> 0:37:57.319
<v Speaker 2>pitchers also need to train a little bit differently. Oh,

0:37:57.440 --> 0:38:01.600
<v Speaker 2>that's to be able to better withstand the shorter rest time.

0:38:03.560 --> 0:38:07.799
<v Speaker 1>Are there aspects of your work and the changes you've

0:38:07.840 --> 0:38:11.799
<v Speaker 1>seen over the course of your career that illuminate sort

0:38:11.840 --> 0:38:15.400
<v Speaker 1>of broader changes in computer vision and AI more generally.

0:38:16.560 --> 0:38:19.239
<v Speaker 2>Yeah, In particular, the most important one has been the

0:38:19.280 --> 0:38:23.279
<v Speaker 2>improvement in computer vision, which because computer vision at its

0:38:23.360 --> 0:38:28.000
<v Speaker 2>core is artificial and intelligence neural networks, and as those

0:38:28.719 --> 0:38:31.239
<v Speaker 2>as that that technology has gotten better and better, you know,

0:38:31.280 --> 0:38:33.799
<v Speaker 2>the latest and greatest people always talk about like the

0:38:33.880 --> 0:38:38.000
<v Speaker 2>Transformer model really changed AI. I mean that changed computer

0:38:38.080 --> 0:38:41.160
<v Speaker 2>vision too, Like lots of the modern more modern like

0:38:41.200 --> 0:38:44.640
<v Speaker 2>computer vision models are based on transformers.

0:38:44.400 --> 0:38:46.560
<v Speaker 1>And which, to be clear to the Transformer model is

0:38:47.440 --> 0:38:50.360
<v Speaker 1>what gives us chat GPT, right, The T in GPT

0:38:50.520 --> 0:38:53.520
<v Speaker 1>is transformed, right, So how has it affected the computer vision.

0:38:53.320 --> 0:38:58.040
<v Speaker 2>Side making the models more accurate and more efficient? It

0:38:58.200 --> 0:38:59.600
<v Speaker 2>used to be you know, a couple of years ago

0:38:59.640 --> 0:39:02.239
<v Speaker 2>when I try to run a computer vision model on

0:39:02.280 --> 0:39:05.399
<v Speaker 2>my laptop, like it could take an hour just to

0:39:05.440 --> 0:39:09.839
<v Speaker 2>like analyze one pitch, one video, and now it takes

0:39:09.840 --> 0:39:11.000
<v Speaker 2>a matter of seconds.

0:39:12.960 --> 0:39:15.920
<v Speaker 1>And so what is the what is the bigger implication

0:39:16.040 --> 0:39:18.480
<v Speaker 1>of that? Beyond your beyond your work?

0:39:19.880 --> 0:39:24.200
<v Speaker 2>More and more data is available regarding how people move,

0:39:25.320 --> 0:39:27.319
<v Speaker 2>you know, like when when I first started, it was

0:39:27.360 --> 0:39:31.480
<v Speaker 2>really hard to have data in a baseball game. Now

0:39:31.600 --> 0:39:35.000
<v Speaker 2>every major league game, every minor league game, every NBA game,

0:39:35.800 --> 0:39:38.680
<v Speaker 2>maybe every G League game, every w NBA game, you know,

0:39:39.040 --> 0:39:44.279
<v Speaker 2>every single uh basketball and baseball game, you know, more

0:39:44.360 --> 0:39:48.200
<v Speaker 2>or less is now like being recorded with computer vision

0:39:48.239 --> 0:39:50.600
<v Speaker 2>to get the three dimensional data about how people are moving.

0:39:51.000 --> 0:39:54.080
<v Speaker 2>Just lots and lots of data on how people move.

0:39:54.120 --> 0:39:58.120
<v Speaker 2>And this is really impacting. I think lots of fields.

0:39:58.520 --> 0:40:02.440
<v Speaker 2>In particular, I think like self driving cars, robots that

0:40:02.480 --> 0:40:05.680
<v Speaker 2>are meant to like interact with the world, all rely

0:40:05.800 --> 0:40:08.360
<v Speaker 2>on computer vision models. I mean, I think one of

0:40:08.400 --> 0:40:11.600
<v Speaker 2>the coolest things about how cars do this sort of

0:40:11.640 --> 0:40:15.680
<v Speaker 2>thing is not only do they have to understand where

0:40:15.719 --> 0:40:20.560
<v Speaker 2>a person is now, but they're really cool models that

0:40:21.800 --> 0:40:25.200
<v Speaker 2>they take where a person is now and the last

0:40:25.320 --> 0:40:28.160
<v Speaker 2>like ten seconds of what that person did and try

0:40:28.160 --> 0:40:30.680
<v Speaker 2>to predict all the different things that the person might do.

0:40:30.960 --> 0:40:34.120
<v Speaker 2>They might run across the street, they might jump out

0:40:34.160 --> 0:40:36.120
<v Speaker 2>of the way, they might jump forward, you know, they

0:40:36.200 --> 0:40:37.520
<v Speaker 2>might run and chase a soccer ball.

0:40:38.760 --> 0:40:41.399
<v Speaker 1>I mean, my sense is all of the hard edge

0:40:41.440 --> 0:40:44.439
<v Speaker 1>cases in self driving cars. Basically, the reason we don't

0:40:44.480 --> 0:40:48.200
<v Speaker 1>truly have self driving cars yet is because people are

0:40:48.239 --> 0:40:50.800
<v Speaker 1>so hard to understate. Yeah, right, Like if the world

0:40:50.920 --> 0:40:53.840
<v Speaker 1>was all self driving cars, then it would be a

0:40:53.880 --> 0:40:56.960
<v Speaker 1>solved problem, right, Like the machine could understand what other

0:40:57.000 --> 0:40:59.959
<v Speaker 1>machines are going to do. But people, human drivers, human

0:41:00.040 --> 0:41:05.480
<v Speaker 1>pedestrians are strange and very hard for machines to understand.

0:41:06.000 --> 0:41:07.040
<v Speaker 3>Yeah.

0:41:07.120 --> 0:41:09.560
<v Speaker 1>Yeah, it's like they need a coach. It's like the

0:41:09.600 --> 0:41:18.160
<v Speaker 1>coaching problem again. We found your SoundCloud. Oh yeah, so,

0:41:18.400 --> 0:41:22.640
<v Speaker 1>Jimmy Buffett fans are called parrot heads. What are Jimmy

0:41:22.680 --> 0:41:23.880
<v Speaker 1>Buffy fans called?

0:41:26.480 --> 0:41:28.759
<v Speaker 3>I never thought about it.

0:41:31.600 --> 0:41:35.760
<v Speaker 1>You have a song called Let's have some Fruit parentheses

0:41:36.040 --> 0:41:40.400
<v Speaker 1>the fruit song is fruit a metaphor.

0:41:41.239 --> 0:41:43.680
<v Speaker 3>Leave it up to your imagination. Fair.

0:41:45.560 --> 0:41:49.120
<v Speaker 1>Jimmy Buffy is the co founder and CEO of Reboot

0:41:49.160 --> 0:42:06.040
<v Speaker 1>Motion Swanson swe Today's show was produced by Gabriel Hunter Cheng.

0:42:06.360 --> 0:42:09.719
<v Speaker 1>It was edited by Lyddy Jean Kott and engineered by

0:42:09.760 --> 0:42:13.320
<v Speaker 1>Sarah Bruguer. You can email us at problem at Pushkin

0:42:13.440 --> 0:42:16.640
<v Speaker 1>dot Fm. I'm Jacob Goldstein and we'll be back next

0:42:16.640 --> 0:42:18.960
<v Speaker 1>week with another episode of What's Your Problems