Creating Profiles and Making them Universal

Report · Nov 10, 2020

Hello all!

Does anyone know if there is a way to make a profile universal when you create it? I've purchased profiles/luts in the past that I'm able to apply to an image in CameraRaw to any file I have open (reguardless of which camera it was captured on). However, when make a new profile of my own in ACR, it appears to only be usable on images captured on the same camera. I'd like to have the profile applied to ANY image, regardless of how it was captured.

Thanks in advance!

Report · Nov 10, 2020

Interesting...I'm not able to reproduce on my end your issue (to my understanding). For example, I've created profiles in ACR and see them available to all file types (TIFF, CR2, RAF) within the profile selector in Lightroom Classic CC. Am I missing part of the issue?

In Response To JBedfordPhoto · Nov 10, 2020

Interesting. I don't think you're missing anything.

When you create your profiles, are you appling a LUT in the dialog?

In Response To ericrwebb · Nov 16, 2020

(not getting notifications re: this thread for some reason...)

Yes, I'm applying a LUT created in LRCC with a LUT exporter plugin. Still a little confused about the consistency of applying these specific LUTs to newly generated profiles created in ACR as results tend to vary (but that's probably my own lack of comprehension on the matter).

Report · Nov 10, 2020

What kind of profile? Camera Profiles (DCP) are per each specific camera model and cannot be universal.

A preset (or XMP) is different.

There are two types of profiles now: DCPs and the newer XMP-based ones. In terms of the newer XMP based profiles, they specify a base DCP. For the vast majority of them, including those made by third parties, that base DCP will be Adobe Standard. So the first consideration is that XMP Profiles are built on top of DCPs and extend the DCP profile. On top of the base DCP, there is an optional Look Up Table/LUT. XMP-based profile can also specify many but not all of the options from the GUI we use. There are some reasons why these profiles do not move corresponding sliders. For example, a preset for vignetting adds just a vignette and do nothing else, the other adjustments are not altered.

If the sliders move, it's a preset. If the sliders don't move, it's a profile. And they are separated in the browser, partially for this reason.

Author “Color Management for Photographers" & "Photoshop CC Color Management/pluralsight"

In Response To TheDigitalDog · Nov 10, 2020

Thanks for the reply.

I'm creating the profiles with the goal of using LUTs (added as a .cube in the Color Lookup Table box) when I create the profile. So, no sliders move in the profiles I'm creating. And, the profiles are .xmps. I'm only using the profile to apply the LUT between the DCP Adobe Standard (or Camera Neutral). The problem is I can't figure out why sometimes I can see profiles I've created, and sometimes I cannot. The profiles I've made seem to be hidden if I'm trying to apply them to an image that was captured on a camera that is different from the one the profile was made with.

In Response To ericrwebb · Nov 10, 2020

Hi,

I began a few days ago to make special camera profiles to replace the ones enbeded in the file and the Adobe ones.

If you want to see them for every camera you use, you have to create one for each camera model. I use three, so it triples the work.

In Response To pdophoto · Nov 11, 2020

What's intersting though is that I've purchased profiles before (like the ones at proedu) and they work universally across all of cameras. So, there's got to be a way to do it. I've cracked open one of the xmps that is created when you make the profile and there's some metadata at the top that I'm going to experiement with. I'll reply if I find anything. Cheers!

In Response To TheDigitalDog · Nov 16, 2020

@TheDigitalDog this was a really clear explanation about a topic that can usually be pretty confusing. Thanks for sharing.

Report · Nov 11, 2020

crs:PresetType="Look"

crs:Cluster=""

crs:UUID=“RemovedInCasePersonalInfo”

crs:SupportsAmount="True"

crs:SupportsColor="True"

crs:SupportsMonochrome="True"

crs:SupportsHighDynamicRange="True"

crs:SupportsNormalDynamicRange="True"

crs:SupportsSceneReferred="True"

crs:SupportsOutputReferred="True"

crs:CameraModelRestriction=""

crs:Copyright=""

crs:ContactInfo=""

crs:Version="13.0"

crs:ProcessVersion="11.0"

crs:ConvertToGrayscale="False"

Report · Nov 11, 2020

I was able to find a workaround that gave me the bahvior I was looking for. If you open an xmp profile with a text editor, you can modify some settings that will make the profiles compatable across all cameras. Below are the settings I modified.