WEBVTT - TechStuff Tackles the Amazon Cloud Player

0:00:00.280 --> 0:00:02.840
<v Speaker 1>Brought to you by the reinvented two thousand twelve camera.

0:00:03.160 --> 0:00:08.920
<v Speaker 1>It's ready. Are you get in touch with technology? With

0:00:09.039 --> 0:00:17.920
<v Speaker 1>tech stuff from how stuff works dot com. Hello again, everyone,

0:00:17.960 --> 0:00:20.799
<v Speaker 1>Welcome to tex stuff. My name is Chris Polette and

0:00:20.880 --> 0:00:22.640
<v Speaker 1>I am an editor at how stuff works dot com.

0:00:22.680 --> 0:00:26.000
<v Speaker 1>Sitting across from me as always a senior writer Jonathan Strickland.

0:00:26.160 --> 0:00:29.520
<v Speaker 1>Nobody comes to visit me in my little cloud. I

0:00:29.560 --> 0:00:34.400
<v Speaker 1>don't know why. Maybe because I'm cutting muffins of all

0:00:34.479 --> 0:00:38.840
<v Speaker 1>the songs. You chose that we're talking about clouds. That's true.

0:00:39.680 --> 0:00:43.840
<v Speaker 1>We were going to talk about Amazon's much heralded new

0:00:44.000 --> 0:00:50.239
<v Speaker 1>cloud service because it's completely unlike everything else that came

0:00:50.240 --> 0:00:52.960
<v Speaker 1>out that's a cloud service. Yes, except well there is

0:00:53.000 --> 0:00:56.560
<v Speaker 1>there is one unique element, or at least it's it's new.

0:00:57.120 --> 0:00:59.320
<v Speaker 1>It's new enough to talk about, right, It's not like

0:00:59.400 --> 0:01:02.960
<v Speaker 1>it's something it is, uh that also has been done

0:01:02.960 --> 0:01:07.000
<v Speaker 1>over and over again. Actually, I think the thing is

0:01:07.920 --> 0:01:10.360
<v Speaker 1>I wanted to talk about this because so many people

0:01:10.400 --> 0:01:14.320
<v Speaker 1>are talking about it, um because it isn't for the

0:01:14.319 --> 0:01:18.279
<v Speaker 1>most part, all that groundbreaking in a lot of ways,

0:01:18.600 --> 0:01:20.920
<v Speaker 1>but people are still talking about it as though it

0:01:20.959 --> 0:01:23.160
<v Speaker 1>were a revolutionary thing and I think in a way,

0:01:23.760 --> 0:01:26.280
<v Speaker 1>it's the mindset behind it and the fact and that

0:01:26.360 --> 0:01:29.000
<v Speaker 1>one that one special instance, and if you're if you're

0:01:29.000 --> 0:01:30.960
<v Speaker 1>new to what we're talking about and have absolutely no

0:01:31.080 --> 0:01:34.360
<v Speaker 1>idea what we're prattling on about this point, it's called

0:01:35.160 --> 0:01:38.880
<v Speaker 1>cloud drive, and that's a a cloud based service. And

0:01:38.959 --> 0:01:41.399
<v Speaker 1>we talk about cloud we're talking about internet storage. So

0:01:42.680 --> 0:01:45.560
<v Speaker 1>rather than using the hard drive on your computer or

0:01:45.600 --> 0:01:47.640
<v Speaker 1>an external hard drive that you plug in your computer

0:01:47.800 --> 0:01:50.840
<v Speaker 1>or maybe even on your network at home, the files

0:01:50.880 --> 0:01:54.200
<v Speaker 1>that you save to this service are going across the

0:01:54.240 --> 0:01:58.880
<v Speaker 1>Internet to be stored on in this case, Amazon's hard

0:01:58.960 --> 0:02:01.840
<v Speaker 1>drives computer. And the reason you would do this, there's

0:02:01.880 --> 0:02:04.760
<v Speaker 1>actually several reasons. One would be that, well, you know,

0:02:04.800 --> 0:02:07.840
<v Speaker 1>there's most of us just have so much storage, and

0:02:08.040 --> 0:02:11.320
<v Speaker 1>you start to accumulate enough stuff. You have, as George

0:02:11.320 --> 0:02:14.160
<v Speaker 1>Carlin would say, not enough places to put your stuff,

0:02:14.720 --> 0:02:17.040
<v Speaker 1>So you gotta find more places for all the stuff

0:02:17.040 --> 0:02:20.240
<v Speaker 1>you got, and uh, that's a great routine. And uh,

0:02:20.240 --> 0:02:23.359
<v Speaker 1>and that cloud storage is a great way of finding

0:02:23.440 --> 0:02:26.360
<v Speaker 1>places to put your stuff. So you are effectively putting

0:02:26.360 --> 0:02:29.200
<v Speaker 1>your stuff in someone else's house, that's one thing. So

0:02:29.240 --> 0:02:32.519
<v Speaker 1>you're getting your you're able to offload storage. But another

0:02:32.560 --> 0:02:35.880
<v Speaker 1>reason you might like it is because, unlike some of us,

0:02:36.680 --> 0:02:40.880
<v Speaker 1>these cloud storage companies tend to have lots of of

0:02:41.040 --> 0:02:45.639
<v Speaker 1>backups and redundancy built into their systems so that if

0:02:45.680 --> 0:02:48.799
<v Speaker 1>something goes wrong, you don't lose your data. Because if

0:02:48.840 --> 0:02:51.960
<v Speaker 1>my hard drive crashes, I lose that stuff. Right, anything

0:02:51.960 --> 0:02:54.919
<v Speaker 1>that's stored locally on that hard drive, I could potentially

0:02:55.160 --> 0:03:01.840
<v Speaker 1>lose forever. That's right. There's also leads us to the downsides.

0:03:02.320 --> 0:03:05.000
<v Speaker 1>And if you have been listening to tech stuff for

0:03:05.120 --> 0:03:07.880
<v Speaker 1>years now, you know that we when we talk about

0:03:08.080 --> 0:03:10.799
<v Speaker 1>cloud computing, in cloud storage, we were going to talk

0:03:10.840 --> 0:03:13.880
<v Speaker 1>about privacy. When you have multiple copies of your information

0:03:14.600 --> 0:03:19.239
<v Speaker 1>stored on someone else's computers, um, then there is the

0:03:19.280 --> 0:03:23.200
<v Speaker 1>possibility that that information could fall into someone else's hands

0:03:23.720 --> 0:03:26.680
<v Speaker 1>and if it's not encrypted, could be or or not

0:03:26.760 --> 0:03:30.400
<v Speaker 1>encrypted well enough, um or if the person is really

0:03:30.440 --> 0:03:34.160
<v Speaker 1>really good at cryptography. Yeah, and we're talking crazy good

0:03:34.400 --> 0:03:36.840
<v Speaker 1>because most of the cryptography that's been use out there

0:03:36.960 --> 0:03:40.240
<v Speaker 1>is is strong enough to defeat all but let's say

0:03:40.440 --> 0:03:45.120
<v Speaker 1>a government's uh resources, Yeah, the most the most sophisticated

0:03:45.920 --> 0:03:49.440
<v Speaker 1>uh crackers. But yeah, I mean, if if you're storing

0:03:49.480 --> 0:03:52.200
<v Speaker 1>this information out there and it's not secure enough. There's

0:03:52.200 --> 0:03:56.720
<v Speaker 1>a possibility that you could put your financial records, or

0:03:57.240 --> 0:04:02.520
<v Speaker 1>genealogical information or kids photos are all kinds of stuff

0:04:02.560 --> 0:04:05.520
<v Speaker 1>that you probably don't want everyone else to have in

0:04:05.560 --> 0:04:07.640
<v Speaker 1>the hands of someone else, and that that is why

0:04:07.680 --> 0:04:11.800
<v Speaker 1>some people avoid using cloud storage. And there's also the

0:04:11.880 --> 0:04:14.240
<v Speaker 1>chance that there's also the thought that if there were

0:04:14.280 --> 0:04:17.680
<v Speaker 1>any loss of connectivity for some reason, you would then

0:04:17.800 --> 0:04:20.599
<v Speaker 1>have you wouldn't have have access to your data anymore.

0:04:20.760 --> 0:04:22.919
<v Speaker 1>I recently had this problem. It's a big pain in

0:04:22.920 --> 0:04:25.200
<v Speaker 1>the neck. Yeah. So if you use cloud storage for

0:04:25.279 --> 0:04:28.640
<v Speaker 1>lots of your stuff and you for some reason, maybe

0:04:28.680 --> 0:04:31.720
<v Speaker 1>you forgot to pay a bill, or maybe the actual

0:04:31.760 --> 0:04:35.080
<v Speaker 1>internet service provider has suffered some sort of failure and

0:04:35.160 --> 0:04:37.240
<v Speaker 1>for some reason or another you're not able to access

0:04:37.240 --> 0:04:39.359
<v Speaker 1>the Internet, well, then you're not able to get to

0:04:39.440 --> 0:04:42.960
<v Speaker 1>all of your files because they're stored remotely on some

0:04:43.000 --> 0:04:48.520
<v Speaker 1>other server. Right now, for consumers, that is you and me,

0:04:48.640 --> 0:04:52.880
<v Speaker 1>or at least most of us. Um we already have

0:04:53.320 --> 0:04:58.080
<v Speaker 1>lots of really well known and pretty well regarded services,

0:04:58.120 --> 0:05:01.719
<v Speaker 1>people like dropbox and Sugar Sinc And Box dot net,

0:05:02.480 --> 0:05:05.120
<v Speaker 1>people like even even things like Google Docs. If you're

0:05:05.160 --> 0:05:09.880
<v Speaker 1>talking about specific types of documents, spreadsheets and presentations, and

0:05:09.920 --> 0:05:13.000
<v Speaker 1>are all cloud services? Yes, and and Amazon has been

0:05:13.000 --> 0:05:16.159
<v Speaker 1>doing this too for a long time, offering uh, storage

0:05:16.160 --> 0:05:21.440
<v Speaker 1>solutions primarily to two companies corporate customers. Yeah, but this

0:05:21.480 --> 0:05:25.440
<v Speaker 1>is so you at this point you might say, so, yeah,

0:05:25.480 --> 0:05:28.760
<v Speaker 1>what what's what's so new about this? Uh, this cloud

0:05:28.839 --> 0:05:32.120
<v Speaker 1>drive allows you to store all kinds of documents. You

0:05:32.120 --> 0:05:36.200
<v Speaker 1>could put word processing files up there, anything that could

0:05:36.240 --> 0:05:40.000
<v Speaker 1>really any file format pretty much. But they really intended

0:05:40.279 --> 0:05:42.960
<v Speaker 1>to serve as a music locker. Yeah, this is the

0:05:43.000 --> 0:05:46.240
<v Speaker 1>brilliance of this system. So Amazon's had this cloud storage

0:05:46.240 --> 0:05:48.520
<v Speaker 1>in place for a couple of years. In fact, when

0:05:48.560 --> 0:05:51.480
<v Speaker 1>we started talking about cloud storage, probably two years ago

0:05:51.600 --> 0:05:54.719
<v Speaker 1>when we were first starting the podcast, Amazon was one

0:05:54.760 --> 0:05:57.560
<v Speaker 1>of the big providers that was leading the way in

0:05:57.880 --> 0:06:01.359
<v Speaker 1>cloud storage, but they had not happed into the general

0:06:01.360 --> 0:06:06.320
<v Speaker 1>consumer until they thought, why don't we combine this cloud

0:06:06.400 --> 0:06:09.720
<v Speaker 1>storage with our amazing MP three store where you can

0:06:09.760 --> 0:06:12.800
<v Speaker 1>buy m P three's from Amazon, and we can package

0:06:12.800 --> 0:06:15.080
<v Speaker 1>it in such a way that it's really attractive to

0:06:15.240 --> 0:06:18.200
<v Speaker 1>Amazon customers and make a service out of it. So

0:06:18.240 --> 0:06:21.719
<v Speaker 1>it's not just a storage service, but is some sort

0:06:21.880 --> 0:06:26.440
<v Speaker 1>of transmission service as well. And it's it's they. I mean,

0:06:26.640 --> 0:06:28.600
<v Speaker 1>you couldn't have asked them to do a better job.

0:06:28.640 --> 0:06:31.400
<v Speaker 1>They not only did they really make a big splash

0:06:31.400 --> 0:06:34.640
<v Speaker 1>in the news, they scooped other major companies that are

0:06:34.680 --> 0:06:37.159
<v Speaker 1>trying to do something similar right now. And when I

0:06:37.200 --> 0:06:41.159
<v Speaker 1>say major companies, I'm talking Google and Apple. Yes, yes,

0:06:41.960 --> 0:06:46.080
<v Speaker 1>um Now there are again other music locker sites. And

0:06:46.120 --> 0:06:50.599
<v Speaker 1>what a music locker is, um, I think primarily of

0:06:50.640 --> 0:06:54.320
<v Speaker 1>groove Shark. There are many others, but um including one

0:06:54.360 --> 0:06:59.120
<v Speaker 1>that was purchased by Apple um la la. But what

0:06:59.200 --> 0:07:01.080
<v Speaker 1>it is is you start an account. And I've I've

0:07:01.120 --> 0:07:03.320
<v Speaker 1>always been kind of weirded out by this because it

0:07:03.320 --> 0:07:06.640
<v Speaker 1>seems so like sort of a dubious uh in terms

0:07:06.680 --> 0:07:09.359
<v Speaker 1>of licensing sort of situation. You sign up for an

0:07:09.400 --> 0:07:12.720
<v Speaker 1>account with one of these services, and the service allows

0:07:12.720 --> 0:07:15.320
<v Speaker 1>you to upload your own music to the service. Now,

0:07:15.320 --> 0:07:18.280
<v Speaker 1>in the case of groove Shark, you can actually listen

0:07:18.320 --> 0:07:21.040
<v Speaker 1>to the music that other people have uploaded on the site.

0:07:21.080 --> 0:07:23.280
<v Speaker 1>And that's where it really gets kind of complicated. Well,

0:07:23.280 --> 0:07:25.480
<v Speaker 1>the artists are getting a cut, according to groove Shark,

0:07:25.960 --> 0:07:29.400
<v Speaker 1>so you know that that apparently, and they have licenses

0:07:29.440 --> 0:07:33.080
<v Speaker 1>with the major music labels. So they are are apparently okay,

0:07:33.120 --> 0:07:35.080
<v Speaker 1>but it took me a little while to go. I

0:07:35.080 --> 0:07:37.600
<v Speaker 1>am not going to get in trouble for using this site. Um,

0:07:37.640 --> 0:07:41.000
<v Speaker 1>but yeah, if you if you use Amazon's cloud drive,

0:07:41.360 --> 0:07:44.520
<v Speaker 1>you can upload music that you have purchased on encrypted

0:07:44.600 --> 0:07:47.840
<v Speaker 1>music in a c r M P three format. If

0:07:47.880 --> 0:07:51.880
<v Speaker 1>you buy music from Amazon from that MP three store

0:07:51.880 --> 0:07:53.880
<v Speaker 1>that you mentioned a moment ago, it'll go straight to

0:07:53.920 --> 0:07:55.680
<v Speaker 1>the cloud. It goes straight to the cloud and you

0:07:55.720 --> 0:07:58.040
<v Speaker 1>can you can download it, but you can also find

0:07:58.080 --> 0:08:01.320
<v Speaker 1>it in your your cloud store cloud storage. Yeah, here's

0:08:01.320 --> 0:08:03.840
<v Speaker 1>the brilliance of this. So let's say that you decided

0:08:03.880 --> 0:08:08.640
<v Speaker 1>to purchase an album from from Amazon dot com and

0:08:08.800 --> 0:08:12.000
<v Speaker 1>it goes into your cloud storage. You can download it

0:08:12.040 --> 0:08:14.160
<v Speaker 1>immediately if you want to. You can wait, you can

0:08:14.160 --> 0:08:16.160
<v Speaker 1>go download it off another computer. All you have to

0:08:16.160 --> 0:08:19.000
<v Speaker 1>do is log into your Amazon dot Com account. So

0:08:19.200 --> 0:08:21.239
<v Speaker 1>and as soon as you have an Amazon dot Com account,

0:08:21.760 --> 0:08:24.920
<v Speaker 1>you get five gigabytes of storage space and in a

0:08:24.960 --> 0:08:27.440
<v Speaker 1>cloud drive for free. Yes, just for being an Amazon

0:08:27.480 --> 0:08:29.720
<v Speaker 1>dot Com customer. You don't have to purchase anything. No

0:08:29.920 --> 0:08:32.000
<v Speaker 1>five gigs for free. If you buy an album, you

0:08:32.040 --> 0:08:34.760
<v Speaker 1>get twenty gigs for free for a full year. Yes,

0:08:35.200 --> 0:08:37.760
<v Speaker 1>and uh, all you have to do is then what

0:08:37.840 --> 0:08:39.400
<v Speaker 1>you would have to renew it from that point and

0:08:39.520 --> 0:08:43.400
<v Speaker 1>essentially Amazon charges a dollar a gig per year. Actually

0:08:43.640 --> 0:08:45.800
<v Speaker 1>is it? Do you have to buy a full album?

0:08:46.200 --> 0:08:47.679
<v Speaker 1>I think if you, I think you have to buy

0:08:47.679 --> 0:08:50.320
<v Speaker 1>a full album to get the twenty gigs. That was

0:08:50.440 --> 0:08:52.640
<v Speaker 1>very smart on their on their part, because somebody was

0:08:52.679 --> 0:08:54.600
<v Speaker 1>suggesting that you could go buy one of the sixty

0:08:54.679 --> 0:08:57.520
<v Speaker 1>nine cent songs, get twenty gigabytes for a year for

0:08:57.520 --> 0:08:59.840
<v Speaker 1>sixty cents. This is the other really cool thing about

0:08:59.840 --> 0:09:03.480
<v Speaker 1>it though, Right, Okay, so you have that five gigabytes

0:09:03.480 --> 0:09:05.480
<v Speaker 1>of space. That's a lot of space. That's up to

0:09:05.520 --> 0:09:09.480
<v Speaker 1>a thousand songs, more or less depending upon the you know,

0:09:09.600 --> 0:09:12.400
<v Speaker 1>how how high quality they are and how long the

0:09:12.440 --> 0:09:14.520
<v Speaker 1>songs are. I mean, granted, if it's meat loaf, it's

0:09:14.520 --> 0:09:17.280
<v Speaker 1>probably more like six songs. Because that dude just never

0:09:17.400 --> 0:09:21.000
<v Speaker 1>never shuts up. Man. I would do anything for love,

0:09:21.320 --> 0:09:25.640
<v Speaker 1>but I won't shut up. I love. By the way,

0:09:25.679 --> 0:09:29.400
<v Speaker 1>I was both the food item and the artist. Oh man,

0:09:29.840 --> 0:09:34.760
<v Speaker 1>so happened to Saturday night? Anyway? Yes? Sorry, I got

0:09:34.800 --> 0:09:37.520
<v Speaker 1>a little off track there. Where was I? I had

0:09:38.160 --> 0:09:40.520
<v Speaker 1>five gigabytes of storage. So you've got five gigabytes of

0:09:40.559 --> 0:09:43.080
<v Speaker 1>storage starting off for free, right, but if you buy

0:09:43.080 --> 0:09:47.439
<v Speaker 1>a song for Amazon dot Com, it doesn't count against

0:09:47.480 --> 0:09:50.360
<v Speaker 1>the five gigabytes. That's right. Yeah, any any music that

0:09:50.400 --> 0:09:53.200
<v Speaker 1>you buy from Amazon dot com. Say you have a

0:09:54.040 --> 0:09:56.560
<v Speaker 1>your your accounts empty, and you're getting ready to buy

0:09:56.600 --> 0:09:59.720
<v Speaker 1>an album. Yes, uh so you you're you're going to

0:09:59.760 --> 0:10:01.959
<v Speaker 1>get the twenty gigabytes. And let's say it's it's nice

0:10:02.040 --> 0:10:06.119
<v Speaker 1>round number that the album is a hundred fifty megabytes

0:10:06.160 --> 0:10:08.800
<v Speaker 1>worth of music. That hundred fifty megabytes does not count

0:10:08.800 --> 0:10:11.440
<v Speaker 1>toward the twenty gigabytes. That's conditioned to You can just

0:10:11.559 --> 0:10:13.840
<v Speaker 1>keep buying music from Amazon dot com and you will

0:10:13.920 --> 0:10:17.319
<v Speaker 1>never fill up that space no matter how many gigs

0:10:17.320 --> 0:10:20.120
<v Speaker 1>of music you have if you bought all right, So,

0:10:20.120 --> 0:10:23.000
<v Speaker 1>twenty gigabytes holds about four thousand songs more or less

0:10:23.080 --> 0:10:26.240
<v Speaker 1>unless it's meat loaf and already did that joke. Anyway,

0:10:26.440 --> 0:10:29.160
<v Speaker 1>So twenty gigabytes about four thousand songs. So let's say

0:10:29.160 --> 0:10:32.720
<v Speaker 1>you bought five thousand songs. You went on a spree. Okay, okay,

0:10:32.720 --> 0:10:35.160
<v Speaker 1>so you bought five thousand songs. Well, because Amazon dot

0:10:35.200 --> 0:10:38.520
<v Speaker 1>Com does not count those against your your cap. You

0:10:38.559 --> 0:10:40.480
<v Speaker 1>can have all those in your cloud drive if you

0:10:40.480 --> 0:10:43.680
<v Speaker 1>bought them all from Amazon dot Com, unless, of course,

0:10:43.920 --> 0:10:47.080
<v Speaker 1>you bought them before, right, that's a problem. If you

0:10:47.080 --> 0:10:49.400
<v Speaker 1>bought them before, then what you're doing is you're uploading

0:10:49.480 --> 0:10:52.079
<v Speaker 1>to the cloud and that does count against your cap. Yeah,

0:10:52.120 --> 0:10:53.520
<v Speaker 1>because I do have a few albums that I have

0:10:53.559 --> 0:10:57.199
<v Speaker 1>purchased from Amazon service, and I I don't get those

0:10:57.280 --> 0:11:00.760
<v Speaker 1>retroactively added to my locker with Amazon doesn't know that

0:11:00.800 --> 0:11:03.840
<v Speaker 1>necessarily that although I'm sure there's some code in there somewhere,

0:11:03.920 --> 0:11:07.240
<v Speaker 1>but Amazon does not quote unquote know that which MP

0:11:07.360 --> 0:11:10.560
<v Speaker 1>three's were ripped from the CD, which ones were purchased

0:11:10.559 --> 0:11:13.000
<v Speaker 1>through iTunes. Of course that wouldn't be an MP three necessarily,

0:11:13.040 --> 0:11:15.679
<v Speaker 1>but uh, or which ones were bought off Amazon dot

0:11:15.720 --> 0:11:19.120
<v Speaker 1>com or some other service. So you even if you

0:11:19.160 --> 0:11:22.160
<v Speaker 1>did buy other songs from Amazon dot Com before, those

0:11:22.160 --> 0:11:27.720
<v Speaker 1>are not going to be grandfathered in. So here's where

0:11:27.760 --> 0:11:33.160
<v Speaker 1>it starts to become a music specific effort, because um,

0:11:33.240 --> 0:11:36.240
<v Speaker 1>you know the services that I mentioned earlier, people like

0:11:36.360 --> 0:11:39.839
<v Speaker 1>Dropbox and box dot net and sugar Sinc. They the

0:11:40.080 --> 0:11:44.040
<v Speaker 1>basic accounts with those the free accounts generally about two

0:11:44.160 --> 0:11:47.640
<v Speaker 1>gigabytes worth the space, um, and they don't discriminate what

0:11:47.720 --> 0:11:49.520
<v Speaker 1>kind of file types you can save in their right

0:11:49.559 --> 0:11:52.720
<v Speaker 1>and and um, well i'll talk about that a little

0:11:52.720 --> 0:11:54.880
<v Speaker 1>bit more in a minute. And yes, those of you

0:11:54.880 --> 0:11:57.720
<v Speaker 1>who have accounts with Dropbox will know that if you

0:11:58.440 --> 0:12:00.360
<v Speaker 1>get other people to sign up in use your name,

0:12:00.400 --> 0:12:03.560
<v Speaker 1>than you get extra space. But yeah, starting out, you

0:12:03.600 --> 0:12:06.120
<v Speaker 1>get to two gigabytes with the space, so you're already

0:12:06.160 --> 0:12:09.280
<v Speaker 1>more than doubling that. But that this is a brilliant

0:12:09.360 --> 0:12:13.640
<v Speaker 1>marketing move for their music store because it is encouraging

0:12:13.679 --> 0:12:18.280
<v Speaker 1>you to down buy and download those uh music files

0:12:18.280 --> 0:12:21.240
<v Speaker 1>from Amazon's MP three store. Yeah, if the lower prices

0:12:21.240 --> 0:12:24.079
<v Speaker 1>weren't enough for you, then this will also help. So yeah,

0:12:24.120 --> 0:12:28.640
<v Speaker 1>that's the big that's the big differentiation there between the

0:12:28.679 --> 0:12:32.080
<v Speaker 1>cloud drive and other services. Now, if you want more

0:12:32.120 --> 0:12:34.840
<v Speaker 1>space other than the twenty gigabytes that we were talking

0:12:34.880 --> 0:12:38.080
<v Speaker 1>about for buying music, um, you can buy that essentially

0:12:38.120 --> 0:12:42.280
<v Speaker 1>a dollar a gigabyte. Yea. It comes in increments um,

0:12:42.320 --> 0:12:46.280
<v Speaker 1>which are D two hundred, five hundred and a thousand gigabytes.

0:12:46.320 --> 0:12:49.120
<v Speaker 1>So if you want a thousand extra gigabytes you need

0:12:49.120 --> 0:12:52.320
<v Speaker 1>a terabyte of storage, yes you can. You can buy

0:12:52.320 --> 0:12:55.000
<v Speaker 1>that for a terabyte of money about a thousand dollars

0:12:55.000 --> 0:12:59.560
<v Speaker 1>a year, a grand a cool grand um. So you know,

0:12:59.600 --> 0:13:01.480
<v Speaker 1>it depends on what you're going to be storing in there,

0:13:02.280 --> 0:13:04.200
<v Speaker 1>what it's worth you to do that. But keep in mind,

0:13:04.280 --> 0:13:06.199
<v Speaker 1>although we're talking a lot about music here, you can

0:13:06.200 --> 0:13:08.720
<v Speaker 1>still store other files in that cloud drive. It doesn't

0:13:08.720 --> 0:13:10.840
<v Speaker 1>all have to be music. So if I bought an

0:13:10.880 --> 0:13:13.640
<v Speaker 1>album from Amazon dot Com got twenty gigabytes of storage,

0:13:13.679 --> 0:13:16.160
<v Speaker 1>I could fill that twenty gigabytes up with video, or

0:13:16.280 --> 0:13:18.560
<v Speaker 1>I could fill it up with documents if I had

0:13:18.679 --> 0:13:21.640
<v Speaker 1>that many. I can't imagine having twenty gigabytes worth the documents.

0:13:21.679 --> 0:13:25.000
<v Speaker 1>I don't want to either or pictures. I mean, you

0:13:25.000 --> 0:13:26.800
<v Speaker 1>can fill that stuff up anyway you want. And of

0:13:26.800 --> 0:13:28.920
<v Speaker 1>course you can keep buying music off Amazon dot Com

0:13:28.960 --> 0:13:32.360
<v Speaker 1>and it won't count against that cap um. But there's

0:13:32.400 --> 0:13:36.680
<v Speaker 1>another element that kind of makes this an interesting and

0:13:37.000 --> 0:13:41.040
<v Speaker 1>somewhat controversial move on Amazon's part, and that's you know,

0:13:41.080 --> 0:13:44.160
<v Speaker 1>the cloud drive. Like we said, not really that that

0:13:44.880 --> 0:13:47.920
<v Speaker 1>groundbreaking because cloud storage has been around for a few years,

0:13:48.640 --> 0:13:52.960
<v Speaker 1>but the cloud player, which again not necessarily groundbreaking, but

0:13:53.280 --> 0:13:58.800
<v Speaker 1>the implementation of the cloud player into this Cloud Drive ecosystem,

0:13:58.840 --> 0:14:01.679
<v Speaker 1>along with the Amazon on dot Com store, makes us

0:14:01.679 --> 0:14:05.000
<v Speaker 1>a really compelling and powerful tool. Now, the Cloud player.

0:14:05.080 --> 0:14:07.480
<v Speaker 1>What that allows you to do is play music that's

0:14:07.480 --> 0:14:10.880
<v Speaker 1>stored in your cloud drive on any computer that's connected

0:14:10.920 --> 0:14:15.000
<v Speaker 1>to the Internet or on any Android device. You just

0:14:15.040 --> 0:14:18.720
<v Speaker 1>have to download the right MP three app and and

0:14:18.840 --> 0:14:22.040
<v Speaker 1>you can stream music from the cloud drive to your

0:14:22.040 --> 0:14:27.080
<v Speaker 1>computer or device. So effectively, this well, for one thing,

0:14:27.280 --> 0:14:30.920
<v Speaker 1>it's a huge shot across the bowl of Apple. And

0:14:30.960 --> 0:14:33.160
<v Speaker 1>the reason I say this because it doesn't It means

0:14:33.160 --> 0:14:35.040
<v Speaker 1>that you can make your smartphone, you can turn it

0:14:35.080 --> 0:14:36.880
<v Speaker 1>into an MP three player, and you don't have to

0:14:36.880 --> 0:14:40.880
<v Speaker 1>worry about filling up your smartphones memory with songs because

0:14:40.920 --> 0:14:44.440
<v Speaker 1>all the songs actually live on a server and you

0:14:44.480 --> 0:14:46.720
<v Speaker 1>can have you know, five gigabytes where the songs are

0:14:46.760 --> 0:14:50.360
<v Speaker 1>more if you've bought them from Amazon, and it doesn't

0:14:50.400 --> 0:14:56.080
<v Speaker 1>affect your smartphones memory like your storage at all. Now, uh,

0:14:56.160 --> 0:14:57.840
<v Speaker 1>I want, I want to make a couple of things clear.

0:14:57.880 --> 0:15:01.880
<v Speaker 1>Of course, this is similar to many other types of services.

0:15:01.920 --> 0:15:05.560
<v Speaker 1>You know, the serious are serious XM has you know

0:15:05.600 --> 0:15:08.000
<v Speaker 1>a player where you can listen to satellite radio over

0:15:08.040 --> 0:15:12.080
<v Speaker 1>the internet. Um, You've got people like Pandora, you've got

0:15:12.360 --> 0:15:17.240
<v Speaker 1>last dot FM, you've got Rdeo streaming streaming radio stations.

0:15:17.680 --> 0:15:19.880
<v Speaker 1>You can use groove Shark if you are if you

0:15:19.920 --> 0:15:22.120
<v Speaker 1>are a subscribed member, you pay for a subscription, you

0:15:22.120 --> 0:15:26.200
<v Speaker 1>can listen to your groove Shark music on your player. Um.

0:15:26.280 --> 0:15:28.560
<v Speaker 1>And some people have pointed out that you can do

0:15:28.600 --> 0:15:33.040
<v Speaker 1>this with the regular storage services as well. You can

0:15:33.120 --> 0:15:35.440
<v Speaker 1>get access to your if you save music to your

0:15:35.480 --> 0:15:41.160
<v Speaker 1>drop box, you can listen to that music too. But again,

0:15:42.080 --> 0:15:44.760
<v Speaker 1>the effort is different the way they've structured it, the

0:15:44.760 --> 0:15:49.640
<v Speaker 1>way Amazon is structured. Yeah, it's it's somewhere in between,

0:15:49.680 --> 0:15:51.840
<v Speaker 1>and it is definitely if you There are people I've

0:15:51.840 --> 0:15:55.800
<v Speaker 1>found in discussions about Sirius XM because I was satellite

0:15:55.920 --> 0:15:59.040
<v Speaker 1>radio subscriber for many years, who wanted to listen to

0:15:59.080 --> 0:16:01.760
<v Speaker 1>their own music, so they preferred their their MP three

0:16:01.800 --> 0:16:06.560
<v Speaker 1>player to a satellite player because they wanted that control. Um.

0:16:06.640 --> 0:16:09.600
<v Speaker 1>So it's going to appeal to people like that. You

0:16:09.600 --> 0:16:12.120
<v Speaker 1>don't know, I don't want somebody else programming my station

0:16:12.120 --> 0:16:13.600
<v Speaker 1>for me. Yeah, that's great for some people, and I

0:16:13.640 --> 0:16:15.960
<v Speaker 1>don't want that. It's really gonna appeal to people who

0:16:16.040 --> 0:16:20.400
<v Speaker 1>either have very specific musical tastes that are not catered

0:16:20.400 --> 0:16:25.120
<v Speaker 1>to on regular terrestrial radio or even even some digital

0:16:25.240 --> 0:16:30.640
<v Speaker 1>radio stations. It will also appeal to people like us

0:16:30.720 --> 0:16:33.920
<v Speaker 1>who are getting older and our musical tastes are becoming

0:16:33.960 --> 0:16:36.520
<v Speaker 1>cemented and we don't like new things because they scare

0:16:36.560 --> 0:16:40.800
<v Speaker 1>us and get off my lawn. Hey, I like my

0:16:40.920 --> 0:16:43.960
<v Speaker 1>Lawrence Wilke playlist, Thank you very much. Yes, you're cutting edge,

0:16:44.400 --> 0:16:47.360
<v Speaker 1>living there on the edge of life. I one nanna

0:16:48.240 --> 0:16:52.520
<v Speaker 1>and tiny. Oh wait no, I'm sorry. So some of

0:16:52.680 --> 0:16:54.920
<v Speaker 1>some of our listeners have no idea what we're talking about.

0:16:55.200 --> 0:16:58.800
<v Speaker 1>But yeah, so I barely do. But now that that's

0:16:58.920 --> 0:17:02.000
<v Speaker 1>the significant different princes the amount of storage space that

0:17:02.080 --> 0:17:06.359
<v Speaker 1>Amazon is offering people. Now, Uh, I was kind of

0:17:06.400 --> 0:17:09.320
<v Speaker 1>wondering how I was going to get this app because

0:17:09.359 --> 0:17:11.880
<v Speaker 1>I was I'm very interested in this offering. I wrote

0:17:11.880 --> 0:17:14.720
<v Speaker 1>a blog post about it, and uh, we're basically covering

0:17:14.760 --> 0:17:15.960
<v Speaker 1>all of that, so you don't need to go read

0:17:15.960 --> 0:17:19.920
<v Speaker 1>it really right now. But um, the thing is, uh,

0:17:20.080 --> 0:17:23.720
<v Speaker 1>it's built into the MP three, the Amazon MP three app,

0:17:23.800 --> 0:17:26.040
<v Speaker 1>which I already had installed on my and you just

0:17:26.080 --> 0:17:27.840
<v Speaker 1>had to update and I had to update the app,

0:17:27.840 --> 0:17:30.640
<v Speaker 1>and there it is the app. Yeah, if you don't

0:17:30.640 --> 0:17:33.399
<v Speaker 1>have that pre installed on an Android device, and we should,

0:17:33.440 --> 0:17:36.080
<v Speaker 1>you know, make it clear we're talking about Android specific

0:17:36.160 --> 0:17:38.600
<v Speaker 1>right now. There are ways where you can take advantage

0:17:38.600 --> 0:17:41.000
<v Speaker 1>of the cloud storage using an iOS device, but if

0:17:41.000 --> 0:17:43.000
<v Speaker 1>you want to listen to the music, you actually have

0:17:43.040 --> 0:17:45.520
<v Speaker 1>to download it to your device. That's one of the

0:17:45.520 --> 0:17:48.360
<v Speaker 1>other things we should point out. Amazon does not restrict

0:17:48.400 --> 0:17:51.200
<v Speaker 1>you from downloading this stuff because it's yours, right. This

0:17:51.320 --> 0:17:54.719
<v Speaker 1>drive is just a storage space. So you've stored music

0:17:54.760 --> 0:17:57.919
<v Speaker 1>in this drive, you can download it as much or

0:17:57.960 --> 0:18:00.760
<v Speaker 1>wherever you like, which that will become more problem later.

0:18:01.080 --> 0:18:05.280
<v Speaker 1>You have a license to use that music, well, the

0:18:05.400 --> 0:18:10.600
<v Speaker 1>songs themselves do not belong to you. Yeah, yeah, that's good. No,

0:18:10.720 --> 0:18:12.640
<v Speaker 1>it's good to point that out. It's good to point

0:18:12.680 --> 0:18:14.639
<v Speaker 1>that out because that's exactly how the companies do it.

0:18:14.880 --> 0:18:17.040
<v Speaker 1>I just like watching that vein in your forehead, Throb.

0:18:17.119 --> 0:18:19.720
<v Speaker 1>But let's say that you don't have the Amazon MP

0:18:19.840 --> 0:18:24.320
<v Speaker 1>three UH app preinstalled on your Android phone. There's if

0:18:24.320 --> 0:18:26.760
<v Speaker 1>you go to the Amazon dot com page and you

0:18:26.800 --> 0:18:29.280
<v Speaker 1>look for their cloud player, they actually have a QR

0:18:29.320 --> 0:18:32.479
<v Speaker 1>code that you can use to you know, use if

0:18:32.520 --> 0:18:35.359
<v Speaker 1>you have a QR code app on your Android phone.

0:18:35.640 --> 0:18:38.720
<v Speaker 1>You can use that and it'll direct you specifically to

0:18:38.800 --> 0:18:41.520
<v Speaker 1>the marketplace where you can get that app. And it's free.

0:18:41.960 --> 0:18:43.359
<v Speaker 1>The app is fhere. You don't have to pay for that.

0:18:43.359 --> 0:18:47.520
<v Speaker 1>There's no subscription for this service. Um. And here's where

0:18:47.560 --> 0:18:49.959
<v Speaker 1>we're gonna get into some of the controversy. So with

0:18:50.000 --> 0:18:52.520
<v Speaker 1>this player being able to listen to this music streaming,

0:18:53.800 --> 0:18:56.560
<v Speaker 1>there's some music companies that are concerned that this is

0:18:56.760 --> 0:19:00.760
<v Speaker 1>violating licensing agreements. Yeah, remember when we were talking a

0:19:00.800 --> 0:19:03.040
<v Speaker 1>few moments ago, or actually Jonathan was talking a few

0:19:03.080 --> 0:19:08.240
<v Speaker 1>moments ago about how Amazon scooped Google and Apple. Both

0:19:08.440 --> 0:19:11.640
<v Speaker 1>of those companies have been known to be working on

0:19:12.080 --> 0:19:15.280
<v Speaker 1>some kind of effort. Well, in Apple's case, it's more

0:19:15.400 --> 0:19:21.000
<v Speaker 1>of a nearly substantiated rumor. They all signs point to

0:19:21.040 --> 0:19:22.960
<v Speaker 1>the the idea that they are going to be doing something.

0:19:22.960 --> 0:19:27.399
<v Speaker 1>Google Music has been known about in some capacity for

0:19:27.400 --> 0:19:29.399
<v Speaker 1>a while, and it's rumored at the time we are

0:19:29.440 --> 0:19:31.560
<v Speaker 1>recording this, and who knows, by the time it goes live,

0:19:31.560 --> 0:19:35.480
<v Speaker 1>it may be public, uh that Google is doing a

0:19:35.600 --> 0:19:39.080
<v Speaker 1>data with its internal employees for Google Music, which is

0:19:39.119 --> 0:19:42.520
<v Speaker 1>supposed to be a similar service to this, a cloud

0:19:42.720 --> 0:19:46.600
<v Speaker 1>music service. Apple, of course purchased La La, which we've

0:19:46.600 --> 0:19:51.760
<v Speaker 1>mentioned I think several times um. And they are building

0:19:51.880 --> 0:19:55.119
<v Speaker 1>a data center in North Carolina, very large data center. UM.

0:19:55.320 --> 0:19:58.040
<v Speaker 1>Rumor has it that it will be used for streaming

0:19:58.359 --> 0:20:02.480
<v Speaker 1>music and or video. Uh so that's been in the

0:20:02.520 --> 0:20:04.800
<v Speaker 1>works for a long time. But what Amazon didn't do

0:20:05.640 --> 0:20:08.320
<v Speaker 1>They wanted to get a jump on everyone else, which

0:20:08.359 --> 0:20:15.200
<v Speaker 1>they did. They also didn't tell the music companies what

0:20:15.240 --> 0:20:18.320
<v Speaker 1>was going on, so and didn't get light Well, they

0:20:18.320 --> 0:20:21.200
<v Speaker 1>didn't get licenses. Let's say this. They didn't get licenses

0:20:21.440 --> 0:20:24.359
<v Speaker 1>to do this, which normally the record companies prefer to do,

0:20:24.400 --> 0:20:27.480
<v Speaker 1>which is why Spotify isn't in the United States as

0:20:27.480 --> 0:20:32.440
<v Speaker 1>of yet. So let's prepare for a Jonathan rant. Everyone

0:20:32.920 --> 0:20:35.920
<v Speaker 1>just settled down because I'm going to get going. Mm hmm.

0:20:36.640 --> 0:20:38.200
<v Speaker 1>Can I go get a cup of water? You can

0:20:38.280 --> 0:20:39.960
<v Speaker 1>go for as long as you need to. I'll turn

0:20:39.960 --> 0:20:42.480
<v Speaker 1>a light on when it's when it's when, when I'm done.

0:20:42.520 --> 0:20:45.040
<v Speaker 1>So here's the deal, folks, here's here's how I see it.

0:20:46.640 --> 0:20:50.960
<v Speaker 1>Cloud storage is just an extension of local storage. As

0:20:51.000 --> 0:20:54.520
<v Speaker 1>far as I'm concerned, that data is your data to

0:20:54.960 --> 0:20:58.880
<v Speaker 1>the limitations of whatever that data might be, and you

0:20:58.960 --> 0:21:02.119
<v Speaker 1>can access it whenever you like, as long as of

0:21:02.119 --> 0:21:04.960
<v Speaker 1>course there's a connection there. It's the same thing that

0:21:05.040 --> 0:21:07.480
<v Speaker 1>if that if you purchased an album or ripped a

0:21:07.560 --> 0:21:09.760
<v Speaker 1>c D and that music is on your hard drive.

0:21:09.840 --> 0:21:13.000
<v Speaker 1>There's no difference. I mean, the only difference is the distance.

0:21:13.560 --> 0:21:16.879
<v Speaker 1>Instead of the hard drive being immediately adjacent to or

0:21:17.040 --> 0:21:21.639
<v Speaker 1>part of your computer, this drive is you know, potentially

0:21:21.680 --> 0:21:26.040
<v Speaker 1>thousands of miles away. But it's still just storage. There's

0:21:26.040 --> 0:21:29.879
<v Speaker 1>it's not like Amazon is his broadcasting new music or

0:21:29.960 --> 0:21:33.439
<v Speaker 1>music you do. You did not yourself put into that drive.

0:21:34.040 --> 0:21:36.760
<v Speaker 1>That's not happening. It's not it's not taking the music

0:21:36.800 --> 0:21:39.119
<v Speaker 1>that's in your drive and then sending you new stuff.

0:21:39.359 --> 0:21:41.119
<v Speaker 1>You know. That's kind of like what Pandora does. You know,

0:21:41.160 --> 0:21:43.399
<v Speaker 1>you create a station based upon a song you like,

0:21:43.440 --> 0:21:46.200
<v Speaker 1>in Pandora finds other songs that are similar, but Pandora

0:21:46.240 --> 0:21:48.679
<v Speaker 1>pays licensing fees for that because that's more of a

0:21:48.720 --> 0:21:54.720
<v Speaker 1>broadcast thing. This is really there's no difference between cloud

0:21:54.800 --> 0:21:57.560
<v Speaker 1>storage and having a server that's a thousand miles away

0:21:57.560 --> 0:22:00.480
<v Speaker 1>and having a thousand mile long cable connected you to

0:22:00.560 --> 0:22:02.840
<v Speaker 1>that server to listen to your music. You could have

0:22:02.880 --> 0:22:06.879
<v Speaker 1>an iPod, all right, and you could be listening to

0:22:06.960 --> 0:22:09.000
<v Speaker 1>your iPod. You've got your headphones on, You're in New

0:22:09.119 --> 0:22:11.600
<v Speaker 1>York City, just so happens, your iPod happens to be

0:22:11.640 --> 0:22:13.920
<v Speaker 1>in San Francisco. But you've got a cable that goes

0:22:14.000 --> 0:22:17.040
<v Speaker 1>all the way across the United States of America and

0:22:17.119 --> 0:22:19.119
<v Speaker 1>you can listen to that. Of course, you're gonna be

0:22:19.160 --> 0:22:21.320
<v Speaker 1>stuck on whatever songs on there, because your controls are

0:22:21.320 --> 0:22:23.520
<v Speaker 1>all the way across this country. But that's not the point.

0:22:23.520 --> 0:22:27.720
<v Speaker 1>The point being that it's the distance doesn't matter. It's

0:22:27.800 --> 0:22:31.440
<v Speaker 1>it's storage. It's a it's a drive. It's the same

0:22:31.520 --> 0:22:34.160
<v Speaker 1>kind of drive that's on an MP three player, that's

0:22:34.160 --> 0:22:37.400
<v Speaker 1>on smartphone, that's on a computer. There is no difference there.

0:22:37.400 --> 0:22:42.359
<v Speaker 1>There's they're not creating this performance. It's just you accessing

0:22:42.400 --> 0:22:46.560
<v Speaker 1>a file. So I'm hoping that Amazon can defend this

0:22:47.119 --> 0:22:51.000
<v Speaker 1>and come forward and say, hey, guys, we're not we're not.

0:22:51.400 --> 0:22:53.359
<v Speaker 1>All we're doing is giving them the tools to listen

0:22:53.359 --> 0:22:56.640
<v Speaker 1>to the music they purchased. We're not doing anything else.

0:22:56.680 --> 0:22:59.080
<v Speaker 1>We're not making you know, we're not trying to go

0:22:59.119 --> 0:23:01.800
<v Speaker 1>behind your backs or anything. And it's just the same

0:23:01.840 --> 0:23:05.240
<v Speaker 1>as if they were pushing play on an MP three player.

0:23:05.480 --> 0:23:07.879
<v Speaker 1>It's just that they're pushing play on a smartphone or

0:23:07.920 --> 0:23:10.600
<v Speaker 1>on a computer and they're just accessing a file that

0:23:10.680 --> 0:23:13.040
<v Speaker 1>happens to rest on our servers. But we don't own

0:23:13.080 --> 0:23:17.360
<v Speaker 1>that file. We sold that to them. Boy, that makes

0:23:17.400 --> 0:23:21.600
<v Speaker 1>me mad. Are you done? I? I think so. I

0:23:21.640 --> 0:23:25.959
<v Speaker 1>need more beans well to be fair. As of right,

0:23:26.280 --> 0:23:31.199
<v Speaker 1>I think I was very fair to two. As of

0:23:31.240 --> 0:23:33.080
<v Speaker 1>the day that we're recording this, I have not seen

0:23:33.119 --> 0:23:36.800
<v Speaker 1>anything that suggests that any of the major players in

0:23:36.840 --> 0:23:39.879
<v Speaker 1>the recording industry are in the process of filing a

0:23:39.920 --> 0:23:46.120
<v Speaker 1>lawsuit against Amazon, and I know that they are planning

0:23:46.240 --> 0:23:50.680
<v Speaker 1>on having some discussions with Amazon about it. Now. This

0:23:50.760 --> 0:23:54.399
<v Speaker 1>is the same industry that wanted that that wanted XM

0:23:54.480 --> 0:23:57.280
<v Speaker 1>to remove the ability to record a show that you

0:23:57.280 --> 0:23:59.840
<v Speaker 1>were listening on on your personal They used to offer

0:24:00.000 --> 0:24:03.840
<v Speaker 1>a portable player that you could um record a song.

0:24:03.840 --> 0:24:06.240
<v Speaker 1>It's sort of like a DVR for your TV. You

0:24:06.280 --> 0:24:08.680
<v Speaker 1>could record a program on it and listen to it later.

0:24:09.240 --> 0:24:14.479
<v Speaker 1>And uh, certain people in the industry wanted XM to stop,

0:24:15.040 --> 0:24:18.600
<v Speaker 1>which they eventually did, but there were lawsuits and things

0:24:18.640 --> 0:24:21.159
<v Speaker 1>over whether or not you're allowed to time shift your radio,

0:24:21.680 --> 0:24:26.720
<v Speaker 1>your satellite radio. UM. So yes, of course this, this

0:24:26.800 --> 0:24:30.520
<v Speaker 1>is the kind of thing that's going to be UM

0:24:30.560 --> 0:24:32.600
<v Speaker 1>I think coming out in the next few weeks. As

0:24:32.640 --> 0:24:37.200
<v Speaker 1>of the time we're recording this, uh although um yesterday,

0:24:37.440 --> 0:24:39.359
<v Speaker 1>as of the day we're recording this, we're recording this

0:24:39.480 --> 0:24:42.680
<v Speaker 1>on April Fools Day. As a matter of fact, UM.

0:24:42.720 --> 0:24:46.159
<v Speaker 1>Greg Sandoval wrote an article in c NET that kind

0:24:46.160 --> 0:24:49.840
<v Speaker 1>of surprised me. I had been talking about cloud Drive

0:24:49.880 --> 0:24:52.600
<v Speaker 1>primarily as a music storage service, but as Jonathan pointed out,

0:24:52.600 --> 0:24:55.720
<v Speaker 1>you can put anything in there. The movie industry is

0:24:55.720 --> 0:24:59.280
<v Speaker 1>not concerned with the same issues that the recording industry

0:24:59.400 --> 0:25:02.760
<v Speaker 1>is because people don't it's not really the service isn't

0:25:02.800 --> 0:25:07.800
<v Speaker 1>really designed to host video the way it is audio.

0:25:08.119 --> 0:25:11.480
<v Speaker 1>There's not The cloud player won't play movies, right. Yeah,

0:25:11.480 --> 0:25:14.359
<v Speaker 1>it will host it, you just can't access it with

0:25:14.400 --> 0:25:17.080
<v Speaker 1>the same ease that you can the music. Right. So

0:25:17.119 --> 0:25:19.960
<v Speaker 1>they apparently are not in the rush to run out

0:25:20.000 --> 0:25:24.000
<v Speaker 1>and have a talk with Amazon at the moment um

0:25:24.040 --> 0:25:27.840
<v Speaker 1>because it's not as urgent for them, although you know,

0:25:27.840 --> 0:25:29.679
<v Speaker 1>I would imagine they will be keeping their eye on

0:25:29.720 --> 0:25:32.280
<v Speaker 1>it because the potential is there for for them to

0:25:32.320 --> 0:25:36.240
<v Speaker 1>add that capability to the player. And make it possible

0:25:36.280 --> 0:25:40.800
<v Speaker 1>to watch video, um, probably both movies and TV, but

0:25:41.600 --> 0:25:45.040
<v Speaker 1>now on a strong connection to your network. In fact,

0:25:45.160 --> 0:25:48.480
<v Speaker 1>for even for the music, Amazon recommends that you use

0:25:48.560 --> 0:25:51.760
<v Speaker 1>a three G or better connection, so we're talking three G,

0:25:51.960 --> 0:25:54.880
<v Speaker 1>four G or Wi Fi connection in order to have

0:25:55.119 --> 0:25:59.320
<v Speaker 1>a satisfying experience listening to the music, because otherwise you're

0:25:59.320 --> 0:26:01.720
<v Speaker 1>gonna have a lot of buff s fring issues where um,

0:26:01.760 --> 0:26:03.320
<v Speaker 1>you know, the song is just not going to come

0:26:03.359 --> 0:26:08.160
<v Speaker 1>across very very well because the bandwidth you have isn't

0:26:08.240 --> 0:26:12.360
<v Speaker 1>enough to transmit that data smoothly. Um. And yeah, there

0:26:12.400 --> 0:26:16.600
<v Speaker 1>hasn't been any move for a lawsuit yet, but shortly

0:26:16.640 --> 0:26:20.480
<v Speaker 1>after Amazon made the announcement, UH, Sony Music Entertainment and

0:26:20.480 --> 0:26:24.240
<v Speaker 1>Warner Music Group both kind of expressed some concerns, and

0:26:24.280 --> 0:26:28.360
<v Speaker 1>in fact, Brian Garritty from Sony said, we're disappointed by

0:26:28.359 --> 0:26:32.320
<v Speaker 1>their decision to launch without a license, which at least

0:26:32.320 --> 0:26:36.440
<v Speaker 1>suggests that they feel that a license would be necessary

0:26:36.520 --> 0:26:40.840
<v Speaker 1>for you to access your file on a hard drive.

0:26:42.000 --> 0:26:43.520
<v Speaker 1>If they tell me that I need a license to

0:26:43.560 --> 0:26:46.880
<v Speaker 1>listen to my music on my m B three player, oh,

0:26:47.040 --> 0:26:52.280
<v Speaker 1>I would guess yes. That the difference is who owns

0:26:52.359 --> 0:26:55.920
<v Speaker 1>the hard drive. I would guess that that's no. I'm

0:26:55.920 --> 0:26:58.040
<v Speaker 1>not I'm not arguing with you, and you're saying, I'm

0:26:58.040 --> 0:27:01.040
<v Speaker 1>guessing for the music industry that that's the big deal.

0:27:01.040 --> 0:27:03.880
<v Speaker 1>If you have let's say a RAID at home, that's

0:27:03.920 --> 0:27:08.080
<v Speaker 1>a ray of independent discs UM for those of you

0:27:08.119 --> 0:27:11.680
<v Speaker 1>who aren't familiar with the term, UH, which is basically

0:27:11.720 --> 0:27:15.240
<v Speaker 1>just a U a giant box with hard drives in it.

0:27:15.560 --> 0:27:18.399
<v Speaker 1>I'm over way oversimplifying that, but yeah, it's you can

0:27:18.440 --> 0:27:20.440
<v Speaker 1>access any of those hard drives over your network. They're

0:27:20.480 --> 0:27:22.320
<v Speaker 1>not part of a computer. They're just a big box

0:27:22.359 --> 0:27:24.520
<v Speaker 1>of hardners. So let's say you have a massive music

0:27:24.520 --> 0:27:28.000
<v Speaker 1>collection and you know it's all on this RAID and

0:27:28.080 --> 0:27:30.280
<v Speaker 1>different discs. If you want to do that, because you

0:27:30.320 --> 0:27:34.600
<v Speaker 1>own the hardware, they're okay with it. I'm guessing that

0:27:35.000 --> 0:27:38.800
<v Speaker 1>for the music studios, they see an opportunity to get

0:27:38.800 --> 0:27:42.359
<v Speaker 1>another license because you are storing it on or you know,

0:27:42.400 --> 0:27:46.639
<v Speaker 1>from Amazon, because they are supplying the internet infrastructure and

0:27:46.680 --> 0:27:49.800
<v Speaker 1>the hardware to you, and that's that's probably the sticking

0:27:49.840 --> 0:27:52.240
<v Speaker 1>point for them. I think I think another sticking point

0:27:52.240 --> 0:27:55.479
<v Speaker 1>though that's that's a legitimate point, and I agree with it.

0:27:55.520 --> 0:27:57.520
<v Speaker 1>I think another sticking point is that some of these

0:27:57.560 --> 0:28:00.480
<v Speaker 1>companies have been known to also be working on their

0:28:00.520 --> 0:28:05.520
<v Speaker 1>own infrastructures that are branded specifically to their labels. Yeah,

0:28:05.600 --> 0:28:10.159
<v Speaker 1>so get like a company like Sony, and Sony starts

0:28:10.240 --> 0:28:14.399
<v Speaker 1>building out its infrastructure. Uh, you know, you don't want

0:28:14.560 --> 0:28:18.320
<v Speaker 1>to have to deal with competition from other other companies

0:28:18.359 --> 0:28:21.680
<v Speaker 1>like Amazon. You know, you you want you want your

0:28:21.760 --> 0:28:23.919
<v Speaker 1>stuff to be safe so that you can sell it

0:28:23.960 --> 0:28:27.199
<v Speaker 1>through yours and lock people into an infrastructure because it

0:28:27.200 --> 0:28:29.800
<v Speaker 1>makes good business sense. You know, it's not necessarily the

0:28:29.800 --> 0:28:32.160
<v Speaker 1>thing that the customer is going to go crazy floor

0:28:32.240 --> 0:28:35.480
<v Speaker 1>unless they're a huge Sony fan, But it makes sense

0:28:35.560 --> 0:28:37.760
<v Speaker 1>from your standpoint where you're saying, look, this is a

0:28:37.760 --> 0:28:40.400
<v Speaker 1>great business decision. It's a way for us to guarantee

0:28:40.440 --> 0:28:43.840
<v Speaker 1>that our online music sales are going to remain steady

0:28:43.960 --> 0:28:46.880
<v Speaker 1>or even grow because music sales are kind of stagnated

0:28:47.280 --> 0:28:49.959
<v Speaker 1>over the last few couple of years and um, and

0:28:50.000 --> 0:28:52.920
<v Speaker 1>that's a big concern for these companies. I mean, the

0:28:52.960 --> 0:28:55.880
<v Speaker 1>whole purpose they're in business is to make money, and

0:28:55.920 --> 0:28:58.920
<v Speaker 1>they make money through selling music, and if people stop

0:28:58.960 --> 0:29:03.160
<v Speaker 1>buying music, that's a problem. So it may be that

0:29:03.160 --> 0:29:04.760
<v Speaker 1>that's one of the things that they were looking at

0:29:04.760 --> 0:29:07.280
<v Speaker 1>that that they're they've got a strategy in place to

0:29:07.360 --> 0:29:10.440
<v Speaker 1>really boost music sales, partially by creating this locked in

0:29:10.520 --> 0:29:14.400
<v Speaker 1>ecosystem that's only good for one major label. Uh, but

0:29:14.640 --> 0:29:18.080
<v Speaker 1>if another company comes in and undercuts them, then they

0:29:18.240 --> 0:29:21.720
<v Speaker 1>no longer have that advantage, right, I mean the music

0:29:21.760 --> 0:29:24.920
<v Speaker 1>industry itself. We're not talking about the artists themselves, the

0:29:25.000 --> 0:29:28.400
<v Speaker 1>music industry, the recording industry. We're talking about the big labels.

0:29:28.840 --> 0:29:32.000
<v Speaker 1>They make their money from recording the arts, basically going

0:29:32.000 --> 0:29:36.040
<v Speaker 1>out discovering people they think will sell, recording those artists,

0:29:37.200 --> 0:29:41.080
<v Speaker 1>packaging and you know, creating the the uh, the recording

0:29:41.160 --> 0:29:44.160
<v Speaker 1>with the packaging and creating the product and distributing it

0:29:44.200 --> 0:29:46.800
<v Speaker 1>to people, marketing it to radio stations to get them

0:29:46.840 --> 0:29:50.360
<v Speaker 1>to play it, um, and then selling bucks of albums

0:29:50.480 --> 0:29:54.800
<v Speaker 1>or digital downloads. As you know, because we're seeing those

0:29:54.800 --> 0:29:57.440
<v Speaker 1>physical album sales, I mean, those are really dropping off.

0:29:57.800 --> 0:30:01.920
<v Speaker 1>Digital music is also kind of stagnating. So but yeah,

0:30:01.920 --> 0:30:04.280
<v Speaker 1>I mean, if you put your your yourself in the

0:30:04.320 --> 0:30:07.880
<v Speaker 1>shoes of the industry itself, it's easy to see why

0:30:07.880 --> 0:30:11.600
<v Speaker 1>they would be frightened by losing control. And if they

0:30:11.640 --> 0:30:14.120
<v Speaker 1>see this as a possibility that they may lose control.

0:30:14.640 --> 0:30:17.840
<v Speaker 1>Of course, they're going to defend their industry because you know,

0:30:17.960 --> 0:30:21.200
<v Speaker 1>that's what they do, So it's not really surprising that

0:30:21.240 --> 0:30:23.960
<v Speaker 1>they would be concerned about what's going on. Then it's

0:30:23.960 --> 0:30:27.479
<v Speaker 1>possible that they could work out um an arrangement with Amazon.

0:30:27.520 --> 0:30:31.520
<v Speaker 1>I mean, ultimately, you're right, Jonathan, it's it's not giving

0:30:31.600 --> 0:30:35.200
<v Speaker 1>music to other people. If Amazon can demonstrate that, hey, look,

0:30:35.240 --> 0:30:38.160
<v Speaker 1>this is this is highly secure. Nobody's going to get

0:30:38.200 --> 0:30:41.160
<v Speaker 1>access to anybody else's music. It's no different than if

0:30:41.160 --> 0:30:43.240
<v Speaker 1>it was on their own computer. Yeah, if they can

0:30:43.280 --> 0:30:46.560
<v Speaker 1>convince the recording industry of that, um, they may be

0:30:46.640 --> 0:30:51.800
<v Speaker 1>able to avoid having to restructure their offering or worry

0:30:51.800 --> 0:30:54.640
<v Speaker 1>about yeah or or or worry about a lawsuit. So

0:30:55.000 --> 0:30:57.160
<v Speaker 1>it is very possible that through discussion that they can

0:30:57.200 --> 0:30:59.800
<v Speaker 1>they can work something out. They just need to reassure people.

0:30:59.800 --> 0:31:02.080
<v Speaker 1>And you know, when you drop the news on him, Yeah,

0:31:02.120 --> 0:31:04.160
<v Speaker 1>I'm sorry what And I should point out that I'm

0:31:04.160 --> 0:31:06.760
<v Speaker 1>a you know, I'm a real advocate for the consumer

0:31:06.840 --> 0:31:10.120
<v Speaker 1>because I am one sure, if I were a major label,

0:31:10.200 --> 0:31:12.160
<v Speaker 1>I probably would have a totally different argument than the

0:31:12.160 --> 0:31:14.880
<v Speaker 1>one I laid out. Yeah, I mean, it's you know,

0:31:15.080 --> 0:31:17.800
<v Speaker 1>it's their livelihood, that's what they do. And so I'm

0:31:17.880 --> 0:31:22.120
<v Speaker 1>arguing for the customer experience, but that's just one piece

0:31:22.120 --> 0:31:24.920
<v Speaker 1>of the puzzle. And I recognize that too. Doesn't make

0:31:24.920 --> 0:31:28.400
<v Speaker 1>me less RANTI though, all right, well let's wrap this

0:31:28.440 --> 0:31:30.640
<v Speaker 1>discussion up. I think it was a really good discussion.

0:31:30.680 --> 0:31:32.920
<v Speaker 1>And and Chris does have a great blog post about

0:31:32.960 --> 0:31:36.080
<v Speaker 1>the Amazon Cloud Drive already, so I would recommend checking

0:31:36.080 --> 0:31:38.560
<v Speaker 1>that out. Go over to our blogs and and just

0:31:38.680 --> 0:31:40.680
<v Speaker 1>click on the little tech stuff thing. You can ignore

0:31:40.680 --> 0:31:42.600
<v Speaker 1>all the rest. And I'm just kidding. All the other

0:31:42.720 --> 0:31:44.680
<v Speaker 1>all the other blogs are also awesome, But if you

0:31:44.680 --> 0:31:47.120
<v Speaker 1>click on tech stuff, it'll just bring up our our

0:31:47.120 --> 0:31:49.760
<v Speaker 1>posts and you can find the one easily that way

0:31:49.840 --> 0:31:52.240
<v Speaker 1>on the cloud drive. And I think it's safe to

0:31:52.320 --> 0:31:56.320
<v Speaker 1>expect that we will see something going on from Google

0:31:56.440 --> 0:31:59.400
<v Speaker 1>or Apple or both in the in the months to come.

0:31:59.440 --> 0:32:02.520
<v Speaker 1>So this is uh, they may actually be happy that

0:32:02.560 --> 0:32:04.840
<v Speaker 1>Amazon beat them to the punch, especially if they get

0:32:05.520 --> 0:32:07.560
<v Speaker 1>punched for it. Yeah, if they get pummeled for it,

0:32:07.640 --> 0:32:11.000
<v Speaker 1>and then Google and Apple can say, hey, let's rethink

0:32:11.000 --> 0:32:13.120
<v Speaker 1>our strategy here so that we can, you know, we

0:32:13.200 --> 0:32:16.640
<v Speaker 1>can avoid the pitfalls that Amazon fell into. That is

0:32:16.680 --> 0:32:18.880
<v Speaker 1>a potential outcome, so we'll have to wait and see.

0:32:19.400 --> 0:32:22.160
<v Speaker 1>If you guys have any comments on the Amazon Cloud

0:32:22.240 --> 0:32:24.880
<v Speaker 1>Drive and Cloud Player, or perhaps you have some request

0:32:24.960 --> 0:32:27.440
<v Speaker 1>for a different topic you would like to hear, Why

0:32:27.440 --> 0:32:31.240
<v Speaker 1>don't you contact us either on Twitter or Facebook. Are handled,

0:32:31.280 --> 0:32:34.040
<v Speaker 1>There is tech stuff h s W or you can

0:32:34.080 --> 0:32:37.280
<v Speaker 1>send us an email that addresses tech stuff at how

0:32:37.320 --> 0:32:39.280
<v Speaker 1>stuff works dot com and Chris and I will talk

0:32:39.280 --> 0:32:43.560
<v Speaker 1>to you again really soon. For moral on this and

0:32:43.640 --> 0:32:46.320
<v Speaker 1>thousands of other topics, visit how stuff works dot com.

0:32:46.560 --> 0:32:49.200
<v Speaker 1>To learn more about the podcast, click on the podcast

0:32:49.400 --> 0:32:52.920
<v Speaker 1>icon in the upper right corner of our homepage. The

0:32:52.960 --> 0:32:55.560
<v Speaker 1>how Stuff Works iPhone app has a ride. Download it

0:32:55.640 --> 0:33:03.080
<v Speaker 1>today on iTunes. Brought to you by the reinvented two

0:33:03.160 --> 0:33:05.960
<v Speaker 1>thousand twelve Camry. It's ready, are you