gchudov / db.cue.tools Goto Github PK

Make sure docker volumes are stored on SSD:
/etc/docker/daemon.json:
{
"data-root": "/media/ephemeral0"
}

Could you document the API for verifying and submitting results, including some documentation for how to calculate things?

Hi,
I'm playing a bit with cd-rips and sometimes I'm not sure what exact release I have.
Some CDs are re-released with unchanged tracklist and it's hard to guess which one is the correct one.
It would be easier to guess if ctdb would show first submission date on cd page.
eg. here: http://db.cuetools.net/?tocid=zE0UJAgdlsBXpkh3fQX.HVN_yfQ-

This issue was originally added to the wrong project and the OP never got around to posting here.

In the past when visiting http://db.cue.tools, it used to be possible to use the arrows at the bottom of the page to browse other results, but nowadays the arrows are greyed out and you're stuck with the first 10 results which makes it impossible for me to find the albums I'm looking for.
Is it possible to restore the previous behaviour or is there a way to search for certain albums?
by YhenZN

Similar things should probably happen when there are too many similar unconfirmed entries.

Example: http://db.cue.tools/top.php?tocid=ctvjFPq3N6GF0IdVCrEPTlr51iI-

This CD is linked to a MusicBrainz album but the site isn't picking up on it. MB did have a DB schema change recently that might be part of the issue: https://blog.metabrainz.org/2022/05/16/musicbrainz-schema-change-release-2022-05-16-with-upgrade-instructions/

http://db.cuetools.net/lookup2.php?version=3&toc=0:12462:42572:71667:100622:121227:131172:142442:163625:201777&metadata=extensive&ctdb=1

As advised by @ha-korth in gchudov/cuetools.net#293 (comment) I am cross-submitting the following issue in this repository.

Thanks for this amazing set of software! I have started ripping CDs again using CUERipper, and it works splendidly and hassle-free.

I've come to notice that my latest additions (e.g. for when a disc was previously unknown) to the MusicBrainz database are not reflected in the metadata fetched by CUERipper from CTDB. Waiting for a week has not changed this issue.

I've read that a schema change on the end of MusicBrainz could be the culprit. This topic on Hydrogenaudio describes problems similar to what I am experiencing.

Please let me know if I can be of any help providing further details.

Hi
I found new added releases to Musicbrainz doesn't appear on CTDB.
So I guess the Musicbrainz server sync is not working now.
Could you check the server status?

This would allow outsourcing user management to Mediawiki.

https://hometechhacker.com/centralizing-docker-logging-using-logspout-and-graylog/