Very interesting and informative post-LR/ACR Camera Profiles

This post by Eric Chan from Adobe is very imformative and reveals the reality of processing of raw files not only from Adobe's perspective but for all software that processes raw files from digital cameras. The thread is concerning Adobe's processing raw files from a Panasonic Camera model in comparison to the Camera's JPEG rendition.
"Sorry for joining this thread late.
Unfortunately this is a limitation of our current color profile process. This limitation actually applies to all of our camera models that we support, not just Panasonic. What is happening is that the color transform we've built is optimized mainly for daylight and incandescent light conditions, but when applied to scenes with bright light sources (especially neon lights, and especially blue/purple lights), the transform will tend to oversaturate and clip those colors.
My team is investigating how to build better profiles going forward, but in the meantime, my main suggestion is to try reducing the Red/Green/Blue Saturation sliders in the Camera Calibration panel (not the HSL tab, and not in the Basic panel). This will help to reduce the oversaturation and clipping, and will give you a better starting point for further edits (Exposure, Contrast, etc.). As a shortcut, you can store your Red/Green/Blue Saturation slider adjustments as a preset that you can then apply quickly to other images you have that show the same issue."
Link to the actual thread.
http://forums.adobe.com/thread/1254354?start=40&tstart=0

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

Similar Messages

  • 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

  • Very interesting and quizzical issue in JNI COding.

    HI All,
    i've been facing a really frustrating, interesting and mindwrenching issue in my native code. Here is a background.
    1. I was given a thirdparty ACtiveX OCX file that needed to be called through JAva.
    2. I wrote a C++ JNI wrapper to call the methods of the activex object.
    3. I first initialize the object, set the relevant parameters (sent from java) and then call the method I need.
    4. For every record, I need to perform step 3. NOw, I am ryuning batch loads. THE code works fine for 9500 records. BUt, once the record count reaches 9885, I get a pop-up error from the activeX OCX control. I've not coded that pop-up. It comes out of the blue.
    I initially thought that it could be a memory issue, but even after doubling my VM Memory allocation, I get the error. Its not a data issue, because the reocrd that causes the issue, if I run the code just for that single record, it works fine.
    Below is the implemetnation of the C++ code. LEt me know if I'm doign somethign wrong or if someone has seen something like this happen before. WHAt is baffling is that it works smoothly for less records. When the pop up appears, no exception is caught on the native side also.!!!
    Does java set aside some memory specfic for native libs and that is exhausted after 9885?
    I'm running on windows, so is it possible to trace the internal malloc and release within the dLL?
    ANy thoughts and ideas will help. I've been struggling for about three days now. ALso, do you know of a good C++ forum that i could post this question?
    #include "stdafx.h"
    #include "jni.h"
    #import "thirdparty.ocx" raw_native_types
    JNIEXPORT jstring JNICALL Java_org_nik_integration_test_Exporter_saveAsImage
      (JNIEnv * env, jobject obj, jint height, jint width , jstring fileName, jstring encryptionKey, jshort encryptionAlgorithm, jstring encryptedImage, jshort imageType)
         const char* fName = NULL;
         const char* encryptionKeyc = NULL;
         const char* encImgc = NULL;
         ThirdPartyLib::_DTPPtr tpptr = 0;
         HRESULT hres = 0;
         try
              hres =  ::CoCreateInstance(__uuidof(ThirdPartyLib::TP),NULL,CLSCTX_ALL, __uuidof(ThirdPartyLib::_DTP), (void**)&tpptr);
              //Retrieve values sent from Java     
              fName = env->GetStringUTFChars(fileName,0);
              encryptionKeyc = env->GetStringUTFChars(encryptionKey,0);
              encImgc = env->GetStringUTFChars(encryptedImage,0);
                         tpptr->Key = _com_util::ConvertStringToBSTR(encryptionKeyc);
              tpptr->Algorithm = encryptionAlgorithm;
              tpptr->Img = _com_util::ConvertStringToBSTR(encImgc);
              tpptr->SaveUnencrypted(width, height,_com_util::ConvertStringToBSTR(fName) , 1);
         catch(_com_error &e)
              _bstr_t bstrSource(e.Source());
             _bstr_t bstrDescription(e.Description());
             printf( "Exception thrown for classes generated by #import" );
             printf( "\tCode = %08lx\n",      e.Error());
             printf( "\tCode meaning = %s\n", e.ErrorMessage());
             printf( "\tSource = %s\n",       (LPCTSTR) bstrSource);
             printf( "\tDescription = %s\n",  (LPCTSTR) bstrDescription);
             // Errors Collection may not always be populated.
             if( FAILED( hres ) )
                printf( "*** HRESULT ***" );
              return NULL;
         __finally
              tpptr->Release();
              tpptr = NULL;
              //Release memory - java specific
              env->ReleaseStringUTFChars(encryptionKey, encryptionKeyc);
              env->ReleaseStringUTFChars(ink, inkc);
              env->ReleaseStringUTFChars(fileName, fName);
         }

    Well you have now demonstrated conclusively that it has nothing to do with JNI.
    It is either a bug with that component and/or you are using it incorrectly. Solutions to either of those would come from the source of that component, which would be somewhere besides here.
    If it was a bug then you might find a way around it by doing one of the following
    1. Try variations of use (options, parameters, whatever.)
    2. Determine if you can solve your problem by only processing 5000 entries at a time (where 5000 chosen just to be significantly lower than the limit you have already found.) If that works then you can solve the problem by using a restartable executable that wraps the component.

  • Default ACR camera profiles always criticized: why?

    A little theme for ACR users (and programmers team):
    The most "diffused" issue against using ACR instead of "branded" software (Nikon Capture NX o Canon DPP to name the most used) is:
    The colors in ACR seem "washed" or with no "punch"!
    If You calibrate ACR with a GM 24 panel colors regains a new life.
    But WHY?
    How can be possible that the 2 (yes two) profiles created by the Thomas Knoll team are ALWAYS more washed (Nikons reds are always offs) than a homemade shot of the GM panel made by a user? Yes, cameras have tolerances but how big they are?
    The factory preset should be the more precise! But to obtain good deltaE values (the error time in perceiving colors) ACR users are FORCED to recalibrate ACR.
    Why? Cannot be created a series of profiles (by Adobe) to be more like the brand company color rendering?
    If ACR had better factory calibrations (contrast or brightness differences doesn't give so much pain) instead of washed colors, many NX or DPP users would use ACR for sure! It has many advantages over other softwares.
    Can an Adobe profile-maker staff member give an answer to this theme?
    Or some forum user has some ideas?
    Thanks!

    Personally, I have found that the results produced by ACR from my Nikon D70, D200, and D3 are not that different from those produced by Nikon Capture (Nikon's raw converter, which gives results very similar to in camera JPEGs) when the camera rendering options are set to neutral.
    Nikon Capture reads the camera settings and applies them, whereas ACR ignores settings except for white balance. By neutral, I mean normal contrast, normal saturation, no hue adjustments, and a normal tone curve. The camera factory defaults vary. Cameras for the amateur market tend to have settings favoring saturation and contrast, whereas the professional cameras tend to have a more neutral default. These defaults are usually given in the DPReview writeup for the camera.
    Since the OP asked for some ΔEs, here they are. I photographed a MacBeth color checker with the D200 with daylight illumination. Settings were: Color Mode, II; Tone Compensation, normal: Hue Adjustment, 0; Saturation, normal; and Sharpening, none. I then compared the results from ACR and Nikon Capture NX with Imatest, which gives the ΔEs, presented here in graphical format.
    Color checker with NC using normal camera settings:
    http://bjanes.smugmug.com/photos/216270605_RK5fe-O.jpg
    Color checker with ACR default settings:
    http://bjanes.smugmug.com/photos/216270602_twDZB-O.jpg
    NC analysis with normal camera settings:
    http://bjanes.smugmug.com/photos/164349487_rWTQN-O.png
    ACR analysis with default settings:
    http://bjanes.smugmug.com/photos/164350910_FMqRN-O.png
    ACR post calibration with Fors Script:
    http://bjanes.smugmug.com/photos/172494801_9vACX-O.png
    For help in interpreting the charts, the reader should refer to the Imatest web site, which has detailed explanations. In summary, the further from the white point in the center of the plot, the more saturated the color is. Shifts in hue are indicated by shifts in the *a, *b axes. As can be seen from the plots, the ACR rendering is actually slightly more saturated and has overall better color accuracy then the NC rendering. The Fors script calibration gives near "ideal" camera results with ACR.
    As Thomas Knoll and others have pointed out, a neutral rendering is often not the most pleasing one, and saturation and contrast are often boosted, but this is a personal preference.
    With the Fors script, the ACR settings are set to a very flat image. After calibration, the ACR controls are reset to normal and the calibration settings (in their own tab are left as set by the script).
    http://bjanes.smugmug.com/gallery/2572598_U5Bow/1/172494801_9vACX#137154990_ketk5-O-LB
    If you re-run the Imatest analysis after calibraiton with the normal settings restored, the colors are quite saturated and you must talk this into account when using the script calibration.
    http://bjanes.smugmug.com/photos/163194057_NEAYm-O.png

  • ACR Camera Profiles - missing?

    I'm new to ACR and would like to open a .nef file using a Nikon D3 camera profile.  I'm running the last version of cs5 and ACR 6.2 (updated today).  When I open the file in ACR, I see the Camera Calibration tab, and the Camera Profile pop up menu.  I see profiles that look generic, like Camera D2X Model 1, Camera Vivid, etc.  I looked in Adobe Application Support (Mac OS 10.6) and see a long list of camera profiles, including the D3..what am I doing wrong?  I'm missing something for sure.

    Since Lightroom will not read in-camera settings for raw images, those profiles have been designed and named to emulate those settings as closely as possible.  I'm not enough of a Nikon historian to understand why they include profiles for the D2X, but they are there for every Nikon camera that I am aware of.  Apparently there was something about the output of that camera that a lot of people look for.
    When I first started using Lightroom and the profiles I was quite satisfied with the Camera Standard profile, which simulates standard output from the camera in JPEG mode.  But it was a little too saturated and the shadows were a little harsh for my liking.  I eventually changed to the Camera Neutral profile and made a couple of adjustments to saturation and vibrance.  It comes a lot closer to what I want.  I have found that the D2X mode 3 will sometimes soften the shadows and give me a better result.  But basically, you just need to experiment with the different profiles to see what they do.  Eventually you will come to know when to turn to them.  It's a pretty simple concept.

  • Very Interesting and Annoying x505 q875 problem

    Greetings,
    I have an x505 q875 laptop and whenever I start gaming with the power cable plugged in (don't matter if the battery itself is inserted or not) the laptop will shut down in about 20 seconds. The moment I start playing a 3d game and enter the game itself from the menu, the computer shuts down.
    The interesting thing is if I plug out the power cable and start playing the game with the battery as the only source of power, there is no shutdown. But the battery lifespan comes shorter after every use and I only have about an hour to play a game before I willingly recharge the battery or plug it in and watch the pc shut down in seconds.
    CAN ANYONE HELP ME PLEASE!!

    hqthief wrote:
    Greetings,
    I have an x505 q875 laptop and whenever I start gaming with the power cable plugged in (don't matter if the battery itself is inserted or not) the laptop will shut down in about 20 seconds. The moment I start playing a 3d game and enter the game itself from the menu, the computer shuts down.
    The interesting thing is if I plug out the power cable and start playing the game with the battery as the only source of power, there is no shutdown. But the battery lifespan comes shorter after every use and I only have about an hour to play a game before I willingly recharge the battery or plug it in and watch the pc shut down in seconds.
    CAN ANYONE HELP ME PLEASE!!
    Sounds like your laptop fans/vents are clogged with dust and thus causing the laptop to overheat, which causes the shutdown.  The reason for the playability when on battery is that x505 Qosmios actually throttle the GPU and CPU preventing them from doing too much "power draining" activities when on battery.
    You can try using compressed air (you can buy at Office Depot) to clean the fans/vents ; use short bursts.  I've already read of people using a shop-vac to suck the dust out.
    Just to verify it is a overheating problem, download this utility which allows you to measure the temperature of the CPU and GPU.
    http://www.cpuid.com/softwares/hwmonitor.html
    As a comparison, my x505-q8102X CPU and GPU idle at low 40s Celsius.
    Good luck and keep us posted with results.
    ========================================================
    QOSMIO - x505 q8102X
    i7-2630QM , GTX 460m , 18.4" screen @ 1680x945p

  • TS3899 Where is the email I sent? It was a very long and informative email that the recipient didn't receive.

    I wrote an email from my iPad. The recepient didnt get it.
    I have researched the information thoroughly so there's no way I can do it again.

    Two words of advice. For complicated / extended emails I prepare the body of the email in the Pages app first where it is saved automatically and then I copy & paste it to the Mail app. Also, I blind CC all my sent emails so that I have a copy on all devices, including my iPad. (my main account is not IMAP). Either of these two practices would have avoided your dilemma.

  • ACR camera profile and 5d2

    Noticed that the ACR profile is not available for my 5d2 images, not in the list at all. I've always had the odd image where it was the best fit, not a big deal, but wondering why it's gone. It's still there for 40d captures.

    MikeLeone wrote:
    On Tue, Oct 20, 2009 at 6:24 PM, bceugene <[email protected]> said:
    AR is not used by LR at all. the code that makes up ACR is included
    within LR. You don't have to have ACR installed at all, for LR to
    develop RAW images. The two are not dependent on each other.
    That being said, LR 2.5 includes the same code that is in ACR 5.5 -
    IOW, that is the latest RAW support.
    But they share common profiles in common folders, don't they?

  • Looking inside of DNG Camera Profiles and editing them

    For those interested in the insides of DNG Camera profiles, and how to edit them, I've written dcpTool.
    dcpTool is a compiler/decompiler for DNG camera profiles (.dcp files). dcpTool can decompile binary format DCP files into an XML format for editing with a text editor or whatever, and then compile the XML format file back into a binary DCP file, as well as extract embedded profiles from DNG files. It runs on Windows and OS X command lines, and is based on V1.2 of the DNG SDK.
    See here: http://dcptool.sourceforge.net/
    Health warning: dcpTool is a command line utility - if you're not comfortable with command line stuff, dcpTool probably won't be of any interest to you.

    Very cool, thanks for the info.

  • Lightroom 5 camera profiles and Olympus EP 5

    hI I'm fairly new to LR and trying to get different camera options besides ADOBE STANDARD in the camera calibration / develop module...
    I would particularly like to get the camera profile for the Olympus EP-5 which I understand is supported by the latest  DNG converter.
    Problem is I've downloaded it but still ONLY get ADOBE STANDARD.  I've converted some RAW images into DNG's, but still no camera profiles...
    I'm not sure how I'm supposed to be using the DNG converter, or if I need it at all in order to see the different camera profiles...?
    Looking forward to some advice on this, since I've found info on this to be very scanty... even tech support was not helpful...
    thx!

    Where are you getting the impression that Olympus cameras have other camera profiles?
    Mostly only Nikon and Canon DSLRs have more camera profiles than Adobe Standard.  I have installed up through LR 5.2 RC and ACR 8.2 RC and DNGC 8.2 RC and there are only Canon (50), Leica (1), Nikon (42), Pentax (4), and Sony (15) camera-matching profiles.  Nothing for Olympus other than Adobe Standard.
    You can, of course, make your own profiles using an X-Rite Color Checker and the DNG Profile Editor:
    http://xritephoto.com/ph_product_overview.aspx?id=1257 <http://xritephoto.com/ph_product_overview.aspx?id=1257&catid=28&action=overview> &catid=28&action=overview

  • Camera Profile missing in ACR 6.7 (PS CS5)

    I have looked all over the place for a solution to this problem and so far can not find one.
    I am running Windows 7 64bit, PS CS5.
    I just noticed that my Nikon D90 camera profile is missing under the Camera Callibration area in Camera Raw (it had been there before). The only thing that shows up is ACR 4.6:
    I have tried reinstalling the ACR 6.7 plug in...didn't work.
    I really don't want to try to uninstall and reinstall Photoshop.
    Oh, I have also looked on my computer in my C drive and found the list of camer profiles...the D90 is not listed (in fact, there are only 8 Nikon cameras listed in my Adobe Standard folder).
    One more thing...I had CS4 installed originally. I have since uninstalled it. I'm not sure if the issue I am having has to do with that or a recent update.
    Adobe should really have a seperate file that you can unstall just for camera profiles.
    Like I said I have searched all over and have not found anything...I am  really hoping there's someone on here that can tell me how to get my  camera profile in there.

    I recently installed Windows 8.
    1. Can I get a ACR profiles for my Canon 1Ds Mk lll and my Sony RX 100?
    2. Can I install the DNG Converter on Windows 8? This OS isn't listed as here as one of those suitable. > http://www.adobe.com/support/downloads/detail.jsp?ftpID=5389
    3. Noel, where are the equivalent locations on a Windows 8 machine? ProgramData doesn't exist, as far as I can see.
    Thanks.
    D.
    Edited:
    Ok. I found another Adobe download that said Windows 8 is compatible, so I installed the DNG Converter.
    However, no cameras are listed under Camera Profile in ACR.
    This is the case whether I load a Canon RAW file or a DNG conversion of a Canon file.
    Any idea how I can get the profiles to load?
    Thanks.
    D
    Message was edited by: Dinarius

  • Lightroom 3.6 / ACR 6.6 Camera Profiles Missing

    Greetings.
    I've read through so many threads about this, and still can't make camera profiles show up in either LR 3.6 or ACR 6.6.
    I'm shooting RAW with a Nikon D7000.  The only camera profiles available are Adobe Standard, Camera Standard, Neutral, etc.  LR/AC recognizes the RAW file was produced by the D7000, or at least that's what shows up as Make & Model in the MetaData.
    I've checked the path
    C:\ProgramData\Adobe\CameraRaw\CameraProfiles\Camera\NikonD7000
    and the 5 DCP files are present.
    I've confirmed LR/ACR is reading from this path by exiting the software, and temporarily changing
    ...\CameraProfiles\...
    to
    ..\FUBARCameraProfiles\...
    and when I then launch LR/ACR, I get a message that camera profiles are missing.
    I'm using Win 7 Ultimate 64-bit, logged in as the administrator to eliminate any security issue, and I installed LR/ACR as the admin as well.
    Lens profiles work fine.  On all my RAW file, the lens is correctly identified, and I can choose it from the dropdown for lens correction.
    If anybody has any ideas on what else to try, I'd be grateful.
    Happy New Year, all!

    The camera profiles that you see in Lightroom don't specify which model they are for. They are automatically chosen for the camera that took the raw image. If you see Camera Standard, that is the Camera Standard for your D7000. When I see that one, it's for my D300.
    Here's what I see for a Canon S90:
    Here's what I get for a Nikon D300:
    The v4's probably aren't there for you, but you shold see the rest of them.
    Hal

  • Odd Camera Profile / Undo Bug in 2.3 RC

    I downloaded the LR 2.3RC tonight and although it seems to be running faster, I've noticed a strange bug that I've never noticed before (or that wasn't there before.
    When using develop presets that change the camera profile (for example Matt Kloskowski's 300 Look) the preset will be applied and then after that the camera profile is changed as a separate step in the History palette (however I have only clicked on the preset and haven't changed the camera profile).
    When clicking undo the overlay that tells me what step I am undoing says that it is "Undo Camera Profile: ACR 4.4" - however this step either (1) gets undone and immediately re-applied, or (2) never gets undone. This problem makes it impossible (without using the History palette) to revert to the step before - and it kind of makes it difficult to apply several presets to see which works best as I have to scroll to the History palette to undo it and apply another.
    This bug only exhibits itself when using presets which change the camera profile.
    Anyone else seeing this?
    Any work arounds (other than reverting to 2.2)?
    Thanks,
    Chris

    Hey Chris,
    Yes I can reproduce this same exact problem on my Macbook Pro (Feb. 2008) with 4GB RAM and 10.5.6 with Lightroom 2.3RC
    I tried this on Lightroom 2.2 and I can say that this problem does not happen. This is a Lightroom 2.3RC bug.
    Is there a place where we are suppose to report RC bugs or is this post enough? Thoughts Adobe?

  • LR 4 Camera Profiles Limit?

    Is there a limit to the number of profiles that can be added to Camera Profiles in LR4? Presently there are 9. I added one via the Library/AppSupport/Adobe/ACR/Camera profiles route where it appears. It does not appear when Camera Profiles are opened in LR4 however. Thanks.

    The first post in that thread shows you how to command line it so that it is no longer hidden as well as the [Opt] Go method.
    That aside, did you get your profile placed and can LR see it now?

  • "Matrix" is only Camera Profile for 7D in update?

    I am using PSE8 and a Canon 7D on Windows 7.
    In the original ACR my drop down only offered "Beta" for Camera Profile.
    I downloaded 6.2 today which I believe is the newest update for PSE8 and the only option for Camera Profile is "Matrix".
    What must I do to get Camera Neutral, Camera Standard, etc?
    Thank you!
    Jen

    twinmommy_jen wrote:
    Are there any ideas when there will be an update for PSE users to include the 7D?
    For Elements v8? Never...Camera Raw 6.2 is the last version of ACR that will work. You'll need Elements v9 to update ACR further.
    But as has been pointed out above, the free DNG converter version 6.4.1 (which is not tied to a Photoshop or Elements version because it's a stand alone app) can install additional DNG Profiles as part of the installer...
    The DNG Converter can be used to convert raw files to DNG for cameras that are not supported by previous versions of Camera Raw.

Maybe you are looking for