WEBVTT - Google's (Nearly) Universal Translator

0:00:03.760 --> 0:00:06.480
<v Speaker 1>Google's new wireless earbuds are the next step toward the

0:00:06.559 --> 0:00:10.640
<v Speaker 1>universal translator in Star Trek. I'm Jonathan Strickland, and this

0:00:10.840 --> 0:00:18.479
<v Speaker 1>is tech Stuff Daily. On October four, Google unveiled some

0:00:18.560 --> 0:00:21.680
<v Speaker 1>new products at a special event, including the second generation

0:00:21.720 --> 0:00:25.160
<v Speaker 1>of the Pixel Android phones and the Google Pixel Buds,

0:00:25.200 --> 0:00:29.240
<v Speaker 1>a pair of wireless earbuds with some nifty extra features. First,

0:00:29.480 --> 0:00:32.960
<v Speaker 1>some Android fans focused on something the new Pixel phones

0:00:33.040 --> 0:00:37.159
<v Speaker 1>expressly lack, which is a headphone jack. Neither the Pixel

0:00:37.200 --> 0:00:40.400
<v Speaker 1>Too nor its larger cousin, the Pixel to XL have

0:00:40.560 --> 0:00:43.680
<v Speaker 1>a three and a half millimeter headphone jack. Instead, you'll

0:00:43.720 --> 0:00:46.440
<v Speaker 1>need to either use a special dongle connected through the

0:00:46.520 --> 0:00:49.879
<v Speaker 1>phone's USB C port, or you'll need to pair a

0:00:49.960 --> 0:00:52.440
<v Speaker 1>wireless headset to the phone if you want to use

0:00:52.440 --> 0:00:55.240
<v Speaker 1>headphones or earbuds. It's a move that's similar to one

0:00:55.320 --> 0:00:58.640
<v Speaker 1>Apple made back in two sixteen. The iPhone seven also

0:00:58.760 --> 0:01:01.960
<v Speaker 1>launched without a headphone AC and while some Android users

0:01:02.000 --> 0:01:04.560
<v Speaker 1>such as myself might have been a bit smug about

0:01:04.560 --> 0:01:07.000
<v Speaker 1>the whole thing, it appears Apple is forging a new

0:01:07.040 --> 0:01:10.200
<v Speaker 1>path into the future, one in which all your headphone

0:01:10.200 --> 0:01:12.600
<v Speaker 1>accessories will either require an adapter or you'll need to

0:01:12.680 --> 0:01:16.240
<v Speaker 1>upgrade to new equipment. Google's explanation for the move is

0:01:16.280 --> 0:01:19.919
<v Speaker 1>all about the display on the phones. According to Mario Quitas,

0:01:20.160 --> 0:01:23.240
<v Speaker 1>a product chief at Google, the reason for the shift

0:01:23.319 --> 0:01:25.840
<v Speaker 1>was that Google wanted to move toward handsets that will

0:01:25.880 --> 0:01:28.120
<v Speaker 1>have the display go all the way right up to

0:01:28.160 --> 0:01:30.240
<v Speaker 1>the edges of the phone, getting rid of the bezel

0:01:30.360 --> 0:01:33.959
<v Speaker 1>as much as possible. This has not stopped some disgruntled

0:01:34.000 --> 0:01:37.080
<v Speaker 1>Android users from pointing out that the basic Pixel too

0:01:37.080 --> 0:01:40.080
<v Speaker 1>still has a bezel on all sides, while the Pixel

0:01:40.120 --> 0:01:42.920
<v Speaker 1>two x l's top and bottom edges also have a

0:01:42.959 --> 0:01:46.960
<v Speaker 1>border on them. Perhaps the more cynical Android fans feel

0:01:47.000 --> 0:01:49.400
<v Speaker 1>that this is a move designed to sell more accessories.

0:01:49.600 --> 0:01:51.960
<v Speaker 1>You can use a special dongle connected to the phone

0:01:52.000 --> 0:01:54.280
<v Speaker 1>to plug in that three and a half millimeter headphone

0:01:54.320 --> 0:01:57.120
<v Speaker 1>set into it, but it also means you can't charge

0:01:57.160 --> 0:01:59.800
<v Speaker 1>the device at the same time, since the charging cable

0:02:00.080 --> 0:02:03.480
<v Speaker 1>normally plug into the USBC port on the phone. If

0:02:03.480 --> 0:02:06.440
<v Speaker 1>you want to listen while charging, you'll need a wireless

0:02:06.440 --> 0:02:09.280
<v Speaker 1>headset that connects via Bluetooth. It seems like a natural

0:02:09.320 --> 0:02:11.720
<v Speaker 1>conclusion that this move was made in order to sell

0:02:11.760 --> 0:02:15.000
<v Speaker 1>those types of headsets, and indeed Google has a pair

0:02:15.040 --> 0:02:17.880
<v Speaker 1>of its own that retails for a cool one hundred

0:02:17.960 --> 0:02:22.000
<v Speaker 1>fifty nine dollars per set. However, Google's earbuds aren't just

0:02:22.160 --> 0:02:25.680
<v Speaker 1>passive listening devices. They serve as an interface for your

0:02:25.680 --> 0:02:28.560
<v Speaker 1>phone and have some cool functions as well. According to

0:02:28.600 --> 0:02:31.160
<v Speaker 1>the website The Verge, you can use swipe gestures and

0:02:31.240 --> 0:02:33.840
<v Speaker 1>the right earbud to control the volume directly, and you

0:02:33.880 --> 0:02:37.040
<v Speaker 1>can press the earbud to activate Google Assistant, the personal

0:02:37.120 --> 0:02:40.320
<v Speaker 1>voice assistant Google developed for the Android platform and Google

0:02:40.360 --> 0:02:43.360
<v Speaker 1>Home devices. You can interact with the assistant by speaking

0:02:43.400 --> 0:02:47.359
<v Speaker 1>directly to it. The assistant has natural language recognition built

0:02:47.440 --> 0:02:50.040
<v Speaker 1>into the system that means you can ask for the

0:02:50.120 --> 0:02:53.280
<v Speaker 1>same information in many different ways and the assistant will,

0:02:53.320 --> 0:02:56.560
<v Speaker 1>in theory, understand what you mean. For example, you could

0:02:56.560 --> 0:02:59.480
<v Speaker 1>say what will the weather be like tomorrow? Or will

0:02:59.520 --> 0:03:03.120
<v Speaker 1>it rain on Wednesday? Or what's tomorrow's forecast, and the

0:03:03.160 --> 0:03:05.640
<v Speaker 1>assistant will retrieve the information for you and speak to

0:03:05.680 --> 0:03:09.040
<v Speaker 1>you over the earbuds. One of the more intriguing features

0:03:09.080 --> 0:03:12.960
<v Speaker 1>Google showed off was the translate feature. Google Translate has

0:03:12.960 --> 0:03:15.920
<v Speaker 1>existed for a while and can automatically detect a language

0:03:15.960 --> 0:03:19.600
<v Speaker 1>based on text and translate it into other languages. Google

0:03:19.600 --> 0:03:22.799
<v Speaker 1>Assistant goes a step further. You can ask the assistant

0:03:22.840 --> 0:03:25.679
<v Speaker 1>to help you speak another language, and it will act

0:03:25.720 --> 0:03:29.000
<v Speaker 1>as a translator between you and someone speaking that language.

0:03:29.280 --> 0:03:31.799
<v Speaker 1>For example, if I wanted to chat with someone who

0:03:31.840 --> 0:03:35.160
<v Speaker 1>only spoke Spanish, I could use my phone to facilitate

0:03:35.200 --> 0:03:38.800
<v Speaker 1>this conversation. I'd activate Google Assistant and tell it to

0:03:38.840 --> 0:03:42.360
<v Speaker 1>help me speak Spanish. When my Spanish friend says something,

0:03:42.520 --> 0:03:45.880
<v Speaker 1>the phone will pick up the audio translated into English

0:03:45.920 --> 0:03:49.200
<v Speaker 1>and send that translation over the earbuds. I could then

0:03:49.360 --> 0:03:51.880
<v Speaker 1>press on the right earbud to activate the assistant and

0:03:51.960 --> 0:03:55.440
<v Speaker 1>speak back in English. The phone would then translate this

0:03:55.480 --> 0:03:58.560
<v Speaker 1>into Spanish, speaking it out to the person I'm chatting with.

0:03:58.920 --> 0:04:01.800
<v Speaker 1>It's not quite the Universal Translator from Star Trek, but

0:04:01.840 --> 0:04:05.880
<v Speaker 1>it's pretty darn close. These translators have been part of

0:04:05.920 --> 0:04:08.720
<v Speaker 1>science fiction for a while, whether in space operas like

0:04:08.840 --> 0:04:12.160
<v Speaker 1>Star Trek or comedies like Hitcheker's Guide to the Galaxy.

0:04:12.200 --> 0:04:15.080
<v Speaker 1>It makes sense because you need some way to address

0:04:15.080 --> 0:04:18.360
<v Speaker 1>the problem of communicating with alien species that would have

0:04:18.440 --> 0:04:22.400
<v Speaker 1>no contact with Earth languages. The Google Pixel buds won't

0:04:22.400 --> 0:04:25.559
<v Speaker 1>help you if you encounter Venusians on holiday, but since

0:04:25.560 --> 0:04:27.680
<v Speaker 1>we still have a heck of a time understanding each

0:04:27.680 --> 0:04:30.960
<v Speaker 1>other down here on Earth. They could come in awfully handy,

0:04:31.000 --> 0:04:34.360
<v Speaker 1>But is it worth the one fifty nine dollars? I

0:04:34.400 --> 0:04:37.120
<v Speaker 1>suppose that depends upon the individual user and how they

0:04:37.200 --> 0:04:40.400
<v Speaker 1>might rely upon the technology. The translate feature is just

0:04:40.560 --> 0:04:44.279
<v Speaker 1>one aspect of the earbuds. Google Assistant has many different

0:04:44.279 --> 0:04:47.840
<v Speaker 1>potential uses, but not all of them are necessarily interesting

0:04:47.880 --> 0:04:50.680
<v Speaker 1>to the average person, and one fifty nine dollars is

0:04:50.680 --> 0:04:53.560
<v Speaker 1>a pretty steep price for wireless headsets. If you're like

0:04:53.640 --> 0:04:56.000
<v Speaker 1>me and have a habit of misplacing your earbuds, you

0:04:56.040 --> 0:04:59.120
<v Speaker 1>may think twice before plopping down the cold, hard cash.

0:04:59.320 --> 0:05:01.640
<v Speaker 1>That's it for to day. To learn more about natural

0:05:01.720 --> 0:05:05.919
<v Speaker 1>language processing, voice recognition, personal assistance, and more, subscribe to

0:05:05.960 --> 0:05:08.520
<v Speaker 1>tech Stuff we published twice a week and do deep

0:05:08.560 --> 0:05:13.440
<v Speaker 1>dives into all sorts of technologies. Join us, Join us.

0:05:14.600 --> 0:05:16.960
<v Speaker 1>That's all for today. I'll see you again soon.