Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feature request: support of musicbrainz.org as information source #25

Open
spali opened this issue Mar 13, 2013 · 4 comments
Open

feature request: support of musicbrainz.org as information source #25

spali opened this issue Mar 13, 2013 · 4 comments

Comments

@spali
Copy link

spali commented Mar 13, 2013

they have an api which can identify songs with fingerprints and have a big database with almost anything.

@celaus
Copy link

celaus commented Mar 14, 2013

as in #7 mentioned, the echo nest offers an api for audio fingerprinting, which could be used as an alternative for musicbrainz.org since it would also cover features for playlist generation. Also I have a working script for mp3 identification using echoprint, which I could contribute.

edit: this also depends on how the indexer is going to be re worked in order to get all the other features and fixes...

@Freso
Copy link

Freso commented Mar 14, 2013

MusicBrainz has tried twice to use proprietary audio fingerprinting algorithms and both have failed. They also has a short flirt with Echonest's fingerprinting, but it wasn't hugely popular. And then AcoustID came along as an open/free/libre alternative. The plan for MusicBrainz is to "support" only AcoustID from October this year.

TL;DR: Using a closed-down fingerprinting algorithm is not the way to go for long-term sustenance. Use an open alternative. Like AcoustID.

@celaus
Copy link

celaus commented Mar 14, 2013

echoprint would also be open source (https://github.com/echonest/echoprint-codegen), but apparently the musicbrainz compatibility is only in testing and also its written in C++. Also the API only calls the compiled binary using the shell, which is not really optimal.

Having that said, I will have a look at AcoustID and try it in my script and if it works well I could offer that instead of EN ;)

@spali
Copy link
Author

spali commented Mar 19, 2013

personally I don't care much about the "technical" solution. For me it's important that a rich and good quality database is behind the information provider and I can easy contribute my own information.
Also important is that the matching works with non 100% exact copies to handle different rips of the same piece of music, which can differ only in silence seconds or maybe quality.
Currently I'm using musicbrainz because I had good experience with it an expect some few Albums i found everything with a good quality. And for this few Albums it was easy to contribute the information's by my self.
If there is an other good service, I wouldn't have a problem to change.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants