-
-
Notifications
You must be signed in to change notification settings - Fork 6
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
Update breaks cwebp on macOS ("cwebp failed") #21
Comments
I can confirm that it's the update. I got the old version from a backup and it works perfectly. |
Thanks for the info. Contributions are welcome. |
I had the same computer configuration and had the problem and the same solution😂, use the github release version 1.5 feel well. |
I'm not sure if this is the same issue, but after a recent update, I got a permission error from P.S. I was looking to see if I can just make a quick PR, but after doing a super quick search, I couldn't find the executables in the repository. I'm guessing they're packed with the addon itself outside of this repository. |
Yes, the executables are added when you run |
The executables included with this add-on are for x86-64. If your computer has a different architecture, install |
While this surely would lead to a performance improvement, it's not the reason we're having this issue. Because the previous, working, version had the very same x86-64 executables no? Intel executables get seamlessly translated on the fly by Rosetta2 in most cases, including cwebp. But thanks for the suggestion! |
So does it work after that? (I can't test right now) |
It does indeed work for me, but as mentioned before, it could be a different issue. |
Hi, the addon suddenly stopped working. There's no error but the tooltip mentions cwebp failed.
I've checked if the executables are present. And yes, they are. Nothing has been changed or touched since it worked. Besides the update perhaps.
Version 2.1.54 (b6a7760c)
Python 3.9.7 Qt 6.3.1 PyQt 6.3.1
MacOS ARM
Thanks for any support :)
The text was updated successfully, but these errors were encountered: