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

ICC and DCP support #245

Open
ghost opened this issue Nov 5, 2022 · 8 comments
Open

ICC and DCP support #245

ghost opened this issue Nov 5, 2022 · 8 comments
Labels
enhancement New feature or request

Comments

@ghost
Copy link

ghost commented Nov 5, 2022

Hello,

Would it be possible to specify which ICC profile and/or DCP is to be included in the converted DNG ?
That would be very useful for archival purposes.

Thank you

@cytrinox cytrinox added the enhancement New feature or request label Dec 24, 2022
@cytrinox
Copy link
Contributor

This should be possible to implement but as embedded DCP profiles are not wide supported by FOSS software, I've not priorize DCP support at all. Could you please describe your workflow and/or benefits from having a embedded DCP profile and what target software you use?

@iiborg
Copy link

iiborg commented Dec 24, 2022

DNG files are open for interpretation, and thus DNG doesn't provide stable rendering.

@ghost
Copy link
Author

ghost commented Dec 24, 2022

DNG files are open for interpretation, and thus DNG doesn't provide stable rendering.

That's actually a good thing. A TIFF is "too cooked" meaning that the treatment artefacts are baked in.

In Cultural Heritage having the DCP embedded would permit to have only 1 file.
The included profile should also be used when the DNG is opened by any viewer ?

@iiborg
Copy link

iiborg commented Dec 24, 2022

If you are not concerned with stable rendering, and for archival purposes, why not preserve the original raw instead of a derivative?

Both DNG and DCP standards are fluid, better DCPs are always around the corner, and if one isn't concerned with stable rendering, embedding obsolete DCPs is a recipe for colour artifacts (blue turns purple and vice versa, red turns orange, unnatural greens, metameric errors, etc)

PS. Smart Objects allow as many trips to ACR as needed because they allow to include raw data. Layered TIFFs are fully editable, with the right workflow no artifacts are baked in.

@ghost
Copy link
Author

ghost commented Dec 25, 2022

Well original raw files are proprietary and that's a big no in terms of data preservation. So having an open raw format is a huge advantage.

Now it's not perfect by all means ! It's also smaller than TIFFs files.

Both DNG and DCP standards are fluid, better DCPs are always around the corner, and if one isn't concerned with stable rendering, embedding obsolete DCPs is a recipe for colour artifacts (blue turns purple and vice versa, red turns orange, unnatural greens, metameric errors, etc)

Shouldn't the DNG / DCP version information take care of that ?

And I'm not familiar with Smart Objects but I guess they're not open ?

@ghost
Copy link
Author

ghost commented Dec 25, 2022

Btw. Adobe Camera Raw does include the DCP in the DNG, but that's not FOSS.

@iiborg
Copy link

iiborg commented Dec 25, 2022

Please take your time to study the subject.

@ghost
Copy link
Author

ghost commented Dec 25, 2022

What FOSS do you recommend to work with Smart Objects ?

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

No branches or pull requests

2 participants