Skip to content
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

Open
JaegerMaster opened this issue Jul 30, 2023 · 8 comments

Comments

@JaegerMaster
Copy link

JaegerMaster commented Jul 30, 2023

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

@Neurrone
Copy link
Owner

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?

@JaegerMaster
Copy link
Author

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?
It can use the existing chapter titles and change anything?

@Neurrone
Copy link
Owner

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

@JaegerMaster
Copy link
Author

No worries. Thanks.

Lets wait and see.

@djdembeck
Copy link

Audible requires authentication again for chapters. I've re-added auth to the Audnexus project. This should be merged into production shortly.

@JaegerMaster
Copy link
Author

Thanks. Works properly now.

@JaegerMaster
Copy link
Author

I think this has cropped up again.

@JaegerMaster JaegerMaster reopened this Sep 23, 2023
@TaroAM
Copy link

TaroAM commented Sep 23, 2023

I can confirm. Wonder if the error can be handled instead of crashing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants