@StevenJackson Hm… would you mind sending me the book so I can take a look on my end?
If you click Help > Get support, you’ll see my email.
@StevenJackson OK, I found the bug, and it actually affects all fields. If a field has any information, it’s impossible to delete it, only replace it 😱
I already fixed it and will push the update in a few hours. It can take a few days for Apple to review it. So, unfortunately, we have to wait. Sorry for that.
@StevenJackson Thanks for clearing that up, the fix I pushed should cover this case as well.
The problem was that the Description field for some of your books was being saved in a different internal field (“atom”) (`ldes/synopsis`) than the one that was getting overwritten (`desc`).
The update now writes to both at the same time, so replacing the description should work correctly.
@StevenJackson Hm... I did a bunch of different tests, and it works on my side.
Would you mind sharing the exact book with me? I’ll take a look and see why updating is acting up.
@StevenJackson iCloud Drive? Dropbox? Google Drive? Anything will work.
@orsolabs Okay. I’ll send you a link tomorrow (I’m not at my computer right now).
I have another question, though. What’s the best way to deal with books where the chapter timestamps “drift”? I have a few books for which I have used the “Fetch metadata” option. It’s more or less fine, but the chapters aren’t quite right further into the book. It’s only a matter of a few seconds, but chapter breaks aren’t quite in the right place…
@StevenJackson That kind of “drift” usually means your local file isn’t the exact same edition/encode as the one the chapters were fetched for.
If it’s just a few books, the quickest workaround is manual:
1. export chapters to a .txt (⌘⇧E)
2. adjust the timestamps
3. drag the .txt back onto the book to re-import
More details here: https://orsolabs.dev/blog/how-to-use-youtube-timestamps-chapters
@StevenJackson But if you’ve got a lot of books, doing that by hand is a pain. That’s why I’m also working on a feature that lets you nudge chapter boundaries visually on the waveform, so you won’t have to edit timestamps in a text file.
That’s the next big thing I’m building — but realistically it won’t be ready for at least ~2 months.