-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Feature request: emit post-processing 'info' event #367
Comments
Hello, we could add a feature where an instance of Given the async nature of this, you would probably need to cork the As an aside, we also need to check why you're seeing "terminating with uncaught exception of type vips::VError" as that should have been caught and emitted as an |
this error message is on mac os, in linux I got more details which point to this line which is becuase of the difference in size |
an |
Commit 86815bc on the |
v0.14.0 now available via npm, thanks for the original suggestion! |
I am using sharp's raw input and output to do some color manipulation on images in addition to resize and crop.
the challenge is that
output
must have the correctnewWidth
andnewHeight
or it will throw an error like:libc++abi.dylib: terminating with uncaught exception of type vips::VError
while knowing the original image size I can calculate what
newWidth
andnewHeight
can be, but since there is a possibility of using different rounding methods than sharp I might get the wrong values.I currently use
Math.round
as sharp does but is it always going to be the case ?One way that might help with this is to add a utility function that exposes sharp internal calculations so we can have the same values.
The text was updated successfully, but these errors were encountered: