acoustid-server
acoustid-server copied to clipboard
acoustid
AcoustID's web site and API
MusicBrainz lookups are a big chunk of the time spend in search requests, which really should not happen. Fingerprint search should be the most expensive operation, metadata should be cheap....
We are always using multi DB sessions in the web handlers, but specifically for search, we only need one connection at the time, so for example, while musicbrainz lookups are...
Track lookups result in 'internal server error.' Not sure if this is the correct place to post this, or if anyone is actively maintaining, but since I couldn't find clear...
I encounter with problem initialising db. I presume, nowdays acoustid-servers uses triple-db configuration: **acoustid_app**, **acoustid_fingerprint**, **acoustid_ingest**. Also it requires musicbrainz db. But in README.md there is no words about it....
Submitting a fingerprint for a duration > 32767 currently fails due to https://github.com/acoustid/acoustid-server/blob/8a8112c1ce26bbdcd73473eccc86d7040a42f834/acoustid/api/v2/__init__.py#L631 Is this a strict limitation because that value gets used elsewhere as a signed integer, or could...
Submitting too many fingerprints at one yields a 'Request Entity Too Large' error from the server. I guess the solution would be to submit it smaller batches, but we need...
Your last commits indicate that the database backend is undergoing a restructure. Will the database dumps and / or replication still be available then, perhaps in a new format? I'm...
When you unlink or link an AcoustID from a MusicBrainz recording ID, the page you are returned to references what I assume to be the database rowID. It should instead...
Hi, I searched in the docs but I couldn't find it. :-(
After clicking the **Sign in** button, we are redirected to homepage instead of where we were before signing in, usually a track page.
