[FileType Plugin] ACSM input plugin

[Metapath]

Originally Posted by Cactus Chef

So this plugin seemed to stop working some time between August 6th (when I last imported books successfully) and today. When I tried pulling down the ascm files today, they simply imported into my calibre library as .ascm files.

Did the ByteBooks acquisition break the Anonymous Auth option?

No, it didn't, Anonymous Auth working fine here. The only time I had the issue you're having is when I inadvertently changed the emulation of the plugin from ADE 2.0 to something higher (4.0?). Then, some books wouldn't download properly due to DRM I suppose.

The UI in the plugin isn't great...if you change the emulation mode, it still looks like it's set for 2.0 when it isn't. Just re-select 2.0 and you should be good, except for the failed books...you won't be able to re-download them with an earlier emulation (at least, I couldn't). But it will prevent future issues.

[Cactus Chef]

Hmm. Well, for whatever reason, I re-downloaded a test file from Kobo and then ran it through, and it worked.

I guess whatever batch I grabbed that day (I downloaded like six at once from My Books) was bad.

[Azimut]

Originally Posted by JSWolf

What was your fix in case anyone has the same error?

From what I read, it looked like a libcryto error of some kind.

I guess I have the same error with DeACSM plug-in:

https://www.dropbox.com/scl/fi/mrxtu...yeffcwlx8&dl=0

Has anyone been able to solve it? I'm on Calibre 9.15 for Mac. I've read the explanation of @desertdaisy but he/she didn't provide any practical solution.

[JSWolf]

Originally Posted by Azimut

I guess I have the same error with DeACSM plug-in:

https://www.dropbox.com/scl/fi/mrxtu...yeffcwlx8&dl=0

Has anyone been able to solve it? I'm on Calibre 9.15 for Mac. I've read the explanation of @desertdaisy but he/she didn't provide any practical solution.

I suggest you PM @desertdaisy and maybe that will get a reply.

[Azimut]

Originally Posted by JSWolf

I suggest you PM @desertdaisy and maybe that will get a reply.

Found a solution: in my case the problem arises because my Mac derives from an old Intel-based Mac , and then the openssl and lib crypto libraries were on x86_64 version. I post the complete solution:

1. Check what's there. In Terminal, run:
file /usr/local/lib/libcrypto.dylib
ls /opt/homebrew/opt/openssl@3/lib/

The first should say x86_64. The second tells you whether you already have an arm64 OpenSSL.

2. If there is no arm64 OpenSSL, install one with Apple Silicon Homebrew:
/opt/homebrew/bin/brew install openssl@3


3. Get the stale x86_64 file out of the way. If you don't need the Intel Homebrew install, rename it, for example sudo mv /usr/local/lib/libcrypto.dylib /usr/local/lib/libcrypto.dylib.bak. I'm not certain oscrypto will then find the arm64 library on its own. If it doesn't, the next steps come into play. ( strongly suggest to completely uninstall old version of Homebrew, including the PATH additions!)


4. Remove the plugin in Calibre (Preferences → Plugins), quit Calibre, delete ~/Library/Preferences/calibre/plugins/DeACSM, and reinstall. Use the newest beta build from the plugin's GitHub Actions page rather than 0.0.16.


5. Restart Calibre and check that the plugin loads without errors.

[Azimut]

Originally Posted by JSWolf

I suggest you PM @desertdaisy and maybe that will get a reply.

SOLVED! In my case I guess it depends on old libraries coming from migration of an Intel-based Mac and silently installed on my Apple Silicon present Mac Mini:

these the steps:

1) Check what's there. In Terminal, run:
file /usr/local/lib/libcrypto.dylib
ls /opt/homebrew/opt/openssl@3/lib/

The first should say x86_64. The second tells you whether you already have an arm64 OpenSSL.

2) If there is no arm64 OpenSSL, install one with Apple Silicon Homebrew:
/opt/homebrew/bin/brew install openssl@3

3) Get the stale x86_64 file out of the way. If you don't need the Intel Homebrew install, rename it, for example sudo mv /usr/local/lib/libcrypto.dylib /usr/local/lib/libcrypto.dylib.bak. I'm not certain oscrypto will then find the arm64 library on its own. If it doesn't, the next steps come into play. (I strongly suggest to completely uninstall the old installation of Homebrew, including the PATH dependencies!)

4) Remove the plugin in Calibre (Preferences → Plugins), quit Calibre, delete ~/Library/Preferences/calibre/plugins/DeACSM, and reinstall. Use the newest beta build from the plugin's GitHub Actions page rather than 0.0.16.


5) Restart Calibre and check that the plugin loads without errors.

[Truus]

Years later, but couldn't find a later thread

Yesterday I installed DeACSM-plugin 0.0.16 in Calibre 9.15.0: saw it appear among the installed Plugins, then restarted Calibre: still there.
Wanted to re-read instructions for connecting with ADE before taking that step, so left that for today. Surprize: it's gone!
Tried installing it again but can't.

What can be the matter?

[DNSB]

A bit more information might be useful. What OS/version/hardware platform are you running? Windows 11 on x64? MacOS on X64? MacOS on ARM64? Linux on ????

[Truus]

This happened on Windows 10 64x
Installed the DeDRM-plugin a few days before and that works fine

Thanks for asking

[PeterT]

In cases where a plugin can't be seen after installation, try starting calibre in debug mode and then examining (or posting here) the startup log.

[Truus]

I still have ADEditions installed: could that be interfering with DeACSM-plugin?

[JSWolf]

Originally Posted by Truus

I still have ADEditions installed: could that be interfering with DeACSM-plugin?

ADE does not interfere with ACSM Input. I have both installed. I've never had an issue with both installed.

[Truus]

Thanks
Pity, getting rid of ADE would be easy