Almost true.

It is pretty picky, as it expects a certain folder structure to get all the info correct when importing. But it is fairly easy to go in and manually “fetch” the correct metadata from one of the metadata providers (Amazon, Google Books, Open Library etc). It’s a chore if you have big library with many different structures, but doable if you don’t want to rename all folders.

It’s not just an issue with incorrect meta data. It will also just flat out refuse to import files if you’re not 100% compliant with what seems like a strict hardcoded folder structure and naming. It will also mess up your manually fetched metadata and any manual adjustments you’ve made if you need to update the library. And don’t even get me started on how it handles chapters in some audiobooks, JFC it can be a shitshow.

I don’t know of a better solution though, so I’m living with it, but it’s a very “hand carried” solution, and were it not for my kids I would rather just have the files directly on my own device with a local player and don’t have the hassle. I wish it would work better like the *arr stack and jellyfin.

I’ve been using it for years and this has never been an issue for me.

Same here. I was using Readarr and now Chaptarr on default setting and never had an issue.