-
-
Notifications
You must be signed in to change notification settings - Fork 75
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Querying CDDB from gnudb.org no longer returns the actual results (in v1.1.7) #548
Comments
Yes, this is happening to me too. Started today |
I've found the reason!!!! This is caused, according to them, by a bug in fre:ac v1.1.7 |
Hi, I have the same issue as the OP, I am using the flatpak version on Pop_OS, is this issue being worked on ? it dose not stop the ripping from being done it just means all the info and cover art needs to be done manually :) I realize there are greater problems in this life for sure but Fre:ac is one of my most used applications and it is kind of strange that gnudb have now decided after seven months that it is not supporting v1.1.7, much respect and thanks to the developers of Fre:ac. |
From the gnudb.org frontpage:
I can confirm that I got correct cddb informations from gnudb with version 1.1.6. |
I'm sort of confused. Is there anything actually wrong with the files created with 1.1.7., in regards to the track offsets? |
It is because freac is submitting inaccurate data to the gnudb lookup query. So it is blocked until it gets fixed. If you are using the flatpak version of freac, you can downgrade to 1.1.6 with this command below. Be sure to mask org.freac.freac flatpak after you downgrade so it does not get updated again until you unmask it. sudo flatpak update --commit=195a236bbd0fe41b9d2533379dcd5d51c488f3466d45cf225cafb4b4565e2e36 org.freac.freac |
It seems that this issue is solved. I've got 1.1.7 installed and gnudb.org is sending results again. Also, the message in the webpage referring to 1.1.7 being non compatible has dissapeard. |
Yep, looks like gnudb.org is no longer complaining about 1.1.7. Closing as fixed. |
how do you add vgmdb as the cddb server in fre;ac, please! assist. |
Describe the bug
When attempting to fetch CDDB info from gnudb, it has started returning the following results:
gnudb.org's website now includes this segment:
To Reproduce
Steps to reproduce the behavior:
Additional context
This appears to be a recent change, queries worked fine yesterday. Downgrading to v1.1.6 returns correct results, looks like gnudb is specifically blocking v1.1.7 queries now.
The text was updated successfully, but these errors were encountered: