StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>I guess there are a number of approaches you could take to this:</p> <h2>1. Compare tags</h2> <p>You could compare the data held in mp3's tags. The tags are held in the <a href="http://id3.org/" rel="nofollow noreferrer">ID3</a> format. There are a number of libraries to help you access the tags, <a href="http://developer.kde.org/~wheeler/taglib.htm" rel="nofollow noreferrer">tagLib</a> is a popular choice (<a href="http://www.novell.com/products/linuxpackages/opensuse11.1/taglib-sharp.html" rel="nofollow noreferrer">TagLib Sharp</a> for .net apps)</p> <h2>2. Acoustic fingerprint</h2> <p>This is by far the most robust method, allowing you to find matches regardless of the compression or even format. A unique fingerprint is created from the actual audio from the file allowing the <em>song</em> to be identified <a href="http://echoprint.me/" rel="nofollow noreferrer">echoprint</a> is an opensource example of this.</p> <h2>3. Creating a hash from the file</h2> <p>This is a quicker method allowing you to find file with content that matches exactly.</p> <hr> <p>Some further reading:</p> <ul> <li><p>There's an interesting MSDN article about managing an mp3 collection (including reading the tags) here: <a href="http://msdn.microsoft.com/en-us/library/ms345151.aspx" rel="nofollow noreferrer" title="Managing a Music Collection Using Visual Basic Express and SQL Server Express">link text</a> (It's in visual basic but might still be useful.)</p></li> <li><p>There's a little description of the file format here: <a href="http://www.mp3-converter.com/mp3codec/mp3_anatomy.htm" rel="nofollow noreferrer" title="Inside the MP3 Codec">link text</a></p></li> </ul>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload