-
Notifications
You must be signed in to change notification settings - Fork 76
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
Incorrect exposure bias value #24
Comments
This is because A Because of this, |
asmaloney
added a commit
to asmaloney/easyexif
that referenced
this issue
Sep 10, 2018
- signed rationals (format 10) are treated the same way as unsigned rationals (format 5) - ShutterSpeedValue is an APEX value, so calculate and store the actual value Fixes mayanklahiri#24
asmaloney
added a commit
to asmaloney/easyexif
that referenced
this issue
Sep 10, 2018
Signed rationals (format 10) are treated the same way as unsigned rationals (format 5) Fixes mayanklahiri#24
I fixed the BUG of read ExposureBiasValue (曝光补偿数值BUG修复) |
Thank you
…---- Replied Message ----
| From | Andy ***@***.***> |
| Date | 12/22/2024 02:57 |
| To | ***@***.***> |
| Cc | ***@***.***>***@***.***> |
| Subject | Re: [mayanklahiri/easyexif] Incorrect exposure bias value (#24) |
FYI this repo isn't updated anymore.
If you look at my commit (just above your comment) from 2018 to my fork , this issue is fixed along with another one. (I also fixed other things and updated the code.)
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: ***@***.***>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello,
Attached are 2 files with non-zero exposure bias value. DSC_5644 is +0.3 EV and DSC02268 is -1.3EV. Easyexif reports 0 for both images.
In fact the exposure bias value is not read at all, as the expected format is 5, but the reported format is 10. I've tried to force-read the tag as format 5, but it crashed.
Thanks for your help.
The text was updated successfully, but these errors were encountered: