I think this would be a great time for Facebook or some large company who is interested in music identification to start using the MusicBrainz database. They already have a huge database and most of them have an acoustic hash as well.
Why music ID resolution matters to every music fan on Facebook
11–15 of 15 posts
Re: Why music ID resolution matters to every music fan on Facebook
#12This is why ISRC exists. It's like ISBN for recordings, and it's in active use. http://en.wikipedia.org/wiki/Isrc A few years back I worked for a startup that was cataloging recorded music. I recall that the major labels would provide us with ISRC, among other things, for all of their recordings. I don't recall whether independent labels and artists used it though. I would guess that it varied. (See also ISWC, which…
Right, ISRC is somewhat useful for glue but is not in wide enough use that it covers the world of music. It also reflects "recordings" not "songs" which actually cause a lot of resolution issues (radio edits, clean vs. explicit and etc.) It also does not help anyone resolve artist names like "The The" when their stopword list turns that into an empty query :)
It is the reason xISBN exists. http://www.worldcat.org/affiliate/webservices/xisbn/app.jsp
Ideally an ID cross-reference would be an open dataset, but it is difficult to achieve that in the market. A proprietary xref is better than no xref.
Re: Why music ID resolution matters to every music fan on Facebook
#13This is why ISRC exists. It's like ISBN for recordings, and it's in active use. http://en.wikipedia.org/wiki/Isrc A few years back I worked for a startup that was cataloging recorded music. I recall that the major labels would provide us with ISRC, among other things, for all of their recordings. I don't recall whether independent labels and artists used it though. I would guess that it varied. (See also ISWC, which…
There's no central database of ISRCs, so even if you have an ISRC in your hand there's no way to find out what artist and song title that ISRC represents.
Re: Why music ID resolution matters to every music fan on Facebook
#14This is why ISRC exists. It's like ISBN for recordings, and it's in active use. http://en.wikipedia.org/wiki/Isrc A few years back I worked for a startup that was cataloging recorded music. I recall that the major labels would provide us with ISRC, among other things, for all of their recordings. I don't recall whether independent labels and artists used it though. I would guess that it varied. (See also ISWC, which…
There's no central database of ISRCs, so even if you have an ISRC in your hand there's no way to find out what artist and song title that ISRC represents.
As someone who implemented metadata matching of two distinct musical catalogs: First you do search, then you do ranking, then you take the best result. You need to take all the needle metadata (isrc, albums' upc/icpn, title, version, album, artists), and then
- If there are results with the same ISRC, it's cool. Choose the best matching album (by UPC, then by title, then by album version)
- If there aren't, match the track + artist pair and then choose the best matching album for it.
- If you don't have ISRC match and can not match on track title + artist, you should probably bail out.
This way you both won't miss a track in compilation, neither would you prefer The Hit Crew to the actual good performer.
Most international content has ISRC. Local, independent and DIY would probably not. But it's usually easier to match because it doesn't have dozens of different recordings for tracks nor endless realms of compilations.
Re: Why music ID resolution matters to every music fan on Facebook
#15That was quite an interesting read. I felt somewhat vindicated at the end of the article when the author mentioned that audio fingerprinting is a potential solution to this problem. While reading about the various issues created by matching songs based on names and artists, I immediately started thinking about how one might instead identify songs based on their acoustic properties. Having looked into it a little bit…
If you want to know more about how to implement it on your own, you could use this as a resource: http://www.redcode.nl/blog/2010/06/creating-shazam-in-java/
I assume the biggest drawback to be that Shazam uses a microphone, which is obviously subject to ambient noise. Shazam doesn't actually seem to have much of a problem with this, but I'm guessing a passive listener that sampled the audio output device instead of a noisy ambient microphone would work much more reliably.