-
Notifications
You must be signed in to change notification settings - Fork 19
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
Beets Audible failing everytime after not being able to get the chapters #54
Comments
Yeah this is a known issue. I suspect that the service that Beets-audible uses hasn't gotten info on the chapters yet for new releases. Does it work for you if you try it 12 - 24 hours later? |
Nah. I have been seeing this for the last 1 week atleast. i think somehow audible is blocking audnexus from getting the chapter data. In that case, can we change the script to not fail and tag the book atleast without chapter data? |
There is no existing chapter titles to fall back on, since the Audnex API is the source of data. We'll have to wait for updates in the issue you created, laxamentumtech/audnexus#658 |
No worries. Thanks. Lets wait and see. |
Audible requires authentication again for chapters. I've re-added auth to the Audnexus project. This should be merged into production shortly. |
Thanks. Works properly now. |
I think this has cropped up again. |
I can confirm. Wonder if the error can be handled instead of crashing. |
Closing this to do some cleanup of old issues. Let me know if this is still relevant. |
Lately, the program fails to match and tag books after the chapter endpint gives a 404 error. It leave the tagging mid-point and does not match the book.
Error:
Error while requesting https://api.audnex.us/books/B0BLJ78Y1Y/chapters: status code 404, Not Found
this happens for monstly newly released books and not for all books.
Beets Audible version:
beets version 1.6.0
Python version 3.10.6
plugins: audible, copyartifacts, edit, fromfilename, scrub
The text was updated successfully, but these errors were encountered: