DNG Profiles and Camera Differences

The primary stated reason for performing a calibration before the DPE was to account for differences between units of the same camera. With the new Adobe Standard profiles, am I correct in saying that it is no longer possible to customize the Adobe Standard profile for a specific camera, since the ACR 4.4 version is always used by DPE as the starting point for the Chart operation?
I find that there is a marked difference between ACR 4.4 and Adobe Standard, with ACR 4.4 being much more saturated - it's not subtle - at least for my camera (Canon XSi/450D).
Thanks,
Selby

Eric - thanks for the response. I was afraid that would be the answer! :-)
Seems I'm likely asking for an enhancement based on the following:
As I understand it, the ACR 4.4 profiles were all based on processing color checker (or other target) shots made in the lab. Then Adobe Standard profiles were built using ACR 4.4 profiles as the starting point, but applying some adjustments to deal with issues raised by users. Due to the large number of cameras supported, I am guessing that this was applied programmatically - that each camera was not reprofiled?
So it appears that what I'm asking for is the ability to use the Chart facility in the DNG Profile Editor to use my image(s) of a Color Checker as the starting point, and then have the same changes applied that were used to build Adobe Standard. I gather that this is not possible at present.
I don't pretend to be an expert on the internal workings of the profiles which leads me to the following question: is this reasonable and/or practical?
BTW, I do find that Adobe Standard works better for me than either ACR 4.4 or anything I can generate with Chart. However, the insistence by those with much more experience than myself that the differences between instances of the same camera model are visible, led me to ask the question.
Since Adobe Standard is a big improvement over ACR 4.4, I'd like to pick up those changes since I doubt I could do anywhere near as good a job trying to make the changes "manually", unless of course, it is possible to describe the adjustments needed to use the DNG Profile Editor to accomplish this (other than by eyeballing it).
Thanks,
Selby

Similar Messages

  • DNG Profiles and the ACR Calibrator

    In the past the Fors ACR Calibrator (and the manual procedure conceived by Bruce Fraser) was required to account for production differences between instances of the same camera model. If I wish to use the new Adobe Standard Profiles, should I then rerun the Calibrator? I realize I will have to update the code to handle the new ACR version number - I already did this for 4.4.1.

    Thanks for the nice feedback, Bill.
    To clarify the point brought up by you and Richard: there are two basic ways to use the chart wizard feature.
    First, you can use it to build a profile optimized for one lighting condition. This is the more familiar case, esp. to those of you who have used the CR calibration scripts in the past. This mode is described in Tutorial 5, and is enabled by choosing the 'Both Color Tables' option from the popup in the Chart tab. What happens here is that a single set of color lookup table adjustments is created, which is applied regardless of the white balance of the image. You can use any illuminant when photographing the ColorChecker; doesn't have to be illuminant A or D65. Such a profile will work pretty well as long as your real images don't stray too far spectrally from the illuminant you used to shoot the CC.
    Second, you can use it to build a more general profile as described in tutorial 6, but you would need to shoot the CC in conditions as close as you can get to A and D65 for best results. (~D50 or ~D55 lighting as a substitute for D65 should work pretty well.) The DNG 1.2 profile format actually allows the two illuminants to be different than A and D65, but currently the DNG Profile Editor's chart wizard feature only supports these two.
    Bill, you should be able to shoot the checker in the manner you describe (i.e., under noon sunlight on a blue sky day, and also under the incandescent bulb) and have it work well.
    When I was testing this, I used a standard household incandescent (very close to illuminant A; I was curious and measured it with an Eye-One spectro) and then tried various flavors of daylight (including Solux bulbs, which aren't that close to D65) for the D65 "half" of the profile. The daylight portion didn't make that much difference.

  • DNG profiles and WB

    Can a DNG profile to change the WB setting?
    Mmhm maybe the video is not so clear, but the new profile canghes the WB from 4650 / 14 to 5000 / 15
    Message was edited by: Marco N.

    If I remember well about the WB values in ACR/LR, those numbers are related to the rendering of the image to give the correct WB "look" but aren't fixed. They can be even different from those in other raw converters.
    So it seems to me the WB values can be influenced by the color profile used.
    May be Jeff Schewe or someone from Adobe can give you more in-deep details about the WB rendering in ACR.
    Massimo

  • ACR Camera Profiles and Camera Manufacturing Tolerances

    For every camera model there is one set of model specific ACR camera profiles. Although those profiles are model specific, they are not camera specific. I'd suspect that not all cameras of the same model will produce exactly the same colors due to manufacturing variations. I'm wondering if differences in color rendition between cameras of the same model are visible or neglectable? Any experiences?
    A similar question: Taking the "same" photo with a Canon 550D and a Nikon D90 camera and processing the RAWs in LR with Adobe Standard profile can result in quite different colors (even when setting WB manually). Shouldn’t the processed photos look almost the same?
    Thanks in advance for any help!

    My Nikon D80 and D90 don't look the same and I have run comparisons between the Canon 7D and the Nikon D90. Taken together, they all different from each other.
    The biggest difference between the D80 and the D90 seems to lie with the much larger dynamic range of the D90. Compared to the D80 at first glance, the D90 seems washed out at the lower values. This is easily overcome in ACR, but even with that, the subjectivity of the reproduction sometimes gives a nod to one over the other.
    The closest film comparison is Fuji Astia vs Provia. The D90 at default Nikon Camera Standard resembles Astia, while the D80 is a cross between Provia and Velvia. All this is controlable. One slider I use to enrich the D90 presentation is the black slider
    The Canon has other undefined differences which I have simply noted by viewing. I haven't engaged in any tweaking of that camera's images.
    So I'll use both the D80 and the D90 according to what I am wanting to happen. Of course, there are times where the differences simply inform the operator of what may be doable, and then one is tweaked to look much like the other.
    I checked out sprengel's links to the calibrator software. They have stopped at CS3, it seems. How does it perform with CS5? I may want to at least run a calibration of both cameras and look again.
    And, of course, Adobe Standard and Nikon Standard do not agree. At all. So, when is a standard not a standard?
    When there is more than one.
    Looking back at your post, I should specify that the profile I used when making the comparisons have been  the Camera standards, not Adobe Standard.
    Message was edited by: Hudechrome

  • Adobe DNG Converter and Camera Raw 4.5 update available

    See: http://www.adobe.com/support/downloads/detail.jsp?ftpID=3940 for both.
    See: http://www.adobe.com/support/downloads/detail.jsp?ftpID=3942 for Camera Raw 4.5 update only.
    Neil

    >> Yesterday's ACR+Photoshop+Bridge works fine here
    I am talking about very specific conditions outlined here that spanned two intel boxes on trustworthy 10.5x installs...
    Buko, "Bug: Multiple Files Open ACR Crashes Photoshop..." #1, 10 Jun 2008 2:57 pm

  • White Balance tool and Camera Calibration Profiles

    Downloaded Lightroom v4 Beta 1 for mac but the installer package failed to launch. (com.apple.installer.pagecontroller error -1.) So I've only watched the adobe tv presentations todate.
    Anyway just wanted to give some feedback as a pro photographer about use of Lightroom and improvments I would like to see in the next version.
    I am a commercial photographer who needs colour accuracy in photographing fashion/garment images - most of my work is reproduced on a printing press for catalogues and brochures. On average a shoot will yeild about 500 images for a client, so workflow is important as they normally want them all!
    As a previous user of Capture One Pro v6 and now lightroom v3.6 - the biggest issue I have with Lightroom is the dominace of red tint when setting the white balance from a gray card reference image, shot at the same time as the images to be processed. I'm not adding anything to the images other than doing a white balance, a tweak on exposure and camera neutral setting on profiles.
    To obtain a white balance setting I use the combination of an  Xrite white balance card and the Q-Card and the old fasioned Kodak Gray cards all mounted on the same surface. I've used spot and ambient light readings on the gray cards to measure exposure and I've used the Adobe DNG Profiler and the Xrite colour checker profiler with the large colour checker card as a reference, (I've made profiles for sunny days, cloudy days, dual illuminant etc etc) and I'm viewing my images on a colour calibrated apple monitor.
    Not withstanding all of the above the best results I get out of Lightroom are using the camera profile neutral setting! Everthing else is just too red!! even though the images do look more punchy; for accuracy of actual colour I choose the camera neutral profile.
    Well when I say best results, those for colour critical garment photography and skin tones, these results are similar to those obtained from capture one pro v6.
    So for the Lightroom v4 I would like to see.
    1. White balance RGB values in numbers rather than percentages.
    2. Add and delete a colour readouts points with a dropper tool on an image to enable more acurate colour balancing particularly in shadow areas - (already available on capture one pro and adobe photoshop)
    3. Curves adjustments in all RGB channels (think you've done this)
    4. Output to CMYK profiles.
    5. Individual levels channel adjustment for RGB
    6. Ability re-organize my tools palette (add and remove) is per Capture One and Photoshop
    Regards

    The legacy ACR X.x profiles are no more produced nor included for newer cameras (AFAIK, since ACR 5.1/LR 2.1). The Adobe Standard is the new default starting point for these.
    While I am at it....are the Canon camera profiles I downloaded for the 1Ds MKII the same as for the 5D MKII or do I have to download different one...I suspect they are the same or Lightroom wouldn't offer them to me...is that correct?
    The profiles are different for each camera model, even if they share the same name in the Calibration panel. If you can see them when developing 5DII files, it means the camera-specific profiles are installed for your particular camera model (otherwise, you wouldn't see them).

  • DNG Beta 2 Camera Profiles

    I installed the beta2 camera profiles for PS CS4.  Camera Raw 5.6.   When I go to the dropdown box in the Camera Profile presets there is only listing for nikon D2x profiles and Camera Standard, Portrait, Neutral, and Vivid.   I have a D300.  Should there be profiles for other cameras other than the Nikon D2x?  If Yes  how do I import them or where can I find them.  Are there profiles for the d300?
    Thanks

    The profiles that don't say a camera are for the current camera which is a D300 in your case.  The D2x ones simulate that camera mode on the D300.
    I think the D300 is new enough not to be supported by the old, old beta profiles, but they will clutter up the list for older cameras, so it's better not to have installed them.  ACR 5.6 comes with its own up-to-date list of profiles.

  • Profile Editor and DNG Profiles - Still Beta 2?

    Are the DNG profiles and Profile Editor still at Beta 2? I am confused because the Adobe Labs DNG Profiles resources page (http://labs.adobe.com/wiki/index.php/DNG_Profiles) has not been updated since Oct 22 2008, but Lightroom 2.2 provides non-beta profiles. What is the present status?
    Thanks.

    It has been several months since I originally posted this inquiry and Thomas replied, and so I'm just checking again.
    Has there been any update to the DNG Profile Editor since Beta 2 was made available? (and, if not, is there anything you can share about what's going on with this tool?)
    I am continuing to use Beta 2 with successful results, but I am curious as to the status...
    Thanks,
    /eddie

  • DNG profiles, Calibration tab and HLS

    X-Rite and Adobe have provisions for creating custom DNG profiles. DataColor just announced a product that appears to operate like these two but instead of making DNG profiles (or as we had in the old days, altering the Calibration Tab), updates the HSL controls. My understanding is that DNG profiles and the Calibration tab operate in a different order of the processing, prior to all the sliders above them. My understanding is there are benefits for doing this but I’d like to know more about this. The question is, what are the practical implications of “calibrating” via a target that affects HSL sliders instead of producing a DNG profile, or at the very least, altering the calibration sliders? Eric you out there bud?

    Andrew,
    Eric is very active in the ACR forum, including in the last 24 hours, and there's no way he'd be ignoring you if he had read this post of yours.
    My impression is that this DNG forum has been neglected if not outright abandoned.  Just look at the obsolete and mistyped "announcement" at the top of the index page.
    I would suggest posting in the ACR forum instead.
    Wo Tai Lao Le
    我太老了

  • DNG profile management

    Is it possible to create and use a shoot-specific custom DNG profile to process a set of images for a given shoot, and then archive that DNG profile for safekeeping but removed from view of Lightroom's Camera Calibration panel, without compromising Lightroom's ability to still work with that shoot's images - say, to make further develop refinements, virtual copy variations, prints, etc.?
    Asked slightly differently, when in Lightroom's Camera Calibration panel you select a specific DNG profile to apply to a given raw image, does the profile data from within that DNG profile become image-specific metadata of the target image and get stored along with the rest of the image-specific metadata in the Lightroom catalog itself (and subsequently in the DNG raw image file when I save the Lightroom data to that image file)? Or, instead, is only the IDENTITY of the selected DNG profile saved as image-specific metadata, with the DNG profile itself needing to remain "installed" in order to carry out any future Lightroom work on that raw image?
    Using the X-Rite ColorChecker Passport in conjunction with Lightroom, it is quite easy to imagine creating custom DNG profiles specific to a given shoot's unique lighting conditions. Creating DNG profiles specific to a given shoot, the collection of shoot-specific DNG profiles for a given camera body could grow to be quite large over time, making it tedious to wade through that collection in Lightroom's Camera Calibration panel to select the particular profile for the shoot being processed. X-Rite makes the "DNG Profile Manager" available to registered users of the ColorChecker Passport to assist with this very problem. It's great that this utility allows us to "Disable" DNG profiles, allowing us to keep our Lightroom Camera Calibration "Profile" menu manageable. But, if you use the X-Rite DNG Profile Manager to do this, does "disabling" a given DNG profile interfere with any further work in Lightroom on images for which that given DNG profile has ALREADY been applied?
    PLEASE do not speculate on this response. If you do not know for certain, please allow someone who does (an Adobe engineer, perhaps?) to enlighten us.
    Thanks in advance,
    /eddie

    Thank you to those who have offered responses.
    Please do not get confused. As the most recent response clarifies, this is not about storing profiles within original raw files, or the differences between DNG files and original raw files. In fact, at it essence, my real concern is not even about DNG files at all, really, although it includes them by association.
    My original question can really be answered in consideration of Lightroom alone: When a custom DNG profile is selected for an image by using the Camera Calibration panel of Lightroom's Develop module, does Lightroom itself internalize that DNG profile selection by recording into the Lightroom metadata database only the IDENTITY of that DNG profile assignment, or the actual DNG profile data contained within that DNG profile? If Lightroom records into the Lightroom database only the identity of the assigned DNG profile, then Lightroom would of course need to go back into that DNG profile later for the actual DNG profile data in order to do any subsequent development processing of the image for which that DNG profile was assigned. If, however, selection of a DNG profile using the Camera Calibration panel of Lightroom's Develop module causes Lightroom to record into the Lightroom database the actual DNG profile data contained within the selected DNG profile, then Lightroom would have no need to go back into that DNG profile later for the profile data, and the DNG profile itself could be safely "un-installed" ("Disabled" by the X-Rite DNG Profile Manager) without adversely affecting Lightroom's ability to properly process that image using the selected DNG profile's information. DNG image files themselves are not even really involved in determining the answer at this level.
    The interplay with the associated raw image's DNG image file occurs when Lightroom-maintained metadata for the image is saved out into the DNG image file itself, either automatically or manually, and, yes, I was being very specific to discuss DNG raw image files in that context. I understand from the response provided by "ssprengel" that saving the actual DNG profile data out into the associated DNG image file only happens when using "Update DNG Metadata & Preview" and does not happen through the more common routes of automatically or manually saving image metadata back to the DNG image file. Why this more robust ("complete"?) level of image metadata preservation out to the DNG image file only occurs through a more obscure mechanism is a mystery to me, but that is not the topic of this discussion.
    So, my real question really still remains. Combining the ideas from both of the paragraphs above, if Lightroom only saves DNG profile data out to the associated DNG image file using this more obscure mechanism, then does that mean that Lightroom does not normally retain the DNG profile data within the Lightroom database at all -- that it really only retains the identity of the selected DNG profile, and that only when this obscure mechanism is explicitly invoked does Lightroom deem it appropriate to actually read the profile data out of the selected DNG profile and pass that profile data along to the associated DNG image file, and that even then Lightroom itself does not retain that profile data internally? If this is the case, then the DNG profile cannot be "Disabled" without adversely affecting normal Lightroom processing of the associated image [by "adversely", I mean without having Lightroom revert to the Adobe Standard profile or any other unintended side effects]. However, if Lightroom actually does retain this profile data internally upon original DNG profile selection, even if it doesn't bother to save it to the associated DNG image file except through the use of the obscure function, then it would be safe to "Disable" the DNG profile after initial profile selection and not interfere with Lightroom's normal ability to process the associated image using that profile.
    Taking the obscure function awareness into account, I guess this now has the possibility of making this subject much more complex. If Lightroom does not store DNG profile data within the Lightroom database (which would require continued availability of the DNG profile for processing associated images), BUT Lightroom provides this obscure mechanism for "forcing" save of assigned DNG profile data out to the associated DNG image file, then what happens when the DNG profile is "Disabled" and Lightroom goes to process that image? Does it look into the associated DNG image file to determine if actual DNG profile data has been saved there and go ahead and use it if it exists? Or does Lightroom ignore DNG profile data saved to a DNG image file in all contexts, and unconditionally always require the assigned DNG profile to remain available in order to carry out normal Lightroom development or rendering processing of the associated image?
    This is admittedly a lot of words to discuss a simple desire: I want to shoot with shoot-specific DNG profiles, assign them to the shoot's images and develop them, and then archive off ("Disable") the DNG profiles from that shoot so that my Camera Calibration "Profile" listbox does not become unmanageable. Period. If I absolutely must go back and re-Enable a specific DNG profile later to make a print of one of those images a year from now, then I guess that's what I have to do, but that seems a real shame when all other image-assigned "edits" store those "edits" as image-specific metadata, and profile assignment is just another "edit" (although saving the profile data, rather than just the profile identity, may not be included in this "edit"). Whatever works out to be the simplest, most straightforward course to accomplish my objective is what I need to do. Ideally, that would be painless if Lightroom records into the Lightroom database the actual DNG profile data when the profile is assigned to an image using the Camera Calibration panel's Profile selector.

  • DNG profile editor

    A couple of questions about DNG Profile Editor:
    1-I know Lab values on my ColorChecker (measured with an EyeOne 2° D50). I shooted it with a Nikon D80 and I want to tweak one of the new Camera Raw profiles to match those values or to go closer. I see that changing the base profile (popup menu in Color Tables Pane) the image appearence changes a lot but the Lab numbers readout doesn't. I followed the tutorial on the Adobe site but I can't figure out how to make the camera calibration without having a numeric value, before and after, to look at. The tutorial tells that you may 'adjust the selected color via the Hue, Saturation and Lightness slider and you will see the preview in real-time'. That's true but does it means that is a sort of 'visual calibration'? Is there a way to tweak colors by the Lab numbers in order to have the best match from original Lab values in input (on the target) and Lab values in output (in a ProPhoto rendered image)?
    2- When I create a Color Table from my ColorChecker it appears that in the Color Tables colors are already (and automatically) changed. Does it work like the ACR Calibration Scripts that way? And is it possible to change the reference Lab values (ColorCheckers are different in color values) as it was with a simple ACR script's editing?
    Giuseppe Andretta

    Eric,
    Before starting, I want to say that I had cataract surgery last month. The vision improvement was almost instantaneous and dramatic. I can now state that color differences in individuals can be much greater than expected. It is hard to express how big the difference is in my own vision, let alone between two other individuals. Any color assessment tools must accommodate numeric as well as visual comparisons. That said, the healing process has also affected how much time I can spend comfortably in front of my screen. I hope my comments will be taken constructively.
    As others have commented, I also feel that the CC24 Lab target values being used should be documented. Published values from Gretag, Lindbloom, Babbage, and others disagree. Without the target numbers it is difficult to determine accurately the calibration result.
    My first attempt seemed to go smoothly, but when I verified the results with ReadColors.jsx (my script) the numbers degraded slightly. I was using the Gretag target values, so these may not be what Adobe is using. Also, I had already calibrated ACR for my D3. The doc seemed to imply that the ACR tabs would all default to zero and that was what displayed in the Color Matrices panel. But that was not what showed in the ACR panel. So I tried again, setting all ACR sliders to zero. This calibration attempt was a disaster, numerically and visually. Now I am confused. What is the relationship between these and what are the recommended user actions? In each case, I exported the DNG profile and selected it subsequently in ACR to re-open the image.
    Next, I played with the Color Tables panel. I set a watchpoint on the blue patch. As long as I hold the eyedropper over the blue patch the Lab (and other numbers) track. But as soon as I move the mouse to the sliders, the numbers disappear. If I move the hue and saturation sliders the image and the patch sample both change. And, yes a little arrow shows in the color wheel. But after moving the eyedropper back, none of the numbers have changed. The lightness slider is even more bizarre. Obviously no arrow (z-axis) but the image brightens and darkens (OK), without any corresponding change in the patch sample (watchpoint) on the right (not OK). And again, no change in the numbers at all. It would be very helpful if the target values were shown here and if the currently selected watchpoint that would track the numeric changes. It would also be nice if the watchpoint could show the target color as well as the initial and changed image patch colors.
    I dont understand the purpose of the Tone Curves. I understand gamma and Adobe linear, but these do not correlate to the ACR tone curves. And again the image changes but the numbers do not. Since we cannot set watchpoints in the neutral patches it is very difficult to assess any changes the user might make.
    Next, I used the Chart panel to Create Color Table. When I return to the Color Tables panel, there are the 18 color (no neutral) watchpoints. I can see that blue has changed in the watch point and the arrow in the color wheel. But the numbers are still the same as before. Scrolling through the watch points I can also see that the hue and saturation sliders have changed. But the lightness slider did not change in any of the color patches. I anticipated that this would be the major improvement over the ACR sliders. Is this just not in the calibration algorithms yet?
    This is a good start, but until I know what the target values are and what I should be doing about the existing ACR slider settings, I am at a stopping point.
    Cheers, Rags :-)

  • DNG profiles, Calibration tab vs. HLS

    Cross post (asked on the DNG forum but there isn’t much activity so forgive me)
    X-Rite and Adobe have provisions for creating custom DNG profiles. DataColor just announced a product that appears to operate like these two but instead of making DNG profiles (or as we had in the old days, altering the Calibration Tab), updates the HSL controls. My understanding is that DNG profiles and the Calibration tab operate in a different order of the processing, prior to all the sliders above them. My understanding is there are benefits for doing this but I’d like to know more about this. The question is, what are the practical implications of “calibrating” via a target that affects HSL sliders instead of producing a DNG profile, or at the very least, altering the calibration sliders? Eric you out there bud?

    thedigitaldog wrote:
    The question is, what are the practical implications of “calibrating” via a target that affects HSL sliders instead of producing a DNG profile, or at the very least, altering the calibration sliders? Eric you out there bud?
    I'm not Eric (not sure he would want to respond to this question) but I'll take a stab...first off, let me state that I haven't personally tested either the  SyderCHECKR PRO color target or the software. I've only watched the video and read the user manual. But I do have some issues regarding usability and the "practical implications" of using the HSL Sliders vs a DNG profile.
    There is one major implication–the SpyderCheckr produces a preset using the HSL adjustments rather than a DNG profile. I have no understanding (and haven't heard the rational) why Datacolor chose a Lightroom or Camera Raw preset instead of a DNG profile. But the first problem with creating "presets" is Lightroom and Camera Raw don't share "presets". So, unlike a DNG profile which will work in both Lightroom AND Camera Raw, the Spyder solution is application specific. The other major issue is that presets are not easily transportable compared to DNG profiles which actually get imbedded in a raw file. I have no reason to suspect that the HSL adjustments of Lightroom and Camera Raw CAN'T handle the color corrections needed for calibration, but the fact that the calibration depends on a "presets" limits its usefulness.
    What is also not mentioned in the videos nor the manual is what the user is supposed to do regarding the starting DNG profile. Does Datacolor suggest using Adobe Standard or some other DNG profile? I ask because the HSL calibration applied as a preset depends upon the DNG profile used to create the color sample file and adding a calibration on top of an existing DNG profile seems to complicate the whole calibration process. When using DNG profiles, it's pretty straightforward what the DNG profile creation is actually doing. Adding an HSL adjustment on top of an existing DNG profile adds complexity to the process and reduces the portability of the camera calibration.
    The documentation seems to imply that both DNG Profile Editor and X-Rite's Passport solution somehow limits the end user's ability to make further adjustments. I think this is false...while you can't currently edit the resulting Passport generated DNG profile in X-Rite's software, you can indeed edit the resulting Passport generated DNG profile in Adobe's free DNG Profile Editor. You can edit the preset that SpyderCheckr creates in either Lightroom or Camera Raw, but you are editing an absolute preset that applies HSL adjustments requiring the saving out of a new subset of HSL adjustments-and again presets are not interchangeable between Lightroom and Camera Raw. I see this as a very limiting factor.
    In principal, I encourage the development of more and better solutions for both Lightroom and Camera Raw. Whether or not the HSL calibration approach is superior to the DNG profile calibration approach, I really wonder whether or not HSL is a better solution than the DNG profile approach. It seems to me that Adobe (and Thomas Knoll and Eric Chan) have spent a lot of time and effort to develop an open solution to camera calibration that the SpyderCHECKR approach is ignoring. Personally, I would have encouraged the option to create either a DNG profile _OR_ an HSL calibration preset. I think it's a mistake to ignore the DNG profile approach.

  • I have downloaded DNG Profile Editor 1_0_4 and prepared a profile which I can not see in my Camera Raw 6.0 (I have photoshop CS5). Could you please give me an advice?

    I have downloaded DNG Profile Editor 1_0_4 and prepared a profile which I can not see in my Camera Raw 6.0 (I have photoshop CS5). Could you please give me an advice?

    Uninstall Trusteer software
    http://www.trusteer.com/support/uninstalling-rapport-mac-os-x
    Remove Sophos
    https://discussions.apple.com/message/21069437#21069437

  • **-Camera Profiles and DNG Profile Editor FAQ-**

    A page containing answers to Frequently Asked Questions about Camera Profiles and the DNG Profile Editor can be found
    here

    New FAQ entries:
    What changed between beta 1 and beta 2?
    Is it safe to delete beta 1 profiles? What will happen if I do?
    I now have the beta 2 profiles and want to delete the older beta 1 profiles. How do I do this?
    Please read carefully.

  • DNG Converter 5.2 and Camera Profiles

    Hi!
    I tried to search for an answer but did not find any.
    Question - how and when DNG Converter will use Camera Profiles?
    How do I specify which profile to use?
    I assume it can use them - version 5.2 comes bundled with them...
    Тhanks for the help!
    P.S. Since new version has installer, I'd suggest to create uninstaller too.

    >This somehow implies that DNG Converter reads settings from installed Lightroom. I'm not sure that this is the case - DNG Converter seems to be completely independent product.
    Yes, it does...for the camera model, if you have modified the Camera Raw Default in either Lightroom or Camera Raw then DNG Converter will use the user specified default. If there is no user set default, then of course will use the regular Camera Raw Defaultwhich in the case of 5.2 is now Adobe Standard. (I can't remember what version of DNG Converter started reading the CR prefs).
    >If I give DNG file to someone, who uses DNG-compatible program (other than Adobe's), do I have to give him all profiles as well?
    If you are using a "custom" profile other than Adobe Standard, the behavior is to embed that profile in the DNG so it is self describing. The only complicating factor is what version of Camera Raw/Lightroom the recipient is using. If they are using a version prior to Lightroom 2 or Camera Raw 4.5, then those older versions ignore the embedded profiles and will use the earlier simple profiles that have been used since DNG/ACR was introduced.
    As for checking on updating the DNG Profiles in the future, DNG Converter, as it's rev'ed, will include any new profiles that come out and will update them for any already installed and add any new profiles available for a given camera. The odds of updating existing DNG Profiles is not largethat's what the 2 beta rounds was for, to shake them out. But it's possible. It's more likely that profiles for new cameras will be added.

Maybe you are looking for