-
-
Notifications
You must be signed in to change notification settings - Fork 471
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
Canon Raw .CR2 file corrupted after ImageGlass saved rotation #1504
Comments
This issue should be fixed in the latest build of ImageGlass Moon 8.7: https://imageglass.org/moon. The saving behaviors are also changed:
|
I checked with version 8.7.113.17 x64 Portable, and unfortunately the bug still exists.
Pardon my lack of understanding regarding image file formats, but I thought there was two ways to "rotate" an image:
I read that the Canon .CR2 file is actually a TIFF image file under the hood, with a full sized JPEG "thumbnail" image in the header, as well as other smaller JPEG thumbnails, and some metadata. I don't know if the aforementioned style of non-destructive rotation is possible with these types of RAW files. |
Unfortunately, I will remove the save (override) image for the unsupported write formats which already documented here: https://imageglass.org/docs/supported-formats. I have tried, but it's getting complicated to make MagickNET detect the input format. If user rotates then press Ctrl+S for the unsupported write formats (e.g. CR2, PSD,...), it will open "Save as..." dialog. |
System information:
To Reproduce
Steps to reproduce the behavior:
0. In settings > Edit: "Save the viewing image after rotating" is checked/on.
Actual behavior:
The file has saved and is bigger, from 33,707,533 bytes ballooning to 84,555,210 bytes.
In ImageGlass, moving back to view the newly rotated .CR2 file displays the error message. See screenshot (below).
Expected behavior:
The newly rotated and saved file should not be corrupted and display in ImageGlass.
Image should be the same size, or within a few bytes.
Screenshots:
Additional context:
Perhaps related to a 2021-06-14 issue: "Image (still) gets corrupted after rotating #1097"
[https://github.com//issues/1097]
The text was updated successfully, but these errors were encountered: