WEBVTT - Ep33  "Why do they start sprinters with a bang instead of a flash?"

0:00:04.600 --> 0:00:07.520
<v Speaker 1>Why do they use a gun at the Olympics to

0:00:07.640 --> 0:00:11.360
<v Speaker 1>start sprinters? Why not use a flash of light? And

0:00:11.400 --> 0:00:14.160
<v Speaker 1>by the way, how can a sprinter come off the

0:00:14.240 --> 0:00:18.759
<v Speaker 1>blocks after the starting gun but still get disqualified for

0:00:18.880 --> 0:00:22.760
<v Speaker 1>jumping the gun? Or here's another question. If you watch

0:00:22.800 --> 0:00:26.200
<v Speaker 1>someone dribbling a basketball, it looks like when the ball

0:00:26.320 --> 0:00:29.880
<v Speaker 1>hits the ground, the sight and the sound are synchronized,

0:00:30.240 --> 0:00:33.040
<v Speaker 1>and if you back up a ways, it still looks synchronized.

0:00:33.560 --> 0:00:36.519
<v Speaker 1>But when you get to a very particular distance one

0:00:36.600 --> 0:00:39.560
<v Speaker 1>hundred and ten feet, it suddenly goes out of sync.

0:00:40.120 --> 0:00:42.839
<v Speaker 1>Why and what does any of this have to do

0:00:42.960 --> 0:00:48.280
<v Speaker 1>with Robert Oppenheimer, or television broadcasting, or the Emperor Kubla

0:00:48.360 --> 0:00:56.960
<v Speaker 1>Khan or schizophrenia. Welcome to Inner Cosmos with me David Eagleman.

0:00:57.080 --> 0:01:00.320
<v Speaker 1>I'm a neuroscientist and an author at Stanford and in

0:01:00.360 --> 0:01:04.400
<v Speaker 1>these episodes we sail deeply into our three pound universe

0:01:04.760 --> 0:01:08.200
<v Speaker 1>to understand why and how our lives look the way

0:01:08.240 --> 0:01:17.880
<v Speaker 1>they do. Today's episode is about time perception, which is

0:01:17.920 --> 0:01:20.200
<v Speaker 1>an area that I've studied in my lab for years.

0:01:20.560 --> 0:01:24.000
<v Speaker 1>For example, my first episode was on what happens when

0:01:24.040 --> 0:01:26.880
<v Speaker 1>an event seems to go into slow motion? When you're

0:01:26.920 --> 0:01:29.720
<v Speaker 1>in fear for your life. But today we're going to

0:01:29.760 --> 0:01:34.240
<v Speaker 1>talk about a different aspect of time. And specifically, what

0:01:34.319 --> 0:01:36.240
<v Speaker 1>we're going to talk about is that you have a

0:01:36.440 --> 0:01:39.920
<v Speaker 1>three pound mission control center that sits in darkness and

0:01:40.000 --> 0:01:43.759
<v Speaker 1>silence and has to figure out the timing of events

0:01:43.800 --> 0:01:47.680
<v Speaker 1>in the outside world. But this is a massive challenge

0:01:48.120 --> 0:01:53.600
<v Speaker 1>because signals stream in through different senses at different rates,

0:01:54.200 --> 0:01:57.280
<v Speaker 1>and we'll see how and why your brain works so

0:01:57.520 --> 0:02:01.840
<v Speaker 1>hard to pull off editing trail to get the timing right.

0:02:03.040 --> 0:02:05.760
<v Speaker 1>I recently saw the movie Oppenheimer, and if you haven't

0:02:05.760 --> 0:02:08.519
<v Speaker 1>seen it yet, you should. It's terrific. It's about J.

0:02:08.800 --> 0:02:12.880
<v Speaker 1>Robert Oppenheimer, who led the Manhattan Project to build the

0:02:12.919 --> 0:02:16.280
<v Speaker 1>first nuclear bomb. As you may know, the first test

0:02:16.400 --> 0:02:18.320
<v Speaker 1>of the nuclear bomb was in the middle of New

0:02:18.360 --> 0:02:21.040
<v Speaker 1>Mexico in a place called White Sands, which is a

0:02:21.040 --> 0:02:25.639
<v Speaker 1>big empty area. They weren't sure if the nuclear bomb

0:02:25.720 --> 0:02:30.440
<v Speaker 1>was going to work, because, as Oppenheimer often said, theory

0:02:30.600 --> 0:02:34.760
<v Speaker 1>takes you only so far. So after four years of

0:02:34.800 --> 0:02:37.920
<v Speaker 1>work and two billion dollars and hundreds of people on

0:02:37.919 --> 0:02:41.320
<v Speaker 1>this project, they were finally going to get a chance

0:02:41.440 --> 0:02:45.000
<v Speaker 1>to test the first ever nuclear bomb, to see if

0:02:45.000 --> 0:02:49.000
<v Speaker 1>this idea was going to work as the equations predicted.

0:02:49.600 --> 0:02:51.920
<v Speaker 1>So they set up the spot where the bomb would

0:02:51.919 --> 0:02:54.680
<v Speaker 1>be set off, and then they set up a few

0:02:54.840 --> 0:02:59.080
<v Speaker 1>observation sites, with the closest one being ten miles away

0:02:59.080 --> 0:03:03.320
<v Speaker 1>from the explosion. So in the movie we witness a

0:03:03.480 --> 0:03:07.960
<v Speaker 1>reconstruction of this scene, and it's tense because this is

0:03:08.000 --> 0:03:11.080
<v Speaker 1>the culmination of years of work, and this is the

0:03:11.400 --> 0:03:14.520
<v Speaker 1>project that might turn the tide of a world war,

0:03:14.880 --> 0:03:16.480
<v Speaker 1>and this is gonna be the first time to get

0:03:16.520 --> 0:03:20.800
<v Speaker 1>to see if it works. So the countdown clock begins,

0:03:21.360 --> 0:03:24.080
<v Speaker 1>and Oppenheimer and the rest of the scientists put on

0:03:24.120 --> 0:03:28.639
<v Speaker 1>their goggles, and finally the clock hits zero and the

0:03:28.680 --> 0:03:33.760
<v Speaker 1>detonation button is pressed and they watch this giant, white

0:03:33.800 --> 0:03:37.840
<v Speaker 1>and red pillar of fire reach up into the heavens.

0:03:38.760 --> 0:03:42.400
<v Speaker 1>And in the movie it's silent. You just hear their

0:03:42.800 --> 0:03:47.760
<v Speaker 1>heavy breathing as they watch this massive mushrooming cloud of

0:03:48.160 --> 0:03:54.720
<v Speaker 1>incendiary flames, just silence. We see the explosion, but we

0:03:54.800 --> 0:03:59.880
<v Speaker 1>hear nothing, and after about fifty seconds of this, suddenly

0:04:00.240 --> 0:04:05.280
<v Speaker 1>we the audience hear a massive shaking boom. So after

0:04:05.320 --> 0:04:07.760
<v Speaker 1>the movie, I was talking with a friend and he

0:04:07.960 --> 0:04:12.600
<v Speaker 1>hypothesized that the director had done this for cinematic effect.

0:04:13.040 --> 0:04:16.360
<v Speaker 1>The long drawn out silence was done so we could

0:04:16.400 --> 0:04:20.359
<v Speaker 1>appreciate the terrifying success of the race to build a

0:04:20.440 --> 0:04:24.560
<v Speaker 1>nuclear bomb. But I pointed out this was not a

0:04:24.600 --> 0:04:27.960
<v Speaker 1>cinematic effect. This is how it really was and how

0:04:28.000 --> 0:04:33.719
<v Speaker 1>it had to be because light travels ten miles very fast.

0:04:33.800 --> 0:04:38.240
<v Speaker 1>It only takes about point one seconds for the light

0:04:38.320 --> 0:04:41.560
<v Speaker 1>to travel from the bomb to the observation station ten

0:04:41.640 --> 0:04:47.000
<v Speaker 1>miles away. But in contrast, sound travels about a million

0:04:47.279 --> 0:04:51.320
<v Speaker 1>times more slowly. Because remember sound is just traveling by

0:04:51.600 --> 0:04:54.800
<v Speaker 1>pushing around the molecules in the air, compressing them together

0:04:54.880 --> 0:04:57.719
<v Speaker 1>and pulling them apart. And so how long does it

0:04:57.760 --> 0:05:04.080
<v Speaker 1>take sound to travel one mile About five seconds. So

0:05:04.200 --> 0:05:07.360
<v Speaker 1>for the folks at the observation station ten miles away,

0:05:07.720 --> 0:05:14.279
<v Speaker 1>the nuclear explosion was silent for fifty seconds, fifty seconds

0:05:14.320 --> 0:05:18.919
<v Speaker 1>of watching the most terrifying destructive force humans had ever

0:05:19.040 --> 0:05:23.840
<v Speaker 1>made in total silence. And this is also what it

0:05:23.880 --> 0:05:27.960
<v Speaker 1>was like for victims on the ground in Hiroshima and Nagasaki.

0:05:28.200 --> 0:05:31.800
<v Speaker 1>People who were one mile away from ground zero saw

0:05:31.800 --> 0:05:36.719
<v Speaker 1>the mushroom cloud but experienced silence for five seconds, or

0:05:36.760 --> 0:05:40.279
<v Speaker 1>if you were across town twelve miles away. You'd have

0:05:40.400 --> 0:05:43.839
<v Speaker 1>a full minute of watching what must have looked like

0:05:44.240 --> 0:05:49.200
<v Speaker 1>a colossal monstrosity that reached the sky, but it must

0:05:49.200 --> 0:05:52.000
<v Speaker 1>have felt the way it does to watch a television

0:05:52.000 --> 0:05:55.839
<v Speaker 1>with the sound off for a full minute. And of

0:05:55.880 --> 0:05:58.760
<v Speaker 1>course you know about this delay between light and sound

0:05:59.200 --> 0:06:03.200
<v Speaker 1>because of watching lightning, which is followed only later by

0:06:03.240 --> 0:06:06.120
<v Speaker 1>the thunder So it takes five seconds for sound to

0:06:06.200 --> 0:06:09.400
<v Speaker 1>travel a mile, So if you count ten seconds after

0:06:09.440 --> 0:06:14.000
<v Speaker 1>the lightning, that means it's two miles away. Okay, so

0:06:14.080 --> 0:06:16.560
<v Speaker 1>there's this difference between the speed of light and the

0:06:16.600 --> 0:06:20.760
<v Speaker 1>speed of sound. But we're about to see something very weird,

0:06:20.960 --> 0:06:24.000
<v Speaker 1>which is that, unless we're watching something like a bomb

0:06:24.080 --> 0:06:28.480
<v Speaker 1>or a thunderbolt, we don't perceive those time differences. Why

0:06:28.520 --> 0:06:32.040
<v Speaker 1>don't we perceive these normally? Since sound is a million

0:06:32.080 --> 0:06:35.719
<v Speaker 1>times slower, why doesn't someone talking to you from across

0:06:35.760 --> 0:06:39.640
<v Speaker 1>the room look like a badly dubbed film. After all,

0:06:39.680 --> 0:06:41.720
<v Speaker 1>the sight of their mouth and the sound of their

0:06:41.800 --> 0:06:45.040
<v Speaker 1>voice arrives at different times, just like the bomb or

0:06:45.040 --> 0:06:49.480
<v Speaker 1>the thunderbolt. And we're generally very sensitive to small differences

0:06:49.520 --> 0:06:53.440
<v Speaker 1>in timing. So why can't we pick this up? So

0:06:53.680 --> 0:06:57.080
<v Speaker 1>to reach our arms down into this problem. I'll give

0:06:57.080 --> 0:07:00.159
<v Speaker 1>you a do it yourself demonstration that will unmask for

0:07:00.200 --> 0:07:04.120
<v Speaker 1>you the deep weirdness of how much your brain constructs

0:07:04.200 --> 0:07:08.960
<v Speaker 1>your reality. So watch some kid dribbling in basketball. It

0:07:09.040 --> 0:07:12.200
<v Speaker 1>will seem like as the basketball is hitting the ground,

0:07:12.280 --> 0:07:15.760
<v Speaker 1>the sight and the sound of that are synchronized. Now

0:07:15.760 --> 0:07:17.640
<v Speaker 1>what you do is you start backing up. So you

0:07:17.760 --> 0:07:20.760
<v Speaker 1>back up, you back up. They're dribbling, You're watching them,

0:07:21.040 --> 0:07:23.960
<v Speaker 1>and it seems synchronized. The more and more you back up,

0:07:24.040 --> 0:07:28.640
<v Speaker 1>it still seems synchronized until you hit one hundred and

0:07:28.720 --> 0:07:32.800
<v Speaker 1>ten feet and then it doesn't seem synchronized anymore. Then

0:07:32.920 --> 0:07:38.040
<v Speaker 1>suddenly the sight and sound seem off. The basketball visually

0:07:38.120 --> 0:07:42.360
<v Speaker 1>hits the ground and then you hear the thump. It's asynchronous,

0:07:42.440 --> 0:07:46.080
<v Speaker 1>like the badly dubbed movie. So what is going on here?

0:07:47.000 --> 0:07:49.560
<v Speaker 1>Strap in, because we're about to see some things that

0:07:49.640 --> 0:07:53.880
<v Speaker 1>will blow our minds, specifically, how much editing work your

0:07:53.920 --> 0:07:57.800
<v Speaker 1>brain does behind the scenes to try to fix timing

0:07:57.840 --> 0:08:01.040
<v Speaker 1>across the senses until the difference is simply too great

0:08:01.040 --> 0:08:04.119
<v Speaker 1>and it says, okay, forget about it. So let's zoom

0:08:04.160 --> 0:08:06.640
<v Speaker 1>out for a minute and consider the big picture. Of

0:08:06.680 --> 0:08:11.920
<v Speaker 1>what your brain has to do. Your conscious perception requires

0:08:11.960 --> 0:08:15.920
<v Speaker 1>the brain to compare different streams of sensory data against

0:08:16.000 --> 0:08:19.920
<v Speaker 1>one another. You've got these different channels of information coming in.

0:08:20.000 --> 0:08:23.720
<v Speaker 1>You've got vision, hearing, touch, and so on, and your

0:08:23.720 --> 0:08:25.880
<v Speaker 1>brain has to put these together to make a big

0:08:25.960 --> 0:08:29.640
<v Speaker 1>picture of what's happening. But there's something which makes this

0:08:29.720 --> 0:08:33.880
<v Speaker 1>a really big challenge, and that is the issue of timing.

0:08:34.360 --> 0:08:37.600
<v Speaker 1>All of these streams of sensory data are processed by

0:08:37.600 --> 0:08:42.320
<v Speaker 1>the brain at different speeds. So think about sprinters at

0:08:42.360 --> 0:08:45.680
<v Speaker 1>a racetrack. It appears that they get off the blocks

0:08:45.800 --> 0:08:50.640
<v Speaker 1>the instant the gunfires, but it's not actually instantaneous. If

0:08:50.679 --> 0:08:54.239
<v Speaker 1>you watch them in slow motion, you'll see this sizeable

0:08:54.480 --> 0:08:58.079
<v Speaker 1>gap between the bang and the start of their movement.

0:08:58.080 --> 0:09:01.720
<v Speaker 1>It's about one hundred and sixty millisecond because it takes

0:09:01.800 --> 0:09:05.880
<v Speaker 1>time for signals to move through the brain, for the

0:09:05.920 --> 0:09:08.120
<v Speaker 1>bang of the gun to work its way through their

0:09:08.200 --> 0:09:11.360
<v Speaker 1>auditory system and over to their motor system and then

0:09:11.440 --> 0:09:14.640
<v Speaker 1>down the spinal cord into the leg muscles and launched

0:09:14.679 --> 0:09:18.640
<v Speaker 1>them off the blocks. In fact, if they move off

0:09:18.640 --> 0:09:23.760
<v Speaker 1>the blocks before that duration, they're disqualified because they've jumped

0:09:23.840 --> 0:09:28.679
<v Speaker 1>the gun. Because racing commissions know that this signal transmission

0:09:28.720 --> 0:09:31.760
<v Speaker 1>takes time, so the rule is that if you move

0:09:31.880 --> 0:09:37.000
<v Speaker 1>within one hundred milliseconds after the gun, you are disqualified.

0:09:37.720 --> 0:09:39.839
<v Speaker 1>This came up in July of twenty twenty two when

0:09:39.880 --> 0:09:43.720
<v Speaker 1>a hurdler named Devin Allen got off the starting blocks

0:09:43.760 --> 0:09:46.800
<v Speaker 1>too early. He didn't go before the gun went off,

0:09:46.800 --> 0:09:50.280
<v Speaker 1>he went after the gun went off. But he launched

0:09:50.360 --> 0:09:54.400
<v Speaker 1>at ninety nine milliseconds after the gun, and even for

0:09:54.440 --> 0:09:58.160
<v Speaker 1>a great athlete like him, this is below the possible

0:09:58.320 --> 0:10:01.240
<v Speaker 1>reaction time, and there was a storm of activity on

0:10:01.280 --> 0:10:04.640
<v Speaker 1>social media. But the fact is that one's reaction time

0:10:05.040 --> 0:10:08.920
<v Speaker 1>can't be that rapid. Athletes trained to make their gap

0:10:08.960 --> 0:10:13.880
<v Speaker 1>as small as possible, but their biology imposes fundamental limits.

0:10:14.440 --> 0:10:17.280
<v Speaker 1>The brain has to register the sound and then send

0:10:17.280 --> 0:10:19.840
<v Speaker 1>the signals to the motor cortex and down the spinal

0:10:19.880 --> 0:10:22.920
<v Speaker 1>cord to the muscles of the body. Now, in a

0:10:23.080 --> 0:10:26.360
<v Speaker 1>sport where thousandths of a second can be the difference

0:10:26.400 --> 0:10:32.720
<v Speaker 1>between winning and losing, that response seems surprisingly slow. So

0:10:32.920 --> 0:10:36.240
<v Speaker 1>could the delay be shortened if we used, say, a

0:10:36.480 --> 0:10:40.160
<v Speaker 1>flash instead of a pistol to start the racers. After all,

0:10:40.679 --> 0:10:43.720
<v Speaker 1>light travels faster than sounds, so wouldn't that allow them

0:10:43.760 --> 0:10:47.680
<v Speaker 1>to get off the blocks faster? For my television show

0:10:47.760 --> 0:10:50.559
<v Speaker 1>The Brain, I went to the track and I invited

0:10:50.600 --> 0:10:53.160
<v Speaker 1>some fellow sprinters so we could all put this to

0:10:53.200 --> 0:10:57.560
<v Speaker 1>the test. So, in one condition, our sprint was triggered

0:10:57.720 --> 0:11:01.800
<v Speaker 1>by the gun. In a second condition, we were triggered

0:11:02.000 --> 0:11:05.280
<v Speaker 1>by a flash of light. And we filmed this in

0:11:05.400 --> 0:11:09.040
<v Speaker 1>super slow motion so we could compare what happened in

0:11:09.080 --> 0:11:12.640
<v Speaker 1>the two conditions. When we were triggered by the bang

0:11:12.679 --> 0:11:14.760
<v Speaker 1>of a gun, we got off the blocks at about

0:11:14.760 --> 0:11:18.400
<v Speaker 1>one hundred and sixty milliseconds, but when we were triggered

0:11:18.400 --> 0:11:22.479
<v Speaker 1>by the light, we got off the blocks more slowly,

0:11:22.679 --> 0:11:25.840
<v Speaker 1>with a longer delay, about one hundred and ninety milliseconds.

0:11:26.240 --> 0:11:28.880
<v Speaker 1>Now that seems to make no sense given what we

0:11:29.040 --> 0:11:32.120
<v Speaker 1>just talked about, with light moving a million times faster

0:11:32.200 --> 0:11:37.160
<v Speaker 1>than sound. So what gives here To understand what's happening?

0:11:37.200 --> 0:11:40.600
<v Speaker 1>We need to look at the speed of information processing

0:11:40.920 --> 0:11:46.400
<v Speaker 1>on the inside. Visual data goes through more complex processing

0:11:46.840 --> 0:11:51.480
<v Speaker 1>than auditory data, so it takes longer for signals carrying

0:11:51.520 --> 0:11:55.040
<v Speaker 1>the flash to wind their way through the visual system

0:11:55.440 --> 0:11:58.480
<v Speaker 1>then for bang signals to snake their way through the

0:11:58.480 --> 0:12:04.880
<v Speaker 1>auditory system, so light takes longer to trigger a motor response,

0:12:04.960 --> 0:12:26.520
<v Speaker 1>and that's why a pistol is used to start sprinters. Now,

0:12:26.600 --> 0:12:30.480
<v Speaker 1>scientists can prove this by putting electrodes in the auditory cortex,

0:12:30.480 --> 0:12:33.600
<v Speaker 1>which responds to the bang, or the visual cortex, which

0:12:33.640 --> 0:12:36.840
<v Speaker 1>responds to the flash, and you can see that the

0:12:36.960 --> 0:12:40.880
<v Speaker 1>speed of the brain response is faster for the bang.

0:12:41.880 --> 0:12:45.880
<v Speaker 1>But here comes the big mystery. Clap your hands in

0:12:45.920 --> 0:12:50.560
<v Speaker 1>front of you. It looks synchronized. Well, that makes no

0:12:50.679 --> 0:12:54.080
<v Speaker 1>sense because we just saw with the sprinters that your

0:12:54.240 --> 0:13:00.880
<v Speaker 1>auditory system processes information more quickly than your visuals. So

0:13:00.920 --> 0:13:04.760
<v Speaker 1>why aren't you seeing the sound and the sight out

0:13:04.800 --> 0:13:08.360
<v Speaker 1>of sync. The answer, as we'll see in a moment,

0:13:08.520 --> 0:13:10.920
<v Speaker 1>is that even though part of your brain gets the

0:13:10.920 --> 0:13:16.160
<v Speaker 1>information before another part, your consciousness goes through a lot

0:13:16.200 --> 0:13:20.560
<v Speaker 1>of trouble to sync things up. Your perception of the

0:13:20.600 --> 0:13:25.040
<v Speaker 1>outside world is the end result of fancy editing tricks.

0:13:25.400 --> 0:13:29.320
<v Speaker 1>The brain hides the difference in arrival times, and I'll

0:13:29.360 --> 0:13:31.440
<v Speaker 1>explain to you how it does this, but first I'll

0:13:31.440 --> 0:13:35.040
<v Speaker 1>give you a couple more examples. So let's step back

0:13:35.120 --> 0:13:40.000
<v Speaker 1>seventy years to the early days of television broadcasting. The

0:13:40.040 --> 0:13:43.960
<v Speaker 1>engineers realized they could be a stream of sound information

0:13:44.320 --> 0:13:47.280
<v Speaker 1>and they could be a stream of visual information. But

0:13:47.320 --> 0:13:50.360
<v Speaker 1>they were worried about how they could broadcast both the

0:13:50.440 --> 0:13:54.160
<v Speaker 1>sound and the visuals and keep them synchronized with one another.

0:13:54.679 --> 0:13:58.280
<v Speaker 1>And what they realized, quite accidentally, was that they don't

0:13:58.400 --> 0:14:02.200
<v Speaker 1>actually need to keep them perfectly synchronized. As long as

0:14:02.240 --> 0:14:06.360
<v Speaker 1>the sound and the visuals arrive to the viewer within

0:14:06.400 --> 0:14:09.520
<v Speaker 1>about eighty milliseconds of each other. That's about a tenth

0:14:09.559 --> 0:14:12.679
<v Speaker 1>of a second. Your brain does all the work of

0:14:12.720 --> 0:14:15.959
<v Speaker 1>synking these up. And if you've ever seen a movie

0:14:16.000 --> 0:14:18.800
<v Speaker 1>that seems out of sync, it means that the audio

0:14:18.880 --> 0:14:22.680
<v Speaker 1>and the video were more than eighty milliseconds away from

0:14:22.720 --> 0:14:26.440
<v Speaker 1>each other, because your brain can't tell the difference. As

0:14:26.480 --> 0:14:29.320
<v Speaker 1>long as they're within eighty milliseconds of one another, it

0:14:29.360 --> 0:14:34.040
<v Speaker 1>seems perfectly synchronized to you. And this allows us to

0:14:34.160 --> 0:14:38.200
<v Speaker 1>understand what's happening. When you're watching the kid dribbling the basketball.

0:14:38.640 --> 0:14:41.160
<v Speaker 1>It seems that as the ball is hitting the ground,

0:14:41.200 --> 0:14:44.200
<v Speaker 1>everything is synced all the way until you back up

0:14:44.240 --> 0:14:46.480
<v Speaker 1>to one hundred and ten feet and then it's not

0:14:46.520 --> 0:14:50.800
<v Speaker 1>synchronized anymore. Why well, one hundred and ten feet is

0:14:50.840 --> 0:14:53.680
<v Speaker 1>where the speed of light and the speed of sound

0:14:53.880 --> 0:14:58.160
<v Speaker 1>are reaching you at over eighty milliseconds apart. So when

0:14:58.200 --> 0:15:01.840
<v Speaker 1>they reach you at that timing apart from one another,

0:15:01.920 --> 0:15:05.200
<v Speaker 1>your brain can't sync it up anymore. But as long

0:15:05.240 --> 0:15:09.560
<v Speaker 1>as they're within that window, your brain has no problem saying, oh, okay,

0:15:09.600 --> 0:15:13.400
<v Speaker 1>those belong together, I'm gonna synchronize that. So this is

0:15:13.440 --> 0:15:15.800
<v Speaker 1>the question I turned to some years ago. If the

0:15:15.920 --> 0:15:19.360
<v Speaker 1>brain is getting all this information at different speeds, how

0:15:19.400 --> 0:15:23.320
<v Speaker 1>does it know how to synchronize things in consciousness? And

0:15:23.360 --> 0:15:26.280
<v Speaker 1>I just want to make clear how challenging this is

0:15:26.360 --> 0:15:29.720
<v Speaker 1>if you're living in the dark inside the skull, because

0:15:29.760 --> 0:15:33.320
<v Speaker 1>these timing difficulties aren't even restricted to hearing and seeing.

0:15:33.640 --> 0:15:37.160
<v Speaker 1>Every type of sensory information takes a different amount of

0:15:37.160 --> 0:15:41.400
<v Speaker 1>time to process and to complicate things even more, even

0:15:41.440 --> 0:15:44.920
<v Speaker 1>within a sense, there are time differences. For example, a

0:15:45.080 --> 0:15:48.640
<v Speaker 1>bright flash moves through your retina and gets to your

0:15:48.640 --> 0:15:53.240
<v Speaker 1>brain a full eighty milliseconds before a dim flash, or

0:15:53.240 --> 0:15:56.920
<v Speaker 1>as another example, it takes longer for signals to reach

0:15:56.960 --> 0:15:59.840
<v Speaker 1>your brain from your big toe than it does from

0:15:59.840 --> 0:16:03.800
<v Speaker 1>your knows So how does your brain solve all of

0:16:03.840 --> 0:16:09.440
<v Speaker 1>this temporal smearing of information. The only possible answer is

0:16:09.520 --> 0:16:14.160
<v Speaker 1>wacky and somewhat mind blowing. Your brain has to collect

0:16:14.320 --> 0:16:18.200
<v Speaker 1>up all the information from all the senses before it

0:16:18.320 --> 0:16:23.440
<v Speaker 1>decides on a story of what happened. And that means

0:16:23.480 --> 0:16:29.040
<v Speaker 1>your conscious perception is actually a delayed version of what's

0:16:29.080 --> 0:16:32.400
<v Speaker 1>happening in the world. So when you clap your hands,

0:16:33.120 --> 0:16:36.560
<v Speaker 1>your brain gathers the auditory information and the visual information

0:16:36.680 --> 0:16:39.680
<v Speaker 1>and the sensory information of your hands touching, and all

0:16:39.760 --> 0:16:43.480
<v Speaker 1>these stream in at different times, and then it puts

0:16:43.520 --> 0:16:47.240
<v Speaker 1>together its story of what just happened, and it puts

0:16:47.280 --> 0:16:50.720
<v Speaker 1>together what should go with what. And I'll explain in

0:16:50.720 --> 0:16:53.160
<v Speaker 1>a second how it does this. But the key thing

0:16:53.200 --> 0:16:55.840
<v Speaker 1>I want to make clear right now is that in

0:16:56.000 --> 0:17:00.480
<v Speaker 1>order to synchronize everything, you have to wait for all

0:17:00.640 --> 0:17:05.639
<v Speaker 1>of the information to arrive. And the strange consequence of

0:17:05.680 --> 0:17:10.080
<v Speaker 1>all this is that you live in the past. By

0:17:10.119 --> 0:17:14.040
<v Speaker 1>the time you think the moment occurs, it's already long gone.

0:17:14.119 --> 0:17:18.760
<v Speaker 1>When you perceive the clap, it's already over. Your perceptual

0:17:18.800 --> 0:17:24.199
<v Speaker 1>world always lags behind the real world. So think of

0:17:24.200 --> 0:17:27.480
<v Speaker 1>it this way. Your perception of the world is like

0:17:27.600 --> 0:17:31.520
<v Speaker 1>a live television show. Think of something like Saturday Night Live,

0:17:32.040 --> 0:17:36.000
<v Speaker 1>which is not actually live. Instead, those shows are aired

0:17:36.080 --> 0:17:39.560
<v Speaker 1>with a delay of a few seconds in case someone

0:17:40.119 --> 0:17:44.000
<v Speaker 1>cusses or falls down or has a clothing mishap. And

0:17:44.080 --> 0:17:47.600
<v Speaker 1>so it goes with your conscious life. It collects a

0:17:47.600 --> 0:17:52.000
<v Speaker 1>lot of information before it goes live, so there's an

0:17:52.119 --> 0:17:56.000
<v Speaker 1>unbridgable gap between an event occurring in the world and

0:17:56.040 --> 0:17:59.680
<v Speaker 1>your conscious experience of it. So that's why your brain

0:17:59.720 --> 0:18:03.200
<v Speaker 1>can sync the television audio at the video or the

0:18:03.520 --> 0:18:06.320
<v Speaker 1>basketball thump with the visual of it hitting the ground

0:18:06.359 --> 0:18:09.359
<v Speaker 1>or whatever. I need to emphasize that what we're talking

0:18:09.400 --> 0:18:13.760
<v Speaker 1>about here is conscious awareness. You can see from pre

0:18:13.880 --> 0:18:17.440
<v Speaker 1>conscious reactions that your motor system doesn't have to wait

0:18:17.520 --> 0:18:21.000
<v Speaker 1>before its decisions. For example, you can duck out of

0:18:21.040 --> 0:18:23.960
<v Speaker 1>the way of a swinging tree branch before you become

0:18:24.040 --> 0:18:27.399
<v Speaker 1>consciously aware of it, or you can start jumping when

0:18:27.440 --> 0:18:31.400
<v Speaker 1>there's a loud sound before you're consciously aware that there

0:18:31.480 --> 0:18:34.320
<v Speaker 1>was a sound. Your body always tries to act as

0:18:34.400 --> 0:18:39.000
<v Speaker 1>quickly as possible, even before the participation of awareness, but

0:18:39.080 --> 0:18:45.040
<v Speaker 1>your conscious perception takes its time. Now that raises a question,

0:18:45.119 --> 0:18:48.640
<v Speaker 1>what is the use of perception, especially since it lags

0:18:48.680 --> 0:18:55.639
<v Speaker 1>behind reality and it's retrospectively attributed, and it's generally outstripped

0:18:55.680 --> 0:18:59.960
<v Speaker 1>by these automatic, unconscious systems. The most likely answer is

0:19:00.080 --> 0:19:04.640
<v Speaker 1>that your perceptions are like objects that your cognitive systems

0:19:04.680 --> 0:19:07.760
<v Speaker 1>can work with later. So it's important for the brain

0:19:08.040 --> 0:19:12.120
<v Speaker 1>to take sufficient time to settle on its best interpretation

0:19:12.240 --> 0:19:15.960
<v Speaker 1>of what just happened, rather than stick with its initial

0:19:16.040 --> 0:19:21.400
<v Speaker 1>rapid interpretation. Its carefully refined picture of what just happened

0:19:21.800 --> 0:19:24.160
<v Speaker 1>is all that it's going to have to work with later,

0:19:24.560 --> 0:19:30.320
<v Speaker 1>so it invests the time. So this brief waiting period

0:19:30.400 --> 0:19:34.199
<v Speaker 1>before consciousness, this is what allows your sensory systems to

0:19:34.880 --> 0:19:39.960
<v Speaker 1>discount the various delays imposed, But it has the disadvantage

0:19:40.000 --> 0:19:43.639
<v Speaker 1>of pushing your perception into the past. Now, there's a

0:19:43.680 --> 0:19:47.080
<v Speaker 1>distinct survival advantage to operating as close to the present

0:19:47.119 --> 0:19:49.840
<v Speaker 1>as possible. An animal doesn't want to live too far

0:19:49.880 --> 0:19:52.800
<v Speaker 1>in the past. Therefore, it may be that a tenth

0:19:52.800 --> 0:19:56.560
<v Speaker 1>of a second window is the smallest delay that allows

0:19:57.040 --> 0:19:59.680
<v Speaker 1>higher areas of the brain to account for the delays

0:19:59.760 --> 0:20:02.840
<v Speaker 1>create in the first stage of the system while still

0:20:02.920 --> 0:20:06.879
<v Speaker 1>operating near the border of the present. Among other things,

0:20:06.920 --> 0:20:10.520
<v Speaker 1>this strategy of waiting for the slowest information to arrive

0:20:11.320 --> 0:20:16.280
<v Speaker 1>has the advantage of allowing object recognition to be independent

0:20:16.400 --> 0:20:19.360
<v Speaker 1>of lighting conditions. So I mentioned a minute ago about

0:20:19.640 --> 0:20:23.320
<v Speaker 1>bright and dim flashes moving through the system at different speeds.

0:20:23.880 --> 0:20:28.560
<v Speaker 1>So imagine a striped tiger coming toward you under the

0:20:28.600 --> 0:20:33.119
<v Speaker 1>forest canopy, and he's passing through successive patches of sunlight.

0:20:33.640 --> 0:20:37.840
<v Speaker 1>Imagine how difficult recognition would be if the bright and

0:20:37.880 --> 0:20:41.600
<v Speaker 1>the dim parts of the tiger caused incoming signals to

0:20:41.640 --> 0:20:45.359
<v Speaker 1>be perceived at different times. You'd perceive the tiger breaking

0:20:45.359 --> 0:20:49.359
<v Speaker 1>into different space time fragments just before you became the

0:20:49.400 --> 0:20:54.960
<v Speaker 1>tiger's lunch. Somehow, the visual system has evolved to reconcile

0:20:55.320 --> 0:20:59.320
<v Speaker 1>these different speeds of incoming information. After all, it is

0:20:59.440 --> 0:21:06.280
<v Speaker 1>advantageous to recognize tigers regardless of the lighting conditions. Now,

0:21:06.320 --> 0:21:10.240
<v Speaker 1>this hypothesis that the system waits to collect information over

0:21:10.280 --> 0:21:13.119
<v Speaker 1>the window of time that it's all streaming in this

0:21:13.160 --> 0:21:15.960
<v Speaker 1>supplies not only to vision, but more generally, to all

0:21:16.040 --> 0:21:20.119
<v Speaker 1>the senses. So, for example, my lab measured that in

0:21:20.240 --> 0:21:22.679
<v Speaker 1>vision you wait at least a tenth of a second,

0:21:23.080 --> 0:21:25.879
<v Speaker 1>But the size of this window might be different for

0:21:26.080 --> 0:21:29.440
<v Speaker 1>hearing or touch. If I touch your toe and your

0:21:29.520 --> 0:21:32.520
<v Speaker 1>nose at the same time, you will feel those touches

0:21:32.520 --> 0:21:36.520
<v Speaker 1>as simultaneous. And that's really surprising, because the signal from

0:21:36.520 --> 0:21:39.920
<v Speaker 1>your nose reaches your brain well before the signal from

0:21:39.960 --> 0:21:43.080
<v Speaker 1>your toe. Why didn't you feel the nose touch when

0:21:43.080 --> 0:21:46.320
<v Speaker 1>it first arrived. Did your brain wait to see what

0:21:46.440 --> 0:21:48.880
<v Speaker 1>else might be coming up the pipeline of the spinal

0:21:48.920 --> 0:21:51.720
<v Speaker 1>cord until it was sure that it had waited long

0:21:51.840 --> 0:21:55.320
<v Speaker 1>enough for the slower signals from the toe. Strange as

0:21:55.320 --> 0:21:57.760
<v Speaker 1>that sounds, that might be correct, and it may be

0:21:57.760 --> 0:22:02.560
<v Speaker 1>that for a unified sensory perception of the world, you

0:22:02.680 --> 0:22:07.000
<v Speaker 1>have to wait for the slowest overall information to get there,

0:22:07.600 --> 0:22:11.800
<v Speaker 1>and given conduction times along whims, this leads to my

0:22:12.160 --> 0:22:16.480
<v Speaker 1>strange but testable hypothesis that I mentioned in episode thirteen,

0:22:16.880 --> 0:22:21.040
<v Speaker 1>which is that tall people may live further in the

0:22:21.080 --> 0:22:24.560
<v Speaker 1>past than short people because they have to wait for

0:22:24.680 --> 0:22:27.480
<v Speaker 1>the signals all the way from their toes before they

0:22:27.520 --> 0:22:33.360
<v Speaker 1>put together their unified perception. Okay, but how does your

0:22:33.359 --> 0:22:37.919
<v Speaker 1>brain know how to put all these signals together? So

0:22:38.000 --> 0:22:42.320
<v Speaker 1>to think about this, let's turn to the Mongol emperor

0:22:42.480 --> 0:22:46.440
<v Speaker 1>Kublai Khan, who ranged from twelve sixty to twelve ninety four,

0:22:46.640 --> 0:22:51.000
<v Speaker 1>and founded the Yuan dynasty. Now he had conquered the

0:22:51.240 --> 0:22:54.679
<v Speaker 1>largest kingdom the world had ever known. His kingdom reached

0:22:54.720 --> 0:22:58.800
<v Speaker 1>from the Pacific to the Black Sea, and from Siberia

0:22:58.840 --> 0:23:03.959
<v Speaker 1>to modern day Afghanis. His territory covered a fifth of

0:23:04.000 --> 0:23:08.679
<v Speaker 1>the world's inhabited areas, so it was absolutely enormous. He

0:23:08.800 --> 0:23:12.639
<v Speaker 1>situated himself in what is modern day Beijing. And the

0:23:12.720 --> 0:23:14.879
<v Speaker 1>thing to note is that this was back in the

0:23:14.960 --> 0:23:18.879
<v Speaker 1>day before iPhones and telegraphs and trains or email or

0:23:18.920 --> 0:23:22.119
<v Speaker 1>anything like that. And so the question is, how in

0:23:22.160 --> 0:23:27.800
<v Speaker 1>the world could Kubla Khan know his own empire. There's

0:23:27.800 --> 0:23:30.760
<v Speaker 1>no way he could travel even a tiny fraction of

0:23:30.800 --> 0:23:35.320
<v Speaker 1>a territory that large in his entire lifetime. So how

0:23:35.359 --> 0:23:39.840
<v Speaker 1>could the Great Khan know what his empire contained? The

0:23:39.960 --> 0:23:45.280
<v Speaker 1>answer is he hired emissaries like the Venetian traveler Marco Polo,

0:23:45.680 --> 0:23:48.760
<v Speaker 1>and these people would travel out to the distant reaches

0:23:48.760 --> 0:23:51.679
<v Speaker 1>of his empire and they would convey news back to

0:23:51.760 --> 0:23:54.719
<v Speaker 1>him about what was going on in the empire. And

0:23:54.800 --> 0:23:57.240
<v Speaker 1>he hired many emissaries that would go out in different

0:23:57.240 --> 0:24:00.840
<v Speaker 1>directions and bring news back to him about what was

0:24:00.880 --> 0:24:04.760
<v Speaker 1>going on. Now, I've never heard a historian talk about this.

0:24:04.880 --> 0:24:08.840
<v Speaker 1>But I imagine the Great Con must have faced a

0:24:08.960 --> 0:24:15.040
<v Speaker 1>tough problem what events in his empire occurred in which order.

0:24:15.840 --> 0:24:18.720
<v Speaker 1>Because of wars and weather and other issues, people might

0:24:18.880 --> 0:24:23.040
<v Speaker 1>travel at different paces, so the different emissaries would come

0:24:23.040 --> 0:24:26.200
<v Speaker 1>back to him at different times. One emissary comes back

0:24:26.240 --> 0:24:29.440
<v Speaker 1>and reports that a war has just ended, and another

0:24:29.480 --> 0:24:33.080
<v Speaker 1>emissary comes back and reports that a war has just begun,

0:24:33.160 --> 0:24:35.760
<v Speaker 1>and they're talking about the same war. But they got

0:24:35.800 --> 0:24:39.520
<v Speaker 1>back to the capitol at different times. And so the

0:24:39.600 --> 0:24:44.080
<v Speaker 1>question is how did the Great con synchronize all these signals.

0:24:44.760 --> 0:24:46.600
<v Speaker 1>The thing I want to make clear is that the

0:24:46.640 --> 0:24:50.800
<v Speaker 1>timing problem Kubla Khan had is the same problem the

0:24:50.920 --> 0:24:54.240
<v Speaker 1>brain has, which is to say, it's getting all these

0:24:54.240 --> 0:24:58.080
<v Speaker 1>different streams of information that come in at different paces.

0:24:58.960 --> 0:25:01.400
<v Speaker 1>And because your brain is locked up in the dark

0:25:01.520 --> 0:25:05.120
<v Speaker 1>tower of the skull, its only contact with the outside

0:25:05.119 --> 0:25:09.119
<v Speaker 1>world is via the electrical signals exiting and entering along

0:25:09.160 --> 0:25:13.360
<v Speaker 1>the highways of nerve bundles. So you've got touch information

0:25:13.480 --> 0:25:16.080
<v Speaker 1>streaming up the body, You've got auditory coming in, you've

0:25:16.119 --> 0:25:19.480
<v Speaker 1>got visual information coming into the brain. But the issue

0:25:19.640 --> 0:25:21.960
<v Speaker 1>is that all of these things get processed by the

0:25:22.000 --> 0:25:25.000
<v Speaker 1>brain at different speeds and at different places in the brain.

0:25:25.440 --> 0:25:29.439
<v Speaker 1>So your brain faces this enormous challenge how to stitch

0:25:29.560 --> 0:25:33.359
<v Speaker 1>together the incoming signals in the best way to make

0:25:33.400 --> 0:25:36.680
<v Speaker 1>a story about what just happened in the outside world.

0:25:37.480 --> 0:25:39.720
<v Speaker 1>For example, as we just saw, when I clap my hands,

0:25:39.720 --> 0:25:43.320
<v Speaker 1>the auditory signals get processed first, then the visual signals,

0:25:43.400 --> 0:25:46.920
<v Speaker 1>and yet they seem synced up. What this tells us

0:25:47.520 --> 0:25:51.080
<v Speaker 1>is that the brain is somehow pulling off major video

0:25:51.200 --> 0:25:54.320
<v Speaker 1>editing tricks, and we're going to find out how. Now,

0:25:54.320 --> 0:25:56.560
<v Speaker 1>my lab has studied this for years, and the first

0:25:56.600 --> 0:25:59.320
<v Speaker 1>thing to appreciate is that your brain doesn't figure this

0:25:59.400 --> 0:26:04.800
<v Speaker 1>out pass. It does this by involving your own actions.

0:26:04.960 --> 0:26:09.080
<v Speaker 1>Your own actions are the secret to understanding how everything

0:26:09.080 --> 0:26:13.040
<v Speaker 1>gets synchronized. And what I've proposed is that your brain

0:26:13.119 --> 0:26:15.960
<v Speaker 1>goes through so much trouble to get all this timing

0:26:16.080 --> 0:26:20.919
<v Speaker 1>right because of one issue causality. Because one of the

0:26:20.920 --> 0:26:25.240
<v Speaker 1>most fundamental things that any animal does is figure out

0:26:25.520 --> 0:26:28.359
<v Speaker 1>whether it was the one that caused something or not.

0:26:29.359 --> 0:26:34.840
<v Speaker 1>And fundamentally judging what caused what requires looking at the

0:26:35.200 --> 0:26:54.880
<v Speaker 1>order of events. So imagine you're walking in the forest

0:26:55.040 --> 0:26:58.000
<v Speaker 1>and you make a step and you hear a twig crack,

0:26:58.680 --> 0:27:01.600
<v Speaker 1>you can assume that was me because of you. But

0:27:01.680 --> 0:27:05.080
<v Speaker 1>if you hear the twig crack just before you land

0:27:05.080 --> 0:27:08.400
<v Speaker 1>your step, then you'd better be worried about a mountain lion.

0:27:09.480 --> 0:27:15.560
<v Speaker 1>So causality requires a temporal order judgment, which is to say,

0:27:16.000 --> 0:27:18.160
<v Speaker 1>did I put out the action and then I got

0:27:18.160 --> 0:27:21.560
<v Speaker 1>sensory feedback, in which case I'm going to take credit

0:27:21.600 --> 0:27:25.919
<v Speaker 1>for having done that, Versus I got sensory feedback and

0:27:25.960 --> 0:27:28.280
<v Speaker 1>then I did some action, in which case I'm not

0:27:28.359 --> 0:27:30.480
<v Speaker 1>taking credit for that. I had nothing to do with that.

0:27:31.560 --> 0:27:35.480
<v Speaker 1>And what we're often talking about is tens of milliseconds

0:27:35.480 --> 0:27:37.920
<v Speaker 1>one way or the other as the only difference between

0:27:37.920 --> 0:27:42.000
<v Speaker 1>these scenarios. But animals are very sensitive to this, and

0:27:42.040 --> 0:27:45.239
<v Speaker 1>at bottom, this is the challenge that animals have to

0:27:45.280 --> 0:27:48.480
<v Speaker 1>figure out. And as we've seen, the reason this is

0:27:48.520 --> 0:27:52.240
<v Speaker 1>really difficult is because the speed of sensory signals differs

0:27:52.680 --> 0:27:56.520
<v Speaker 1>and also they can change. So, for example, when you

0:27:56.560 --> 0:28:01.360
<v Speaker 1>go from a bright outdoors into a dimly lit room,

0:28:01.720 --> 0:28:04.080
<v Speaker 1>the speed at which your eyes are talking to your

0:28:04.119 --> 0:28:07.639
<v Speaker 1>brain slows down by quite a bit. And what that

0:28:07.760 --> 0:28:10.840
<v Speaker 1>means is that now your vision and your motor actions

0:28:11.080 --> 0:28:13.679
<v Speaker 1>are out of sink a little bit. So if right

0:28:13.720 --> 0:28:15.840
<v Speaker 1>when you walked into the dim room, I threw you

0:28:15.880 --> 0:28:18.520
<v Speaker 1>a ball, you'd probably miss it. I don't know if

0:28:18.560 --> 0:28:21.880
<v Speaker 1>you've ever played volleyball right when the sun's going down,

0:28:22.200 --> 0:28:25.080
<v Speaker 1>but everyone's having good time, and then right as the

0:28:25.200 --> 0:28:27.760
<v Speaker 1>sun's going down, everyone starts getting hit in the face

0:28:27.800 --> 0:28:31.159
<v Speaker 1>with the ball and so on. Because what's happening is

0:28:31.200 --> 0:28:34.920
<v Speaker 1>your time is getting out of sync. Now, now that's

0:28:34.960 --> 0:28:37.959
<v Speaker 1>an example of a short term fast change, but on

0:28:38.000 --> 0:28:41.600
<v Speaker 1>a longer time scale, as you grow from a baby

0:28:41.640 --> 0:28:44.360
<v Speaker 1>to an adult, it takes a longer time to send

0:28:44.400 --> 0:28:48.160
<v Speaker 1>signals out to your hand and get signals back. And

0:28:48.200 --> 0:28:50.640
<v Speaker 1>so all of this led me to think a while ago,

0:28:50.880 --> 0:28:54.800
<v Speaker 1>somehow the brain is having to figure out what its

0:28:55.080 --> 0:28:59.840
<v Speaker 1>expectations are. It's having to modulate on the fly how

0:28:59.840 --> 0:29:03.160
<v Speaker 1>long it expects for signals to come back. And so

0:29:03.240 --> 0:29:06.920
<v Speaker 1>I hypothesize that the brain is always doing this on

0:29:06.960 --> 0:29:11.960
<v Speaker 1>the fly. It's always recalibrating, it's readjusting the expected time

0:29:12.000 --> 0:29:14.880
<v Speaker 1>that it takes for signals to come in. But how

0:29:14.920 --> 0:29:19.080
<v Speaker 1>does it do that? And the answer is by interacting

0:29:19.160 --> 0:29:21.880
<v Speaker 1>with the world. Because whenever you touch things, or you

0:29:22.000 --> 0:29:25.040
<v Speaker 1>kick things, or you do anything like that. Your brain

0:29:25.160 --> 0:29:29.640
<v Speaker 1>is saying, okay, everybody, synchronize your watches. I'm putting out

0:29:29.640 --> 0:29:32.440
<v Speaker 1>an action, and what I expect is that I'm going

0:29:32.520 --> 0:29:34.160
<v Speaker 1>to see it and hear it and feel it all

0:29:34.200 --> 0:29:38.360
<v Speaker 1>at the same time. That's the prior expectation that it

0:29:38.360 --> 0:29:40.680
<v Speaker 1>comes to the table with. And if I hit the

0:29:40.680 --> 0:29:45.280
<v Speaker 1>table and it goes hit knock like that, my brain

0:29:45.320 --> 0:29:49.480
<v Speaker 1>will adjust the timing. In other words, your brain doesn't

0:29:49.480 --> 0:29:52.520
<v Speaker 1>know in advance how long your limbs are, or what

0:29:52.560 --> 0:29:55.360
<v Speaker 1>the lighting level is, or how fast sound travels and

0:29:55.360 --> 0:29:58.200
<v Speaker 1>so on. It just figures out what it needs by

0:29:58.840 --> 0:30:02.560
<v Speaker 1>reaching out and interacting with the world. It just needs

0:30:02.560 --> 0:30:05.720
<v Speaker 1>to embed the single assumption that if it sends out

0:30:05.760 --> 0:30:08.800
<v Speaker 1>an action such as a knock on the table or

0:30:08.800 --> 0:30:11.360
<v Speaker 1>a clap of the hands, all the feedback should be

0:30:11.400 --> 0:30:16.240
<v Speaker 1>assumed to be simultaneous, and any delays between the senses

0:30:16.560 --> 0:30:22.200
<v Speaker 1>should be adjusted until simultaneity is perceived. In other words,

0:30:22.560 --> 0:30:26.040
<v Speaker 1>the best way to predict the expected timing of the

0:30:26.080 --> 0:30:28.800
<v Speaker 1>signals is to interact with the world. Is to go

0:30:28.800 --> 0:30:31.160
<v Speaker 1>out and touch and kick and push and knock on

0:30:31.280 --> 0:30:34.560
<v Speaker 1>the world, and your brain makes the assumption that all

0:30:34.560 --> 0:30:37.960
<v Speaker 1>the feedback is simultaneous. The best way to predict the

0:30:38.000 --> 0:30:41.760
<v Speaker 1>future is to create it. You cause something and all

0:30:41.800 --> 0:30:48.200
<v Speaker 1>the consequences should be synchronized. That's how you keep yourself calibrated. So,

0:30:48.560 --> 0:30:52.280
<v Speaker 1>just to be clear, what this suggests is that if

0:30:52.320 --> 0:30:56.600
<v Speaker 1>the feedback signal arrives with a delay, the brain's going

0:30:56.640 --> 0:30:59.640
<v Speaker 1>to adjust things to make it seem like it happened

0:30:59.680 --> 0:31:03.560
<v Speaker 1>close in time. So I took this hypothesis and in

0:31:03.600 --> 0:31:07.760
<v Speaker 1>my lab we created a very simple experiment. You come

0:31:07.760 --> 0:31:10.520
<v Speaker 1>into the lab and you're seated in front of a button,

0:31:11.080 --> 0:31:14.400
<v Speaker 1>and whenever you hit the button that causes a flash

0:31:14.400 --> 0:31:17.160
<v Speaker 1>of light. You press the button, the light flashes, But

0:31:17.280 --> 0:31:21.760
<v Speaker 1>then we sneakily inject a small delay in there, let's

0:31:21.760 --> 0:31:25.520
<v Speaker 1>say one hundred milliseconds. So you hit the button and

0:31:25.560 --> 0:31:29.400
<v Speaker 1>then the flash of light appears. What happens very quickly

0:31:29.440 --> 0:31:33.480
<v Speaker 1>is that your brain adjusts to the delay. Because you're

0:31:33.560 --> 0:31:36.600
<v Speaker 1>the one causing it, the button and the light are

0:31:36.600 --> 0:31:41.840
<v Speaker 1>interpreted as simultaneous, or at least close to simultaneous. So

0:31:42.080 --> 0:31:44.560
<v Speaker 1>after just a couple of hits, it doesn't feel like

0:31:44.720 --> 0:31:48.240
<v Speaker 1>one hundred millisecond delay. It feels like the button pressed

0:31:48.240 --> 0:31:50.560
<v Speaker 1>and the flash are happening at the same time. Why

0:31:51.080 --> 0:31:53.800
<v Speaker 1>it's because your brain is the one putting out the action,

0:31:54.320 --> 0:31:58.640
<v Speaker 1>so it knows what to expect. And then we pull

0:31:58.720 --> 0:32:02.080
<v Speaker 1>the big trick on you after your brain is used

0:32:02.080 --> 0:32:06.280
<v Speaker 1>to this delay and thinks this is simultaneity. Now you

0:32:06.360 --> 0:32:09.800
<v Speaker 1>press the button, and we make the flash happen immediately,

0:32:09.920 --> 0:32:15.040
<v Speaker 1>no delay. And what is your perception? You think that

0:32:15.080 --> 0:32:19.120
<v Speaker 1>the flash happened before you hit the button, So you

0:32:19.200 --> 0:32:22.400
<v Speaker 1>hit the button, the flash occurs immediately, and you say, WHOA,

0:32:22.440 --> 0:32:27.080
<v Speaker 1>I didn't do that. It flashed just before I hit it. Now,

0:32:27.080 --> 0:32:30.760
<v Speaker 1>this is amazing to witness because this is an illusory

0:32:30.840 --> 0:32:35.240
<v Speaker 1>reversal of action and effect. You hit the button, but

0:32:35.400 --> 0:32:40.760
<v Speaker 1>you believe the consequence happened before your action. Your brain

0:32:40.840 --> 0:32:43.880
<v Speaker 1>gives you the wrong answer because it has adjusted it

0:32:43.920 --> 0:32:48.240
<v Speaker 1>expects a certain delay, and now we've tricked it. Now,

0:32:48.280 --> 0:32:51.160
<v Speaker 1>this is a very simple experiment that you can reproduce

0:32:51.200 --> 0:32:53.360
<v Speaker 1>at home with a little bit of programming, but it's

0:32:53.400 --> 0:32:57.280
<v Speaker 1>a really big deal because it demonstrates that the timing

0:32:57.360 --> 0:33:00.680
<v Speaker 1>you perceive in the world is not what it's truly

0:33:00.760 --> 0:33:05.400
<v Speaker 1>happening out there, but an easily manipulated story put together

0:33:05.520 --> 0:33:08.720
<v Speaker 1>by your brain now. I presented this research at a

0:33:08.800 --> 0:33:11.440
<v Speaker 1>university recently, and a professor there came up to me

0:33:11.480 --> 0:33:14.320
<v Speaker 1>afterwards and asked me about something. He said, they just

0:33:14.360 --> 0:33:18.160
<v Speaker 1>got a new telephone system installed and he types at

0:33:18.200 --> 0:33:20.880
<v Speaker 1>his desk all day and sometimes he turns to the

0:33:20.880 --> 0:33:24.240
<v Speaker 1>phone and dials the number, and his impression was that

0:33:24.320 --> 0:33:28.600
<v Speaker 1>the line starts ringing just before he hits the final number. Well,

0:33:28.640 --> 0:33:32.160
<v Speaker 1>I immediately understood what was happening here, although he wasn't

0:33:32.200 --> 0:33:36.120
<v Speaker 1>aware of it. His computer keyboard has a delay between

0:33:36.400 --> 0:33:39.320
<v Speaker 1>hitting the key and a letter appearing on the screen.

0:33:39.360 --> 0:33:42.560
<v Speaker 1>Typically for computers that's about one hundred milliseconds, but we

0:33:42.680 --> 0:33:46.800
<v Speaker 1>never notice it because we calibrate to the delay. Anyway,

0:33:47.000 --> 0:33:50.040
<v Speaker 1>he now turns to the phone, and this new system

0:33:50.120 --> 0:33:53.120
<v Speaker 1>has a much smaller delay. So when he hits the

0:33:53.160 --> 0:33:57.000
<v Speaker 1>final number on the phone, the ringing starts, but it

0:33:57.120 --> 0:34:00.280
<v Speaker 1>feels like it happens just before he hit the final

0:34:00.400 --> 0:34:06.600
<v Speaker 1>number key. He's experiencing this illusory reversal of action and effect,

0:34:06.840 --> 0:34:09.920
<v Speaker 1>and it's because the delay of the two machines is different.

0:34:10.280 --> 0:34:14.120
<v Speaker 1>He's calibrated to one, and suddenly the delay is different

0:34:14.200 --> 0:34:16.759
<v Speaker 1>on the other. And by the way, you can turn

0:34:16.800 --> 0:34:19.919
<v Speaker 1>this into a game of sorts. My graduate student John

0:34:20.000 --> 0:34:25.279
<v Speaker 1>Jacobson was inspired by this discovery to program an unbeatable

0:34:25.360 --> 0:34:28.480
<v Speaker 1>game of rocks, as or paper. So here's how that goes.

0:34:28.640 --> 0:34:31.000
<v Speaker 1>There's a countdown and then you hit a key to

0:34:31.080 --> 0:34:33.880
<v Speaker 1>register whether you're throwing a rock or as or a paper,

0:34:34.040 --> 0:34:36.680
<v Speaker 1>And just like in the game, the computer presents its

0:34:36.800 --> 0:34:39.879
<v Speaker 1>choice at the same time, or so you think it's

0:34:40.000 --> 0:34:43.560
<v Speaker 1>actually waiting one hundred and fifty milliseconds and seeing what

0:34:43.600 --> 0:34:46.600
<v Speaker 1>you did, But it feels simultaneous to you because your

0:34:46.600 --> 0:34:49.960
<v Speaker 1>brain adjusts to you pressing the button and you're seeing

0:34:49.960 --> 0:34:52.239
<v Speaker 1>the result on the screen. And then every once in

0:34:52.280 --> 0:34:54.680
<v Speaker 1>a while the delay gets dropped, so it feels like

0:34:54.719 --> 0:34:58.440
<v Speaker 1>the computer answered before you, even though it was again

0:34:58.640 --> 0:35:02.440
<v Speaker 1>just registering your press and reacting immediately. You have the

0:35:02.520 --> 0:35:06.520
<v Speaker 1>feeling that you reacted after it and that you answered

0:35:06.560 --> 0:35:09.480
<v Speaker 1>exactly the wrong thing. And by the way, I'll just

0:35:09.560 --> 0:35:11.680
<v Speaker 1>mention that my students and I ran a bunch of

0:35:11.719 --> 0:35:16.319
<v Speaker 1>experiments in which we showed that this temporal recalibration can

0:35:16.480 --> 0:35:19.880
<v Speaker 1>last through time, which, as you may remember from episode

0:35:19.920 --> 0:35:24.680
<v Speaker 1>twenty four, is exactly what happens with the motion after effect.

0:35:24.719 --> 0:35:28.640
<v Speaker 1>When you say, watch a downward waterfall for a while,

0:35:28.719 --> 0:35:31.680
<v Speaker 1>and then you see everything moving upward. It turns out

0:35:31.719 --> 0:35:34.520
<v Speaker 1>if you watch the waterfall and close your eyes and

0:35:34.560 --> 0:35:38.520
<v Speaker 1>then open your eyes later, the illusion still happens. And

0:35:38.600 --> 0:35:42.240
<v Speaker 1>without going into details, this indicates the mechanism by which

0:35:42.320 --> 0:35:47.800
<v Speaker 1>the active recalibration happens under the hood in the neural circuitry. Anyway,

0:35:48.000 --> 0:35:50.720
<v Speaker 1>my lab published some years ago a model in which

0:35:51.120 --> 0:35:56.040
<v Speaker 1>recalibrations of motion are exactly the same mechanism as the

0:35:56.080 --> 0:36:00.480
<v Speaker 1>recalibrations in the time domain. In other words, words, this

0:36:00.520 --> 0:36:04.560
<v Speaker 1>suggests the possibility that the brain uses exactly the same

0:36:04.680 --> 0:36:09.640
<v Speaker 1>circuitry for time and space. I'll skip the details here,

0:36:09.680 --> 0:36:12.399
<v Speaker 1>but for interested parties, I've linked to the paper at

0:36:12.400 --> 0:36:16.400
<v Speaker 1>eagleman dot com slash podcast. Okay, so we can show

0:36:16.760 --> 0:36:21.640
<v Speaker 1>that the brain constantly recalibrates its timing. But remember this

0:36:21.680 --> 0:36:24.880
<v Speaker 1>isn't just a party trick of the brain. It's critical

0:36:24.960 --> 0:36:28.440
<v Speaker 1>to solving the problem of causality. The only way this

0:36:28.560 --> 0:36:32.160
<v Speaker 1>problem can be accurately solved in a brain with lots

0:36:32.160 --> 0:36:35.920
<v Speaker 1>of senses where timing is always changing is by keeping

0:36:35.960 --> 0:36:39.759
<v Speaker 1>the expected time of signals actively calibrated so that you

0:36:39.800 --> 0:36:45.200
<v Speaker 1>can determine before and after, even with these different sensory pathways,

0:36:45.200 --> 0:36:48.960
<v Speaker 1>so your brain's always making this adjustment. But here's something

0:36:49.000 --> 0:36:53.319
<v Speaker 1>really important. Let's return to what we saw with this recalibration.

0:36:53.840 --> 0:36:57.080
<v Speaker 1>A person hits the button, but if we've just removed

0:36:57.160 --> 0:37:00.200
<v Speaker 1>the delay, they say, WHOA, that wasn't me. The light

0:37:00.280 --> 0:37:04.399
<v Speaker 1>flashed before I did anything. And that got me thinking

0:37:04.480 --> 0:37:08.239
<v Speaker 1>about something because I realized I had seen that kind

0:37:08.280 --> 0:37:12.200
<v Speaker 1>of reaction before. So when I saw participants saying that

0:37:12.360 --> 0:37:17.239
<v Speaker 1>wasn't me, I thought that looks really familiar. Specifically, this

0:37:17.360 --> 0:37:22.000
<v Speaker 1>is called credit misattribution, and this is where you cause

0:37:22.080 --> 0:37:24.239
<v Speaker 1>something but you deny that you were the one who

0:37:24.280 --> 0:37:27.800
<v Speaker 1>did it. And this is one of the striking symptoms

0:37:27.840 --> 0:37:32.600
<v Speaker 1>that we see in schizophrenia. A person suffering from schizophrenia

0:37:32.840 --> 0:37:36.080
<v Speaker 1>will often do something and not take credit for it.

0:37:36.080 --> 0:37:38.680
<v Speaker 1>They believe that it was not them who caused the

0:37:38.760 --> 0:37:42.080
<v Speaker 1>thing to happen, and then it's perfectly rational for them

0:37:42.120 --> 0:37:44.759
<v Speaker 1>to cook up a different sort of explanation for it

0:37:45.040 --> 0:37:48.040
<v Speaker 1>and say someone else is doing it, or this was

0:37:48.160 --> 0:37:51.200
<v Speaker 1>caused by a signal from a radio tower or whatever,

0:37:51.280 --> 0:37:53.680
<v Speaker 1>but it's not me that did it. Whatever's going on,

0:37:54.600 --> 0:37:58.080
<v Speaker 1>And so some years ago, I started to hypothesize that

0:37:58.160 --> 0:38:04.600
<v Speaker 1>schizophrenia may actually be a problem with time recalibration. What

0:38:04.680 --> 0:38:08.280
<v Speaker 1>if you're not properly adjusting the timing of your inputs

0:38:08.280 --> 0:38:10.840
<v Speaker 1>to your outputs, you would have a very difficult time

0:38:11.520 --> 0:38:16.200
<v Speaker 1>judging causality. But that's just the beginning. I immediately started

0:38:16.200 --> 0:38:21.560
<v Speaker 1>thinking about another symptom of schizophrenia, which is auditory hallucinations.

0:38:22.600 --> 0:38:26.560
<v Speaker 1>So here's the thing. Under normal circumstances, you're always talking

0:38:26.560 --> 0:38:30.120
<v Speaker 1>to yourself. You have an internally generated voice, and you

0:38:30.280 --> 0:38:32.640
<v Speaker 1>listen to that. And by the way, if you're thinking,

0:38:33.000 --> 0:38:37.280
<v Speaker 1>what internal voice, that's the internal voice. But what happens

0:38:37.680 --> 0:38:41.799
<v Speaker 1>if you get the timing wrong, even by a few milliseconds,

0:38:41.840 --> 0:38:45.680
<v Speaker 1>such that you thought you were hearing the voice just

0:38:45.840 --> 0:38:49.680
<v Speaker 1>before feeling like you generated it, you would have to

0:38:49.719 --> 0:38:52.760
<v Speaker 1>conclude that it was somebody else's voice, not your own.

0:38:53.200 --> 0:38:56.880
<v Speaker 1>And it's all simply because the timing is off between

0:38:56.960 --> 0:39:00.560
<v Speaker 1>generating the voice and listening to it. And if thinking

0:39:00.640 --> 0:39:03.279
<v Speaker 1>led me and my students to run experiments at a

0:39:03.600 --> 0:39:08.120
<v Speaker 1>county mental health facility with people who had schizophrenia, and indeed,

0:39:08.160 --> 0:39:12.399
<v Speaker 1>we found that people with schizophrenia do not recalibrate their

0:39:12.480 --> 0:39:16.400
<v Speaker 1>timing as well as healthy controls do. So when we

0:39:16.480 --> 0:39:18.960
<v Speaker 1>give them a test like hit the button and did

0:39:18.960 --> 0:39:21.640
<v Speaker 1>the flash of light occur before or after, and we

0:39:21.760 --> 0:39:26.640
<v Speaker 1>measure their recalibration, it's much less or it's absent. Now,

0:39:26.680 --> 0:39:29.320
<v Speaker 1>like all science, this is going to require many more studies,

0:39:29.360 --> 0:39:32.600
<v Speaker 1>but if this is the right way to think about schizophrenia,

0:39:32.960 --> 0:39:37.279
<v Speaker 1>it completely changes our approach to it. It means that

0:39:37.360 --> 0:39:41.800
<v Speaker 1>instead of throwing pharmacological solutions at it, which have limited success,

0:39:42.680 --> 0:39:45.800
<v Speaker 1>just imagine if you could give somebody a video game

0:39:46.080 --> 0:39:48.879
<v Speaker 1>that they play for a few minutes and then their

0:39:48.920 --> 0:39:54.120
<v Speaker 1>auditory hallucinations go away because we've recalibrated their timing. So

0:39:54.239 --> 0:39:56.920
<v Speaker 1>this is work I'm pursuing now, and it all began

0:39:57.080 --> 0:40:02.399
<v Speaker 1>with these very simple experiments. So to wrap up today's episode,

0:40:02.560 --> 0:40:05.439
<v Speaker 1>it's an ongoing passion of mind to figure out how

0:40:05.480 --> 0:40:09.240
<v Speaker 1>the brain constructs reality. And there are very few things

0:40:09.280 --> 0:40:13.799
<v Speaker 1>weirder than time. What we saw today is that to

0:40:13.920 --> 0:40:19.000
<v Speaker 1>synchronize the incoming information from the senses, our conscious awareness

0:40:19.080 --> 0:40:22.319
<v Speaker 1>has to lag behind the physical world. But none of

0:40:22.320 --> 0:40:26.440
<v Speaker 1>that is obvious to your perception. And even weirder, the

0:40:26.600 --> 0:40:31.359
<v Speaker 1>order of sensory events in the world is dynamically recalibrated,

0:40:31.680 --> 0:40:34.520
<v Speaker 1>so you can hit a button that causes a flash,

0:40:34.680 --> 0:40:38.840
<v Speaker 1>but under different circumstances, you'll believe that happened before or after,

0:40:38.960 --> 0:40:42.040
<v Speaker 1>and we can easily change that around. And this is

0:40:42.080 --> 0:40:46.600
<v Speaker 1>because your brain can't automatically know what the timing should be,

0:40:47.320 --> 0:40:51.600
<v Speaker 1>especially as sensory timing changes all the time. So your brain,

0:40:52.160 --> 0:40:57.640
<v Speaker 1>living in darkness, constantly interacts with the world to recalibrate

0:40:57.760 --> 0:41:00.759
<v Speaker 1>its timing. It says, I'm going to knock on something now.

0:41:00.920 --> 0:41:05.480
<v Speaker 1>Everyone synchronize your watches. And this matters to the brains

0:41:05.680 --> 0:41:08.440
<v Speaker 1>so much to get all this timing right, because this

0:41:08.600 --> 0:41:14.160
<v Speaker 1>is the basis of judging causality, and when that recalibration

0:41:14.400 --> 0:41:17.440
<v Speaker 1>isn't working well, it makes it difficult to interpret the

0:41:17.440 --> 0:41:22.680
<v Speaker 1>world as we see in schizophrenia. And this episode points

0:41:22.719 --> 0:41:25.680
<v Speaker 1>us back to a fundamental lesson that we've seen a

0:41:25.719 --> 0:41:30.000
<v Speaker 1>lot in earlier episodes, with visual illusions and auditory illusions.

0:41:30.880 --> 0:41:35.839
<v Speaker 1>Reality is not passively received by our brains, but is

0:41:36.000 --> 0:41:45.520
<v Speaker 1>actively constructed. Go to Eagleman dot com slash podcast for

0:41:45.640 --> 0:41:49.360
<v Speaker 1>more information and to find further reading, and send me

0:41:49.400 --> 0:41:53.600
<v Speaker 1>an email at podcast at eagleman dot com with questions

0:41:53.680 --> 0:41:56.600
<v Speaker 1>or discussion, and I'll be making more episodes in which

0:41:56.640 --> 0:42:02.560
<v Speaker 1>I address those. Until next time, I'm David Eagleman, and

0:42:02.680 --> 0:42:04.480
<v Speaker 1>this is Inner Cosmos.