Topic: Increase number of results returned? (in VM or python)
I am writing some scripts that use python-musicbrainz-ngs to query an MB server running in a Virtual Machine.
Occasionally my query will not get the result that I really want because it's not in the first 25 results returned. I've tried setting the query command limit to 1000, like so:
result = musicbrainzngs.search_recordings(artist=a, recording=b, limit=1000)
But that still returns a maximum of 25 results. That is,
equals 25, whether the limit is set to 25 or 1000 or 1000000.
I took a look through musicbrainz.py and couldn't find anything that indicated that the limit is set there. It seems pretty wide open to any number, really.
I'm going to take a wild-ass guess and think that something inside the server is set to return 25 results per page. Maybe?
If this is the case, is there a way that I can change this on my VM server?
Needing to search through many results does indicate that my search is not exact enough. Currently I am just running off the Artist Name and Recording Name as stored in the tags in the MP3s. I know that they're not always accurate, so my query results are not always accurate.
What else can I do to make my queries more accurate?
I tried using duration, but that didn't work well, and a thread in this forum indicates that searching using duration might be buggy.
I have come across some threads mentioning "MBIDs" and "fingerprints" - will they help? Can anyone point me to some more information on how/if I could programmatically use these to better match my MP3s to MB entries?
What about AcoustID? Can that be used? Does the database contain enough AcoustIDs to make that a viable option?
Thanks in advance...