Forked from viewtopic.php?t=5979
This is only informational.
Some more observations on issues with cddb_query:
Audacious 3.9 (compiled in Slacko64 6.9.9.9) also shows the wrong tracknames
for the afore mentioned Audio CD when first playing.
After clearing cached files and downloading the queried cddb file, audacious
now shows the appropriate informations.
At https://github.com/qyot27/libcddb/blob/ ... .howto.txt i found some more information about multiple matches:
We consider the use of the "cddb query" command mandatory for all freedb
clients. It is not valid to issue a "cddb read" command without issuing a prior
"cddb query" and receiving a good response, as it may yield incorrect results.
In addition, it is required that clients support close matches (aka "fuzzy"
matches, or response code 211) and multiple exact matches (response code 210)
in response to a query.The proper way to handle fuzzy matches and multiple exact matches is to present
the entire list of matches to the user and to let the user choose between them.
Fuzzy matches are listed in the order of best fit for the user's disc, so they
should be presented to the user in the order they are listed by the server.
So at the moment of writing, the solution is to delete the cached files in ~/.cddbslave
or ignore the local cache with cddb_query -c off -s gnudb.gnudb.org -p 8880 query
and download either the one file that matches for you with the command
cddb_query -s gnudb.gnudb.org -p 8880 read <category> <discid>
or all matching files with cd-info --cddb-server=gnudb.gnudb.org --cddb-cache=~/.cddbslave .
If your Audio CD contains additional Data cddb_query fails to calculate the discid.
In this case, cd-info may be helpful.
About search command:
duckduckgo returns results for similar CDDB search problems with EasyTAG.
I've installed EasyTAG for testing.
Changing the CDDB servers in EasyTAG does not produce any search results. The response
of the server is something like 'HTTP/1.1 301 Moved Permanently'
Looks like http protocol is hardcoded in EasyTAG.
Back to cddb_query's search:
Setting log level to debug you will find a line debug: ...buf = 'GET /freedb_search.php?'
gnudb.org's search site is search.php so search is broken due to hardcoded search site in
cddb_query or libcddb(?).
For the album command libcddb reports an unknown error.
cddb_query -h indicates that the album command is only available on freedb2.org servers.
So it's no wonder that the response is 500 Unrecognized command.
I hope this information is helpful to someone...
Have fun and stay curious 
