WEBVTT - TechStuff Looks at the iCloud 0:00:00.280 --> 0:00:02.960 Brought to you by the reinvented two thousand twelve Camray. 0:00:03.160 --> 0:00:08.920 It's ready. Are you get in touch with technology? With 0:00:09.000 --> 0:00:17.800 tech Stuff from how stuff works dot com. Hello again, everyone, 0:00:17.840 --> 0:00:21.079 welcome to tech stuff. My name is Chris Polette and 0:00:21.120 --> 0:00:23.680 I'm an editor here at how stuff works dot com. 0:00:23.720 --> 0:00:27.160 Sitting across from me as always a senior writer, Jonathan Strickland. 0:00:27.400 --> 0:00:32.720 I can see clearly now the rain is gone. Nice. 0:00:32.960 --> 0:00:35.120 That was a particularly good one for our topic too. Yes, 0:00:35.200 --> 0:00:39.199 we're talking about iCloud, which is a new service, a 0:00:39.280 --> 0:00:42.360 new as the recording of this podcast anyway, service from Apple, 0:00:42.680 --> 0:00:44.760 and it's facts in fact, so new that it's just 0:00:44.840 --> 0:00:47.440 in beta right now, which we're like, hey, Apple, who 0:00:47.479 --> 0:00:53.480 do you think you are? Google? Sometimes? Um, yeah, well 0:00:53.560 --> 0:00:55.320 not not all of it's in Vada. Some of it 0:00:55.400 --> 0:00:57.120 is still slated to come out. We had a lot 0:00:57.160 --> 0:01:02.480 of requests from people After Apple Worldwide Developers Conference Keynote, 0:01:02.640 --> 0:01:05.800 which was an early which was in early June, they 0:01:05.840 --> 0:01:09.759 announced basically they gave updates on three major things, two 0:01:09.760 --> 0:01:12.840 of which were one of which was no secret at all. 0:01:12.880 --> 0:01:16.319 That was the new Apple OS ten Lion that's the 0:01:16.400 --> 0:01:22.840 next version, which, um, then people were really expecting to 0:01:22.880 --> 0:01:27.080 hear about the new iOS that's the operating system for iPod, Touch, 0:01:27.319 --> 0:01:30.679 iPhone and iPad, so it'd be iOS five. Yeah. Yeah, 0:01:30.760 --> 0:01:32.640 people were pretty sure that they were going to hear 0:01:32.760 --> 0:01:35.000 and they did well of course as the developer's conference, 0:01:35.000 --> 0:01:37.280 so you would expect them to talk about the software 0:01:37.280 --> 0:01:41.120 available for the platform the platforms. But the third and 0:01:41.120 --> 0:01:43.360 the one that we're going to talk about today is 0:01:43.360 --> 0:01:47.480 is iCloud. And that's UM again something that people really expected. 0:01:47.560 --> 0:01:51.920 In fact, uh, people actually identified the logo before it's 0:01:51.920 --> 0:01:54.000 where it got announced. People called it the most poorly 0:01:54.080 --> 0:01:57.880 kept secret uh for this particular conference, which I mean, 0:01:59.000 --> 0:02:01.680 everyone was pretty sure that Apple was going to come 0:02:01.680 --> 0:02:04.680 out with some sort of cloud based service because of 0:02:05.400 --> 0:02:09.440 uh movements from Amazon and Google and the fact that 0:02:09.760 --> 0:02:13.160 Apple had purchased some other companies that were related to 0:02:13.240 --> 0:02:19.360 cloud services. Uh. Everything pointed towards that the the giant 0:02:19.440 --> 0:02:21.760 data center they were building in North Carolina, right, but 0:02:21.800 --> 0:02:27.040 the details behind the service were still pretty fuzzy. And 0:02:27.080 --> 0:02:30.880 then actually, to tell you the truth, even almost a 0:02:30.960 --> 0:02:34.880 month later, the details are still a little scarce. Uh. 0:02:34.919 --> 0:02:36.919 You know, there's there's some stuff we know, and then 0:02:36.919 --> 0:02:39.360 there's some stuff we suspect and there's some stuff that 0:02:39.400 --> 0:02:43.600 just hasn't been answered yet. Yeah. And um, it's it's 0:02:43.600 --> 0:02:46.560 funny because with the building of this data center, which 0:02:46.560 --> 0:02:48.480 has been going on for what probably a couple of 0:02:48.560 --> 0:02:51.400 years now, I mean, people knew that Apple was building 0:02:51.440 --> 0:02:56.079 a very very large building in North Carolina. Um. When 0:02:56.120 --> 0:02:58.960 you see other companies doing this, people like Google and Facebook, 0:02:59.360 --> 0:03:02.120 you realize that there's, uh, they're probably gonna be quite 0:03:02.120 --> 0:03:04.160 a few employees in there, there's probably gonna be a 0:03:04.160 --> 0:03:08.360 whole lot of hardware in there. Um, especially if they're 0:03:08.400 --> 0:03:11.240 looking for giant sources of power like Google, you know, 0:03:11.280 --> 0:03:15.160 building along the Columbia River for hydro electricity. You know, 0:03:15.240 --> 0:03:17.000 there's there's gonna be so you can you can take 0:03:17.040 --> 0:03:20.880 some inferences from from the way they're behaving. Um. And 0:03:21.080 --> 0:03:23.800 a lot of the speculation revolved around the possibility that 0:03:23.840 --> 0:03:29.040 there would be a cloud based iTunes service and or 0:03:30.280 --> 0:03:33.160 a streaming video service to rival you know, someone like 0:03:33.360 --> 0:03:38.040 uh Netflix or Amazon Prime, um, you know, something where 0:03:38.080 --> 0:03:41.040 where Apple would or Hulu they would you know, you 0:03:41.040 --> 0:03:43.360 would subscribe to or I guess in this case, Hulu Plus, 0:03:43.400 --> 0:03:46.160 where you would pay a subscription fee and you'd get 0:03:46.160 --> 0:03:50.280 your music and your uh, your video on download. That's 0:03:50.760 --> 0:03:53.440 and I think that's why people have been sort of 0:03:54.680 --> 0:03:58.360 nonplussed about what actually came out by a little perplexed 0:03:58.560 --> 0:04:02.440 or a little perplexed and um, and I think there 0:04:02.440 --> 0:04:04.920 are some of that is sort of in there, and 0:04:04.960 --> 0:04:06.880 I don't know that you can rule out those things 0:04:06.920 --> 0:04:09.760 showing up in the service later. It's just that the 0:04:09.840 --> 0:04:12.440 wording has been very careful to avoid that kind of 0:04:12.480 --> 0:04:16.680 stuff recently. Yeah. Yeah, And what what rolled out is actually, 0:04:17.080 --> 0:04:19.839 I think, compared to some of the other services that 0:04:19.839 --> 0:04:22.800 we've been talking about recently, sort of compelling, you know, 0:04:22.880 --> 0:04:26.560 they're they're definitely some advantages and some disadvantages of I 0:04:26.760 --> 0:04:30.839 Cloud if you compare it to similar services. So let's 0:04:30.880 --> 0:04:32.719 kind of talk about what I cloud is and what 0:04:32.880 --> 0:04:35.600 it is not. I'll start off with what it is 0:04:35.600 --> 0:04:37.880 not in the sense that, as far as we know 0:04:38.000 --> 0:04:40.320 right now, it is not going to be any sort 0:04:40.360 --> 0:04:43.160 of streaming service. So, in other words, you will not 0:04:43.200 --> 0:04:47.120 be streaming content from a cloud storage system to a 0:04:47.200 --> 0:04:51.520 device in order to enjoy it on the fly. Um. So, 0:04:52.120 --> 0:04:56.000 unlike some of the other services like the Amazon Music 0:04:56.040 --> 0:04:59.520 Player service, where you can store music in an Amazon 0:05:00.040 --> 0:05:03.400 count and then access a streaming file version of that 0:05:03.480 --> 0:05:07.120 song and listen to it. Uh. You will not necessarily 0:05:07.240 --> 0:05:10.520 be able to do that on iCloud, at least according 0:05:10.600 --> 0:05:12.919 to the way they've worded things so far. In the 0:05:12.920 --> 0:05:15.479 way the system works right now, Well, that's that's sort 0:05:15.520 --> 0:05:20.440 of pardon the pun, seriously hazy. Um, there is one 0:05:20.520 --> 0:05:26.119 feature that sort of suggests that there is something like that. Um, 0:05:26.200 --> 0:05:28.560 should we should we get into the futures that maybe 0:05:28.560 --> 0:05:31.800 we can we can touch on that way, get closer. Um, Yeah, 0:05:31.800 --> 0:05:34.520 they're the iCloud website is actually a great place to 0:05:34.520 --> 0:05:37.240 look for information if you want to learn more about it. Um. 0:05:37.480 --> 0:05:41.680 And it's where I what I use for my primary source. UM. Basically, 0:05:41.680 --> 0:05:44.560 what they want to try to do over overall is 0:05:44.600 --> 0:05:50.080 to give you the ability to sink your information will 0:05:50.160 --> 0:05:52.359 will was use it in a general sense here different 0:05:52.440 --> 0:05:56.640 kinds of files to multiple devices, your iOS devices and 0:05:56.720 --> 0:05:59.800 your computers, and not just MAX but PCs as well. 0:06:00.040 --> 0:06:05.479 Hey how about Lennox. Well no, sorry at yes, that 0:06:05.960 --> 0:06:09.359 that would be a bunto one. UM and I have 0:06:09.360 --> 0:06:14.880 account there to actually, But anyway, h so for one thing, 0:06:14.920 --> 0:06:16.760 and where where should we start? Should we start with 0:06:16.760 --> 0:06:19.480 the music things. Let's start with storage. Okay, we're just okay. 0:06:19.560 --> 0:06:22.600 So so basically, your eye Cloud account would be a 0:06:22.640 --> 0:06:26.000 storage account where you could store uh. Now, primarily in 0:06:26.040 --> 0:06:30.479 the beta version, you're storing things like apps, books, and music, right, 0:06:30.680 --> 0:06:35.039 and UH you get by signing up, you get five 0:06:35.080 --> 0:06:38.200 gigabytes of storage for free. Now here's the Here are 0:06:38.200 --> 0:06:42.240 two things that make this really compelling. Uh. It will 0:06:42.279 --> 0:06:49.200 go through your iTunes library and we'll match uh any 0:06:49.200 --> 0:06:52.200 song that you've purchased through iTunes since you since you're 0:06:52.240 --> 0:06:55.320 registering it through your iTunes account. UH, any song that 0:06:55.320 --> 0:06:58.240 you purchased through iTunes automatically becomes part of your eye 0:06:58.279 --> 0:07:03.480 Cloud storage locker we'll call it, but does not count 0:07:03.480 --> 0:07:07.680 against your five gigabytes of storage. So if you've purchased, 0:07:08.080 --> 0:07:12.040 you know, five thousand songs through iTunes over the history 0:07:12.040 --> 0:07:14.120 of your iTunes account, all those songs are going to 0:07:14.200 --> 0:07:17.920 show up in your eye Cloud UH locker without you 0:07:18.040 --> 0:07:20.680 having to uh to have that kind of gainst your 0:07:20.680 --> 0:07:24.680 five gigabytes of storage. And you can share that information 0:07:24.720 --> 0:07:27.760 with any other device that's hooked up through your iTunes account, 0:07:27.840 --> 0:07:31.720 up to ten devices, which is another big move. Right. 0:07:32.120 --> 0:07:34.680 Five used to be the magic number for things like that, 0:07:34.720 --> 0:07:37.200 and you can do it wirelessly, which is the beautiful thing. 0:07:37.280 --> 0:07:40.000 So you could say, let's say that you have a 0:07:40.040 --> 0:07:42.800 desktop computer at home and that's like your media computer. 0:07:43.200 --> 0:07:45.240 You have a we'll call it. We'll say it's a 0:07:45.240 --> 0:07:47.040 Mac because this happens to be me. I've got a 0:07:47.040 --> 0:07:51.920 Mac media computer at home and that has my iTunes 0:07:52.000 --> 0:07:55.560 library on it, and then I sink my iPod to 0:07:55.920 --> 0:07:58.120 my iTunes library. So whenever I buy a new song, 0:07:58.160 --> 0:08:00.000 I have to sink my iPod in order to get it. 0:08:00.040 --> 0:08:01.880 Now I've got an older iPod. But let's say that 0:08:01.920 --> 0:08:04.120 I get a newer iPod. And then let's say we 0:08:04.440 --> 0:08:08.200 I buy some music on my uh, my iPod Touch 0:08:08.360 --> 0:08:12.280 or my iPhone. Then I have to sync my device 0:08:12.440 --> 0:08:14.880 to my computer. I have to, you know, it's it's 0:08:14.880 --> 0:08:16.840 a whole lot of steps in order to make sure 0:08:16.880 --> 0:08:21.280 that your music collection is is equal across multiple devices. Yes, 0:08:21.320 --> 0:08:23.280 and it's a pain in the neck to to uh 0:08:23.480 --> 0:08:26.640 to have to restore your music player, especially if it's 0:08:26.680 --> 0:08:29.200 got if you've got a large music collection. It even 0:08:29.240 --> 0:08:34.280 on a faster connection on the USB two for example, UM, 0:08:34.320 --> 0:08:37.320 which is you know, I know, not necessarily the fastest. 0:08:37.320 --> 0:08:40.160 There are other standards like USB three and Thunderbolt that 0:08:40.200 --> 0:08:45.680 are technically faster, but I mean reasonably fast by today's standards. Um, 0:08:45.720 --> 0:08:48.760 it's still gonna take you a while to upload you know, 0:08:49.080 --> 0:08:53.800 gigs of data these songs to your your iPod again. Right, 0:08:53.880 --> 0:08:57.080 So with iCloud, using your iTunes library to start with, 0:08:57.160 --> 0:08:59.320 you know, the purchase history you have to start with, 0:09:00.040 --> 0:09:02.439 uh it uh. The means that you don't have to 0:09:02.520 --> 0:09:06.000 upload those songs. That that's a huge advantage over things 0:09:06.040 --> 0:09:09.080 like the Amazon and Google approaches, where you do have 0:09:09.120 --> 0:09:11.880 to upload your files to that cloud storage in order 0:09:11.880 --> 0:09:14.800 to store them there. Right, So if I have five 0:09:14.800 --> 0:09:16.720 thousand songs on my computer and I want to use 0:09:16.760 --> 0:09:20.800 Google's approach, I have to actually upload those songs first 0:09:20.880 --> 0:09:23.680 to my Google account. So that's gonna take a while 0:09:23.840 --> 0:09:27.120 because upload speeds tend to be slower than download speeds 0:09:27.280 --> 0:09:29.800 because you know, people download more than they upload, so 0:09:29.920 --> 0:09:33.640 upstream is a slower data transfer rate. So if you're 0:09:34.520 --> 0:09:38.440 uploading a lot of content, depending on your Internet connection, 0:09:38.440 --> 0:09:42.560 it can take a long long time. So iTunes approach 0:09:42.640 --> 0:09:45.960 there saves you all that time. Right, Your purchase history 0:09:46.040 --> 0:09:50.680 becomes your library immediately in the iCloud. On top of that, 0:09:51.200 --> 0:09:53.360 if you have songs in your iTunes library that you 0:09:53.400 --> 0:09:56.160 did not purchase through iTunes. Let's say that you had 0:09:56.200 --> 0:09:59.600 a collection of cd s that you ripped from using 0:09:59.600 --> 0:10:02.760 iTunes and you've got them in your library, but you 0:10:02.800 --> 0:10:07.720 didn't purchase them through iTunes. Well, if iTunes has those 0:10:07.760 --> 0:10:11.000 albums and those songs in its library, that's got like 0:10:11.040 --> 0:10:13.920 eighteen million songs in the iTunes library. So if those 0:10:13.960 --> 0:10:16.960 songs appear in the iTunes library, what will happen is 0:10:17.600 --> 0:10:20.920 the the service will identify those songs and match it 0:10:21.080 --> 0:10:26.240 to the song that's in the iTunes library. Yeah, so basically, um, 0:10:26.280 --> 0:10:29.840 you know, say you have, um, I don't know, a 0:10:29.920 --> 0:10:33.120 cold Play album and your I'm just picking cold Play. 0:10:33.120 --> 0:10:37.000 It's a band that I don't particularly like. I you know, Sorry, 0:10:37.240 --> 0:10:38.800 I just picked something. I was gonna say, you too. 0:10:38.800 --> 0:10:42.079 I don't know why either of them. So sorry, Okay. 0:10:44.280 --> 0:10:46.640 So you know, let's say you have a record that's 0:10:46.720 --> 0:10:48.480 in your collection and you want to add it to 0:10:49.080 --> 0:10:53.439 your you know, your cloud storage. Um, as soon as 0:10:53.679 --> 0:10:56.880 it recognizes that you have that in there, it says, oh, well, 0:10:56.920 --> 0:10:59.480 we've already got that. Well we'll just give you. You 0:10:59.480 --> 0:11:01.600 don't have to uploaded, we'll put it in here for you. 0:11:01.640 --> 0:11:04.800 And the files that they're using are two fifty six 0:11:04.920 --> 0:11:09.360 K iTunes plus level files. So so it might even 0:11:09.400 --> 0:11:11.320 be like, let's say that you when you ripped the CD, 0:11:11.360 --> 0:11:14.160 you ripped it at a lower a lower rate than 0:11:14.520 --> 0:11:18.440 technically the higher rates one it essentially equates to as 0:11:18.480 --> 0:11:22.720 a higher rate in general means better sound or more 0:11:22.760 --> 0:11:26.559 accurate to the original version sound. So the more compression 0:11:26.600 --> 0:11:28.880 you use, the smaller bit rate that you encode the 0:11:28.920 --> 0:11:32.760 file ad basically means that you're leaving out more information 0:11:33.280 --> 0:11:36.120 in the music file. So it's not going to have 0:11:36.120 --> 0:11:40.319 his high fidelity. Depending upon your the sensitivity of your hearing, 0:11:40.360 --> 0:11:42.080 you may or may not be able to detect that 0:11:42.120 --> 0:11:45.240 with certain songs. Uh, my hearing has been to the 0:11:45.240 --> 0:11:48.559 point where I really don't tend to notice unless it's really, 0:11:48.600 --> 0:11:53.400 really really bad transfer. So yeah, so for me, it's 0:11:53.400 --> 0:11:54.920 not as big a deal. But it's a nice thing 0:11:54.960 --> 0:11:57.480 to know that that iTunes is going to match your 0:11:57.559 --> 0:12:00.440 songs and probably match them to a quality that is 0:12:00.640 --> 0:12:04.240 superior to whatever it was you were you were using before. Yeah, 0:12:04.320 --> 0:12:06.480 and and this is where this is where I'm a 0:12:06.520 --> 0:12:10.200 little fuzzy, because it suggests that those files are in 0:12:10.640 --> 0:12:13.080 our stored in the cloud, and therefore that's how you 0:12:13.080 --> 0:12:17.839 would access the access them, um, rather than having it, 0:12:18.120 --> 0:12:21.640 you know, download back to your music player. I think 0:12:22.760 --> 0:12:25.960 it's yeah, it's it's worded in a very vague way, 0:12:26.000 --> 0:12:29.400 but based upon what I've been reading, it sounds to 0:12:29.440 --> 0:12:33.439 me that you would then, uh, let's say again, We'll 0:12:33.520 --> 0:12:35.959 use the example of my my desktop computer at home 0:12:36.360 --> 0:12:38.800 and I've got my master music collection on there, and 0:12:38.800 --> 0:12:41.720 then I've got several eye devices. Um, it sounds to 0:12:41.760 --> 0:12:45.000 me that even the iTunes match part would just mean 0:12:45.040 --> 0:12:49.160 that if my brand new iPhone, I brought my brand 0:12:49.200 --> 0:12:52.120 new iPhone home and registered it and connected it to 0:12:52.120 --> 0:12:55.120 my iTunes account, it would then download all those songs 0:12:55.160 --> 0:12:58.480 that wouldn't stream them, it would download them and store 0:12:58.520 --> 0:13:03.000 them locally on the uh the iPhone. Uh So that's 0:13:03.040 --> 0:13:05.960 my interpretation based upon the wording. And again, like we said, 0:13:05.960 --> 0:13:10.439 it's pretty vague. Uh there there. Maybe it's vague because 0:13:10.440 --> 0:13:12.960 they plan to open up streaming later. It maybe that 0:13:13.400 --> 0:13:16.439 streaming is still a sensitive topic with the music labels 0:13:16.440 --> 0:13:19.480 that iTunes has partnered with. UM, I mean, that's one 0:13:19.480 --> 0:13:21.120 of the reasons why I think they went with the 0:13:21.200 --> 0:13:24.440 download method is because you know, they actually had to 0:13:24.520 --> 0:13:27.520 partner with these music labels, as opposed to Amazon's approach 0:13:27.520 --> 0:13:31.400 where they're like, this is just another way of accessing 0:13:31.440 --> 0:13:35.600 content you already own. iTunes wanted this to be uh 0:13:36.320 --> 0:13:43.000 more of a widespread data management system where you could 0:13:43.000 --> 0:13:45.120 have that you can have access to the same data 0:13:45.200 --> 0:13:50.520 across multiple devices. So uh, I think it's still download, 0:13:50.600 --> 0:13:53.640 upload and download, it's not streaming. That's that's based upon 0:13:53.920 --> 0:13:57.960 my interpretation of what they've written, and I understand that. Um. 0:13:58.000 --> 0:14:01.240 The other piece being that, uh what we've talked about 0:14:01.280 --> 0:14:06.320 basically the free option here because basically anyone with an account, um, 0:14:06.360 --> 0:14:10.600 an iTunes account should be able to get iCloud just 0:14:10.640 --> 0:14:15.240 as part of the service. But you can. They're offering 0:14:15.240 --> 0:14:18.480 an option for ninety nine a year where you can 0:14:18.720 --> 0:14:23.160 hold your entire collection. So that would be you know, 0:14:23.240 --> 0:14:24.840 for a lot of people, that's going to be more 0:14:25.000 --> 0:14:27.560 than an iPod will hold well, depending on size of 0:14:27.560 --> 0:14:30.120 your iPod and your music collection. But you know, people 0:14:30.120 --> 0:14:34.280 with very large music collections, uh may have gigabytes or 0:14:34.280 --> 0:14:38.240 even terabytes worth of music, and you know, there's not 0:14:38.280 --> 0:14:41.160 an iPod yet that will hold a terabyte. Um now, 0:14:41.200 --> 0:14:43.880 granted give it a week. If all of your if 0:14:43.880 --> 0:14:46.280 all of your music, and all of your books, and 0:14:46.320 --> 0:14:48.400 all of your apps were purchased through the iTunes store, 0:14:48.480 --> 0:14:50.760 then the five gigabytes is all you need anyway, because 0:14:50.760 --> 0:14:53.840 it doesn't count against the five gigabytes. It's when you 0:14:53.880 --> 0:14:58.400 start talking about music that is outside of of the 0:14:58.520 --> 0:15:02.360 iTunes library when you start having problems. So let's say 0:15:02.360 --> 0:15:06.240 that you've you've ripped a CD from a local band 0:15:06.640 --> 0:15:09.400 that doesn't that's not on iTunes, and you want that 0:15:09.480 --> 0:15:12.440 music available, Well, then you're gonna have to have you're 0:15:12.440 --> 0:15:15.560 gonna actually have to pay that that yearly fee to 0:15:15.680 --> 0:15:20.360 have the option to upload those files to your Actually, 0:15:20.400 --> 0:15:22.200 I guess not because you've got the five gigabytes, but 0:15:22.360 --> 0:15:25.360 those those songs will count against the five gigabytes and storage. 0:15:25.400 --> 0:15:31.280 Maybe they're particularly prolific band with many many records. Um yeah, 0:15:31.320 --> 0:15:34.680 the iTunes the iTunes Match service is kind of interesting 0:15:34.760 --> 0:15:38.080 that that actually has the limit on it is a 0:15:38.120 --> 0:15:42.760 twenty five thousand song limit. So if you've got now, 0:15:43.280 --> 0:15:46.520 if you've got a whole bunch of CDs that you've 0:15:46.560 --> 0:15:48.880 ripped and then and you may have to start making 0:15:48.920 --> 0:15:51.720 some choices once you're like, oh this is twenty hundred 0:15:51.800 --> 0:15:53.920 seventy five, which one was is gonna be twenty four thousand, 0:15:54.000 --> 0:15:58.440 hundred seventy six. Well make a meatloads songs that way, 0:15:58.440 --> 0:16:04.640 I get more quant to T. So again, we were 0:16:04.720 --> 0:16:08.280 we were talking earlier about the I'm sorry you always 0:16:08.320 --> 0:16:14.720 throw me off with me loo, I'm kind of hungry myself. UM. Yeah. 0:16:14.760 --> 0:16:18.760 The thing is it's not just gonna be about video 0:16:18.840 --> 0:16:21.080 and audio. I mean there's really not a video option 0:16:21.360 --> 0:16:26.920 here yet, um. But there are other other compelling bits 0:16:26.960 --> 0:16:30.400 to this service. Sorry for the again bits pun UM. 0:16:30.640 --> 0:16:34.960 For example, photo stream UH. Photo stream behaves a little 0:16:35.040 --> 0:16:38.600 similarly to the to the music portion of the service. 0:16:38.800 --> 0:16:41.960 If you have a an iPhone or an iPod, toucher 0:16:42.000 --> 0:16:44.600 an iPad with a camera UM, and you take a 0:16:44.640 --> 0:16:49.360 photo while you're out with it, it should use iCloud 0:16:49.440 --> 0:16:51.720 automatically to sink it. Let's say you have one of 0:16:51.800 --> 0:16:55.000 all of the above plus a a computer UM where 0:16:55.040 --> 0:16:58.720 you have an iTunes account, it should download everything over 0:16:58.840 --> 0:17:03.840 to uh the different machines. So you've been on a 0:17:03.960 --> 0:17:06.240 trip and you took your your phone with you and 0:17:06.280 --> 0:17:09.880 you've taken pictures, it will sink to your home computer 0:17:10.000 --> 0:17:12.520 so that you can show them off there without you 0:17:12.560 --> 0:17:15.439 having to upload them. Likewise, if you take pictures with 0:17:15.520 --> 0:17:19.800 a a UH standalone digital camera and you upload them, 0:17:20.200 --> 0:17:22.679 say through I Photo on a Mac, you would be 0:17:22.720 --> 0:17:26.160 able to share those to your phone and your I 0:17:26.160 --> 0:17:29.000 iPod Touch and your iPad, assuming you have all those 0:17:29.000 --> 0:17:32.720 devices UM, without having to take an extra step to 0:17:32.800 --> 0:17:35.120 do that. It does that automatically. Now, it only will 0:17:35.160 --> 0:17:38.480 save your last UH. It keeps what they call a 0:17:38.600 --> 0:17:41.640 rolling collection of your last thousand photos. So you get 0:17:41.680 --> 0:17:45.040 into a thousand, fifteen, thousand, sixteen, the first fifteen and 0:17:45.080 --> 0:17:49.600 sixteen photos chronologically will start to drop off. They won't 0:17:49.600 --> 0:17:51.440 go any they won't go anywhere, but they won't be 0:17:51.480 --> 0:17:54.439 in your eye cloud anyway. Right, Well, the UM and 0:17:54.520 --> 0:17:56.000 I thought I would go ahead and mention this because 0:17:56.000 --> 0:17:59.159 I'm sure we're gonna get email UH or Facebook comments 0:17:59.240 --> 0:18:02.840 or Twitter comments. So year that's what gives you the 0:18:02.880 --> 0:18:07.840 access to iTunes match so so without even though as 0:18:07.880 --> 0:18:10.080 far as I can tell, the the music that would 0:18:10.080 --> 0:18:14.240 be matched through iTunes, I don't think that would be 0:18:14.280 --> 0:18:17.879 counted against your five gigabytes, but I'm not entirely sure. 0:18:18.520 --> 0:18:21.120 I know that any music you've purchased through iTunes will 0:18:21.200 --> 0:18:25.280 not count against the five gigabytes of storage. The music 0:18:25.320 --> 0:18:28.200 that's been matched through iTunes that might actually count against 0:18:28.200 --> 0:18:30.399 your five gigabytes. So this is the music that you 0:18:30.480 --> 0:18:32.679 own that is also on iTunes, but you did not 0:18:32.760 --> 0:18:37.400 purchase it through iTunes. UM, so I know you. There 0:18:37.480 --> 0:18:42.119 is the yearly fee, which is uh, and I based 0:18:42.200 --> 0:18:45.080 upon this, I'm guessing that does count against your your 0:18:45.240 --> 0:18:49.520 storage space, which might be why they said the song limit. Um, 0:18:49.560 --> 0:18:52.399 I'm not entirely certain of that. Like I said, a 0:18:52.440 --> 0:18:54.879 lot of this is vague right now, and and I 0:18:54.920 --> 0:18:57.000 have I just got back for a vacation and I 0:18:57.000 --> 0:19:00.240 haven't had a chance to to play with this yet. UM, 0:19:00.240 --> 0:19:03.480 but yeah, it's uh. The it is interesting. They do 0:19:03.560 --> 0:19:09.000 a a UM comparison of Apple's I Cloud service against 0:19:09.160 --> 0:19:12.159 Amazon Service and Google Service on Apple, so you can 0:19:12.200 --> 0:19:16.159 guess how it shapes up. But they talk about how 0:19:17.160 --> 0:19:19.640 the methods, like the fact that you do not need 0:19:19.680 --> 0:19:23.840 to scan your music collection to start off an iCloud. 0:19:23.920 --> 0:19:26.760 Anything that you've purchased through iTunes will automatically be put 0:19:26.880 --> 0:19:28.800 up there. So you don't have to upload it, and 0:19:28.840 --> 0:19:30.520 then of course the iTunes match if you go with 0:19:30.600 --> 0:19:33.520 that method, again, you don't need to upload that music. 0:19:33.560 --> 0:19:36.359 It just has to be matched to iTunes library and 0:19:36.400 --> 0:19:38.920 then that will be put into your eye Cloud as well, 0:19:39.280 --> 0:19:42.080 whereas with Amazon and Google you both have to upload 0:19:42.119 --> 0:19:44.560 those files to that system in order to use those 0:19:45.040 --> 0:19:49.000 um and then that there is a specific app from 0:19:49.080 --> 0:19:53.560 for the desktop computers and laptops which is called iTunes. 0:19:53.680 --> 0:19:55.520 You may have heard of it that you use to 0:19:55.680 --> 0:19:59.000 access the eye Cloud, whereas Amazon and Google you access 0:19:59.040 --> 0:20:03.640 through a web brow are uh them that talks about that. 0:20:03.800 --> 0:20:06.200 You know it has the upgrade option to the two 0:20:06.520 --> 0:20:11.840 fifty six k UH rate for the songs um and 0:20:11.880 --> 0:20:16.439 that the price to have access to five thousand or 0:20:16.480 --> 0:20:18.800 twenty thousand songs is the same. It's twenty ninety nine 0:20:18.800 --> 0:20:20.720 a year. You can have up to twenty thousand songs 0:20:20.760 --> 0:20:23.880 that way, But if you wanted to do that with Amazon, uh, 0:20:23.920 --> 0:20:26.760 the price for five thousand songs would be fifty dollars 0:20:26.760 --> 0:20:29.639 a year and for twenty thousand songs two hundred dollars 0:20:29.640 --> 0:20:33.200 a year. And then for Google, it's question mark, question 0:20:33.240 --> 0:20:36.720 mark question mark because it hasn't been mentioned yet, so 0:20:37.600 --> 0:20:40.200 we're still hashing that out. And we should also mention that, 0:20:40.320 --> 0:20:43.600 you know, we've talked a lot about music because obviously 0:20:43.680 --> 0:20:47.360 the the tie in with iTunes means that that's where 0:20:47.359 --> 0:20:49.520 a lot of the focus is going. Uh. And we've 0:20:49.520 --> 0:20:51.520 also talked about you know, any books you purchased through 0:20:51.680 --> 0:20:54.000 iTunes or any apps you purchased through iTunes will live 0:20:54.040 --> 0:20:56.840 in the eye cloud as well, but you can also 0:20:56.920 --> 0:21:01.520 have other kinds of files and documents stored your eye cloud. Yeah. Yeah, 0:21:01.520 --> 0:21:03.600 Before before we get away from that, I wanted to 0:21:03.640 --> 0:21:07.200 point out that UM iTunes match is scheduled to hit 0:21:07.240 --> 0:21:10.280 this fall. Yeah. I believe that's supposed to be concurrent 0:21:10.320 --> 0:21:14.480 with the iOS five UM. But you can get your 0:21:14.680 --> 0:21:19.280 your new and past purchases SINCD now via beta and 0:21:19.320 --> 0:21:21.280 I had I had forgotten to mention that. So if 0:21:21.320 --> 0:21:25.880 you've UM, if you've bought music on on your home 0:21:25.920 --> 0:21:29.080 computer and you want to get it on uh, say 0:21:29.119 --> 0:21:32.520 you forgot to sink your the music over. You should 0:21:32.560 --> 0:21:36.600 be able to see it in iTunes on an iPhone 0:21:36.720 --> 0:21:39.399 or an I pad for example, sitting in front of 0:21:39.400 --> 0:21:41.760 me where my notes are UM, and I should be 0:21:41.800 --> 0:21:43.960 able to Uh, if I wanted to turn off my 0:21:44.000 --> 0:21:46.080 notes and go look, I should theoretically be able to 0:21:46.160 --> 0:21:48.840 see that past stuff and download it if I want 0:21:48.840 --> 0:21:52.400 to do that device, which is again in beta already now. 0:21:52.480 --> 0:21:55.480 But yeah, and you can set the download feature to 0:21:55.600 --> 0:21:57.920 automatic if you wanted to, which means that every time 0:21:57.960 --> 0:22:01.440 you purchased a song through iTunes or an app or 0:22:01.480 --> 0:22:05.320 a book through iTunes, anytime you purchased one, it would 0:22:05.320 --> 0:22:08.760 automatically download to all devices that were set to automatic. 0:22:08.960 --> 0:22:10.639 I don't think I would want to do that. You 0:22:10.640 --> 0:22:13.199 can also do it manually, so because I have, I 0:22:13.320 --> 0:22:16.159 used my devices separately for separate reasons, and a lot 0:22:16.200 --> 0:22:18.639 of people do. Write like some people might have a 0:22:18.720 --> 0:22:22.400 specific iOS device that they use when they're working out, 0:22:22.760 --> 0:22:26.359 and they have a workout song list, and they don't 0:22:26.480 --> 0:22:29.639 want their Broadway musical list to being mixed up with 0:22:29.680 --> 0:22:32.800 their workout song list because you know, put on a 0:22:32.840 --> 0:22:34.679 Happy Face is not the song they want to hear 0:22:34.720 --> 0:22:38.400 while they're on the elliptical. So uh, yeah, there there 0:22:38.400 --> 0:22:40.320 are reasons why you might want to have some of 0:22:40.359 --> 0:22:42.600 your devices set to manual. Especially let's say that you 0:22:42.600 --> 0:22:45.320 have an enormous music collection and you don't want your 0:22:45.680 --> 0:22:49.719 smartphone to be completely bogged down with music, um when 0:22:49.760 --> 0:22:51.480