WEBVTT - How Shazam and Midomi Work 0:00:00.320 --> 0:00:02.880 Brought to you by the reinvented two thousand twelve camera. 0:00:03.240 --> 0:00:08.920 It's ready. Are you get in touch with technologies? With 0:00:09.039 --> 0:00:16.120 tech stuff from how stuff works dot com. You've heard 0:00:16.160 --> 0:00:19.760 the rumors before, perhaps, and whispers written between the lines 0:00:19.800 --> 0:00:24.759 of the textbooks. Conspiracies, paranormal events, all those things that 0:00:24.880 --> 0:00:28.760 disappear from the official explanations. Tune in and learn more 0:00:28.800 --> 0:00:30.560 of the stuff they don't want you to know in 0:00:30.600 --> 0:00:43.200 this video podcast from how stuff works dot com. Hello, everybody, 0:00:43.400 --> 0:00:45.960 welcomes to text stuff. My name is Chris Platt, and 0:00:45.960 --> 0:00:49.080 I'm an editor here at how stuff works dot com, 0:00:49.080 --> 0:00:53.080 sitting across from me as usual as senior writer Jonathan Strickland. 0:00:53.280 --> 0:00:57.600 Hey there, do you think people can identify our voices 0:00:57.600 --> 0:01:00.680 pretty easily? Well, I would imagine, so we don't sound 0:01:00.720 --> 0:01:04.319 exactly alike or anything at all alike, really, I know, 0:01:04.440 --> 0:01:06.240 But I mean, do you think people could listen to us, 0:01:06.280 --> 0:01:08.280 people who have listened to the podcast before and say, 0:01:08.319 --> 0:01:12.280 I know that's Jonathan and that's Chris. Possibly, although I 0:01:12.360 --> 0:01:15.119 have heard at least one person claim after we did 0:01:15.120 --> 0:01:17.880 a phone interview that I was the only person who 0:01:17.920 --> 0:01:22.600 sounded the way I did on the podcast. But you 0:01:22.640 --> 0:01:24.720 know what makes you look taller. You were sitting further 0:01:24.959 --> 0:01:26.840 You were sitting further away from the phone, and it 0:01:26.880 --> 0:01:28.440 was on speaker phone at the time, so that may 0:01:28.480 --> 0:01:32.039 have played apart. But um, what we're getting to here 0:01:32.240 --> 0:01:35.200 is kind of working our way slowly around to the 0:01:35.319 --> 0:01:38.920 topic we're gonna discuss today. But that actually comes courtesy 0:01:38.959 --> 0:01:46.840 of a little listener mail. This listener mail comes from 0:01:46.959 --> 0:01:51.440 Mason in Iowa, and he says, Hey, there, love the podcast. 0:01:51.800 --> 0:01:54.800 How about an episode on how Shazam and Medomi work? 0:01:55.160 --> 0:01:59.240 How does the program segment compare against a database and 0:01:59.280 --> 0:02:02.920 return result? It's so darn quickly, especially when I'm the 0:02:02.920 --> 0:02:07.360 one doing the singing in Medomi's case. Well, Mason, first 0:02:07.400 --> 0:02:09.200 of all, I should I should point out I would 0:02:09.200 --> 0:02:11.480 be remiss if I did not point out that we 0:02:11.520 --> 0:02:14.160 have a sister podcast called Stuff from the B Side, 0:02:14.560 --> 0:02:19.280 and they actually did an episode about this kind of software. However, 0:02:19.480 --> 0:02:23.440 we're gonna tackle it ourselves because we actually tend to 0:02:23.480 --> 0:02:26.560 cover the same topics now and then we've we've done 0:02:26.600 --> 0:02:29.720 both done the electric guitar, so I see no reason 0:02:29.760 --> 0:02:32.079 for us not to uh tackle this one. Sure, and 0:02:32.120 --> 0:02:35.080 there's uh you know, we can add a little stuff 0:02:35.080 --> 0:02:38.320 that they didn't add. Sure, yeah, like puns that in 0:02:38.440 --> 0:02:41.079 some updates about what's going on. Oh oh yeah, we 0:02:41.120 --> 0:02:44.240 can do that too. So let's how about which one 0:02:44.240 --> 0:02:46.840 do you us start with? Zam or Medomi? Um? Well, 0:02:46.880 --> 0:02:49.119 she Zam has been around longer, that's true. She Zam 0:02:49.120 --> 0:02:52.000 has been around since the early two thousands. Like two 0:02:52.040 --> 0:02:54.400 thousand two was when it first the company first started. 0:02:54.400 --> 0:02:56.800 In two thousand thirty was really when the service started 0:02:56.840 --> 0:02:59.560 to get some attention. Actually I had it down as 0:03:00.000 --> 0:03:04.600 sam starting in two thousand really wow, okay, so I 0:03:04.720 --> 0:03:08.840 stand corrected. Yeah, the the earliest version of Shazam was 0:03:09.639 --> 0:03:12.320 an interesting version. You would you would hold your cell 0:03:12.360 --> 0:03:15.040 phone up to the source of music and you would 0:03:15.200 --> 0:03:18.519 uh send that to the Shazam service, and you would 0:03:18.520 --> 0:03:22.720 get a text message back identifying the song. And I 0:03:22.760 --> 0:03:25.119 can see why this could be considered like some sort 0:03:25.120 --> 0:03:28.280 of weird magic. I mean, how could a service figure 0:03:28.320 --> 0:03:30.440 that out so quickly because it was usually just a 0:03:30.480 --> 0:03:32.799 matter of a few seconds between when you sent the 0:03:33.120 --> 0:03:37.280 the music and when or when you held the phone 0:03:37.320 --> 0:03:39.200 up to the music source and when you got the reply. 0:03:39.960 --> 0:03:45.480 Oh it's magic, you know, right. Uh, you have to 0:03:45.560 --> 0:03:50.960 believe we are magic. We can do this. You appreciate 0:03:51.000 --> 0:03:53.240 that you do in the Zany reference, well, yeah, you're welcome. 0:03:53.280 --> 0:03:56.400 I was gonna go with Loving Spoonful, but even I think, Sanna, 0:03:56.440 --> 0:04:00.160 do we already lost everybody Loving Spoonful? I don't. There's 0:04:00.160 --> 0:04:01.680 probably three of you out there who even know who 0:04:01.680 --> 0:04:04.960 that is. So but yeah, I think you're right. And 0:04:05.160 --> 0:04:09.480 it's um stuff like this and in voice recognition. I 0:04:09.480 --> 0:04:10.880 think it's one of those things that just sort of 0:04:10.880 --> 0:04:13.560 surprises people because you don't think that the computer has 0:04:13.680 --> 0:04:18.040 enough I don't know intelligence to figure it out. Wait, 0:04:18.120 --> 0:04:19.839 wait a minute, that's a machine, and the machine figure 0:04:19.880 --> 0:04:21.360 out what I was doing there. Let's talk about how 0:04:21.400 --> 0:04:26.360 Shazam does this. Now, what Shazam does It breaks down 0:04:26.400 --> 0:04:30.880 any recording into um, just some very simple data. They 0:04:30.960 --> 0:04:36.120 call it fingerprinting. They fingerprints songs. And if you were 0:04:36.120 --> 0:04:38.000 to if you were to try and if you were 0:04:38.080 --> 0:04:40.719 to try and and and chart out a song from 0:04:40.760 --> 0:04:44.320 start to finish with all the different elements that go 0:04:44.480 --> 0:04:47.440 into that, like you know, you're you're essentially assigning data 0:04:47.480 --> 0:04:50.680 points to every single frequency in that song, you would 0:04:50.760 --> 0:04:54.120 end up with a fairly substantial amount of data yeah, 0:04:54.160 --> 0:04:57.480 and Shazam has something like one point seven one point 0:04:57.480 --> 0:05:00.600 eight million songs in the database, probably even more than 0:05:00.640 --> 0:05:03.520 that now because that was the most recent data I 0:05:03.520 --> 0:05:07.240 saw too, but I think that data was yeah. Yeah. 0:05:07.440 --> 0:05:11.680 So what sasam does is they take the peaks and 0:05:11.720 --> 0:05:14.560 the troughs, the highest points in the frequency and the 0:05:14.600 --> 0:05:17.960 lowest points of the frequency to map out patterns and 0:05:18.040 --> 0:05:20.520 the fingerprint songs in that way. So they're cutting out 0:05:20.560 --> 0:05:23.520 a lot of the information in the middle and uh. 0:05:23.640 --> 0:05:26.360 That actually saves lots of space. It also saves time 0:05:26.400 --> 0:05:29.560 when you're trying to match one song or or one 0:05:29.640 --> 0:05:32.400 clip to a database full of songs. So when you 0:05:32.440 --> 0:05:36.039 hold your phone up to a SEV speakers or uh, 0:05:36.160 --> 0:05:39.000 you know whatever whatever is making the music, um, it 0:05:39.279 --> 0:05:43.760 starts to uh. It sends that clip to the Shazam service, 0:05:44.240 --> 0:05:47.920 which then immediately analyzes it and looks at those peaks 0:05:47.920 --> 0:05:51.240 and troughs and tries to find a match in the database. Now, 0:05:51.880 --> 0:05:54.719 the reason why it's so fast is it Shazam keeps 0:05:54.800 --> 0:05:58.520 all of this in the computer's memory. It's not stored 0:05:58.520 --> 0:06:01.560 on a hard drive. The the database doesn't have to 0:06:02.000 --> 0:06:04.560 you know, the process sucsessor doesn't have to search the 0:06:04.600 --> 0:06:07.280 hard drive to find a match. Everything's in memory, which 0:06:07.320 --> 0:06:09.240 means they have to have lots and lots of machines 0:06:09.880 --> 0:06:12.760 to uh to be able to hold all those songs 0:06:12.839 --> 0:06:16.560 within computer memory, or at least the fingerprints of those songs. 0:06:16.800 --> 0:06:19.360 And so once it finds a match, it then sends 0:06:19.400 --> 0:06:23.320 that data back to you, and usually it's it's fairly accurate. 0:06:23.360 --> 0:06:26.880 It's especially accurate for more modern music, the stuff that's 0:06:26.880 --> 0:06:29.400 been out for the last couple of years. Um, if 0:06:29.400 --> 0:06:32.520 you start going back further, you may start encountering songs 0:06:32.560 --> 0:06:35.159 that just aren't not in the database, and so you 0:06:35.200 --> 0:06:39.239 won't get a legitimate match. And there are cases where 0:06:40.040 --> 0:06:42.520 if you have a song that is very similar to 0:06:42.520 --> 0:06:45.239 another song, it may come back with an incorrect match. 0:06:45.360 --> 0:06:47.240 But that doesn't happen that often. I suppose if you 0:06:47.279 --> 0:06:50.240 were to, you know, try and identify a Creed or 0:06:50.320 --> 0:06:53.360 Nickelback song, it would might come back wrong because all 0:06:53.360 --> 0:06:57.080 those damn songs sound the same to me. I mean, seriously, kids, 0:06:57.200 --> 0:07:01.320 find some better music, all right, So get off his lawn, Yes, 0:07:01.520 --> 0:07:03.720 get off my lawn. While I listened to, you know, 0:07:03.880 --> 0:07:05.440 music that they made in the good old days, like 0:07:05.480 --> 0:07:09.480 the late nineteen seventies in London. Um, like the sex pistols. 0:07:09.560 --> 0:07:13.320 So not that not that modern stuff that's just junk 0:07:15.360 --> 0:07:19.520 as an email to anyway, there's there are they're actually 0:07:19.560 --> 0:07:22.640 papers online. They go into very great to tail about 0:07:22.680 --> 0:07:27.440 the algorithms that they that Shazam uses to identify to 0:07:27.560 --> 0:07:29.800 match up songs and and to send the data back 0:07:29.840 --> 0:07:31.920 to you. Yeah, they go into quite a bit of 0:07:31.960 --> 0:07:35.840 depth and as our actually as our sister podcast pointing out, 0:07:35.840 --> 0:07:39.880 as uh John and Mark talked about, they used a 0:07:40.040 --> 0:07:43.520 three dimensional graph to do this. Yeah, it's kind of cool. Yeah, 0:07:43.520 --> 0:07:45.760 it's called a uh, well you can call it a 0:07:45.800 --> 0:07:51.320 couple different things of time frequency graph where a spectrogram, um, sorry, 0:07:51.360 --> 0:07:56.200 spectrogram and uh, basically it's a it's three dimensional and 0:07:56.200 --> 0:07:59.360 that it goes it shows you over time how the 0:07:59.520 --> 0:08:04.080 you know, theeks and valleys of the song frequencies change, um. 0:08:04.600 --> 0:08:08.200 And that's kind of interesting that that it can that 0:08:08.240 --> 0:08:10.160 it's able to do that in the first place. But 0:08:10.960 --> 0:08:12.960 that's how it's you know, that's how it's looking at it, 0:08:12.960 --> 0:08:15.640 and that's having the element of time in there is 0:08:15.640 --> 0:08:18.880 crucial because otherwise, um, you know, wouldn't be able to 0:08:19.000 --> 0:08:21.680 uh look at that Yeah. The the cool thing about 0:08:21.680 --> 0:08:25.360 this services that you can hold your phone up to 0:08:25.440 --> 0:08:28.600 any point of the song and and as long as 0:08:28.640 --> 0:08:31.880 you're able to get about fifteen seconds worth of of 0:08:31.880 --> 0:08:36.079 of content, then that's enough for sam to work with 0:08:36.200 --> 0:08:38.720 to find a match. So it doesn't have to be 0:08:38.760 --> 0:08:40.160 the beginning of the song, it doesn't have to be 0:08:40.160 --> 0:08:42.360 the end. It can be at any point, and as 0:08:42.440 --> 0:08:44.760 long as it is able to map out those troughs 0:08:44.760 --> 0:08:48.600 and valleys accurately, then you should be able to get 0:08:48.600 --> 0:08:52.000 a pretty good result. There are some things that can 0:08:52.080 --> 0:08:54.560 cause some problems besides the fact that some songs do 0:08:54.640 --> 0:08:56.560 sound alike. I mean that I was kind of making 0:08:56.559 --> 0:08:58.680 a joke there, but that could happen if you had 0:08:59.080 --> 0:09:01.400 if you're holding up a phone to a part where 0:09:01.400 --> 0:09:03.439 there was it was sampling another song and it was 0:09:03.480 --> 0:09:06.320 long enough, you could conceivably get the wrong result. But 0:09:06.400 --> 0:09:10.920 also if there's ambient sound that's interfering in the area, 0:09:11.160 --> 0:09:13.959 you may not be able to get a result because 0:09:14.520 --> 0:09:17.080 you know, it can't identify the song because it's getting 0:09:17.120 --> 0:09:20.920 all these other sound inputs that are mixing it up. Yeah, 0:09:20.920 --> 0:09:22.680 I mean that's one of the things they sort of advertise. 0:09:22.760 --> 0:09:25.520 Wishes am is that you could take your phone around 0:09:26.200 --> 0:09:28.959 the mall, for example, or you know, on the radio 0:09:29.000 --> 0:09:31.520 in your car, um and hold it up to the 0:09:31.840 --> 0:09:35.160 speaker and it'll tell you what song that is. Well, 0:09:35.240 --> 0:09:36.840 I mean, if you're at the mall, you're dealing with 0:09:36.880 --> 0:09:39.720 all those people at the mall, You're dealing with perhaps 0:09:39.720 --> 0:09:44.800 conflicting songs coming from different places. We're acoustics, the distance 0:09:44.800 --> 0:09:46.960 from you to the speaker. I mean, there are all 0:09:47.040 --> 0:09:49.000 kinds of things can interfere with that. Not to mention 0:09:49.559 --> 0:09:54.480 your cell phone frequence frequency, you know, cutting out suddenly 0:09:54.520 --> 0:10:00.839 you're yes, so I've uh yeah, I thankfully there was 0:10:00.880 --> 0:10:03.920 a visual queue there. You guys don't get to see 0:10:03.920 --> 0:10:06.600 because this is an audio podcast. Brows did go up 0:10:06.600 --> 0:10:09.440 about a foot. That was nice. I was like, I know, 0:10:09.559 --> 0:10:13.000 I'm not supposed to talk now. Um No, I've used 0:10:13.040 --> 0:10:16.560 this this application several times and uh and I have. 0:10:16.760 --> 0:10:20.280 I've had varying degrees of success. There's a a theater 0:10:20.400 --> 0:10:22.720 I go to on a fairly regular basis at a 0:10:22.800 --> 0:10:27.520 stage play theater, not a cinema theata. I got to 0:10:27.559 --> 0:10:32.080 the Theatah fairly regularly actually, and they have some They 0:10:32.080 --> 0:10:35.000 have a pretty cool mix of of pre show and 0:10:35.080 --> 0:10:37.840 post show music that they play on the sound system, 0:10:37.920 --> 0:10:40.080 And there have been a couple of times where there's 0:10:40.080 --> 0:10:42.480 been songs that I played that I just I didn't recognize, 0:10:43.280 --> 0:10:46.680 and Shazam is pretty good at identifying those. The hard 0:10:46.720 --> 0:10:50.280 part is being able to get a long enough section 0:10:50.360 --> 0:10:54.600 where people aren't talking loud so loudly that it's interfering 0:10:54.640 --> 0:10:59.400 with the sample, right, So there have been times where 0:10:59.440 --> 0:11:02.079 I've stood next to the speaker and held my phone 0:11:02.160 --> 0:11:04.199 up to it. But now there's problems with that too, 0:11:04.200 --> 0:11:06.800 because if the volume is too loud, then you get 0:11:06.840 --> 0:11:09.600 some distortion and then it doesn't really work in that 0:11:09.640 --> 0:11:14.120 way either. But also there's this incredibly obscure Japanese song 0:11:14.200 --> 0:11:17.160 that they play that Shasam just doesn't seem to recognize. 0:11:17.240 --> 0:11:19.520 So I'm gonna have to break down and ask someone 0:11:19.559 --> 0:11:22.520 at the theater what the heck it is. Yeah, and 0:11:22.520 --> 0:11:25.280 then there's the the other factor, you know, the part 0:11:25.280 --> 0:11:27.680 where you're standing there holding your cell phone up to 0:11:27.800 --> 0:11:29.640 a speaker and people are starting to wonder what the 0:11:29.679 --> 0:11:33.640 heck you're doing. But I mean, if I start worrying 0:11:33.640 --> 0:11:36.760 about what people think of me, now, I mean, come on, 0:11:36.960 --> 0:11:39.920 I've made it this far, why should I worry now? 0:11:40.280 --> 0:11:42.000 So let's let's kind of shift over a little bit 0:11:42.000 --> 0:11:45.520 and talk about Medomi, which is a little different from Shasanna. 0:11:45.640 --> 0:11:51.400 There's actually a few interesting uh and and fairly major differences, 0:11:51.480 --> 0:11:54.640 one of which is that the database that that Medomi 0:11:54.800 --> 0:11:58.920 uses is not it's not collected by the company necessarily, 0:11:59.000 --> 0:12:04.400 it's user jim rated. Users of Medomi have sung songs 0:12:04.480 --> 0:12:09.359 or hummed songs or whistled songs into their phones and identified, 0:12:09.480 --> 0:12:13.280 you know, tagged the file as being a certain song, 0:12:13.920 --> 0:12:17.920 and the user community tends to comment on these, vote 0:12:17.960 --> 0:12:22.880 him up or down? Uh, submit their own version. Yeah, yeah, 0:12:23.200 --> 0:12:25.000 what are you kidding? That doesn't sound like that. Yeah, 0:12:25.040 --> 0:12:27.600 here's my version, because god lord, the one that's in 0:12:27.640 --> 0:12:30.200 the database is terrible. And you could you could sing 0:12:30.280 --> 0:12:32.440 your own version and upload it to medomie and then 0:12:32.440 --> 0:12:35.640 people can vote on which one is the more representative 0:12:35.800 --> 0:12:40.160 version of the song. The wiki model, right, and the 0:12:40.200 --> 0:12:43.320 idea behind Medomi is that, you know, with Shazam, you 0:12:43.360 --> 0:12:46.199 really need the original source or you need you need 0:12:46.240 --> 0:12:49.520 to be able to hold the phone up to something 0:12:49.520 --> 0:12:53.239 that's playing the actual song. You can't necessarily sing it yourself, 0:12:53.800 --> 0:12:56.240 or even if there's a band playing it live. That 0:12:56.280 --> 0:12:58.360 doesn't necessarily mean it's going to be able to identify 0:12:58.440 --> 0:13:02.240 the song because it's looking for a specific pattern, and 0:13:02.320 --> 0:13:04.679 depending on the way you sing it or the way 0:13:04.720 --> 0:13:07.640 the band sings it or whatever, it may not match 0:13:07.760 --> 0:13:10.600 up to anything in their database, even though the song 0:13:10.679 --> 0:13:15.160 itself maybe in the database. Because of this fingerprint technology, 0:13:15.200 --> 0:13:17.520 Madomi is different. You know, it may be able to 0:13:18.120 --> 0:13:21.720 track your the way you sing the song and find 0:13:21.720 --> 0:13:26.600 a match within its user generated database. Now, the way 0:13:26.720 --> 0:13:30.319 Medomi explains that the how this works is a little 0:13:30.480 --> 0:13:35.520 um vague, I guess you could say, I'd say, okay, 0:13:35.559 --> 0:13:39.800 So in general, what happens is you submit the song 0:13:39.920 --> 0:13:44.160 and whatever format that you've chosen, whether it's whistling, singing, humming, whatever. 0:13:45.440 --> 0:13:50.080 The software they use converts this into a special length 0:13:50.120 --> 0:13:54.000 computer language they call Crystal language. Um, it's actually computer 0:13:54.040 --> 0:13:56.160 language is probably the wrong term, but it's their own 0:13:56.200 --> 0:14:01.000 proprietary format format exactly. And so then it looks into 0:14:01.040 --> 0:14:03.760 the database and sees if there are any files that 0:14:03.840 --> 0:14:08.240 have a similar, uh similar style to what you just 0:14:08.320 --> 0:14:11.240 sang or hummed or whistled or whatever, and then it 0:14:11.559 --> 0:14:16.400 gives you a selection of songs that most likely are 0:14:16.440 --> 0:14:19.360 going to fit what you sang. I say most likely 0:14:19.440 --> 0:14:24.400 because um, it's this. Yes, I've actually played with Medomie. 0:14:24.400 --> 0:14:27.360 Now I don't as far as I know, Medomi doesn't 0:14:27.400 --> 0:14:30.600 have an Android application. They may have it now, but 0:14:30.720 --> 0:14:32.320 at the time when I first heard of it, they 0:14:32.360 --> 0:14:34.360 did not have an Android application, so I don't have 0:14:34.400 --> 0:14:37.480 it on my phone. But you can use the service 0:14:37.600 --> 0:14:39.640 on the web. You can use it with a computer, 0:14:39.720 --> 0:14:42.200 so as long as your computer has a microphone, you 0:14:42.240 --> 0:14:44.760 can give it a try. And I decided to do this, 0:14:45.440 --> 0:14:47.720 and the first couple of songs I tried it was 0:14:48.000 --> 0:14:51.520 surprisingly very accurate. You know, I am not a good singer, 0:14:51.720 --> 0:14:54.800 as I'm sure many of you can imagine, my singing 0:14:54.800 --> 0:14:59.280 ability is is very poor. Um. I can do character 0:14:59.440 --> 0:15:04.440 voices for certain musicals and that's it. But I decided 0:15:04.440 --> 0:15:06.120 to give it a shot, and the first couple of 0:15:06.120 --> 0:15:09.600 songs I tried came out pretty accurate. I think the 0:15:09.600 --> 0:15:13.680 first one I did was uh, Sedated by the Ramans 0:15:14.360 --> 0:15:16.480 and I want to be Sedated, and it came came 0:15:16.480 --> 0:15:20.760 back right away. But the more I tried, the more 0:15:20.880 --> 0:15:25.640 I was encountering um anomalies, or maybe maybe the correct 0:15:25.640 --> 0:15:28.200 one was the anomaly for me. But I was having 0:15:28.320 --> 0:15:30.720 issues where I would sing something and I would get 0:15:30.760 --> 0:15:33.600 a result that was totally not what I was singing. 0:15:33.760 --> 0:15:37.280 The most egregious of these would be Blue Oyster Cults 0:15:37.760 --> 0:15:42.680 classic hit Don't Fear the Reaper. Uh My version, apparently 0:15:42.720 --> 0:15:47.240 to Medomi, sounds an awful lot like the girl from Ipanema. 0:15:48.080 --> 0:15:53.160 There wasn't nearly enough cow bell. No. I clearly was 0:15:53.480 --> 0:15:57.400 lacking the cowbell, and therefore Medomi was unable to understand 0:15:57.440 --> 0:16:00.720 what it was. But uh so, but if I had 0:16:01.080 --> 0:16:03.480 think of it this way, if I had recorded Don't 0:16:03.520 --> 0:16:06.680 Fear the Reaper and submitted it to Medomi and then 0:16:06.800 --> 0:16:09.560 tried to do it again, it would have identified my 0:16:09.760 --> 0:16:12.520 version of Don't Fear the Reaper as being correct. There 0:16:12.520 --> 0:16:15.560 you go, so that that's not, you know, difficult at all, 0:16:15.840 --> 0:16:18.800 just because they accord all your own songs, so that 0:16:18.840 --> 0:16:20.360 you can go and go, oh, what's the name of 0:16:20.360 --> 0:16:23.200 that song that I always yeah, exactly, Well, that that 0:16:23.200 --> 0:16:27.160 would more It would mostly be to impress or distress 0:16:27.280 --> 0:16:29.920 your friends, because you could sing a song that sounds 0:16:30.000 --> 0:16:32.280 nothing like the original, but it would come back and 0:16:32.320 --> 0:16:34.640 know what it was you were singing, because you were 0:16:34.680 --> 0:16:37.080 the one who provided the template for that song. Do 0:16:37.200 --> 0:16:40.760 you see that that seems problematic for me? Well, because 0:16:40.800 --> 0:16:43.840 it seems like you could intentionally go in and sing 0:16:43.880 --> 0:16:46.600 a whole bunch of stuff and tag it and just 0:16:46.680 --> 0:16:49.320 drive people nuts. Well that's that's why you know, it's 0:16:49.360 --> 0:16:53.920 it's user user police, so you have to it's one 0:16:53.960 --> 0:16:57.600 of those services that depends heavily upon the community of users. 0:16:58.000 --> 0:17:02.160 If the community is being very uh you know, honest 0:17:02.360 --> 0:17:07.280 and forthright, then they are going to police the different 0:17:07.440 --> 0:17:10.400 submissions and make sure that only the ones that actually 0:17:10.840 --> 0:17:14.640 and accurately represent the songs are the ones that make 0:17:14.680 --> 0:17:18.920 it into the database. Otherwise, uh, you know, they essentially say, well, 0:17:19.240 --> 0:17:21.399 this is someone who's just goofing around and trying to 0:17:21.440 --> 0:17:26.000 cause problems, and they'll they'll nix it, right. So, um, 0:17:26.040 --> 0:17:29.080 but yeah, I mean, anytime there's a user, anytime there's 0:17:29.080 --> 0:17:32.040 a service that depends upon the community of users to 0:17:32.040 --> 0:17:35.000 to keep it going, it makes me a little nervous 0:17:35.080 --> 0:17:37.240 because you know, you never know when a group of 0:17:37.240 --> 0:17:40.680 people is just gonna get a little capricious and decide 0:17:40.720 --> 0:17:43.439 that you know, they that every song needs to be 0:17:43.520 --> 0:17:45.520 sung to the tune of the Yellow Rose in Texas 0:17:46.760 --> 0:17:52.479 and why not. Yeah. So, uh as for the new information, well, 0:17:52.520 --> 0:17:56.080 I mean I didn't know if we were. That's pretty 0:17:56.160 --> 0:18:00.320 much the way that those and again it's it's referring 0:18:00.359 --> 0:18:04.920 to a database. It's sending you the results pretty quickly. Um. 0:18:04.960 --> 0:18:08.359 But they they don't Madonie doesn't share as much of 0:18:08.400 --> 0:18:12.520 it's it's uh back end operations as Shazam does, so 0:18:12.600 --> 0:18:15.639 we can't for sure. Men say that they use the 0:18:15.680 --> 0:18:18.119 same sort of setup where they you know, everything stored 0:18:18.160 --> 0:18:20.680 in memory as opposed to hard drive space or whatever. 0:18:21.280 --> 0:18:24.399 We just don't know because we aren't privy to that information. 0:18:24.920 --> 0:18:27.639 But um, yeah, that's that's all I have on just 0:18:27.720 --> 0:18:32.480 the basic operations. So what's this new info you've well, um, 0:18:32.520 --> 0:18:37.000 you know, in in in general, Jasam basically offers the 0:18:37.040 --> 0:18:42.520 application for free for you know, iPhones and Nokia phones. Um. 0:18:42.720 --> 0:18:47.040 But actually, in the as of the ninth don't know, 0:18:47.440 --> 0:18:50.840 late middle part of October two thousand nine when we're 0:18:50.840 --> 0:18:53.800 recording this, um Chasm actually just got a new round 0:18:53.800 --> 0:18:56.840 of funding from Kleiner Perkins, call Field and Buyers. They 0:18:56.840 --> 0:19:03.119 actually have their own iPhone Apple Cation fund called the 0:19:03.160 --> 0:19:05.720 I fund this hundred million dollars and uh, you know 0:19:05.760 --> 0:19:09.639 it's specifically geared towards iPhone developers. Well, Shasam got some 0:19:09.680 --> 0:19:12.280 of that money, and there, um they're going to continue 0:19:12.320 --> 0:19:16.120 to offer their services for free for a while. Uh. Well, 0:19:16.119 --> 0:19:18.840 they actually charge for the BlackBerry version, but the iPhone 0:19:18.920 --> 0:19:21.680 and Nokia Phones version. I don't think they charge for Android, 0:19:21.720 --> 0:19:24.119 or if they have, I am totally unaware of it 0:19:24.480 --> 0:19:27.040 because I have Shazam for the Android phone and and 0:19:27.720 --> 0:19:30.360 if they're charging me for it, I need to pay 0:19:30.400 --> 0:19:32.480 better attention to my bills. Well, you need to pay 0:19:32.520 --> 0:19:34.080 attention to your bills by the end of the year 0:19:34.160 --> 0:19:37.360 in two thousand nine, because um, there you will start 0:19:37.400 --> 0:19:40.320 to get five free song identifications a month, and then 0:19:40.480 --> 0:19:43.440 four nine a month after that if you want unlimited 0:19:43.480 --> 0:19:46.160 usage and all the extra goodies. And they're talking about 0:19:46.160 --> 0:19:50.480 selling application or i'm sorry, selling items, uh you know 0:19:50.520 --> 0:19:53.600 as part of the application to like you know, banned 0:19:53.680 --> 0:19:58.120 gear and you know, possibly selling video. I'm pretty sure 0:19:59.200 --> 0:20:01.879 you know what. I can't be certain now, but I could. 0:20:02.560 --> 0:20:06.320 I seem to recall the last time that Sasam correctly 0:20:06.359 --> 0:20:08.400 identified a song for me. It gave me a link 0:20:08.440 --> 0:20:13.240 to where I could purchase the album on Amazon. But 0:20:13.280 --> 0:20:15.639 maybe maybe I've got that mistaken now because it has 0:20:15.680 --> 0:20:17.240 been a while since I've used it and had it 0:20:17.320 --> 0:20:21.080 actually work. Because it turns out that most music that 0:20:21.119 --> 0:20:24.840 I really like, I already know what the song is. Yeah, 0:20:24.920 --> 0:20:27.879 it's just the really really obscure stuff that tends to 0:20:28.080 --> 0:20:30.560 like I'm like, wow, that's so cool. I've never heard 0:20:30.600 --> 0:20:34.119 that before, and apparently neither has Shazam, so I haven't 0:20:34.160 --> 0:20:36.760 had much call to use it recently. I don't have 0:20:36.800 --> 0:20:38.920 a Nokia phone, and I don't have an iPhone or 0:20:38.960 --> 0:20:41.359 an Android or BlackBerry um, but I do have the 0:20:41.400 --> 0:20:44.480 iPod and I could download Susanne. But I have the 0:20:44.560 --> 0:20:48.360 first generation iPod Touch, and so I could stand there 0:20:48.359 --> 0:20:52.000 all day holding up my microphone lists iPod Touch up, 0:20:52.000 --> 0:20:55.960 and She'sam's just gonna go anytime? You just just I'll 0:20:56.000 --> 0:21:00.440 be waiting. Actually, I could use a microphone that ugs in, 0:21:00.560 --> 0:21:04.320 but you know that costs money, right, and then you 0:21:03.840 --> 0:21:06.920 don't and you have to carry around an extra pace 0:21:07.000 --> 0:21:09.200 of gear and you have to be someplace where there's 0:21:09.240 --> 0:21:12.320 WiFi for you to be able to actually indeed, you 0:21:12.320 --> 0:21:16.280 know that could be problematic that's a lot of qualifiers 0:21:16.320 --> 0:21:18.600 for a single application. So maybe I'll invest in a 0:21:18.640 --> 0:21:22.040 smartphone eventually. Yeah, that would um, that would be my recommendation. 0:21:22.200 --> 0:21:25.280 You know, there's a there's this awesome new phone called 0:21:25.280 --> 0:21:29.479 the Motorola Droid. Have you heard about it? I do 0:21:29.560 --> 0:21:33.679 think I have. It's kind of hard not to, um 0:21:33.720 --> 0:21:36.439 so at any rate. Yeah, that's that's interesting stuff. Uh, 0:21:36.960 --> 0:21:40.120 I mean, I think these these services are really cool ideas, 0:21:41.320 --> 0:21:43.280 especially for people who happen to be out and about 0:21:43.320 --> 0:21:44.679 a lot and they hear a lot of you know, 0:21:44.800 --> 0:21:47.919 encountering a lot of new music. Um. It's it's a 0:21:48.000 --> 0:21:52.320 really interesting way to to to educate yourself about stuff 0:21:52.359 --> 0:21:54.600 that you like that you know, you you encounter, but 0:21:54.640 --> 0:21:59.080 you don't necessarily you're not really familiar with it. Um. 0:21:59.119 --> 0:22:00.760 I mean, there are a lot of other options to Like, 0:22:00.800 --> 0:22:03.480 there are a lot of like HD radio stations which 0:22:03.480 --> 0:22:06.280 will identify the song that you are listening to. And 0:22:06.320 --> 0:22:09.720 there's some HD radio applications where you can even get 0:22:09.760 --> 0:22:12.880 access to buying the song off of something like Amazon 0:22:12.960 --> 0:22:16.960 or iTunes. So uh yeah. Of course satellite radio also 0:22:17.200 --> 0:22:20.440 identify as those and um, you know there are other 0:22:21.280 --> 0:22:23.919 and this really isn't all that especially new. You know, 0:22:24.040 --> 0:22:27.440 Grace Note alias c d dB, you know, has been 0:22:27.480 --> 0:22:32.480 identifying songs mathematically, uh, you know, based on identification numbers, 0:22:32.480 --> 0:22:34.159 and at least, you know, it's a little bit different 0:22:34.160 --> 0:22:37.760 from the way that Shazam and Medomi do. And then 0:22:37.800 --> 0:22:40.520