Hi everyone!
We want to program a music player that allows users to clean up the tags of their music library. To do so, we would like to use the amazing fingerprinting capacity of ENMFP .
As we looked at the echonest API, it appeared to us that identifying tracks can only be performed through individual requests.
PROBLEM : a user can have in his music library thousands of tracks (and more!). Identifying his whole music library by individual requests, would result in serious HTTP flooding. If we consider now that our music player could be used by many users at the same time, the htttp flooding would be MASSIVE.
Any idea of a reasonable way to perform massive fingerprint identifications? Would it be reasonable to set up cache servers to store the fingerprints of our users and thus limit the identification queries to echonest? If we do so, wouldn't be echoprint a more appropriate solution than ENMFP?
Thanks in advance for your answers! Paul