Do not forget to uncheck the noise and optical correction settings.

once the settings have been made in the raw and just before switching to PureRaw, make a copy of the settings, then paste them once the dng has returned to LR.

To solve your problem, I only see two workarounds: For example, if I choose Adobe Monochrome, it is this profile that is applied to the dng (it is indeed in black and white).īut as soon as you go to other profiles, such as “camera matching” profiles, it is the Adobe color profile that is applied instead of the chosen profile.Įxamination of the xmp files shows that Lightroom does not save in the same place and in the same way the info of the “Adobe xxx” profiles and the “camera matching” profiles.Įven though it’s possible that PureRaw had some part of the blame for this problem, I’d have a strong inclination to think it’s a Lightroom bug, since it’s obvious that PureRaw doesn’t modify xmp files at all : it does not read them, it does not modify them… in any case on all the tests that I could do.

As long as we use a “standard” setting from the “Adobe xxx” list, we recover the correct setting when the dng returns. Then Lightroom retrieves this dng and immediately applies the same settings to it as to the raw file.Īfter a lot of research, I actually see a problem in the corrections that LR applies to the dng for the color profiles. It is a linear dng file with only noise and lens corrections. The dng file that PureRaw sends to Lightroom does not include any changes made to the original raw file. Special Uses For Lightroom Camera ProfilesĬamera Profiles actually have more to offer than just the basic camera colors! Its possible to actually create lightroom presets with custom camera profiles that can improve your photography & your editing workflow by giving you more flexibility when editing.If I remember correctly, when it returns the dng, it just instructs Lightroom not to enable noise and lens corrections, but it doesn’t know what corrections were applied in LR.

Lightroom profiles