WEBVTT - How Touch Screens Work

0:00:00.320 --> 0:00:02.880
<v Speaker 1>Brought to you by the reinvented two thousand twelve camera.

0:00:03.240 --> 0:00:08.959
<v Speaker 1>It's ready. Are you get in touch with technology? With

0:00:09.039 --> 0:00:17.840
<v Speaker 1>tech Stuff from how stuff works dot com. Hello everybody,

0:00:17.840 --> 0:00:20.120
<v Speaker 1>and welcome to tech stuff. My name is Chris Poulette,

0:00:20.120 --> 0:00:21.919
<v Speaker 1>and I'm the tech editor here at how stuff works

0:00:21.960 --> 0:00:24.840
<v Speaker 1>dot com. Sitting next to me as usual as senior

0:00:24.840 --> 0:00:29.360
<v Speaker 1>writer Jonathan Strickland. I have the swine flu. Actually, yes,

0:00:29.800 --> 0:00:34.240
<v Speaker 1>yes he does. Yeah, that's I'm I'm beyond the contagious stage.

0:00:34.240 --> 0:00:36.440
<v Speaker 1>But if you guys think I sound a little weird

0:00:36.680 --> 0:00:38.800
<v Speaker 1>or maybe even sounded weird and past episodes, because the

0:00:38.800 --> 0:00:41.480
<v Speaker 1>episodes we recorded last week, I was already coming down

0:00:41.520 --> 0:00:45.520
<v Speaker 1>with it, that's why. And uh, I can report that

0:00:45.600 --> 0:00:50.520
<v Speaker 1>it kind of is awful. It's very much like the flu.

0:00:50.680 --> 0:00:54.600
<v Speaker 1>It is, um, except that apparently I now also have

0:00:54.800 --> 0:01:01.360
<v Speaker 1>the uncontrollable urge to lick pigs. I'll so let's uh

0:01:01.360 --> 0:01:04.560
<v Speaker 1>and then of course lead Yes, I was about to say,

0:01:04.600 --> 0:01:08.000
<v Speaker 1>it leads directly into our topic. UM. Now, I don't

0:01:08.040 --> 0:01:10.880
<v Speaker 1>have a listener mail for this specifically, we did have

0:01:10.920 --> 0:01:13.240
<v Speaker 1>a request for this topic, and it was from a

0:01:13.280 --> 0:01:17.080
<v Speaker 1>listener and it did arrive in mail, but our listener

0:01:17.200 --> 0:01:24.319
<v Speaker 1>Thomas sit in several requests for different text stuff podcast episodes, right, Like,

0:01:24.360 --> 0:01:28.520
<v Speaker 1>he had about five or six different lists topics listed,

0:01:28.560 --> 0:01:30.720
<v Speaker 1>And so we're just gonna tackle one of those today,

0:01:31.360 --> 0:01:35.679
<v Speaker 1>and that one is touch screens. And of course touch

0:01:35.720 --> 0:01:41.520
<v Speaker 1>screens are becoming more and more ubiquitous ever present all

0:01:41.600 --> 0:01:45.600
<v Speaker 1>over the place because things like smartphones. You got a

0:01:45.640 --> 0:01:48.400
<v Speaker 1>lot of cell phones out there that now have touch screens. Um.

0:01:48.440 --> 0:01:54.400
<v Speaker 1>You've got things like the iPod, TOUCHERSK reader right that

0:01:54.480 --> 0:01:56.400
<v Speaker 1>has a touch screen. Um. So yeah, there are a

0:01:56.440 --> 0:01:58.280
<v Speaker 1>lot of them out there. And of course then they're

0:01:58.320 --> 0:02:00.520
<v Speaker 1>always the other ones that have been around for ages

0:02:00.680 --> 0:02:05.280
<v Speaker 1>a t M S. Yeah, good example, vending machines, Um, yeah,

0:02:05.720 --> 0:02:09.760
<v Speaker 1>vending machines. I always think back to, uh, Epcot, the

0:02:09.800 --> 0:02:12.760
<v Speaker 1>old days of Epcot where they would have a computer

0:02:12.840 --> 0:02:14.960
<v Speaker 1>screen and you could walk up to it and touch

0:02:15.040 --> 0:02:18.679
<v Speaker 1>the computer screen and uh and and pull up information

0:02:18.720 --> 0:02:21.480
<v Speaker 1>about the park and about you know, the different aspects

0:02:21.480 --> 0:02:24.000
<v Speaker 1>of the park and make reservations. And this was back

0:02:24.040 --> 0:02:26.360
<v Speaker 1>in the early eighties, you know, when Epcot first opened

0:02:26.720 --> 0:02:29.600
<v Speaker 1>and uh and back then, a touch screen seemed like

0:02:29.760 --> 0:02:32.960
<v Speaker 1>freaking science fiction to me. It was. It was pretty

0:02:33.000 --> 0:02:34.960
<v Speaker 1>amazing because you didn't have to have like any sort

0:02:34.960 --> 0:02:36.920
<v Speaker 1>of keyboard to get it. In fact, that was that

0:02:37.000 --> 0:02:42.440
<v Speaker 1>was even before computer mouse had become really a commonplace item. Yeah,

0:02:42.520 --> 0:02:45.079
<v Speaker 1>you know, some of those early touch screens, at least

0:02:45.080 --> 0:02:46.960
<v Speaker 1>the ones that I used, were sort of like touched

0:02:47.520 --> 0:02:52.720
<v Speaker 1>touch touch touch, touch, touch, touch touch touch touch screens. Punch, punch, cry,

0:02:53.040 --> 0:02:56.640
<v Speaker 1>mop up blood. Yes, those were the stupid thing doesn't work. Yeah,

0:02:56.639 --> 0:03:01.399
<v Speaker 1>that the technology has improved somewhere, it hasnally. Now, there

0:03:01.440 --> 0:03:07.520
<v Speaker 1>are different touchscreen technologies that that are commonly used today.

0:03:07.680 --> 0:03:10.400
<v Speaker 1>The two most common when it comes to things like

0:03:11.160 --> 0:03:14.720
<v Speaker 1>portable electronic devices, so things like NP three players or

0:03:14.880 --> 0:03:20.880
<v Speaker 1>smartphones or whatever, would be resistive screens and capacitive screens. Yes,

0:03:21.080 --> 0:03:24.600
<v Speaker 1>all right, so let's talk about the differences between these

0:03:24.639 --> 0:03:27.639
<v Speaker 1>two systems since these are the most common that you'll

0:03:27.680 --> 0:03:33.320
<v Speaker 1>find out there a resistive screen or resistive system. It

0:03:33.360 --> 0:03:38.240
<v Speaker 1>consists of several layers of screens. It's like an onion

0:03:38.320 --> 0:03:41.920
<v Speaker 1>of screen. Yes, And the way that the system works

0:03:42.080 --> 0:03:46.360
<v Speaker 1>is when you press upon the screen, you compress these

0:03:46.400 --> 0:03:49.720
<v Speaker 1>different layers together and when they touch, it creates an

0:03:49.720 --> 0:03:53.240
<v Speaker 1>electric circuit. Right. Normally, there are spacers they keep the

0:03:53.280 --> 0:03:56.920
<v Speaker 1>two the layers apart. Right, If those spacers were to

0:03:57.120 --> 0:04:01.600
<v Speaker 1>be damaged and the space the screen were to permanently

0:04:01.680 --> 0:04:06.000
<v Speaker 1>be fused together, you would lose your resistive UH capabilities.

0:04:06.040 --> 0:04:09.280
<v Speaker 1>It would it would constantly be detecting a specific point

0:04:09.320 --> 0:04:12.600
<v Speaker 1>of pressure somewhere on the screen. So those the spacers

0:04:12.640 --> 0:04:16.000
<v Speaker 1>are very important because basically where you're touching it, the

0:04:16.040 --> 0:04:19.960
<v Speaker 1>computer is able to tell basically the coordinates of where

0:04:19.960 --> 0:04:22.480
<v Speaker 1>you're touching, and you know, maps that up to what's

0:04:23.000 --> 0:04:24.920
<v Speaker 1>being displayed on the screen, and that's how it knows

0:04:25.000 --> 0:04:27.960
<v Speaker 1>what you're touching and when. Right, So there's a processor

0:04:28.000 --> 0:04:33.200
<v Speaker 1>that is um it's receiving this information based upon where

0:04:33.240 --> 0:04:36.960
<v Speaker 1>the different layers of the screen are touching, and that

0:04:37.040 --> 0:04:39.920
<v Speaker 1>way it can it can give the correct response. So,

0:04:40.040 --> 0:04:41.800
<v Speaker 1>for example, if you have a phone that has a

0:04:41.839 --> 0:04:46.760
<v Speaker 1>resistive screen touch screen and you're pushing the call feature,

0:04:47.320 --> 0:04:50.960
<v Speaker 1>then it's going to map out the location of the

0:04:51.000 --> 0:04:54.520
<v Speaker 1>touch send that information to the processor. The processor says, hey,

0:04:55.080 --> 0:04:58.360
<v Speaker 1>when this particular area on the screen is touched, that

0:04:58.400 --> 0:05:01.919
<v Speaker 1>means that this action must be performed, and your phone

0:05:01.960 --> 0:05:04.520
<v Speaker 1>makes a call. And this all happens very very quickly.

0:05:04.960 --> 0:05:08.320
<v Speaker 1>Anklebone is connected to the footphone something like that. And

0:05:08.720 --> 0:05:13.479
<v Speaker 1>old resist of screens had a few big disadvantages really

0:05:13.680 --> 0:05:17.200
<v Speaker 1>compared to the other type the capacity of screen. One

0:05:17.240 --> 0:05:22.599
<v Speaker 1>of those was that the the the different layers would

0:05:22.640 --> 0:05:26.320
<v Speaker 1>somewhat obscure the light coming from the screen, so you

0:05:26.360 --> 0:05:29.400
<v Speaker 1>would only get a certain percentage of the light coming

0:05:29.400 --> 0:05:31.200
<v Speaker 1>out of the screen that you would get if the

0:05:31.480 --> 0:05:35.120
<v Speaker 1>if the screen were completely clear or transparent. UM. The

0:05:35.160 --> 0:05:37.520
<v Speaker 1>layers had to be really thin, yes, in order for

0:05:37.560 --> 0:05:40.919
<v Speaker 1>this to work properly, right, and some of them could.

0:05:41.760 --> 0:05:44.680
<v Speaker 1>Some of them could detect things like the amount of

0:05:44.680 --> 0:05:47.200
<v Speaker 1>pressure that you used, and really the amount of pressure

0:05:47.279 --> 0:05:49.800
<v Speaker 1>was coming from not how hard you were pushing, but

0:05:49.920 --> 0:05:53.720
<v Speaker 1>how much surface area of your finger or other whatever

0:05:53.760 --> 0:05:56.839
<v Speaker 1>it was was in contact with the screen. UM and

0:05:56.880 --> 0:05:59.000
<v Speaker 1>that could give it an indication of how hard you're pushing,

0:05:59.000 --> 0:06:00.760
<v Speaker 1>because the harder you push, the more of your finger

0:06:00.920 --> 0:06:03.760
<v Speaker 1>is going to be against the screen. So that whole

0:06:03.760 --> 0:06:06.839
<v Speaker 1>punching thing not really effective. No, that would be a

0:06:06.839 --> 0:06:09.160
<v Speaker 1>bad idea. It's pretty much a guarantee that you're gonna

0:06:09.160 --> 0:06:13.760
<v Speaker 1>break your resistive or any other touch screen. UM. The

0:06:13.760 --> 0:06:18.279
<v Speaker 1>the other disadvantage was that early resistive screens couldn't do

0:06:18.400 --> 0:06:23.680
<v Speaker 1>multi touch. Um, they were not capable of of accepting

0:06:23.680 --> 0:06:26.800
<v Speaker 1>two different points of contact at the same time and

0:06:26.880 --> 0:06:32.080
<v Speaker 1>could not interpret that as a you know, a legitimate command. Now.

0:06:32.120 --> 0:06:33.960
<v Speaker 1>Of course, we've got a lot of devices out there

0:06:33.960 --> 0:06:36.440
<v Speaker 1>that support multi touch now, and most of those are

0:06:36.520 --> 0:06:40.520
<v Speaker 1>using capacity screens. However, I can report it is possible

0:06:40.720 --> 0:06:44.000
<v Speaker 1>to create a resistive touch screen that supports multi touch.

0:06:44.080 --> 0:06:47.520
<v Speaker 1>You have to create a system that specifically supports this.

0:06:47.640 --> 0:06:49.920
<v Speaker 1>You know. It's not just like any resistive screen could

0:06:49.960 --> 0:06:52.400
<v Speaker 1>do this with a firmware update. You'd actually have to

0:06:52.400 --> 0:06:55.560
<v Speaker 1>go through the manufacturing process. But engadget has a video

0:06:55.640 --> 0:07:00.760
<v Speaker 1>on their site of a pretty cool device. Um. It

0:07:00.920 --> 0:07:06.440
<v Speaker 1>really was a concept of prototype where it's resistive screen,

0:07:06.640 --> 0:07:09.960
<v Speaker 1>it can detect pressure, and it is uh, it can

0:07:10.000 --> 0:07:13.320
<v Speaker 1>detect multi touch. One of the advantages of the resistive

0:07:13.320 --> 0:07:16.760
<v Speaker 1>system to the capacitive system is that you don't have

0:07:16.960 --> 0:07:20.080
<v Speaker 1>to You can use pretty much anything to contact the

0:07:20.120 --> 0:07:22.720
<v Speaker 1>screen and and give a command. So it doesn't have

0:07:22.760 --> 0:07:24.280
<v Speaker 1>to be your finger. It could be a stylist, right,

0:07:24.320 --> 0:07:28.480
<v Speaker 1>it could be anything, because it could be a dog. Yes,

0:07:28.760 --> 0:07:33.320
<v Speaker 1>it could be a rock, it could be some play doh. Um,

0:07:33.360 --> 0:07:35.480
<v Speaker 1>it really doesn't matter because as long as it is

0:07:35.520 --> 0:07:38.680
<v Speaker 1>able to make that pressure against the screen, that's going

0:07:38.720 --> 0:07:43.360
<v Speaker 1>to count as a an input. Now, capacity of screens

0:07:43.400 --> 0:07:47.880
<v Speaker 1>are different. Now they actually have a layer that stores

0:07:47.920 --> 0:07:52.480
<v Speaker 1>an electrical charge in them. That would be the capacitance layer. Yes,

0:07:52.800 --> 0:07:56.040
<v Speaker 1>Thus the name kind of makes sense now, doesn't it amazing,

0:07:56.120 --> 0:07:59.200
<v Speaker 1>isn't it. I mean the capacitive layer is uh, you know,

0:07:59.360 --> 0:08:03.040
<v Speaker 1>storing a like Tron's right, So it's storing these electrons

0:08:03.160 --> 0:08:05.200
<v Speaker 1>right there on the screen. When your finger comes in

0:08:05.280 --> 0:08:09.760
<v Speaker 1>contact with the screen, this actually ends up transferring the

0:08:09.880 --> 0:08:13.080
<v Speaker 1>charge to you. So technically you are kind of getting

0:08:13.080 --> 0:08:16.800
<v Speaker 1>a very mild shock. I find that revolting. Do you

0:08:17.280 --> 0:08:19.760
<v Speaker 1>do you get a charge out of it? We can

0:08:19.800 --> 0:08:21.760
<v Speaker 1>do this all day, palass oh, I know, and and

0:08:21.880 --> 0:08:27.800
<v Speaker 1>our listeners are depart like lightning was especially a shocking

0:08:27.880 --> 0:08:31.520
<v Speaker 1>kind of experience as long as you stay current. But

0:08:31.600 --> 0:08:35.319
<v Speaker 1>you know, I could tell that my iPod Touch has

0:08:35.360 --> 0:08:42.239
<v Speaker 1>a capacity screen because I'm stopping because you know, sitting

0:08:42.400 --> 0:08:45.200
<v Speaker 1>out and waiting for the bus or the train to

0:08:45.440 --> 0:08:48.400
<v Speaker 1>bring me to work here in the morning in the wintertime,

0:08:48.760 --> 0:08:52.440
<v Speaker 1>and having gloves on. You can't change you know, the

0:08:52.520 --> 0:08:57.280
<v Speaker 1>volume on your iPod because you know, my bears get

0:08:57.320 --> 0:08:59.959
<v Speaker 1>you know, the gloves won't because they start for the chart.

0:09:00.000 --> 0:09:02.079
<v Speaker 1>If they don't, they don't, they won't pick up the

0:09:02.160 --> 0:09:07.440
<v Speaker 1>charge like your skin would if you are But otherwise,

0:09:07.520 --> 0:09:09.800
<v Speaker 1>if you if you are outside on a really cold,

0:09:09.880 --> 0:09:12.720
<v Speaker 1>dry day, you might have problems getting a capacity of

0:09:12.760 --> 0:09:16.320
<v Speaker 1>screen to work at all. Uh. Capacity screens work best

0:09:16.360 --> 0:09:18.440
<v Speaker 1>when there's at least a little bit of humidity to

0:09:18.520 --> 0:09:23.000
<v Speaker 1>help conduct that electricity. Right. Yeah, but if it were

0:09:23.080 --> 0:09:26.560
<v Speaker 1>really called dry day, you might find that your touch

0:09:26.600 --> 0:09:28.960
<v Speaker 1>screen is not very responsive. It's not necessarily because your

0:09:28.960 --> 0:09:31.959
<v Speaker 1>phone is cold. It may be because you don't have

0:09:32.120 --> 0:09:35.720
<v Speaker 1>the moisture on your finger that helps create that that

0:09:35.800 --> 0:09:40.280
<v Speaker 1>electrical connection. And um, we'll see. That's good because I

0:09:40.320 --> 0:09:42.800
<v Speaker 1>like licking my iPod, So that explains why it always

0:09:42.840 --> 0:09:45.480
<v Speaker 1>works pretty well. Also explains why I have the swine flu.

0:09:46.480 --> 0:09:51.839
<v Speaker 1>So anyway, the capacity of screens actually do support multi

0:09:51.880 --> 0:09:55.840
<v Speaker 1>touch if you create the right hardware and software around it.

0:09:56.000 --> 0:09:59.160
<v Speaker 1>They don't automatically. It's not like magically supports it. You

0:09:59.200 --> 0:10:01.880
<v Speaker 1>have to build the system around it. Um. And of course,

0:10:01.920 --> 0:10:03.880
<v Speaker 1>if you were to build the system around it, you

0:10:03.920 --> 0:10:09.839
<v Speaker 1>could very possibly engender the wrath of Apple because they

0:10:09.880 --> 0:10:15.559
<v Speaker 1>patented it. They patented multi touch for for mobile devices.

0:10:15.920 --> 0:10:19.880
<v Speaker 1>That was really smart of them. It's also incredibly mean

0:10:20.400 --> 0:10:25.360
<v Speaker 1>because the Android operating system actually supports multi touch, but

0:10:25.480 --> 0:10:29.320
<v Speaker 1>it is not um enabled in any Android device that

0:10:29.480 --> 0:10:35.199
<v Speaker 1>I know of. Specifically, I assumes the patent I should have. Yeah,

0:10:35.200 --> 0:10:37.440
<v Speaker 1>I should assume it's because of this patent, and if

0:10:37.960 --> 0:10:40.640
<v Speaker 1>if the phones were to support multi touch, then it

0:10:40.679 --> 0:10:43.560
<v Speaker 1>could very well be Even if it's not directly in

0:10:44.360 --> 0:10:47.200
<v Speaker 1>violation of the patent, I'm sure that an argument could

0:10:47.200 --> 0:10:49.480
<v Speaker 1>be made and then you've got a costly legal battle.

0:10:49.920 --> 0:10:51.880
<v Speaker 1>So that would be why the iPhone is this great

0:10:51.960 --> 0:10:55.880
<v Speaker 1>multi touch device and most other devices don't support multi

0:10:55.920 --> 0:10:59.120
<v Speaker 1>touch in the same way. Um, some of you may

0:10:59.160 --> 0:11:01.840
<v Speaker 1>be yelling, hey, what the Microsoft surface. We'll get to that.

0:11:01.920 --> 0:11:05.760
<v Speaker 1>It's a it's a totally different animal. But the capacitive system,

0:11:05.880 --> 0:11:09.040
<v Speaker 1>so you know, like I said, it's it's it detects

0:11:09.040 --> 0:11:13.319
<v Speaker 1>this electrical uh connection, and that it's in a way

0:11:13.480 --> 0:11:15.400
<v Speaker 1>does the same sort of thing as the resistive screen

0:11:15.400 --> 0:11:18.000
<v Speaker 1>in the sense that it finds out you know, it

0:11:18.040 --> 0:11:21.560
<v Speaker 1>says where the connection happens on the screen, it maps

0:11:21.640 --> 0:11:25.240
<v Speaker 1>that to a specific command, and then the processor executes

0:11:25.280 --> 0:11:28.920
<v Speaker 1>that command. So the big difference between the two systems

0:11:29.200 --> 0:11:33.280
<v Speaker 1>is how it how the electrical connection is made. Yeah,

0:11:33.320 --> 0:11:36.679
<v Speaker 1>basically the one Once the the circuit or you know,

0:11:37.280 --> 0:11:41.520
<v Speaker 1>is completed and an electrical connection is made, the computer

0:11:41.640 --> 0:11:43.680
<v Speaker 1>on the other end figures out where it is and

0:11:43.880 --> 0:11:45.800
<v Speaker 1>what it's supposed to be doing at that point, right,

0:11:45.880 --> 0:11:48.160
<v Speaker 1>and and again with capacity of screens, you would have

0:11:48.240 --> 0:11:51.120
<v Speaker 1>to use something like a finger or you know, your

0:11:51.120 --> 0:11:55.600
<v Speaker 1>nose or you know, something that could create could accept

0:11:55.600 --> 0:11:58.199
<v Speaker 1>this charge from the screen. You couldn't use something that

0:11:58.320 --> 0:12:03.520
<v Speaker 1>was passive like a stylus or the rock four mentioned rock. Right,

0:12:03.600 --> 0:12:05.720
<v Speaker 1>you could possibly use a dog, depending on what part

0:12:05.760 --> 0:12:09.559
<v Speaker 1>of the dog was touching the screen. Yeah, yeah, you know,

0:12:10.480 --> 0:12:16.200
<v Speaker 1>or nose or something. But well yeah, well some of

0:12:16.280 --> 0:12:19.760
<v Speaker 1>us can leave a lot of finger smudges already, so um.

0:12:19.920 --> 0:12:22.559
<v Speaker 1>But yeah, if you wanted to use a stylist with

0:12:22.600 --> 0:12:24.360
<v Speaker 1>a capasity screen, you would have to have a stylist

0:12:24.440 --> 0:12:27.640
<v Speaker 1>had an active point on it that could accept that charge,

0:12:27.720 --> 0:12:31.760
<v Speaker 1>otherwise you wouldn't get anything out of it. So that

0:12:31.840 --> 0:12:36.000
<v Speaker 1>actually makes me wonder what the Microsoft Courier tablet, the

0:12:36.160 --> 0:12:39.120
<v Speaker 1>prototype that we we We've seen a video that was

0:12:39.160 --> 0:12:42.680
<v Speaker 1>more or less an animation of this prototype tablet that

0:12:42.720 --> 0:12:45.200
<v Speaker 1>Microsoft is coming out with. It's got two screens and

0:12:45.240 --> 0:12:48.480
<v Speaker 1>it has a touch screen interface, and it shows people

0:12:48.600 --> 0:12:52.480
<v Speaker 1>flicking through with their wealth. It shows an animation of

0:12:52.520 --> 0:12:56.040
<v Speaker 1>a finger flicking through pages UM and it also shows

0:12:56.040 --> 0:12:59.120
<v Speaker 1>an animation of like a stylist writing on a page.

0:12:59.600 --> 0:13:03.079
<v Speaker 1>So I kind of wonder what kind of touchscreen technology

0:13:03.120 --> 0:13:05.040
<v Speaker 1>it's playing on using if if they're using going to

0:13:05.120 --> 0:13:08.080
<v Speaker 1>use resistive or they're going to use capacitive UM. There

0:13:08.200 --> 0:13:11.640
<v Speaker 1>is another choice, but you don't see it that often

0:13:11.760 --> 0:13:18.040
<v Speaker 1>in in smaller devices. Is the surface acoustic waves system. Yeah.

0:13:18.120 --> 0:13:19.640
<v Speaker 1>Now this is something that you would see in and

0:13:20.200 --> 0:13:21.920
<v Speaker 1>more often in things like a t M S and

0:13:23.040 --> 0:13:26.080
<v Speaker 1>bigger displays. But what this uses is a couple of

0:13:26.080 --> 0:13:29.760
<v Speaker 1>transducers and they are placed along the X and y

0:13:29.800 --> 0:13:34.280
<v Speaker 1>axes of the glass plate of the monitor, and whenever

0:13:34.800 --> 0:13:37.880
<v Speaker 1>it sends an electrical signal, one transducer sends it to

0:13:37.920 --> 0:13:41.000
<v Speaker 1>another transducer, and there are reflectors on there to kind

0:13:41.000 --> 0:13:43.760
<v Speaker 1>of reflect the signal from one to the other. When

0:13:43.840 --> 0:13:48.160
<v Speaker 1>something makes contact with the screen, it disturbs that electrical wave,

0:13:48.600 --> 0:13:54.040
<v Speaker 1>and by measuring the disturbance, the touchscreen knows where it

0:13:54.160 --> 0:13:57.760
<v Speaker 1>was touched that. When I say knows, of course, we're

0:13:57.760 --> 0:14:03.000
<v Speaker 1>talking about a processor that that that the screen. Yeah,

0:14:03.000 --> 0:14:06.280
<v Speaker 1>the screen itself does not know. Um, it's not magic,

0:14:06.320 --> 0:14:09.320
<v Speaker 1>and it doesn't it's not sentient. It's once touch screens

0:14:09.360 --> 0:14:12.680
<v Speaker 1>become sentient, sexual harassment lawsuits will go through the roof

0:14:14.440 --> 0:14:18.920
<v Speaker 1>because of inappropriate touch screen interface. Let's we'll see if

0:14:18.920 --> 0:14:24.320
<v Speaker 1>that stays in the right. At any rate, the surface

0:14:24.360 --> 0:14:28.280
<v Speaker 1>acoustic wave system UH is not often Now, for one thing,

0:14:29.240 --> 0:14:31.040
<v Speaker 1>the equipment that you need in order to make this

0:14:31.080 --> 0:14:36.040
<v Speaker 1>thing work is kind of um big. It wouldn't really

0:14:36.040 --> 0:14:41.480
<v Speaker 1>be easy to miniaturize this into a mobile format, right,

0:14:41.520 --> 0:14:44.000
<v Speaker 1>So you wouldn't want to try and use this kind

0:14:44.000 --> 0:14:47.640
<v Speaker 1>of technology in your in your general mobile device because

0:14:47.640 --> 0:14:50.880
<v Speaker 1>it would make it too fat, too heavy. Um. And

0:14:50.920 --> 0:14:55.040
<v Speaker 1>of course we all want sleek and stylish. Well, I mean,

0:14:55.160 --> 0:14:58.040
<v Speaker 1>you know, the iPod pretty much proves that the sleek

0:14:58.080 --> 0:15:01.240
<v Speaker 1>and stylish approaches is really popular. I mean, it's a

0:15:01.240 --> 0:15:04.320
<v Speaker 1>good product anyway, but I think that the style is

0:15:04.360 --> 0:15:08.520
<v Speaker 1>definitely a large contributing factor to the popularity of the

0:15:08.560 --> 0:15:14.160
<v Speaker 1>iPod line. So at any rate, uh, capacity of resistive,

0:15:14.280 --> 0:15:15.960
<v Speaker 1>that's the two that you're going to see the most

0:15:16.000 --> 0:15:19.880
<v Speaker 1>often in your in your average mobile devices. Um, the

0:15:19.960 --> 0:15:24.840
<v Speaker 1>iPhone uses a capacity of screen, and like we said before,

0:15:24.960 --> 0:15:28.440
<v Speaker 1>it actually can detect multi touch. So that means that

0:15:28.520 --> 0:15:33.080
<v Speaker 1>you can use gestures instead of just touching. Two give

0:15:33.120 --> 0:15:37.480
<v Speaker 1>commands things like pinching, you know, like if you pinch. No, not,

0:15:37.640 --> 0:15:40.600
<v Speaker 1>I'm not actually pinching, Pillette. I want to make that clear.

0:15:40.640 --> 0:15:45.120
<v Speaker 1>I've already made one sexual harassment. I am not. I

0:15:45.160 --> 0:15:48.640
<v Speaker 1>am not even within pinching range of palette. Um, he

0:15:48.680 --> 0:15:52.560
<v Speaker 1>has barricaded himself in the corner and he's perfectly safe.

0:15:52.920 --> 0:15:56.600
<v Speaker 1>I got my blanky. Yes, he does have his blankie. No.

0:15:56.760 --> 0:15:59.560
<v Speaker 1>But but you know, like like when you wanna when

0:15:59.560 --> 0:16:04.120
<v Speaker 1>you want to squish or enlarge a photo doing various

0:16:04.120 --> 0:16:08.480
<v Speaker 1>pinching motions, or if you're panning or whatever, these are gestures. Okay,

0:16:08.480 --> 0:16:11.480
<v Speaker 1>But so these are commands that your phone should or

0:16:11.960 --> 0:16:14.200
<v Speaker 1>m P three player or whatever should be able to

0:16:14.240 --> 0:16:18.280
<v Speaker 1>recognize as a very general command as opposed to open

0:16:18.360 --> 0:16:20.400
<v Speaker 1>up this application I want to use it. It's more

0:16:20.440 --> 0:16:24.480
<v Speaker 1>of a you know, I'm I'm manipulating something, rotating a picture,

0:16:24.720 --> 0:16:28.240
<v Speaker 1>or you know, scrolling from one screen screen to another,

0:16:29.080 --> 0:16:32.960
<v Speaker 1>that kind of thing. And UM. I mean, regular touch

0:16:33.000 --> 0:16:36.080
<v Speaker 1>screens can identify some gestures as well. It's just multi

0:16:36.120 --> 0:16:43.280
<v Speaker 1>touch can identify more complex gestures. Uh. So that's pretty

0:16:43.400 --> 0:16:47.360
<v Speaker 1>much the the basis there. I mean, the the both

0:16:47.560 --> 0:16:49.880
<v Speaker 1>kinds of display are both kind of touch screens are

0:16:50.080 --> 0:16:54.440
<v Speaker 1>fairly accurate if they're done well. The execution has to

0:16:54.480 --> 0:17:00.160
<v Speaker 1>be there. But there's nothing about either u I Their

0:17:00.240 --> 0:17:04.679
<v Speaker 1>technology that makes one far more accurate than the other. UM.

0:17:04.720 --> 0:17:09.399
<v Speaker 1>They're both challenging to do well. But if you do uh,

0:17:09.520 --> 0:17:12.600
<v Speaker 1>you know, if you do the good work, then either

0:17:12.640 --> 0:17:16.720
<v Speaker 1>one should be more than accurate enough for the average user. UM.

0:17:16.800 --> 0:17:22.240
<v Speaker 1>The resistive screens are much cheaper than capacitive screens. UM

0:17:22.400 --> 0:17:28.399
<v Speaker 1>capacity seems to have the probably more support among the

0:17:28.440 --> 0:17:33.280
<v Speaker 1>technology savvy crowd. They seem to like the capacity screens more,

0:17:33.920 --> 0:17:37.280
<v Speaker 1>probably because of things like the old resistive screens were

0:17:37.320 --> 0:17:41.920
<v Speaker 1>harder to it's harder to see the images they were scratched.

0:17:42.320 --> 0:17:44.760
<v Speaker 1>They weren't scratch proof that they could get scratched pretty

0:17:44.800 --> 0:17:47.159
<v Speaker 1>easily because the screens had to be soft enough for

0:17:47.160 --> 0:17:51.000
<v Speaker 1>you to press them in a little bit. UM. But

0:17:52.240 --> 0:17:55.919
<v Speaker 1>if you're concerned with manufacturing a device that's going to

0:17:56.040 --> 0:18:00.680
<v Speaker 1>be an inexpensive one for your customers than the resistive

0:18:00.720 --> 0:18:03.440
<v Speaker 1>screen is a more attractive approach because it's less expensive

0:18:03.520 --> 0:18:06.880
<v Speaker 1>for those components. If you're doing a premium product, capacitive

0:18:06.880 --> 0:18:09.040
<v Speaker 1>it is probably the way to go. Yeah, well, it

0:18:09.080 --> 0:18:12.280
<v Speaker 1>seems like, you know, over the past few years, with

0:18:12.359 --> 0:18:17.359
<v Speaker 1>the ubiquitous nous of these devices, it's you know, it's

0:18:17.400 --> 0:18:22.000
<v Speaker 1>harder to find the implementation done poorly. He thinks that

0:18:22.240 --> 0:18:24.760
<v Speaker 1>more and more people are getting it right, which is

0:18:24.800 --> 0:18:29.119
<v Speaker 1>what's making you know, applications for these devices more and

0:18:29.200 --> 0:18:32.800
<v Speaker 1>more common. And a lot of the problems with touch

0:18:32.880 --> 0:18:36.439
<v Speaker 1>screens have more to do with the underlying operating system

0:18:36.480 --> 0:18:40.360
<v Speaker 1>than the technology of the screens themselves. So like older

0:18:40.760 --> 0:18:44.399
<v Speaker 1>operating systems for smartphones are tend to tend to have

0:18:44.400 --> 0:18:46.480
<v Speaker 1>a little more trouble with touch screens than the more

0:18:46.520 --> 0:18:49.560
<v Speaker 1>recent ones. You might have an older phone that's running

0:18:49.760 --> 0:18:53.680
<v Speaker 1>an older version of Windows Mobile, for example, that UH

0:18:54.240 --> 0:18:58.040
<v Speaker 1>is not as responsive as newer versions. UM. I think

0:18:59.320 --> 0:19:03.560
<v Speaker 1>Microsoft philosophy right now is from now on going forward,

0:19:03.680 --> 0:19:08.760
<v Speaker 1>smartphones running running Windows Mobile will have resistive screens. Smartphones

0:19:08.800 --> 0:19:11.800
<v Speaker 1>that will run the Windows Mobile or the Windows seven

0:19:12.640 --> 0:19:16.679
<v Speaker 1>modified modified UH operate system for mobile devices will have

0:19:16.800 --> 0:19:20.720
<v Speaker 1>multi touch and will be capacitive screens. So that's kind

0:19:20.720 --> 0:19:24.400
<v Speaker 1>of interesting that they've actually developed two different strategies that

0:19:24.600 --> 0:19:27.960
<v Speaker 1>and each one focuses on a specific technology. Well, it

0:19:28.040 --> 0:19:30.120
<v Speaker 1>makes sense that they would try to keep the cost

0:19:30.200 --> 0:19:33.199
<v Speaker 1>down by using a resistive screen in a you know,

0:19:33.680 --> 0:19:37.040
<v Speaker 1>more consumer device and higher end screens. Yeah, it's it's

0:19:37.040 --> 0:19:40.000
<v Speaker 1>actually a pretty clever approach. I think it'll be interesting

0:19:40.040 --> 0:19:41.960
<v Speaker 1>to see how that plays out. The only thing I

0:19:41.960 --> 0:19:44.040
<v Speaker 1>could think of that might cost them more money down

0:19:44.080 --> 0:19:47.240
<v Speaker 1>the road is by having the complexity of having another

0:19:47.320 --> 0:19:49.520
<v Speaker 1>system and another device, and it's another thing they have

0:19:49.600 --> 0:19:52.400
<v Speaker 1>to tool up for and another thing they have to support. Yeah. Well,

0:19:52.400 --> 0:19:56.040
<v Speaker 1>they've also got issues with their their Windows Mobile store,

0:19:56.320 --> 0:19:59.440
<v Speaker 1>and there there are a lot of things that the issues,

0:20:00.040 --> 0:20:02.760
<v Speaker 1>a lot of things Microsoft look at. Yeah, never any

0:20:02.800 --> 0:20:05.040
<v Speaker 1>issues with technology. I was going to mention also that

0:20:05.400 --> 0:20:09.520
<v Speaker 1>Research in Motion also known as risk Yes, the the

0:20:09.560 --> 0:20:12.959
<v Speaker 1>company behind BlackBerry. They filed a patent in January two

0:20:12.960 --> 0:20:17.760
<v Speaker 1>thousand eight for a hybrid resistive capacitive screen would have

0:20:17.840 --> 0:20:21.160
<v Speaker 1>both resistive and capacitive layers. I tried reading this patent

0:20:21.240 --> 0:20:23.240
<v Speaker 1>to figure out how it would work for this podcast,

0:20:23.640 --> 0:20:25.560
<v Speaker 1>and I think I would need another three or four

0:20:25.640 --> 0:20:28.760
<v Speaker 1>days to really get through it to understand it. Um.

0:20:28.880 --> 0:20:31.840
<v Speaker 1>I can't even pretend to go into the science behind

0:20:31.880 --> 0:20:34.600
<v Speaker 1>it because part of it is written in Martian. Well,

0:20:34.640 --> 0:20:37.879
<v Speaker 1>it's written in patent ease and okay, so it's a

0:20:38.520 --> 0:20:41.679
<v Speaker 1>level of difficulty above Martia. It's slightly more difficult than

0:20:41.720 --> 0:20:44.040
<v Speaker 1>Martian UM. And then I said, we were going to

0:20:44.080 --> 0:20:48.000
<v Speaker 1>talk about the Microsoft Surface very quickly. So the surface,

0:20:48.280 --> 0:20:52.000
<v Speaker 1>it doesn't use a capacitive resistive It does not. It

0:20:52.119 --> 0:20:54.040
<v Speaker 1>is if you don't know what it is. It is

0:20:54.119 --> 0:20:57.239
<v Speaker 1>a table like device. It has a monitor on the

0:20:57.240 --> 0:21:00.080
<v Speaker 1>top of it, so you would sit down at one

0:21:00.119 --> 0:21:03.680
<v Speaker 1>of these things, and it has a big screen that

0:21:03.720 --> 0:21:07.080
<v Speaker 1>you can touch and manipulate things on the screen. You

0:21:07.119 --> 0:21:10.080
<v Speaker 1>can have images there, you can play games, and it

0:21:10.119 --> 0:21:13.720
<v Speaker 1>can detect dozens of different touch points, so it's not

0:21:13.800 --> 0:21:15.919
<v Speaker 1>just you know, two finger touching. You could have a

0:21:16.000 --> 0:21:18.240
<v Speaker 1>game where five people are sitting around this table and

0:21:18.280 --> 0:21:20.480
<v Speaker 1>are playing a little pinball game or whatever, and each

0:21:20.480 --> 0:21:23.919
<v Speaker 1>one's controlling a set of flippers, you know, or tons

0:21:23.920 --> 0:21:27.560
<v Speaker 1>of other different implications. It does not use capacity or

0:21:27.640 --> 0:21:33.479
<v Speaker 1>resistive touch screens. Instead, it uses cameras and an image

0:21:33.520 --> 0:21:37.800
<v Speaker 1>recognition UH software that is in the infrared spectrum. So

0:21:37.840 --> 0:21:42.320
<v Speaker 1>these cameras are pointing up from inside the device. They're

0:21:42.359 --> 0:21:46.040
<v Speaker 1>pointing up at the screen, the screen surface, and they

0:21:46.080 --> 0:21:49.520
<v Speaker 1>detect the points of contact and then send that information

0:21:49.560 --> 0:21:53.280
<v Speaker 1>to the processor, which then you know, translates into a command.

0:21:54.160 --> 0:21:57.320
<v Speaker 1>The neat thing about this is you can use multiple

0:21:57.400 --> 0:22:02.439
<v Speaker 1>objects on the surface and and automatically transmit commands. So

0:22:02.520 --> 0:22:06.119
<v Speaker 1>let's say that you have a an MP three player

0:22:06.320 --> 0:22:10.640
<v Speaker 1>that can wirelessly sink with a computing device. So let's

0:22:10.640 --> 0:22:14.560
<v Speaker 1>say you've got a Microsoft Zoom and you lay this

0:22:14.680 --> 0:22:19.199
<v Speaker 1>down on the surface, the surface, the surface of the surface. Yes,

0:22:19.240 --> 0:22:21.000
<v Speaker 1>you could lay it on the screen of the surface,

0:22:21.400 --> 0:22:24.560
<v Speaker 1>and you could sink your device with the surface automatically

0:22:24.640 --> 0:22:26.680
<v Speaker 1>just by laying it on the screen, because it would

0:22:26.720 --> 0:22:29.600
<v Speaker 1>detect the shape and size of that Say, hey, you

0:22:29.680 --> 0:22:33.200
<v Speaker 1>know what that is. That's a zoom uh, and it

0:22:33.320 --> 0:22:35.639
<v Speaker 1>just automatically has the command that when that device is

0:22:35.680 --> 0:22:38.920
<v Speaker 1>placed on there, it'll sink. Yeah. So there are a

0:22:38.960 --> 0:22:44.879
<v Speaker 1>lot of interesting swine flu interesting um applications for this device.

0:22:45.960 --> 0:22:48.600
<v Speaker 1>So anyway, that was one thing I wanted to bring

0:22:48.680 --> 0:22:51.119
<v Speaker 1>up because technically that's not even if you think of

0:22:51.119 --> 0:22:54.439
<v Speaker 1>it as a touch screens. It's not really a touch screen.

0:22:54.560 --> 0:22:57.360
<v Speaker 1>It's really all because the camera. You had a similar

0:22:57.400 --> 0:23:00.320
<v Speaker 1>device you wanted to mention briefly, right, Well, yeah, because uh,

0:23:00.480 --> 0:23:02.879
<v Speaker 1>you know, as we were talking before hand, I started

0:23:02.920 --> 0:23:07.640
<v Speaker 1>thinking about other devices like that UM and uh one

0:23:07.680 --> 0:23:10.720
<v Speaker 1>of the ones that our friends that stuff from the

0:23:10.760 --> 0:23:15.000
<v Speaker 1>B side uh recorded And actually John Fuller wrote about

0:23:15.040 --> 0:23:19.520
<v Speaker 1>the React table, which uses a series of acrylic shapes

0:23:20.119 --> 0:23:25.240
<v Speaker 1>on a Microsoft surface like surface UM to control music.

0:23:25.680 --> 0:23:28.800
<v Speaker 1>And I started thinking about how that worked, and you said, basically,

0:23:28.800 --> 0:23:32.119
<v Speaker 1>it's the same, you know, a similar situation of cameras

0:23:32.160 --> 0:23:35.240
<v Speaker 1>underneath the table. And I remember from editing that that yes,

0:23:35.280 --> 0:23:38.440
<v Speaker 1>it's got UM, it's got a screen on which the

0:23:38.480 --> 0:23:42.440
<v Speaker 1>shapes said, and it's you know, the cameras tracking where

0:23:42.480 --> 0:23:45.160
<v Speaker 1>those those different pieces are. And it says, okay, well

0:23:45.160 --> 0:23:47.439
<v Speaker 1>this is a this is a circle. I know, you

0:23:47.480 --> 0:23:50.159
<v Speaker 1>know when his circle it controls the beat is you know,

0:23:50.320 --> 0:23:53.840
<v Speaker 1>the square does this. So that's uh yeah, So depending

0:23:53.880 --> 0:23:58.320
<v Speaker 1>on the position of those and the position and configuration

0:23:58.520 --> 0:24:02.560
<v Speaker 1>right those different objects, it'll create a different set of

0:24:02.600 --> 0:24:05.800
<v Speaker 1>sounds and you can rotate things in it, you know

0:24:05.520 --> 0:24:09.600
<v Speaker 1>it because it's the shape and the position of the

0:24:09.680 --> 0:24:12.320
<v Speaker 1>uh implement that it has to do a certain thing. Yeah,

0:24:12.320 --> 0:24:15.360
<v Speaker 1>I've seen similar applications which would do things like even

0:24:15.440 --> 0:24:20.160
<v Speaker 1>incorporate stuff like colors, so you might have a one

0:24:20.200 --> 0:24:22.359
<v Speaker 1>circle that's blue and one circle that's red, and it

0:24:22.440 --> 0:24:25.320
<v Speaker 1>actually translates to two different commands, so you can have

0:24:25.400 --> 0:24:28.000
<v Speaker 1>multiple circles on the same sort of surface and and

0:24:28.080 --> 0:24:30.320
<v Speaker 1>it would Yeah. Again, mostly it's it tends to be

0:24:30.359 --> 0:24:33.920
<v Speaker 1>things for like music performance art. I think Byork toured

0:24:33.920 --> 0:24:37.720
<v Speaker 1>with one of these, so, um, the thing is, my

0:24:37.840 --> 0:24:40.400
<v Speaker 1>question is if you, you know, have an instrument that's

0:24:40.480 --> 0:24:42.560
<v Speaker 1>using you know, reds and yellows, can it help you

0:24:42.560 --> 0:24:47.000
<v Speaker 1>play the blues? Let's move on. I'm glad that we

0:24:47.040 --> 0:24:50.840
<v Speaker 1>have exhausted touch screen, or at least I'm exhausted. But

0:24:50.920 --> 0:24:55.720
<v Speaker 1>then again, I've got puns aren't helping, I'm sure. Let's

0:24:55.720 --> 0:25:03.800
<v Speaker 1>move on to a little listener mail. This listener mail

0:25:03.840 --> 0:25:09.560
<v Speaker 1>comes from Chase, and Chase is an Oregonian living in Osaka, Japan.

0:25:10.240 --> 0:25:14.320
<v Speaker 1>He's also very verbose. Chase, I loved your email, and

0:25:14.320 --> 0:25:16.679
<v Speaker 1>I responded to Chase already, so I'm gonna have to

0:25:16.760 --> 0:25:20.880
<v Speaker 1>sort of summarize Chase's email here um, but he said

0:25:20.880 --> 0:25:23.639
<v Speaker 1>they had an He has an iPod Touch and he

0:25:23.760 --> 0:25:28.520
<v Speaker 1>got an application called Anti Young Free, which emits a

0:25:28.600 --> 0:25:31.280
<v Speaker 1>sound that only young people or people who took very

0:25:31.280 --> 0:25:34.600
<v Speaker 1>good care of their ears can hear. Because I work

0:25:34.640 --> 0:25:36.440
<v Speaker 1>in a high school, so I decided to test it

0:25:36.480 --> 0:25:38.600
<v Speaker 1>out on the class of fifteen to sixteen year old

0:25:39.600 --> 0:25:41.760
<v Speaker 1>I got them all to stand up and then push

0:25:41.840 --> 0:25:43.720
<v Speaker 1>the button to turn the sound on and told everyone

0:25:43.760 --> 0:25:46.200
<v Speaker 1>to sit down and they could hear something. To my surprise,

0:25:46.280 --> 0:25:49.960
<v Speaker 1>eight of the forty students remain standing and mystified. According

0:25:50.000 --> 0:25:52.960
<v Speaker 1>to the descriptions for this app, people who people should

0:25:53.000 --> 0:25:54.840
<v Speaker 1>be able to hear it until they are around twenty

0:25:54.920 --> 0:25:56.840
<v Speaker 1>to thirty years old. I'm twenty five years old and

0:25:56.840 --> 0:25:58.640
<v Speaker 1>cannot hear it, but my wife, who was twenty four

0:25:58.760 --> 0:26:01.800
<v Speaker 1>freaked out when I turned the sound on. That aside,

0:26:01.840 --> 0:26:04.120
<v Speaker 1>I also discovered a number of other absolute things like

0:26:04.240 --> 0:26:07.800
<v Speaker 1>repel mosquitoes or act as dog whistles. And you wanted

0:26:07.840 --> 0:26:09.800
<v Speaker 1>to know, one, how does it work? And two is

0:26:09.840 --> 0:26:12.800
<v Speaker 1>it doing any damage to his speakers? Let's take the

0:26:12.840 --> 0:26:16.200
<v Speaker 1>second one. First, most speakers can emit sounds that are

0:26:16.240 --> 0:26:20.680
<v Speaker 1>well beyond the range of human hearing, and so they're

0:26:20.680 --> 0:26:24.959
<v Speaker 1>perfectly capable of doing this. Nothing bad is going to happen, um,

0:26:25.000 --> 0:26:27.520
<v Speaker 1>you know, on its own, because that's what speakers do.

0:26:27.600 --> 0:26:30.359
<v Speaker 1>They're capable of emitting these sounds. It's not not like

0:26:30.400 --> 0:26:34.160
<v Speaker 1>it's suddenly ripping itself apart. But the first part about

0:26:34.160 --> 0:26:36.119
<v Speaker 1>how does it work? Well, humans can hear in a

0:26:36.280 --> 0:26:40.919
<v Speaker 1>range of of sound frequencies that it's between about twenty

0:26:40.960 --> 0:26:43.800
<v Speaker 1>hurts and twenty thousand hurts, give or take a few thousands.

0:26:44.280 --> 0:26:48.560
<v Speaker 1>All depends on who you ask, really, but whether you're

0:26:48.560 --> 0:26:50.720
<v Speaker 1>male or female. And of course, as we get older,

0:26:50.760 --> 0:26:54.200
<v Speaker 1>we start to lose the capability of hearing that complete range,

0:26:54.800 --> 0:26:59.560
<v Speaker 1>and in general we lose the upper ranges first. And

0:26:59.640 --> 0:27:04.200
<v Speaker 1>so if you are in your late twenties, early thirties,

0:27:04.560 --> 0:27:07.440
<v Speaker 1>you may only be able to hear up to fourteen

0:27:07.480 --> 0:27:11.400
<v Speaker 1>thousand hurts or sixteen thousand hurts or sixteen killer hurts

0:27:11.400 --> 0:27:15.440
<v Speaker 1>if you prefer. But um so, anything above that frequency

0:27:15.480 --> 0:27:18.240
<v Speaker 1>you just you don't, you don't hear it. But younger

0:27:18.280 --> 0:27:20.919
<v Speaker 1>people could still hear that. And in general, human beings

0:27:20.920 --> 0:27:26.520
<v Speaker 1>don't like high pitched noises. They tend to irritate us um,

0:27:26.560 --> 0:27:29.640
<v Speaker 1>which is you know why Chris likes to drown me out,

0:27:29.680 --> 0:27:34.960
<v Speaker 1>I guess at any rate. So that's how that really works,

0:27:35.040 --> 0:27:37.720
<v Speaker 1>is that as we age, we just naturally begin to

0:27:37.800 --> 0:27:40.199
<v Speaker 1>lose that ability, and some of us lose it more

0:27:40.240 --> 0:27:43.320
<v Speaker 1>slowly than others. So you may find someone who's thirty

0:27:43.320 --> 0:27:45.199
<v Speaker 1>two who can hear the same thing that a sixteen

0:27:45.240 --> 0:27:46.960
<v Speaker 1>year old can hear, or you may find you know

0:27:47.000 --> 0:27:49.159
<v Speaker 1>a fourteen year old kid who can't hear anything at

0:27:49.160 --> 0:27:53.040
<v Speaker 1>all from that particular range. Um, it's very subjective. There

0:27:53.040 --> 0:27:55.760
<v Speaker 1>are no hardened past rules, but in general, if you're

0:27:55.760 --> 0:27:59.040
<v Speaker 1>talking about big numbers, that's kind of how it works.

0:27:59.080 --> 0:28:00.959
<v Speaker 1>So thanks for writing in Chase. If any of you

0:28:01.000 --> 0:28:05.360
<v Speaker 1>have any questions, concerns, criticisms, suggestions per episodes, you can

0:28:05.400 --> 0:28:08.360
<v Speaker 1>write us tech Stuff at how stuff works dot com.

0:28:08.520 --> 0:28:11.800
<v Speaker 1>Remember we have a live show every Tuesday at one

0:28:11.920 --> 0:28:14.399
<v Speaker 1>pm Eastern. You can find that if you go to

0:28:14.440 --> 0:28:18.320
<v Speaker 1>the blogs over at how stufforks dot com and Crispy

0:28:18.320 --> 0:28:20.680
<v Speaker 1>and I will talk to you again. Hopefully I will

0:28:20.720 --> 0:28:26.720
<v Speaker 1>be talking without a raspy voice really soon. For moral

0:28:26.800 --> 0:28:29.280
<v Speaker 1>thiss and thousands of other topics, does it how stuff

0:28:29.320 --> 0:28:31.520
<v Speaker 1>works dot com and be sure to check out the

0:28:31.520 --> 0:28:34.920
<v Speaker 1>new tech stuff blog now on the house Stuff Works homepage,

0:28:39.200 --> 0:28:41.800
<v Speaker 1>brought to you by the reinvented two thousand twelve camera.

0:28:42.120 --> 0:28:43.320
<v Speaker 1>It's ready, are you