Skip to content
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

Fixing DNGs to work with more raw converters #91

Open
borissimo86 opened this issue Oct 12, 2016 · 2 comments
Open

Fixing DNGs to work with more raw converters #91

borissimo86 opened this issue Oct 12, 2016 · 2 comments

Comments

@borissimo86
Copy link

Could the following be implemented to make Kalpanika DNGs more compatible with raw converters?

Stated by Brian Griffith (author of Iridient Developer) at https://www.dpreview.com/forums/thread/3912319

"The per channel white levels is likely what caused the most noticeable color issues with the images previously and would probably be an easy change to improve theDNG compatibility with even more RAW processors. Just multiply the color channels prior to saving to DNG so that they share the same identical maximum channel white.

The use of the gain map DNG opcode was the other missing piece in prior versions of Iridient Developer and that too could probably be baked in without much if any negative impact on the final image just shift the maximum white point some such that no clipping occurs after applying the gain maps..."

@rolkar
Copy link
Contributor

rolkar commented Oct 12, 2016

Thanx for your information. I assume we care about both white level and gain map. But, Erik would know that better.

@erikrk
Copy link
Contributor

erikrk commented Oct 12, 2016

The channels could in principle be multiplied so that the white levels are the same, but it wouldn’t necessarily fix the problem. It depends on if the problem is with the actual handling of per channel white levels, or with handling of white balance. The gain map could in principle be baked in, but then there wouldn’t be any way of correctly specifying the white level. It has to be specified exactly where clipping occurs. If the white level is set too high, clipped data will be handled incorrectly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants