Replies: 1 comment 6 replies
-
Is your ereader key still in there? Can't imagine anything has changed -- except maybe you're the first to test that part of the code since calibre/DeDRM switched to Python 3. For new Kindle books, you'll need DeDRM 10.0.9 and the KFX Input plugin. |
Beta Was this translation helpful? Give feedback.
6 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello everybody. I recently upgraded from Calibre 4.13 with DeDRM 6.5.1 to the current versions--Calibre 7.26.0 and DeDRM 10.0.9. I wasn't sure how to move my customization data to the new version of the plugin, so I simply copied the calibre-adeptkey.der and dedrm.json files to the new plugins folder. This seems to have worked, as all of my customization fields seem to be properly populated.
With my new setup I've confirmed that my Kindle ebooks are being added to my library as expected. However, when I add eReader PDBs, DeDRM doesn't seem to be doing anything. If I recall correctly, with the old version a PDB would be converted to a PMLZ that could then be converted to other formats. Now, however, PDBs are added but they remain DRM-protected, with no PMLZ created. Is there something I need to change in settings to get the conversion to PMLZs?
Also, have there been any significant changes to PDB conversions since version 6.5.1? With that version certain characters (quotation marks, dashes, hard hyphens, apostrophes and probably several others) in my PDBs were not converted properly and had to be fixed manually. I am under the impression that this was not something for which a fix was likely to be developed, but . . . maybe the conversions work much better now?
Thanks in advance for any advice!
Beta Was this translation helpful? Give feedback.
All reactions