flash
Member
+1 for the huelight profiles. Much beter colour as far as I'm concerned. Ive made several of my own profiles and Colin's are better than any of them. well worth the 10.00.
Gordon
Gordon
M9 profile: embedded or adobe standard?
- Thread starter EdwardKaraa
- Start date
- Latest activity Latest activity:
- Replies 24
- Views 712
MCTuomey
Veteran
just placed an order for the huelight profiles ... excited to try them based on the testimonials above, thanks Duane and Gordon.
Update: Received the huelight profiles over the weekend. Three copied into LR 4.3 profile folder: Low, Standard, and High. Initial rest drive, running some ambient indoor mixed lighting files with the huelight profiles (torture test) - very pleasing results. Better skin tones than embedded or Adobe Standard, clearly, and nice baseline contrast from which to start tweaking.
If I have time this week, I'll post some comparisons.
Update: Received the huelight profiles over the weekend. Three copied into LR 4.3 profile folder: Low, Standard, and High. Initial rest drive, running some ambient indoor mixed lighting files with the huelight profiles (torture test) - very pleasing results. Better skin tones than embedded or Adobe Standard, clearly, and nice baseline contrast from which to start tweaking.
If I have time this week, I'll post some comparisons.
EdwardKaraa
Well-known
So Mike, how are the profiles working for you so far?
Ronald M
Veteran
Adobe Lab> profile editor and profile the camera for 6500k and 2800k. Then set the ACR to recognize the camera by serial number. Color will be correct.
Whi Bal card gets you correct in camera. Save as a profile . I use profile 1 as daylight, do one for flash, override any for special conditions but do not save.
Whi Bal allows magenta/green to be set properly. Leica only allows blue/yellow . Now color is correct in camera. Profile is set in ACR.
Gone are color management issues to a large extent.
Whi Bal card gets you correct in camera. Save as a profile . I use profile 1 as daylight, do one for flash, override any for special conditions but do not save.
Whi Bal allows magenta/green to be set properly. Leica only allows blue/yellow . Now color is correct in camera. Profile is set in ACR.
Gone are color management issues to a large extent.
willie_901
Veteran
Profiles Are Not Color Spaces
Profiles Are Not Color Spaces
Different LR Camera Calibrations use different parameters in the raw-file demosaicing algorithms. One of the many things these parameters affect is hue rendition. In LR these are selected using the Camera Calibration panel. There are two main options - the Process and the Profile.
LR 6 has three Processes - 2003, 2010 and 2012. Older versions may not have 2012. Different Processes use different rendering algorithms. If you can use 2012, I can't think of a single advantage to using older Processes.
The Camera Calibration Profiles use different variables in the Process rendering algorithms. The Profiles are meant to accommodate differences between cameras. Different sensor color-filter array properties are accommodated by different Profiles.
Adobe Standard is the default raw file rendering based on Adobe Labs' empirical testing.
Adobe also provides Profiles for raw rendering that are purposed and specific to a camera. In some cases Adobe attempts to reproduce the set of in-camera JPEG profiles. One can also create and use custom Profiles using several different calibration tools. Creating a custom Profile without a carefully calibrated monitor is a fool's errand. As with all LR raw renderings using any of the Camera Calibration options is reversible.
The Embedded Profile applies to in-camera JPEGs (or other devices whose on-board firmware controls raw rendering). For in-camera JPEGS LR uses JPEG rendering parameters form the camera menu options. TIFF image files from my iPhone also use an Embedded Profile.
The color space is completely different. LR uses ProPhotoRGB for on-screen rendering. When you export an image you get to choose its color space. As mentioned above, sRGB, Adobe RGB, etc, have different purposes and should be selected to match the technical aspects of the viewing platform, including the printer's software and hardware. Photo editors, marketing directors, print labs and consumer printer documentation usually specify the color space.
Problems with global color rendering can be resolved several ways. One is to use a Profile you prefer. Creating your own custom Profile provides complete flexibility. The other is to create a custom user Development Preset. A Development Preset operates on any Profile's default rendering. As mentioned above it is trivial to apply any Development Preset automatically upon import.
Profiles Are Not Color Spaces
Different LR Camera Calibrations use different parameters in the raw-file demosaicing algorithms. One of the many things these parameters affect is hue rendition. In LR these are selected using the Camera Calibration panel. There are two main options - the Process and the Profile.
LR 6 has three Processes - 2003, 2010 and 2012. Older versions may not have 2012. Different Processes use different rendering algorithms. If you can use 2012, I can't think of a single advantage to using older Processes.
The Camera Calibration Profiles use different variables in the Process rendering algorithms. The Profiles are meant to accommodate differences between cameras. Different sensor color-filter array properties are accommodated by different Profiles.
Adobe Standard is the default raw file rendering based on Adobe Labs' empirical testing.
Adobe also provides Profiles for raw rendering that are purposed and specific to a camera. In some cases Adobe attempts to reproduce the set of in-camera JPEG profiles. One can also create and use custom Profiles using several different calibration tools. Creating a custom Profile without a carefully calibrated monitor is a fool's errand. As with all LR raw renderings using any of the Camera Calibration options is reversible.
The Embedded Profile applies to in-camera JPEGs (or other devices whose on-board firmware controls raw rendering). For in-camera JPEGS LR uses JPEG rendering parameters form the camera menu options. TIFF image files from my iPhone also use an Embedded Profile.
The color space is completely different. LR uses ProPhotoRGB for on-screen rendering. When you export an image you get to choose its color space. As mentioned above, sRGB, Adobe RGB, etc, have different purposes and should be selected to match the technical aspects of the viewing platform, including the printer's software and hardware. Photo editors, marketing directors, print labs and consumer printer documentation usually specify the color space.
Problems with global color rendering can be resolved several ways. One is to use a Profile you prefer. Creating your own custom Profile provides complete flexibility. The other is to create a custom user Development Preset. A Development Preset operates on any Profile's default rendering. As mentioned above it is trivial to apply any Development Preset automatically upon import.
Similar threads
