WEBVTT - Media in the Stream

0:00:04.240 --> 0:00:07.240
<v Speaker 1>Welcome to Tech Stuff, a production of I Heart Radios

0:00:07.320 --> 0:00:13.960
<v Speaker 1>How Stuff Works. Hey there, and welcome to tech Stuff.

0:00:14.000 --> 0:00:17.119
<v Speaker 1>I'm your host, Jonathan Strickland. I'm an executive producer with

0:00:17.200 --> 0:00:20.079
<v Speaker 1>I Heart Radio and I love all things tech and

0:00:20.200 --> 0:00:24.720
<v Speaker 1>ages ago in the Dark Times, our listener Susannah asked

0:00:24.720 --> 0:00:28.000
<v Speaker 1>if I might do an episode about streaming hardware. And

0:00:28.040 --> 0:00:30.840
<v Speaker 1>I got all excited because I was ready to talk

0:00:30.880 --> 0:00:34.600
<v Speaker 1>about fishing bowls and wading boots and nets and stuff.

0:00:34.640 --> 0:00:39.559
<v Speaker 1>And then then she explained that she meant streaming media hardware,

0:00:40.040 --> 0:00:42.440
<v Speaker 1>and specifically, she wanted to learn more about the various

0:00:42.440 --> 0:00:45.880
<v Speaker 1>devices you can purchase to stream Internet content to a television,

0:00:45.960 --> 0:00:48.800
<v Speaker 1>like a Roku or an Amazon fire stick, that kind

0:00:48.800 --> 0:00:51.760
<v Speaker 1>of stuff. And you know, these days, there are tons

0:00:51.920 --> 0:00:54.320
<v Speaker 1>of different options you could choose from if you wanted

0:00:54.360 --> 0:00:57.320
<v Speaker 1>to do that. Plus there are plenty of televisions that

0:00:57.400 --> 0:01:00.080
<v Speaker 1>have at least some of those capabilities built in to

0:01:00.120 --> 0:01:02.800
<v Speaker 1>them natively. But in this episode, we're going to do

0:01:02.880 --> 0:01:05.960
<v Speaker 1>a rundown on the history of the trend and how

0:01:06.000 --> 0:01:09.760
<v Speaker 1>those various devices work from kind of a high level. Plus,

0:01:10.160 --> 0:01:14.240
<v Speaker 1>what if anything really differentiates one device from another? Well,

0:01:14.600 --> 0:01:17.440
<v Speaker 1>to understand these devices it's actually a good idea for

0:01:17.560 --> 0:01:20.319
<v Speaker 1>us to step back a bit and talk about streaming

0:01:20.440 --> 0:01:24.440
<v Speaker 1>media in general. And that actually means that you guys

0:01:24.480 --> 0:01:27.520
<v Speaker 1>got to step into the elevator with me. So come

0:01:27.520 --> 0:01:30.640
<v Speaker 1>on in, let's playing room, guys, come on, just you know,

0:01:31.360 --> 0:01:35.320
<v Speaker 1>cramming here. Okay, Now that we're all in the elevator,

0:01:35.760 --> 0:01:39.720
<v Speaker 1>we know a couple of things. First, that darn closed

0:01:39.720 --> 0:01:43.280
<v Speaker 1>door button is just total garbage, is not connected to anything.

0:01:43.319 --> 0:01:46.080
<v Speaker 1>But we also know that our ears will now be

0:01:46.200 --> 0:02:05.520
<v Speaker 1>treated to some lovely instrumental music. Listen. Soothing, isn't it?

0:02:06.120 --> 0:02:09.799
<v Speaker 1>And you've likely heard this symphonic masterpiece referred to as

0:02:10.320 --> 0:02:14.839
<v Speaker 1>Musaic mu z a K. Well, that's a trademark name,

0:02:15.160 --> 0:02:18.080
<v Speaker 1>and it's possible because of a guy named George Owen

0:02:18.200 --> 0:02:22.040
<v Speaker 1>Squire way back in the nineteen tents. See, Georgie was

0:02:22.080 --> 0:02:24.280
<v Speaker 1>a heck of a guy. He attained the rank of

0:02:24.360 --> 0:02:27.320
<v Speaker 1>major general in the U. S. Military. He had a

0:02:27.400 --> 0:02:31.000
<v Speaker 1>doctorate from Johns Hopkins University. So this dude was both

0:02:31.160 --> 0:02:34.160
<v Speaker 1>super smart and he believed in serving his country, which,

0:02:34.680 --> 0:02:38.800
<v Speaker 1>you know, Wow, hats off to you, Major General Squire anyway,

0:02:38.919 --> 0:02:43.320
<v Speaker 1>not content with you know, just being a decorated soldier

0:02:43.560 --> 0:02:48.040
<v Speaker 1>and holding a PhD. He was also an inventor. In

0:02:48.160 --> 0:02:52.240
<v Speaker 1>nineteen eleven, Squire was looking into a method of delivering audio,

0:02:52.560 --> 0:02:55.480
<v Speaker 1>both in the form of music and in speech, over

0:02:55.560 --> 0:03:00.440
<v Speaker 1>electrical wires, and he called it wired radio, meaning instead

0:03:00.480 --> 0:03:04.640
<v Speaker 1>of broadcasting signals using an antenna, he could deliver audio

0:03:04.760 --> 0:03:08.760
<v Speaker 1>over physical electrical cables. Now, this was before the days

0:03:08.840 --> 0:03:12.160
<v Speaker 1>of consumer radio, and very few people had the equipment

0:03:12.240 --> 0:03:15.040
<v Speaker 1>or know how to use a radio at all, so

0:03:15.160 --> 0:03:18.000
<v Speaker 1>Squire saw this as a way to deliver audio to

0:03:18.040 --> 0:03:21.480
<v Speaker 1>the home without the need for all that equipment and knowledge.

0:03:22.120 --> 0:03:25.480
<v Speaker 1>Now that brief explanation makes it sound a lot like

0:03:25.840 --> 0:03:29.519
<v Speaker 1>the telephone, which had already been invented, but Squire made

0:03:29.560 --> 0:03:34.120
<v Speaker 1>some significant contributions to this technology. In nineteen eleven, he

0:03:34.200 --> 0:03:38.520
<v Speaker 1>patented a way to transmit high frequency signals across wires

0:03:38.520 --> 0:03:43.240
<v Speaker 1>that were intended for lower frequency transmission. The patent has

0:03:43.280 --> 0:03:48.640
<v Speaker 1>the name quote multiplex Telephony and Telegraphy end quote. Now

0:03:48.640 --> 0:03:51.520
<v Speaker 1>what this meant in practical terms is that Squire had

0:03:51.520 --> 0:03:55.640
<v Speaker 1>found a way to transmit quote a plurality of telephonic

0:03:55.720 --> 0:04:00.600
<v Speaker 1>and telegraphic messages over a single telephone circuit end quote,

0:04:00.840 --> 0:04:04.400
<v Speaker 1>So one circuit could serve as a conduit for multiple

0:04:04.480 --> 0:04:09.640
<v Speaker 1>transmissions simultaneously, and this was done by encoding the audio

0:04:09.760 --> 0:04:14.280
<v Speaker 1>signals using different frequencies. So for signal one, you would

0:04:14.280 --> 0:04:17.040
<v Speaker 1>have one band of frequencies, for signal two you would

0:04:17.040 --> 0:04:19.800
<v Speaker 1>have a different band of frequencies, and because you had

0:04:19.839 --> 0:04:25.640
<v Speaker 1>these different bands, you could easily differentiate between different signals.

0:04:26.120 --> 0:04:28.960
<v Speaker 1>You would need an encoding device on one end and

0:04:29.040 --> 0:04:32.200
<v Speaker 1>a decoding device on the other end in order to

0:04:32.320 --> 0:04:35.560
<v Speaker 1>send and receive the proper signals, but the circuits wouldn't

0:04:35.600 --> 0:04:37.800
<v Speaker 1>have to do anything special at all. The circuits would

0:04:37.880 --> 0:04:41.320
<v Speaker 1>just be the pathway. You didn't have to do anything

0:04:41.360 --> 0:04:44.600
<v Speaker 1>special to them, so in many ways this wasn't that

0:04:44.720 --> 0:04:49.440
<v Speaker 1>different from actual radio broadcasts. A receiver is capable of

0:04:49.480 --> 0:04:53.920
<v Speaker 1>picking up a wide range of radio frequencies. Using a tuner,

0:04:54.320 --> 0:04:57.479
<v Speaker 1>you can select one frequency, or in actuality, it's a

0:04:57.560 --> 0:05:02.080
<v Speaker 1>narrow band of frequencies around a key frequency. Then you

0:05:02.080 --> 0:05:06.080
<v Speaker 1>can pick up a single radio signal, and really it's

0:05:06.080 --> 0:05:09.320
<v Speaker 1>more like you're tuning out all the signals that are

0:05:09.440 --> 0:05:12.360
<v Speaker 1>not the one you are interested in, right. It's like

0:05:12.640 --> 0:05:15.560
<v Speaker 1>it's like making sure that you're ignoring all the noise

0:05:15.839 --> 0:05:18.640
<v Speaker 1>so that you get the signal. So, to use an analogy,

0:05:18.640 --> 0:05:21.000
<v Speaker 1>it's like if you went to a party where there

0:05:21.000 --> 0:05:23.359
<v Speaker 1>are a lot of people talking all at once, but

0:05:23.480 --> 0:05:27.560
<v Speaker 1>you're focusing on one specific person to hear what they're saying,

0:05:27.760 --> 0:05:29.800
<v Speaker 1>and as a result, you're focusing on them and you're

0:05:29.839 --> 0:05:33.080
<v Speaker 1>ignoring everyone else. Well, Squire did the same thing for

0:05:33.120 --> 0:05:36.440
<v Speaker 1>transmissions across an electrical wire. He was just using it

0:05:36.480 --> 0:05:40.839
<v Speaker 1>with technology as opposed to your focus. Squire donated his

0:05:40.880 --> 0:05:44.920
<v Speaker 1>patents to the American public because I mean, come on,

0:05:45.000 --> 0:05:49.040
<v Speaker 1>this guy, folks, this guy anyway, by the nineteen twenties,

0:05:49.360 --> 0:05:52.000
<v Speaker 1>he was looking to use his technology to send music

0:05:52.160 --> 0:05:56.080
<v Speaker 1>to speakers directly. He was taken by the name Kodak.

0:05:56.400 --> 0:05:59.520
<v Speaker 1>He thought that sounded really good and thought something similar

0:05:59.560 --> 0:06:02.039
<v Speaker 1>would serve as a good name for this service that

0:06:02.040 --> 0:06:07.159
<v Speaker 1>would deliver music to customers, and thus he chose Muzak. Now,

0:06:07.160 --> 0:06:10.560
<v Speaker 1>it took several years for the Musaic company to get

0:06:10.600 --> 0:06:12.840
<v Speaker 1>to the point where it could actually deliver music to

0:06:12.960 --> 0:06:17.839
<v Speaker 1>customers over electrical wires. Sadly, Major General Squire would pass

0:06:17.880 --> 0:06:23.080
<v Speaker 1>away before that day came. Meanwhile, radio had matured and

0:06:23.120 --> 0:06:27.000
<v Speaker 1>companies like our Cia had created consumer radio sets, which

0:06:27.040 --> 0:06:30.479
<v Speaker 1>meant there wasn't much point targeting the general public with

0:06:30.640 --> 0:06:33.760
<v Speaker 1>this service because radio was already doing it, but it

0:06:33.800 --> 0:06:37.599
<v Speaker 1>did still make sense to offer it to businesses and restaurants,

0:06:37.760 --> 0:06:40.120
<v Speaker 1>you know, places that might not be able to pick

0:06:40.240 --> 0:06:43.279
<v Speaker 1>up a radio signal easily, but these are places that

0:06:43.360 --> 0:06:46.320
<v Speaker 1>still maybe wanted to make use of music to improve

0:06:46.360 --> 0:06:50.120
<v Speaker 1>the ambiance of the environment. And thus we got elevator

0:06:50.240 --> 0:06:54.880
<v Speaker 1>music and an early concept in streaming media. Now we're

0:06:54.880 --> 0:06:59.880
<v Speaker 1>gonna skip ahead to nineteen seventy two, so several dec

0:07:00.000 --> 0:07:01.360
<v Speaker 1>aids at this point. We can all get out of

0:07:01.360 --> 0:07:04.600
<v Speaker 1>the elevator now, by the way, So in nineteen seventy two,

0:07:04.640 --> 0:07:08.160
<v Speaker 1>there was a computer scientist an electrical engineer named Nasir

0:07:08.279 --> 0:07:13.520
<v Speaker 1>Ahmed who invented a process called discrete cosign transform or

0:07:13.640 --> 0:07:17.520
<v Speaker 1>d c T. Now that probably sounds really technical, and

0:07:17.680 --> 0:07:20.240
<v Speaker 1>it is, but if we want to be super general

0:07:20.280 --> 0:07:22.600
<v Speaker 1>about it to kind of understand what was going on,

0:07:23.240 --> 0:07:27.280
<v Speaker 1>we can say that this is a method of representing something,

0:07:27.480 --> 0:07:32.440
<v Speaker 1>representing an image, for example, or an audio file, and

0:07:32.520 --> 0:07:36.160
<v Speaker 1>you represent it as the sum of various waves that

0:07:36.240 --> 0:07:41.320
<v Speaker 1>represent different magnitudes and frequencies, so you're mathematically describing something.

0:07:41.720 --> 0:07:45.120
<v Speaker 1>Now that representation has the benefit of taking up much

0:07:45.320 --> 0:07:48.800
<v Speaker 1>less data than the thing itself would if you were

0:07:48.840 --> 0:07:51.640
<v Speaker 1>to encode it directly. Now, if I were to use

0:07:51.680 --> 0:07:55.200
<v Speaker 1>a very general analogy, I would say that we would

0:07:55.240 --> 0:07:59.000
<v Speaker 1>imagine there's an artist who has created a painting on

0:07:59.200 --> 0:08:03.560
<v Speaker 1>an a norm canvas, and it would be difficult, would

0:08:03.600 --> 0:08:06.520
<v Speaker 1>be a hassle, and it would be expensive to ship

0:08:06.720 --> 0:08:10.440
<v Speaker 1>this painted canvas because it's just big and bulky, and

0:08:10.520 --> 0:08:12.600
<v Speaker 1>it would be delicate, so it'd be hard to do.

0:08:12.840 --> 0:08:17.320
<v Speaker 1>So Instead, a messenger of some artistic ability shows up

0:08:17.440 --> 0:08:21.480
<v Speaker 1>and studies this painting and writes down a careful description

0:08:21.720 --> 0:08:25.200
<v Speaker 1>of that painting, everything from what the painting is, of

0:08:25.560 --> 0:08:30.000
<v Speaker 1>the types of materials used in the painting, the colors, everything.

0:08:30.520 --> 0:08:34.640
<v Speaker 1>They bring that description then to a destination. At the destination,

0:08:34.920 --> 0:08:38.800
<v Speaker 1>another artist takes that description to recreate the original painting,

0:08:39.440 --> 0:08:42.679
<v Speaker 1>and it probably won't be a perfect representation of the original.

0:08:43.000 --> 0:08:46.480
<v Speaker 1>And in fact, compression technologies that rely on d c

0:08:46.720 --> 0:08:50.520
<v Speaker 1>T tend to be lossy formats. That means you lose

0:08:50.760 --> 0:08:55.400
<v Speaker 1>some data in the process of compression and decompression. So

0:08:55.440 --> 0:09:00.080
<v Speaker 1>I think this tracks anyway. D c T was an

0:09:00.120 --> 0:09:03.559
<v Speaker 1>important factor in finding a way to compress a file

0:09:03.679 --> 0:09:07.480
<v Speaker 1>down to a more manageable size, and that's the underlying

0:09:07.520 --> 0:09:10.920
<v Speaker 1>technology that would make streaming possible in the early days

0:09:10.960 --> 0:09:14.400
<v Speaker 1>of the Internet. Okay, well skip ahead again another twenty

0:09:14.480 --> 0:09:17.120
<v Speaker 1>years or so. It's time to talk about a former

0:09:17.280 --> 0:09:22.480
<v Speaker 1>Microsoft executive named Rob Glazer who formed a new company

0:09:22.559 --> 0:09:28.040
<v Speaker 1>in nine called Progressive Networks. Glazier had made a fortune

0:09:28.360 --> 0:09:31.600
<v Speaker 1>over at Microsoft. He was part of Microsoft as it

0:09:31.679 --> 0:09:35.320
<v Speaker 1>experienced explosive growth, and he rose in the ranks while

0:09:35.360 --> 0:09:38.800
<v Speaker 1>he was there, and he became a wealthy man because

0:09:38.800 --> 0:09:43.840
<v Speaker 1>of it. He also possesses very strong liberal views. He

0:09:43.920 --> 0:09:46.640
<v Speaker 1>grew up with a very strong liberal point of view.

0:09:46.920 --> 0:09:50.240
<v Speaker 1>So his original intent with Progressive Networks was to create

0:09:50.280 --> 0:09:54.359
<v Speaker 1>a media company that could spread progressive messaging and advocate

0:09:54.440 --> 0:09:59.080
<v Speaker 1>for progressive political policies. His team began developing technologies that

0:09:59.080 --> 0:10:02.840
<v Speaker 1>would allow of this mission, and that included a downloadable

0:10:02.880 --> 0:10:05.160
<v Speaker 1>media player that could act as a sort of plug

0:10:05.160 --> 0:10:07.679
<v Speaker 1>in for a web browser. And as it turned out,

0:10:07.840 --> 0:10:11.120
<v Speaker 1>when they would talk to investors, the investors were way

0:10:11.160 --> 0:10:14.920
<v Speaker 1>more interested in the underlying technology of the company than

0:10:15.000 --> 0:10:18.360
<v Speaker 1>the message that Glasier was hoping to spread. Now, keep

0:10:18.360 --> 0:10:22.600
<v Speaker 1>in mind that in n the web itself was a

0:10:22.640 --> 0:10:25.880
<v Speaker 1>pretty new thing. The very first web page was created

0:10:25.920 --> 0:10:29.720
<v Speaker 1>in August nine, so the Web had not been around

0:10:29.720 --> 0:10:32.559
<v Speaker 1>for very long at all. The World Wide Web was growing,

0:10:32.920 --> 0:10:37.040
<v Speaker 1>but it was extremely primitive compared to what we have today.

0:10:37.320 --> 0:10:42.600
<v Speaker 1>It also wasn't able to support rich dynamic material natively.

0:10:42.960 --> 0:10:46.200
<v Speaker 1>This is why a plug in would be needed, because

0:10:46.200 --> 0:10:51.680
<v Speaker 1>the HTTP protocol couldn't support streaming on its own. Those

0:10:51.720 --> 0:10:54.520
<v Speaker 1>were the days when browsing the Internet meant you had

0:10:54.559 --> 0:10:57.440
<v Speaker 1>to download half a dozen different plugins if you wanted

0:10:57.480 --> 0:11:01.520
<v Speaker 1>to experience everything that was being created, and simultaneously, you

0:11:01.559 --> 0:11:05.080
<v Speaker 1>would be opening up potential security vulnerabilities on your computer

0:11:05.200 --> 0:11:07.880
<v Speaker 1>because you had to download all these other things to

0:11:08.040 --> 0:11:13.240
<v Speaker 1>make that connectivity possible and that that dynamic material possible. Anyway,

0:11:13.240 --> 0:11:18.080
<v Speaker 1>back to streaming, Progressive Networks created a suite of technologies

0:11:18.120 --> 0:11:23.640
<v Speaker 1>that collectively we're called real Audio all one word big

0:11:23.640 --> 0:11:27.840
<v Speaker 1>are big A. This included a proprietary streaming format and

0:11:27.880 --> 0:11:30.800
<v Speaker 1>a plug in player, and the concept was great because

0:11:30.800 --> 0:11:33.040
<v Speaker 1>it would allow you to listen to an audio file

0:11:33.360 --> 0:11:36.680
<v Speaker 1>while you were in the process of downloading that file,

0:11:37.040 --> 0:11:38.800
<v Speaker 1>so you didn't have to wait for the full file

0:11:38.880 --> 0:11:41.720
<v Speaker 1>to download before you could start to listen. Sort of

0:11:41.720 --> 0:11:44.560
<v Speaker 1>similar to how images used to load in browsers, because

0:11:44.600 --> 0:11:47.319
<v Speaker 1>in the good old days, downloading an image meant you

0:11:47.320 --> 0:11:50.680
<v Speaker 1>would watch as line by line of pixels appeared on

0:11:50.720 --> 0:11:53.440
<v Speaker 1>your screen until you got the finished picture. Well, this

0:11:53.520 --> 0:11:56.920
<v Speaker 1>was similar, except you were hearing audio that was recorded

0:11:56.960 --> 0:11:59.360
<v Speaker 1>at a low bit rate, so it wasn't super high

0:11:59.400 --> 0:12:02.280
<v Speaker 1>quality do that was a limitation of the technology at

0:12:02.280 --> 0:12:04.920
<v Speaker 1>the time, and you could listen to it while that

0:12:05.000 --> 0:12:07.880
<v Speaker 1>audio file was downloading to your machine. It was sort

0:12:07.920 --> 0:12:11.560
<v Speaker 1>of like laying down railroad tracks while there's a train

0:12:11.679 --> 0:12:15.600
<v Speaker 1>slowly catching up to you from behind. Blazer's team recognized

0:12:15.920 --> 0:12:17.680
<v Speaker 1>that this approach would let you do more than just

0:12:17.760 --> 0:12:21.320
<v Speaker 1>listen to, say, a music file as you downloaded it.

0:12:21.320 --> 0:12:24.720
<v Speaker 1>It would also let you stream audio from a broadcast

0:12:24.720 --> 0:12:28.720
<v Speaker 1>source across the Internet so that people could listen in live.

0:12:29.440 --> 0:12:32.120
<v Speaker 1>It was like a live radio broadcast, but using the

0:12:32.160 --> 0:12:35.120
<v Speaker 1>Internet to carry the signal rather than the airwaves. So

0:12:35.200 --> 0:12:37.240
<v Speaker 1>really you could think of this as the next step

0:12:37.280 --> 0:12:40.920
<v Speaker 1>after using those electrical wires to carry multiple audio signals

0:12:40.920 --> 0:12:47.040
<v Speaker 1>like music did so. On September five, Progressive Networks partnered

0:12:47.040 --> 0:12:51.480
<v Speaker 1>with ESPN Sports Zone and they transmitted a baseball game.

0:12:51.760 --> 0:12:54.880
<v Speaker 1>It was the Seattle Mariners versus the New York Yankees,

0:12:55.280 --> 0:12:58.280
<v Speaker 1>and for the first time, anyone interested in the game

0:12:58.600 --> 0:13:02.440
<v Speaker 1>who happened to be subscriber to ESPN Sports Zone and

0:13:02.480 --> 0:13:05.640
<v Speaker 1>have a computer enabled with sound and an Internet connection,

0:13:06.160 --> 0:13:10.040
<v Speaker 1>and this player could listen in on this audio transmission

0:13:10.240 --> 0:13:12.880
<v Speaker 1>on this real audio platform. It was a good game

0:13:13.040 --> 0:13:15.400
<v Speaker 1>to the Mariners led six to one at the top

0:13:15.440 --> 0:13:17.920
<v Speaker 1>of the sixth and then the Yankees managed to score

0:13:18.000 --> 0:13:21.480
<v Speaker 1>four more runs, so the final game score was six

0:13:21.600 --> 0:13:25.559
<v Speaker 1>five Mariners, which is not a bad debut for streaming audio,

0:13:26.000 --> 0:13:28.560
<v Speaker 1>might have been a tough blow to Yankees fans. It

0:13:28.720 --> 0:13:31.520
<v Speaker 1>was a big pr success for Glazier's company, not to

0:13:31.520 --> 0:13:34.120
<v Speaker 1>mention for Glazier himself, since he was part owner of

0:13:34.160 --> 0:13:39.000
<v Speaker 1>the Mariners. However, the actual reach of this broadcast was

0:13:39.080 --> 0:13:42.079
<v Speaker 1>pretty modest. Only a few hundred people had the ability

0:13:42.160 --> 0:13:45.040
<v Speaker 1>to receive the streaming audio because they met all the

0:13:45.040 --> 0:13:48.240
<v Speaker 1>criteria that were required in order to do so. But

0:13:48.400 --> 0:13:52.360
<v Speaker 1>it marked the beginning of an era. That being said,

0:13:52.400 --> 0:13:55.640
<v Speaker 1>it wasn't exactly off to the races for streaming media.

0:13:56.040 --> 0:13:59.920
<v Speaker 1>Glazier's team had created the first platform capable of play

0:14:00.000 --> 0:14:02.920
<v Speaker 1>being live streamed audio on the Internet, but there wasn't

0:14:02.960 --> 0:14:07.880
<v Speaker 1>exactly an overabundance of opportunities to use that capability. The

0:14:07.920 --> 0:14:11.320
<v Speaker 1>Internet in general and the Web in particular, we're still

0:14:11.440 --> 0:14:16.080
<v Speaker 1>pretty young, at least for the public use of those utilities. Moreover,

0:14:16.360 --> 0:14:21.280
<v Speaker 1>connectivity speeds weren't exactly at broadband levels. The vast majority

0:14:21.320 --> 0:14:23.760
<v Speaker 1>of Internet users in the United States were relying on

0:14:23.880 --> 0:14:27.800
<v Speaker 1>dial up modems that had hefty limitations on download speeds,

0:14:28.080 --> 0:14:31.320
<v Speaker 1>so it would take time for communications companies to develop

0:14:31.360 --> 0:14:35.000
<v Speaker 1>and roll out broadband connectivity. Heck, you know, we're still

0:14:35.320 --> 0:14:38.680
<v Speaker 1>seeing pretty slow rollout in some communities in the United States,

0:14:38.720 --> 0:14:42.640
<v Speaker 1>but that's a discussion for another day. Progressive Networks struck

0:14:42.720 --> 0:14:47.760
<v Speaker 1>up a deal in with Microsoft, and this agreement meant

0:14:47.760 --> 0:14:51.000
<v Speaker 1>that Microsoft would include a distribution of the Real Audio

0:14:51.080 --> 0:14:54.840
<v Speaker 1>player with Internet Explorer, and that gave Progressive Networks a

0:14:54.920 --> 0:14:59.280
<v Speaker 1>huge boost in adoption. Meanwhile, the company was hard at

0:14:59.280 --> 0:15:02.720
<v Speaker 1>work to create Real Video, which was essentially for streaming

0:15:02.800 --> 0:15:06.880
<v Speaker 1>video what Real Audio was for streaming audio. Real Video

0:15:06.920 --> 0:15:11.320
<v Speaker 1>would debut in around that same time. Bill Gates over

0:15:11.360 --> 0:15:13.680
<v Speaker 1>at Microsoft was beginning to think he made an error

0:15:13.760 --> 0:15:17.680
<v Speaker 1>in helping out Progressive Networks. Gates saw that streaming media

0:15:17.880 --> 0:15:21.000
<v Speaker 1>had the potential to be much bigger than it had

0:15:21.080 --> 0:15:24.480
<v Speaker 1>been in it was mostly viewed as a curiosity then,

0:15:25.080 --> 0:15:27.800
<v Speaker 1>and he felt that Microsoft really needed to own a

0:15:27.840 --> 0:15:31.560
<v Speaker 1>piece of that business, or being Microsoft, he probably felt

0:15:31.560 --> 0:15:35.160
<v Speaker 1>that it needed to own all of it. Initially, Microsoft

0:15:35.280 --> 0:15:40.040
<v Speaker 1>entered the industry by purchasing a competing streaming media company,

0:15:40.120 --> 0:15:43.080
<v Speaker 1>but then Glazer met with Gates and the two hashed

0:15:43.080 --> 0:15:46.240
<v Speaker 1>out a licensing deal that would embed real audio and

0:15:46.280 --> 0:15:51.560
<v Speaker 1>real video technology in Microsoft's Windows Media Player platform. Progressive

0:15:51.600 --> 0:15:54.880
<v Speaker 1>Networks would then change its name to Real Networks and

0:15:54.920 --> 0:15:58.200
<v Speaker 1>it would continue to butt heads against Microsoft, but that's

0:15:58.240 --> 0:16:01.160
<v Speaker 1>outside the realm of our focus for this episode. Now,

0:16:01.160 --> 0:16:03.800
<v Speaker 1>before I go on, let's take a quick break to

0:16:03.840 --> 0:16:08.120
<v Speaker 1>thank our sponsor. Hiring the right person takes time, time

0:16:08.160 --> 0:16:11.600
<v Speaker 1>that you often don't have. Urgency can be your enemy

0:16:11.640 --> 0:16:14.680
<v Speaker 1>when it comes to finding candidates that are truly meant

0:16:14.800 --> 0:16:17.880
<v Speaker 1>for your business. That's why LinkedIn is the best place

0:16:17.920 --> 0:16:20.600
<v Speaker 1>to post your job. With LinkedIn, you can find the

0:16:20.680 --> 0:16:24.440
<v Speaker 1>right person quickly and easily. I like it because I

0:16:24.560 --> 0:16:28.000
<v Speaker 1>want businesses and job candidates to get matched up efficiently.

0:16:28.400 --> 0:16:32.800
<v Speaker 1>It's to everyone's benefit. LinkedIn Jobs screens candidates with the

0:16:32.800 --> 0:16:35.160
<v Speaker 1>skills you're looking for, so you can hire the right

0:16:35.240 --> 0:16:41.240
<v Speaker 1>person fast. Things like collaboration, creativity, adaptability. LinkedIn looks beyond

0:16:41.600 --> 0:16:44.040
<v Speaker 1>the work skills and puts your job post in front

0:16:44.040 --> 0:16:48.000
<v Speaker 1>of qualified candidates who match your business requirements perfectly. That's

0:16:48.000 --> 0:16:50.280
<v Speaker 1>how linked In make sure your job post is seen

0:16:50.320 --> 0:16:53.840
<v Speaker 1>by the people you want to hire, people with the skills, qualifications,

0:16:53.840 --> 0:16:57.000
<v Speaker 1>and other interests that will help your business grow. It's

0:16:57.040 --> 0:17:00.560
<v Speaker 1>no wonder a person is hired every eight seconds with LinkedIn,

0:17:01.080 --> 0:17:04.480
<v Speaker 1>and why companies rated LinkedIn jobs the number one hiring

0:17:04.480 --> 0:17:08.159
<v Speaker 1>platform for delivering quality hires. Find the right person for

0:17:08.240 --> 0:17:11.840
<v Speaker 1>your business today. With LinkedIn jobs, you can pay what

0:17:11.960 --> 0:17:14.959
<v Speaker 1>you want and get the first fifty dollars off. Just

0:17:15.160 --> 0:17:20.160
<v Speaker 1>visit LinkedIn dot com slash tech pod again, that's LinkedIn

0:17:20.560 --> 0:17:23.800
<v Speaker 1>dot com slash tech pod to get fifty dollars off

0:17:23.840 --> 0:17:27.560
<v Speaker 1>your first job post. Terms and conditions apply. All right,

0:17:27.640 --> 0:17:31.359
<v Speaker 1>let's get back to streaming media. Back in the nineteen nineties,

0:17:32.119 --> 0:17:35.160
<v Speaker 1>no one was really sure how the streaming media thing

0:17:35.240 --> 0:17:37.600
<v Speaker 1>was going to play out. There was a real sense

0:17:37.640 --> 0:17:40.639
<v Speaker 1>that there would be some big battles brewing between the

0:17:40.840 --> 0:17:44.680
<v Speaker 1>entrenched old media, that being radio and television and this

0:17:44.880 --> 0:17:49.760
<v Speaker 1>upstart new media enabled by the Internet. There's a piece

0:17:49.840 --> 0:17:54.359
<v Speaker 1>and Wired titled Real Revolution, which obviously is largely about

0:17:54.440 --> 0:17:58.320
<v Speaker 1>progressive network slash real networks Rise, and it has a

0:17:58.440 --> 0:18:01.960
<v Speaker 1>very prescient vision of what would eventually turn into reality

0:18:02.200 --> 0:18:04.560
<v Speaker 1>in the form of sites like YouTube. Now I'm gonna

0:18:04.640 --> 0:18:09.719
<v Speaker 1>quote Robert Ride's article because it's really interesting how on

0:18:09.880 --> 0:18:13.919
<v Speaker 1>target he was, though it was about a decade early.

0:18:14.560 --> 0:18:17.840
<v Speaker 1>Ryan was talking about the possibilities that open up once

0:18:17.880 --> 0:18:20.960
<v Speaker 1>technology allows for the transmission of video so that you

0:18:21.000 --> 0:18:23.840
<v Speaker 1>can view it in a full sized window on a

0:18:23.880 --> 0:18:29.520
<v Speaker 1>computer screen. And here's what he says him quote all

0:18:29.600 --> 0:18:32.919
<v Speaker 1>this could wreak havoc with the competitive dynamics of the

0:18:32.960 --> 0:18:36.959
<v Speaker 1>TV industry, opening millions of living rooms to any hyperactive

0:18:37.040 --> 0:18:40.480
<v Speaker 1>kid with a video camera, a computer and a phone line,

0:18:40.840 --> 0:18:44.080
<v Speaker 1>which may soon mean most kids in America. Or it

0:18:44.160 --> 0:18:46.960
<v Speaker 1>could give the likes of Murdoch and Ted Turner and

0:18:47.119 --> 0:18:51.480
<v Speaker 1>eight Lane Highway into the heartland of the traditionally democratized,

0:18:51.600 --> 0:18:56.399
<v Speaker 1>decentralized net or maybe do both end quote and you

0:18:56.440 --> 0:19:00.520
<v Speaker 1>know what, bingo, he hit the nail on the head there,

0:19:00.560 --> 0:19:05.000
<v Speaker 1>because that's exactly what we've seen. YouTube created the opportunity

0:19:05.080 --> 0:19:07.639
<v Speaker 1>for regular folks to upload videos for the world to

0:19:07.720 --> 0:19:10.960
<v Speaker 1>see and later to stream live video to the world

0:19:11.000 --> 0:19:14.879
<v Speaker 1>as well. Bigger media companies, the traditional ones, would also

0:19:14.920 --> 0:19:18.920
<v Speaker 1>take advantage of tech to offer streaming services from established

0:19:19.000 --> 0:19:23.359
<v Speaker 1>traditional media companies. And we've seen content made for cinemas

0:19:23.400 --> 0:19:27.240
<v Speaker 1>and broadcast or cable television repackaged for the Internet. But

0:19:27.320 --> 0:19:30.320
<v Speaker 1>we've also seen a lot of projects made specifically for

0:19:30.400 --> 0:19:34.640
<v Speaker 1>those streaming services themselves. So yeah, that was a great prediction.

0:19:35.600 --> 0:19:38.960
<v Speaker 1>Now let's shift gears a bit. So while real video

0:19:39.240 --> 0:19:44.960
<v Speaker 1>was launching in another company was just getting started. That

0:19:45.000 --> 0:19:48.560
<v Speaker 1>company was Netflix, which when it started was all about

0:19:48.680 --> 0:19:52.160
<v Speaker 1>renting out DVDs to customers who would pay a monthly

0:19:52.240 --> 0:19:55.080
<v Speaker 1>fee to watch as many DVDs as they liked, or

0:19:55.200 --> 0:19:58.840
<v Speaker 1>really as many as they could, depending on how much

0:19:58.880 --> 0:20:01.240
<v Speaker 1>time it took to ship a new DVD to the

0:20:01.280 --> 0:20:05.160
<v Speaker 1>customer and return old DVDs back to Netflix through the mail.

0:20:05.800 --> 0:20:09.480
<v Speaker 1>By two thousand, Netflix founder Read Hastings saw the potential

0:20:09.560 --> 0:20:12.159
<v Speaker 1>for streaming media to act as a new way to

0:20:12.240 --> 0:20:15.760
<v Speaker 1>deliver this type of service to customers. He was also

0:20:15.840 --> 0:20:20.280
<v Speaker 1>in fierce competition with Blockbuster, which was still a thing

0:20:20.840 --> 0:20:25.960
<v Speaker 1>back then. Initially, Hastings approached Blockbuster with the opportunity of

0:20:26.000 --> 0:20:30.000
<v Speaker 1>a partnership in which Netflix would become the streaming component

0:20:30.320 --> 0:20:34.520
<v Speaker 1>for the company Blockbuster, but that deal didn't go anywhere.

0:20:35.119 --> 0:20:38.120
<v Speaker 1>And that makes sense because back in two thousand when

0:20:38.119 --> 0:20:42.360
<v Speaker 1>Hastings was meeting with Blockbuster, broadband connectivity wasn't really a

0:20:42.440 --> 0:20:46.160
<v Speaker 1>thing yet. Most customers wouldn't be able to take advantage

0:20:46.320 --> 0:20:49.560
<v Speaker 1>of a streaming service, or if they did, it would

0:20:49.560 --> 0:20:51.560
<v Speaker 1>have to be at such a compression rate that the

0:20:51.560 --> 0:20:54.280
<v Speaker 1>image and sound would be awful, or the size of

0:20:54.320 --> 0:20:58.359
<v Speaker 1>a postage stamp, so it didn't make sense at the time.

0:20:58.760 --> 0:21:01.400
<v Speaker 1>It would be like watching everything on a super crappy

0:21:01.440 --> 0:21:04.760
<v Speaker 1>bootleg VHS tape, and it would take several years for

0:21:04.840 --> 0:21:07.520
<v Speaker 1>the technology to evolve to the point that it would

0:21:07.520 --> 0:21:10.520
<v Speaker 1>work for the average customer, which is why Netflix wouldn't

0:21:10.560 --> 0:21:14.199
<v Speaker 1>introduce its streaming service or even announce it until two

0:21:14.280 --> 0:21:17.440
<v Speaker 1>thousand seven. I'll get to that in a little bit,

0:21:17.880 --> 0:21:21.240
<v Speaker 1>But in the fall of two thousand six, Steve Jobs

0:21:21.280 --> 0:21:24.399
<v Speaker 1>revealed at an Apple event that the company was making

0:21:24.440 --> 0:21:28.119
<v Speaker 1>an Apple product that would bring content offered through the

0:21:28.160 --> 0:21:33.399
<v Speaker 1>Apple iTunes store to consumer televisions. The original concept was

0:21:33.440 --> 0:21:36.960
<v Speaker 1>a box that would sink with an iTunes customers computer

0:21:37.520 --> 0:21:40.440
<v Speaker 1>so that the customer could send content that they had

0:21:40.480 --> 0:21:44.080
<v Speaker 1>rented or purchased on the iTunes store on their computer

0:21:44.640 --> 0:21:48.080
<v Speaker 1>to this box via standard eight oh two eleven WiFi,

0:21:48.520 --> 0:21:51.800
<v Speaker 1>So you would send it via WiFi to this box,

0:21:51.840 --> 0:21:54.639
<v Speaker 1>and the box would then push this content to a

0:21:54.680 --> 0:21:58.240
<v Speaker 1>television through an h d M I cable or through

0:21:58.320 --> 0:22:02.280
<v Speaker 1>component video cables d IS remember component video, and then

0:22:02.359 --> 0:22:06.439
<v Speaker 1>it also supported both analog and digital audio outputs, so

0:22:06.520 --> 0:22:09.680
<v Speaker 1>this box was sort of a middleman between a computer

0:22:09.840 --> 0:22:12.960
<v Speaker 1>and the television, and Jobs called it i t V

0:22:13.240 --> 0:22:16.000
<v Speaker 1>in the demo, but when it launched the following year,

0:22:16.280 --> 0:22:19.600
<v Speaker 1>the company would simply call it Apple TV, and its

0:22:19.640 --> 0:22:22.800
<v Speaker 1>initial form, the Apple TV required a networked computer to

0:22:22.840 --> 0:22:25.439
<v Speaker 1>supply the content, so this was not a box that

0:22:25.520 --> 0:22:27.679
<v Speaker 1>you could just hook up to the Internet at large

0:22:28.040 --> 0:22:31.200
<v Speaker 1>and pull down video or music using a user interface

0:22:31.280 --> 0:22:35.480
<v Speaker 1>with the box itself. There was this intermediary step with

0:22:35.560 --> 0:22:38.359
<v Speaker 1>the networked computer, but this was to try and solve

0:22:38.359 --> 0:22:40.520
<v Speaker 1>a problem that a lot of people had, which was

0:22:40.560 --> 0:22:43.560
<v Speaker 1>that for a lot of folks, they weren't sure how

0:22:43.640 --> 0:22:47.439
<v Speaker 1>to connect their computers to their televisions so that they

0:22:47.480 --> 0:22:52.479
<v Speaker 1>could watch Internet streaming content on their TVs. There were

0:22:52.520 --> 0:22:55.800
<v Speaker 1>ways to do it, but it wasn't exactly easy for

0:22:55.880 --> 0:23:02.600
<v Speaker 1>the average consumer. There involved a lot of different uh hardware, cables,

0:23:02.640 --> 0:23:06.480
<v Speaker 1>and different software packages that you needed to do. You

0:23:06.480 --> 0:23:09.160
<v Speaker 1>have to worry about different resolutions. It ended up being

0:23:09.240 --> 0:23:13.760
<v Speaker 1>something that the average person just wasn't comfortable handling. So

0:23:14.280 --> 0:23:18.440
<v Speaker 1>this was Apple's solution to that problem. But in addition

0:23:18.480 --> 0:23:22.840
<v Speaker 1>to this intermediary step, the media services that Apple supported

0:23:22.880 --> 0:23:27.120
<v Speaker 1>did not include stuff like Netflix or other online media,

0:23:27.280 --> 0:23:30.480
<v Speaker 1>and most of the content on iTunes had been optimized

0:23:30.520 --> 0:23:34.159
<v Speaker 1>for much smaller screens than your average television, so the

0:23:34.200 --> 0:23:38.000
<v Speaker 1>resulting video in those early days of Apple TV wasn't

0:23:38.040 --> 0:23:41.159
<v Speaker 1>super high quality. Apple would make adjustments to how it

0:23:41.200 --> 0:23:44.000
<v Speaker 1>approached the Apple TV over the following years, and it

0:23:44.080 --> 0:23:47.920
<v Speaker 1>includes some online media connectivity and remove the requirement to

0:23:48.000 --> 0:23:50.760
<v Speaker 1>sync with a networked computer, which made it more of

0:23:50.800 --> 0:23:54.520
<v Speaker 1>a true streaming box over time. But in that early

0:23:54.600 --> 0:23:58.639
<v Speaker 1>incarnation you probably wouldn't call it a streaming box. It

0:23:58.720 --> 0:24:02.639
<v Speaker 1>was more like a sinking slash downloading box. Also in

0:24:02.680 --> 0:24:07.320
<v Speaker 1>two thousand and six, Amazon announced a service called Amazon Unboxed. Now.

0:24:07.359 --> 0:24:11.159
<v Speaker 1>This was Amazon's digital video download service, and again This

0:24:11.240 --> 0:24:14.919
<v Speaker 1>was all about downloading video content, not streaming it, but

0:24:15.000 --> 0:24:17.840
<v Speaker 1>it would serve as the foothold for Amazon to evolve

0:24:17.880 --> 0:24:21.200
<v Speaker 1>this service later and to what we now call Prime Video.

0:24:21.359 --> 0:24:24.439
<v Speaker 1>I'll get back to that later in this episode. So

0:24:24.480 --> 0:24:28.600
<v Speaker 1>while Netflix was emerging from struggling business into a successful

0:24:28.600 --> 0:24:32.480
<v Speaker 1>competitor with Blockbuster, there was another guy named Anthony Wood

0:24:32.680 --> 0:24:35.920
<v Speaker 1>who was the founder of a DVR company called Replay TV,

0:24:36.359 --> 0:24:41.120
<v Speaker 1>who created his sixth company. He named it Roku, which

0:24:41.160 --> 0:24:44.119
<v Speaker 1>is Japanese for six. Roku was in the business of

0:24:44.200 --> 0:24:48.800
<v Speaker 1>making streaming media products like digital radios and digital signage.

0:24:49.320 --> 0:24:52.280
<v Speaker 1>He got into some early discussions with Read Hastings about

0:24:52.280 --> 0:24:55.560
<v Speaker 1>developing a streaming video set top box for the company,

0:24:56.520 --> 0:25:00.959
<v Speaker 1>but Hastings wasn't really sure about it. Eventually, Anthony would

0:25:01.080 --> 0:25:03.840
<v Speaker 1>joined the Netflix team to head up their Internet TV

0:25:03.960 --> 0:25:08.000
<v Speaker 1>division while also still running things back at Roku. So

0:25:08.760 --> 0:25:11.760
<v Speaker 1>we get close to when Netflix is getting ready to

0:25:11.960 --> 0:25:15.879
<v Speaker 1>launch its streaming service, It's web based streaming service in

0:25:15.880 --> 0:25:19.199
<v Speaker 1>two thousand seven, and originally Hastings was on board with

0:25:19.320 --> 0:25:22.720
<v Speaker 1>actually making a piece of hardware, a set top box

0:25:23.000 --> 0:25:25.679
<v Speaker 1>that would be like a VCR or a DVD player,

0:25:26.119 --> 0:25:29.760
<v Speaker 1>or more recently a DVR, but this device would pull

0:25:30.040 --> 0:25:33.719
<v Speaker 1>content down over the Internet and send it to the television,

0:25:34.080 --> 0:25:37.800
<v Speaker 1>so Netflix would have a selection of its titles available

0:25:38.040 --> 0:25:43.920
<v Speaker 1>to stream to this box. Internally at Netflix, this device

0:25:44.040 --> 0:25:47.320
<v Speaker 1>project was called Griffin. It was named after a character

0:25:47.400 --> 0:25:51.040
<v Speaker 1>in the film The Player. Netflix launched a beta of

0:25:51.080 --> 0:25:55.600
<v Speaker 1>its streaming service, which again that was just purely web based,

0:25:55.680 --> 0:26:00.600
<v Speaker 1>so people were watching these streaming programs on their computers,

0:26:00.640 --> 0:26:03.880
<v Speaker 1>and things were headed toward a manufacturing run of the

0:26:03.960 --> 0:26:07.400
<v Speaker 1>hardware box that would bring that capability to the living

0:26:07.480 --> 0:26:13.280
<v Speaker 1>room television set. But then Hastings began to reconsider this strategy,

0:26:13.320 --> 0:26:17.000
<v Speaker 1>and his fear was that if Netflix produced and shipped

0:26:17.040 --> 0:26:20.919
<v Speaker 1>its own hardware, its own branded box, it would be

0:26:21.000 --> 0:26:24.400
<v Speaker 1>seen as a competitive move against some of the company's

0:26:24.440 --> 0:26:28.760
<v Speaker 1>Netflix was partnering with in licensing agreements. So in addition

0:26:28.800 --> 0:26:31.879
<v Speaker 1>to the set top box, Woods team was creating a

0:26:31.920 --> 0:26:35.240
<v Speaker 1>technology that could be used by other types of manufacturers,

0:26:35.480 --> 0:26:40.359
<v Speaker 1>including television manufacturers, video game console manufacturers, and more. The

0:26:40.400 --> 0:26:45.159
<v Speaker 1>whole idea was get Netflix on everything, to add that

0:26:45.240 --> 0:26:50.280
<v Speaker 1>Netflix connectivity to any device. Hastings reportedly said to someone

0:26:50.400 --> 0:26:53.760
<v Speaker 1>in Netflix his worry was if he produced the hardware,

0:26:53.960 --> 0:26:57.440
<v Speaker 1>then a company like Apple would never agree to include

0:26:57.480 --> 0:27:00.719
<v Speaker 1>Netflix as an option on its own hardware are and

0:27:00.760 --> 0:27:04.040
<v Speaker 1>one thing Hastings really wanted to make certain happen was

0:27:04.080 --> 0:27:06.840
<v Speaker 1>that Netflix would be available pretty much on any platform

0:27:06.920 --> 0:27:09.680
<v Speaker 1>that had an Internet connection. I mean, you even find

0:27:09.800 --> 0:27:13.679
<v Speaker 1>refrigerators that have Netflix apps on them. So after some debate,

0:27:13.760 --> 0:27:18.840
<v Speaker 1>he scrapped this project. Now that was a big hard

0:27:18.880 --> 0:27:22.080
<v Speaker 1>decision to make, because you have to remember that Netflix

0:27:22.119 --> 0:27:26.439
<v Speaker 1>had spent a huge amount of money, not to mention

0:27:26.560 --> 0:27:29.919
<v Speaker 1>time and effort to develop the technologies for this player.

0:27:30.400 --> 0:27:33.680
<v Speaker 1>The company had worked on video buffering techniques to help

0:27:33.720 --> 0:27:35.679
<v Speaker 1>make sure that the end user could actually watch a

0:27:35.760 --> 0:27:39.240
<v Speaker 1>video without too many interruptions or sudden dips and image

0:27:39.240 --> 0:27:41.760
<v Speaker 1>and audio quality. Keeping in mind that even in two

0:27:41.800 --> 0:27:43.479
<v Speaker 1>thousand and seven and two thousand and eight when this

0:27:43.560 --> 0:27:47.040
<v Speaker 1>was launching, broadband internet speeds still were not you know,

0:27:47.200 --> 0:27:50.440
<v Speaker 1>universal by any stretch of the imagination. They had also

0:27:50.520 --> 0:27:56.040
<v Speaker 1>gone through all the different phases of design, prototyping, building

0:27:56.040 --> 0:28:00.720
<v Speaker 1>out various production early production models, and testing them. It

0:28:00.800 --> 0:28:04.000
<v Speaker 1>really had gone pretty darn far. I mean they were

0:28:04.040 --> 0:28:06.440
<v Speaker 1>almost at the stage where they could go into full

0:28:06.480 --> 0:28:10.000
<v Speaker 1>on production when Hastings decided to pull the plug on

0:28:10.040 --> 0:28:14.160
<v Speaker 1>the project, but that work would not go to waste. Instead,

0:28:14.560 --> 0:28:19.520
<v Speaker 1>Hastings chose to spin off this development back to Woods company.

0:28:19.760 --> 0:28:24.800
<v Speaker 1>Roku now would had been an integral part of developing

0:28:24.840 --> 0:28:28.680
<v Speaker 1>this technology, so this wasn't exactly a gift. He had

0:28:28.720 --> 0:28:32.080
<v Speaker 1>played an important role in making it happen, so this

0:28:32.160 --> 0:28:34.800
<v Speaker 1>was a savvy move to save all of that work

0:28:35.200 --> 0:28:38.560
<v Speaker 1>and to leverage it in a different way. Netflix would

0:28:38.600 --> 0:28:41.920
<v Speaker 1>be one of many services that the Roku player would

0:28:41.920 --> 0:28:45.480
<v Speaker 1>be able to access. It gave Netflix a prominent way

0:28:45.520 --> 0:28:48.160
<v Speaker 1>to be a part of a new type of hardware

0:28:48.560 --> 0:28:52.200
<v Speaker 1>without the company appearing to horn in on hardware partners.

0:28:52.720 --> 0:28:56.080
<v Speaker 1>It also meant Netflix was free to license tech out

0:28:56.120 --> 0:29:00.400
<v Speaker 1>to other hardware companies and not create a possible conflicked

0:29:00.760 --> 0:29:03.000
<v Speaker 1>as would put it. Ad meant that the company wasn't

0:29:03.040 --> 0:29:06.160
<v Speaker 1>faced with questions like should we make decisions based on

0:29:06.240 --> 0:29:09.680
<v Speaker 1>what's best for licensing or what's best for our own hardware.

0:29:10.200 --> 0:29:13.520
<v Speaker 1>The Roku player would launch in two thousand and eight.

0:29:13.800 --> 0:29:15.640
<v Speaker 1>I'll talk about that more in just a second, but

0:29:15.720 --> 0:29:26.080
<v Speaker 1>first let's take another quick break. All right back to

0:29:26.240 --> 0:29:29.320
<v Speaker 1>late two thousand seven. That's the same year that A

0:29:29.440 --> 0:29:35.960
<v Speaker 1>O L Comcast MSN Yahoo, MySpace, remember when my Space

0:29:36.000 --> 0:29:39.960
<v Speaker 1>was a thing and Facebook created a joint venture called

0:29:40.160 --> 0:29:44.680
<v Speaker 1>Hulu dot Com. The rise of Netflix was making some

0:29:44.800 --> 0:29:49.480
<v Speaker 1>media companies a little nervous. No One, and by no one,

0:29:49.560 --> 0:29:52.920
<v Speaker 1>I mean none of these media companies really liked the

0:29:52.960 --> 0:29:57.320
<v Speaker 1>idea of Netflix becoming the dominant provider of online streaming media,

0:29:57.440 --> 0:30:00.080
<v Speaker 1>because then it would be able to dictate terms to

0:30:00.200 --> 0:30:03.840
<v Speaker 1>everyone else. Customers might love being able to get everything

0:30:03.880 --> 0:30:07.280
<v Speaker 1>on one service, but for the media companies, that wasn't

0:30:07.320 --> 0:30:12.800
<v Speaker 1>necessarily the most advantageous arrangement. So Fox and NBC quickly

0:30:12.880 --> 0:30:15.800
<v Speaker 1>signed on with Hulu to provide content to the service.

0:30:16.200 --> 0:30:20.080
<v Speaker 1>Hulu dot Com would launch on March twelve, two thousand eight.

0:30:21.000 --> 0:30:22.880
<v Speaker 1>Back in two thousand and seven, again, there was a

0:30:22.920 --> 0:30:27.360
<v Speaker 1>company that was called Voo Doo vu Du that released

0:30:27.400 --> 0:30:30.480
<v Speaker 1>its own media player. The media player had the sexy

0:30:30.600 --> 0:30:34.840
<v Speaker 1>name of b X one hundred. Now, according to c net,

0:30:35.200 --> 0:30:39.400
<v Speaker 1>it was the quote first real internet video on demand

0:30:39.480 --> 0:30:43.080
<v Speaker 1>box worthy of the name end quote. Now. To use

0:30:43.120 --> 0:30:46.520
<v Speaker 1>the box, you would purchase or rent video. Using the

0:30:46.560 --> 0:30:51.480
<v Speaker 1>Voodoo service, you could order programs on screen, which differentiated

0:30:51.520 --> 0:30:54.200
<v Speaker 1>it from the early Apple TV. Remember you had to

0:30:54.200 --> 0:30:58.200
<v Speaker 1>have a sinc computer to send stuff to the first

0:30:58.520 --> 0:31:01.000
<v Speaker 1>generation Apple TV, and it had to be on the

0:31:01.040 --> 0:31:04.640
<v Speaker 1>same network as the Apple TV was. The Voodoo b

0:31:04.920 --> 0:31:08.720
<v Speaker 1>X one hundred sported a two hundred fifty gigabyte hard drive,

0:31:09.080 --> 0:31:11.480
<v Speaker 1>which should be a dead giveaway that this was not

0:31:11.720 --> 0:31:15.080
<v Speaker 1>a streaming box. Now, this was a device that was

0:31:15.120 --> 0:31:18.280
<v Speaker 1>meant to store videos on an internal hard drive for

0:31:18.320 --> 0:31:22.000
<v Speaker 1>you to watch later, so you were effectively downloading movies

0:31:22.040 --> 0:31:24.719
<v Speaker 1>to the box. To watch, users would have to connect

0:31:24.880 --> 0:31:27.840
<v Speaker 1>an Ethernet cable to the Voodoo box. There was no

0:31:27.960 --> 0:31:31.200
<v Speaker 1>built in WiFi support, though you could get an add

0:31:31.240 --> 0:31:35.040
<v Speaker 1>on kit that would kind of create a WiFi bridge.

0:31:35.440 --> 0:31:37.920
<v Speaker 1>The player had several options when it came to connecting

0:31:37.920 --> 0:31:40.120
<v Speaker 1>to a television, though the preferred one was with an

0:31:40.200 --> 0:31:43.360
<v Speaker 1>HDMI cable because that would serve as a conduit for

0:31:43.440 --> 0:31:48.080
<v Speaker 1>both high definition video and digital audio signals. Still, while

0:31:48.200 --> 0:31:51.800
<v Speaker 1>this wasn't early Internet TV box, it wasn't really for

0:31:51.880 --> 0:31:56.160
<v Speaker 1>streaming media in the strictest sense. In May two eight,

0:31:56.640 --> 0:32:00.440
<v Speaker 1>Roku would launch its Media player, and at that point

0:32:00.480 --> 0:32:04.520
<v Speaker 1>it was essentially a Netflix set top box. It retailed

0:32:04.520 --> 0:32:08.240
<v Speaker 1>for nine and it had no monthly fee, so you

0:32:08.240 --> 0:32:10.720
<v Speaker 1>didn't have to have a subscription to use the Roku.

0:32:10.800 --> 0:32:14.800
<v Speaker 1>So a Netflix customer could buy this box for one dollars,

0:32:15.320 --> 0:32:17.840
<v Speaker 1>then they bring it home connected to their home network,

0:32:18.120 --> 0:32:21.560
<v Speaker 1>connected to their television, and then after a brief set

0:32:21.640 --> 0:32:25.000
<v Speaker 1>up process, they could link it with their existing Netflix

0:32:25.040 --> 0:32:29.040
<v Speaker 1>account and as long as they maintained that Netflix subscription,

0:32:29.240 --> 0:32:32.640
<v Speaker 1>the service would work. Netflix boasted a library of about

0:32:32.840 --> 0:32:36.720
<v Speaker 1>one hundred thousand DVD titles at that time, but only

0:32:36.760 --> 0:32:41.080
<v Speaker 1>about ten of that library was available for streaming. That

0:32:41.160 --> 0:32:44.960
<v Speaker 1>was due to the complicated licensing issues that media companies

0:32:45.240 --> 0:32:47.800
<v Speaker 1>always have in place, but that early version of the

0:32:47.880 --> 0:32:52.120
<v Speaker 1>Roku was essentially limited to just Netflix. Later updates to

0:32:52.160 --> 0:32:55.240
<v Speaker 1>the service and to the hardware would open up compatibility

0:32:55.360 --> 0:32:59.800
<v Speaker 1>with numerous services, including stuff like YouTube and Amazon Video,

0:32:59.840 --> 0:33:04.080
<v Speaker 1>among others. Speaking of Amazon Video, two thousand eight was

0:33:04.120 --> 0:33:09.840
<v Speaker 1>when Amazon renamed Unboxed as Amazon Video on Demand. They

0:33:09.840 --> 0:33:12.760
<v Speaker 1>would stick with that name until two thousand eleven, when

0:33:12.760 --> 0:33:15.680
<v Speaker 1>they'd rename it again. This time they called it Amazon

0:33:15.840 --> 0:33:18.640
<v Speaker 1>Instant Video. This would be about the time when they

0:33:18.680 --> 0:33:23.120
<v Speaker 1>started to allow streaming, not just downloads. In two thousand fifteen,

0:33:23.480 --> 0:33:27.400
<v Speaker 1>it would get renamed again and would become Amazon Video,

0:33:27.480 --> 0:33:30.920
<v Speaker 1>and in two thousand eighteen, it would become Prime Video.

0:33:31.240 --> 0:33:33.960
<v Speaker 1>Amazon likes to thumb it's knows that the common wisdom

0:33:34.040 --> 0:33:36.719
<v Speaker 1>that changing the name of a product too many times

0:33:36.760 --> 0:33:40.800
<v Speaker 1>creates confusion. I guess now. It really wasn't until eleven,

0:33:40.920 --> 0:33:44.200
<v Speaker 1>with the rebranding of Amazon Instant Video, that the company

0:33:44.240 --> 0:33:48.000
<v Speaker 1>began to push streaming along with the concept of downloading videos,

0:33:48.160 --> 0:33:52.720
<v Speaker 1>and eventually they moved away from downloading entirely. They focused

0:33:52.840 --> 0:33:56.800
<v Speaker 1>solely on delivering digital video via streaming, so you had

0:33:56.840 --> 0:34:00.000
<v Speaker 1>to have a persistent Internet connection to watch these movies.

0:34:00.440 --> 0:34:02.640
<v Speaker 1>Now there are a couple of ways you can still

0:34:02.720 --> 0:34:05.760
<v Speaker 1>download a digital video, but you have to do it

0:34:05.840 --> 0:34:08.799
<v Speaker 1>onto something like a fire tablet or an Android or

0:34:08.800 --> 0:34:14.080
<v Speaker 1>iOS device. The big streaming services now included Netflix, Hulu,

0:34:14.200 --> 0:34:18.640
<v Speaker 1>and Amazon, but lots of others would follow, like HBO now,

0:34:19.160 --> 0:34:24.400
<v Speaker 1>CBS All Access, brit Box for British shows, ESPN Plus,

0:34:24.760 --> 0:34:27.239
<v Speaker 1>Disney Plus which is just about the debut as I

0:34:27.280 --> 0:34:29.680
<v Speaker 1>record this episode and will be live by the time

0:34:29.719 --> 0:34:33.400
<v Speaker 1>this episode goes live, I believe YouTube tv also launched,

0:34:33.760 --> 0:34:36.560
<v Speaker 1>and services for video game consoles like Xbox One and

0:34:36.600 --> 0:34:42.279
<v Speaker 1>the PlayStation consoles also had online streaming options, but that's

0:34:42.320 --> 0:34:45.040
<v Speaker 1>just the services and we're really here to talk also

0:34:45.080 --> 0:34:48.200
<v Speaker 1>about the hardware, like the Roku. So what are the

0:34:48.239 --> 0:34:50.759
<v Speaker 1>options if you want to hook up a set top

0:34:50.800 --> 0:34:54.480
<v Speaker 1>box to your television in order to watch online content,

0:34:55.000 --> 0:34:57.279
<v Speaker 1>You've got a whole bunch of them. There are the

0:34:57.360 --> 0:35:01.320
<v Speaker 1>video game consoles. That's a great option. The latest versions

0:35:01.320 --> 0:35:04.600
<v Speaker 1>can support ultra high definition video content, which is great

0:35:04.640 --> 0:35:07.120
<v Speaker 1>if you have a four K television. They also tend

0:35:07.160 --> 0:35:11.239
<v Speaker 1>to have support for just about all streaming services. Netflix

0:35:11.320 --> 0:35:13.319
<v Speaker 1>led the way on that front because they made sure

0:35:13.360 --> 0:35:15.520
<v Speaker 1>that they could be included on all types of hardware,

0:35:15.800 --> 0:35:18.759
<v Speaker 1>and a lot of other services followed suit. It's not

0:35:18.800 --> 0:35:21.920
<v Speaker 1>the universal truth, however. You might find that some services

0:35:22.400 --> 0:35:26.040
<v Speaker 1>are only on one but not the other, particularly the

0:35:26.080 --> 0:35:29.960
<v Speaker 1>ones that were made specifically for that console. Obviously, you're

0:35:29.960 --> 0:35:32.799
<v Speaker 1>not going to find the PlayStation View Network on the

0:35:32.960 --> 0:35:36.080
<v Speaker 1>Xbox console, for example, But on top of the consoles,

0:35:36.520 --> 0:35:39.600
<v Speaker 1>you've got lots of other options. For one thing, Most

0:35:39.640 --> 0:35:42.600
<v Speaker 1>Blu ray players these days have at least some support

0:35:42.640 --> 0:35:45.920
<v Speaker 1>for online streaming services. The very first Blu ray player

0:35:46.000 --> 0:35:48.319
<v Speaker 1>launched in the United States did not do that. It

0:35:48.480 --> 0:35:51.279
<v Speaker 1>lacked internet connectivity. There was no Ethernet port, and there

0:35:51.320 --> 0:35:54.360
<v Speaker 1>was no WiFi, but lots of the Blu ray players

0:35:54.360 --> 0:35:59.040
<v Speaker 1>that followed could connect either via WiFi or Ethernet, and

0:35:59.080 --> 0:36:01.879
<v Speaker 1>the original intent for that was to create the opportunity

0:36:02.120 --> 0:36:05.360
<v Speaker 1>for media companies to enhance the features of a physical

0:36:05.440 --> 0:36:08.919
<v Speaker 1>disc with additional online content. So let's say you bought

0:36:08.920 --> 0:36:11.440
<v Speaker 1>a Blu Ray version of Oh I don't know, um

0:36:12.800 --> 0:36:16.319
<v Speaker 1>Berry Gordon's the Last Dragon, Well, you might discover that

0:36:16.360 --> 0:36:19.920
<v Speaker 1>because of internet connectivity, you also have access to additional

0:36:19.960 --> 0:36:22.880
<v Speaker 1>features that are not actually found on the disc itself.

0:36:23.239 --> 0:36:25.759
<v Speaker 1>But beyond this use case, a lot of companies began

0:36:25.800 --> 0:36:29.759
<v Speaker 1>to include support for various online streaming services into Blu

0:36:29.880 --> 0:36:32.560
<v Speaker 1>ray players, which turned the Blu ray players into more

0:36:32.560 --> 0:36:36.040
<v Speaker 1>of a general media center, not just a disc player.

0:36:36.680 --> 0:36:39.440
<v Speaker 1>Then there are the dedicated devices that you connect to

0:36:39.480 --> 0:36:43.799
<v Speaker 1>your TV and are all about delivering streaming content. There's

0:36:43.840 --> 0:36:47.040
<v Speaker 1>the various versions of Roku, like the Roku Express, the

0:36:47.120 --> 0:36:50.839
<v Speaker 1>Roku Premier, plus the Roku Ultra devices. All of those

0:36:50.840 --> 0:36:55.400
<v Speaker 1>plug into support on a modern television. There's Google's Chrome Cast,

0:36:55.560 --> 0:36:58.000
<v Speaker 1>which lets you stream from a network to computer to

0:36:58.040 --> 0:37:01.320
<v Speaker 1>the television, very much like the Apple TV product did.

0:37:01.600 --> 0:37:05.000
<v Speaker 1>There's the Video Shield TV with built in support for

0:37:05.040 --> 0:37:09.800
<v Speaker 1>Google Assistant. Amazon has the Fire family of streaming devices,

0:37:10.120 --> 0:37:13.200
<v Speaker 1>so these are the really big contenders in that space.

0:37:13.680 --> 0:37:17.480
<v Speaker 1>From a technological standpoint, they're fairly similar. Most of the

0:37:17.480 --> 0:37:21.520
<v Speaker 1>options today can not only push out ultra high definition video,

0:37:21.719 --> 0:37:24.640
<v Speaker 1>assuming you have an Internet connection that can accommodate that,

0:37:25.160 --> 0:37:28.919
<v Speaker 1>most of them are also compatible with HDR, or high

0:37:29.040 --> 0:37:32.160
<v Speaker 1>dynamic range that describes the range of color in a

0:37:32.320 --> 0:37:36.279
<v Speaker 1>video feed. So that's both sharpness with the resolution and

0:37:36.360 --> 0:37:41.279
<v Speaker 1>color representation with HDR. The differences mostly boiled down to

0:37:41.640 --> 0:37:45.920
<v Speaker 1>two really big things, how you interface with the underlying

0:37:45.960 --> 0:37:47.960
<v Speaker 1>system so that you can get to the stuff you

0:37:48.000 --> 0:37:51.920
<v Speaker 1>want to see, and which streaming services are supported on

0:37:52.040 --> 0:37:56.279
<v Speaker 1>each device. But otherwise they're really not that different. There

0:37:56.320 --> 0:38:00.080
<v Speaker 1>are proprietary elements to each one, but ultimately all of

0:38:00.120 --> 0:38:03.360
<v Speaker 1>them are geared toward pulling data down from the Internet

0:38:03.680 --> 0:38:06.040
<v Speaker 1>and feeding it to your television and a signal that

0:38:06.120 --> 0:38:09.880
<v Speaker 1>the TV quote unquote understands. Now, in my personal experience,

0:38:10.239 --> 0:38:12.880
<v Speaker 1>the thing that matters the most to me is the

0:38:13.000 --> 0:38:17.440
<v Speaker 1>UI for the device itself doesn't make sense. Can you

0:38:17.600 --> 0:38:19.920
<v Speaker 1>find the stuff you want to look for if you

0:38:20.000 --> 0:38:23.680
<v Speaker 1>have to type in a title? Is that easy to do?

0:38:24.040 --> 0:38:27.000
<v Speaker 1>Is it responsive. Is there a delay between when I

0:38:27.080 --> 0:38:30.080
<v Speaker 1>hit a command and when something actually happens, because if

0:38:30.080 --> 0:38:33.719
<v Speaker 1>there is, I hate that. Delays make it really hard

0:38:33.760 --> 0:38:36.480
<v Speaker 1>to tell if a device has registered a command. I

0:38:36.520 --> 0:38:39.120
<v Speaker 1>can't tell you how many times I've sent back to

0:38:39.200 --> 0:38:42.960
<v Speaker 1>back commands to play and then pause because I didn't

0:38:43.000 --> 0:38:46.600
<v Speaker 1>realize the device had already registered the play command, so

0:38:46.640 --> 0:38:51.600
<v Speaker 1>I pushed it again and then everything just starts, stops,

0:38:51.640 --> 0:38:54.640
<v Speaker 1>and jutters, and I hate it. It really gets my

0:38:54.719 --> 0:38:58.400
<v Speaker 1>biscuits and burning. And of course, a lot of television

0:38:58.400 --> 0:39:02.359
<v Speaker 1>manufacturers are build again a native capability to access these

0:39:02.360 --> 0:39:05.440
<v Speaker 1>sorts of services. Many of you out there probably have

0:39:05.640 --> 0:39:09.040
<v Speaker 1>televisions that already supports some or all of the streaming

0:39:09.080 --> 0:39:12.440
<v Speaker 1>services that I've mentioned on here. The television connects to

0:39:12.480 --> 0:39:15.279
<v Speaker 1>your in home network, either hardlined by the net or

0:39:15.280 --> 0:39:18.680
<v Speaker 1>through WiFi, and there's no need for any additional hardware

0:39:18.800 --> 0:39:21.640
<v Speaker 1>to get access to stuff like Netflix or Amazon Video.

0:39:21.680 --> 0:39:23.800
<v Speaker 1>You just have to link it to your existing account.

0:39:24.360 --> 0:39:27.600
<v Speaker 1>You're dependent upon the UI designed for that particular television,

0:39:28.120 --> 0:39:31.680
<v Speaker 1>which sometimes can be a bit lacking. You might be

0:39:31.719 --> 0:39:35.120
<v Speaker 1>surprised to hear that, despite the fact that I host

0:39:35.160 --> 0:39:38.280
<v Speaker 1>a technology podcast, I do not have the most cutting

0:39:38.360 --> 0:39:42.160
<v Speaker 1>edge versions of these technologies in my own home. For

0:39:42.239 --> 0:39:45.799
<v Speaker 1>one thing, I don't own a four K television, so

0:39:46.120 --> 0:39:50.279
<v Speaker 1>stuff like Ultra high definition and HDR support would be

0:39:50.320 --> 0:39:53.200
<v Speaker 1>wasted on me because my television isn't capable of taking

0:39:53.200 --> 0:39:56.440
<v Speaker 1>advantage of those features. So before I did that, I

0:39:56.440 --> 0:39:59.040
<v Speaker 1>would need to go out and buy a brand new television,

0:39:59.239 --> 0:40:02.359
<v Speaker 1>and believe me, I'm tempted to do it. But at

0:40:02.400 --> 0:40:05.560
<v Speaker 1>the same time, my current television still works just fine.

0:40:06.000 --> 0:40:08.440
<v Speaker 1>It just can't support anything beyond good old ten A

0:40:08.480 --> 0:40:13.200
<v Speaker 1>D resolution, so it's not the best TV, but it works.

0:40:13.360 --> 0:40:15.319
<v Speaker 1>So it's hard for me to justify going out and

0:40:15.360 --> 0:40:18.480
<v Speaker 1>buying a new one, especially since I'm married to a

0:40:18.520 --> 0:40:21.640
<v Speaker 1>woman who's extremely practical. Because trust me, there have been

0:40:21.680 --> 0:40:24.200
<v Speaker 1>moments of weakness where I've almost ordered a new four

0:40:24.280 --> 0:40:28.759
<v Speaker 1>K TV, but fear for my own personal safety has

0:40:28.800 --> 0:40:32.399
<v Speaker 1>outweighed my desire to have the new shiny thing now.

0:40:32.440 --> 0:40:35.000
<v Speaker 1>I have owned a Roku Player in the past. I

0:40:35.160 --> 0:40:37.640
<v Speaker 1>very much liked it, though it was pretty bare bones

0:40:37.680 --> 0:40:39.960
<v Speaker 1>on features and it was a little bit of a

0:40:40.040 --> 0:40:43.080
<v Speaker 1>chore to navigate using the stubby little remote control that

0:40:43.160 --> 0:40:46.440
<v Speaker 1>came with it. But finally I could watch online content

0:40:46.560 --> 0:40:49.759
<v Speaker 1>on my television without much trouble, which was awesome. Now

0:40:49.800 --> 0:40:52.320
<v Speaker 1>these days, I have a Chrome Cast, but it's a

0:40:52.440 --> 0:40:56.600
<v Speaker 1>first generation Chrome Cast, so it's the one that originally

0:40:56.600 --> 0:40:59.560
<v Speaker 1>came out from Google and has just those features. I

0:40:59.600 --> 0:41:02.359
<v Speaker 1>also have a first generation Xbox one and a first

0:41:02.360 --> 0:41:05.880
<v Speaker 1>generation PlayStation four, so these are all capable of streaming

0:41:05.880 --> 0:41:09.400
<v Speaker 1>media to my television, but they lack the more recent

0:41:09.440 --> 0:41:13.360
<v Speaker 1>capabilities of Ultra high definition and HDR. In fact, these days,

0:41:13.880 --> 0:41:16.520
<v Speaker 1>it's the only way I do watch television is through

0:41:16.560 --> 0:41:20.640
<v Speaker 1>these streaming services and these devices. I haven't turned on

0:41:20.760 --> 0:41:25.439
<v Speaker 1>cable or even broadcast television in a couple of years now.

0:41:25.440 --> 0:41:28.239
<v Speaker 1>Maybe in a future episode, I'll do a full rundown

0:41:28.480 --> 0:41:31.560
<v Speaker 1>on the various streaming services that are out there, where

0:41:31.600 --> 0:41:34.080
<v Speaker 1>they came from, and how they're competing with each other.

0:41:34.360 --> 0:41:36.880
<v Speaker 1>I think there's also a very valuable conversation to have

0:41:36.960 --> 0:41:40.959
<v Speaker 1>about consumer frustration. One of the big attractive things about

0:41:41.040 --> 0:41:45.200
<v Speaker 1>streaming was this idea of cutting the cord for cable companies.

0:41:45.440 --> 0:41:47.279
<v Speaker 1>You'd be able to get what you wanted and you

0:41:47.280 --> 0:41:50.319
<v Speaker 1>could ignore the rest of the junk. But we now

0:41:50.400 --> 0:41:54.480
<v Speaker 1>have a very fractured online media landscape out there, with

0:41:54.640 --> 0:41:58.799
<v Speaker 1>some shows and films that are exclusive to certain platforms,

0:41:58.960 --> 0:42:02.920
<v Speaker 1>which means unless you subscribe to multiple services, you're probably

0:42:02.960 --> 0:42:06.000
<v Speaker 1>missing out on something you really want to see. The

0:42:06.040 --> 0:42:09.759
<v Speaker 1>headaches of streaming are rapidly approaching the same levels of

0:42:09.800 --> 0:42:13.480
<v Speaker 1>frustration that you had when you subscribe to an enormous

0:42:13.520 --> 0:42:16.200
<v Speaker 1>cable package in which you might only care about a

0:42:16.239 --> 0:42:20.000
<v Speaker 1>half dozen channels. But that's a topic for another time.

0:42:20.360 --> 0:42:23.160
<v Speaker 1>If you guys have suggestions for future episodes of tech Stuff,

0:42:23.480 --> 0:42:26.359
<v Speaker 1>send me a message the email addresses tech Stuff at

0:42:26.400 --> 0:42:28.839
<v Speaker 1>how stuff works dot com, or drop me a line

0:42:28.880 --> 0:42:30.879
<v Speaker 1>on Facebook or Twitter. The handle for both of those

0:42:31.000 --> 0:42:34.520
<v Speaker 1>is text Stuff hs W. Don't forget to visit our

0:42:34.560 --> 0:42:37.920
<v Speaker 1>website that's tech stuff podcast dot com. You'll find a

0:42:38.000 --> 0:42:40.840
<v Speaker 1>link to the archive of every tech stuff episode that

0:42:40.880 --> 0:42:43.520
<v Speaker 1>has ever been recorded. You also find a link to

0:42:43.520 --> 0:42:46.920
<v Speaker 1>our online store where you can make a purchase and

0:42:46.960 --> 0:42:49.640
<v Speaker 1>it goes to help our show, and we greatly appreciate it,

0:42:50.000 --> 0:42:58.000
<v Speaker 1>and I'll talk to you again really soon. Text Stuff

0:42:58.040 --> 0:43:00.360
<v Speaker 1>is a production of I Heart Radio's How Stuff Works.

0:43:00.520 --> 0:43:03.360
<v Speaker 1>For more podcasts from I heart Radio, visit the i

0:43:03.440 --> 0:43:06.680
<v Speaker 1>heart Radio app, Apple Podcasts, or wherever you listen to

0:43:06.760 --> 0:43:12.200
<v Speaker 1>your favorite shows, h