DPP Settings to ACR

Hello I have a Canon EOS 60D in DPP the image looks fantastic but when i transfer it to ACR the colors and everything look completely different is there a profiloe or something that can get these two programs images to look the same?

Well...no.
You can try using a different DNG Profile (in the Camera Calibration panel) to get different color rendering but the bottom line is that what the camera or DPP thinks is optimal in a raw file has no bearing on what ACR thinks is optimal. A raw file is raw and is expected to be adjusted to taste. There is no "correct" rendering...Canon has it's own interpretation of what Canon thinks your raw file should look like and it really isn't any more "correct" (nor incorrect) that what ACR thinks it should look like. Learn how to use ACR's controls and how to adjust your image to your taste. And the odds are it won't be what either Canon nor Adobe thinks your image should look like at "Default".

Similar Messages

  • Olympus Settings in ACR

    Hi Everyone;
    I'm an Olympus user. I've done a number of comparisons of ACR against competing Raw converters. Olympus Master or Studio which both have the same internal conversion engine and is similar to the in camera performance sharpens the photograph and also increases saturation and contrast. Some of the pictures look quite good through Olympus software others not so. What I'd like to know is has anyone researched the settings in ACR that duplicate the results from Olympus software (or the camera itself when using the in camera conversion)? I'd was thinking it might be interesting to use them as a starting point for edits in ACR.
    Thanks
    Jim

    Hi Eric;
    I downloaded a copy of ACR 4.5 and installed the Standard Camera profiles. I think I saw your name as one of the software team members. There is a very noticeable difference between 4.4 profiles and the Standard Camera betas. A very nice and pleasing difference. This helps a great deal (IMHO) in replicating the Olympus colour without the over the sharpening (to my tastes anyway) that seems to be the default for the Olympus conversion engines in the camera (e510) and the software Master 2.04 or Studio or, when using ACR using trail and error to approximate some of the good points of the Olympus conversion. The Standard beta for the e510 seems to be at first blush a great starting point for what I'd like to do with the ORF RAW's. I may tweak the Standard with the PE software but you've come very close to my tastes the way it is and what corrections I'd make in general are quite small from that starting point.
    Keep up the good work! Kudos
    Thanks
    Jim

  • Exporting / Copying settings from ACR Smart Object

    How do I export the RAW processing settings from an ACR Smart Object in Photoshop?
    If I use Save Settings it only allows exporting a subset of the settings (no spot removal and local adjustments).
    If I use Export Settings to XMP it doesn't seem to do anything.
    The only way I've found to do it is to Save Image (from the Smart Object in ACR), save as a DNG, then use ExifTool to extract the XMP. Surely there must be an easier way?

    I ABSOLUTELY agree......  That's exactly, I believe, how it's SUPPOSED to work.
    Except that mine didn't.
    I opened a 12.2 MP RAW file. 
    And made absolutely no changes to the workflow uptions at the time of opening.
    But instead of "Image Sizing" saying "Default 12.2 MP", it said "3.6MP"
    Resize was turned OFF
    Width was 2321 px and height was 1824 px, BOTH GRAYED OUT.
    Upon leaving ACR, I had a 2321x1824 file.
    Eventually, after wasting another hour screwing around with it, I finally blew away all of Bridge AND the preferences and all that,
    and rebooted since the %$#)(*& Adobe CC thing wouldn't figure out there was no more Bridge, and resintalled...........
    Now, when I open a file in there, at LEAST it knows it's 12.2MP.
    It STILL wants to change the Space to sRGB, which I NEVER use from here, and the Depth to 8-bit, which again, I never use in ACR,
    but I can set those back to what they should be...
    So, in this case, by using a large enough bludgeon, I appear to have gotten around the problem.  Now I'm just waiting to see how soon it screws up again.

  • How do I change the Transparency Settings in ACR 8.7.1?

    I work on three different computers, one at home and two at work. In Camera Raw on my home computer the transparency section of an image where I have done a major perspective correction will have the checkerboard rendering of the transparency section. Of the two computers at work, one will display the checkerboard pattern and the other displays dark gray. I prefer the dark gray over the checkerboard but cannot find the setting. Scott Kelby's CS6 book for Digital Photographers has the dark gray view in his tutorial on page 69 and references the dark gray area as if it was the default color. Any help?  

    You can't change the transparency colour. What you might be seeing is a change in colour between different versions of Camera Raw.

  • Clear Settings Anomaly in ACR 7.1rc

    First, a bug: when you click Clear Settings in ACR 7.1rc (Mac version, at least), the Edit menu highlighting stays on after the operation is complete.
    Second, Clear Settings in ACR 7, when applied to DNGs that have had settings made in earlier versions of ACR, are not cleared.  Only the additional settings made in ACR 7 are cleared.
    This latter may be intended.  But, if so, it would be useful to have an additional menu item that Clears All Settings.
    Edit:  Indeed, I notice that several items leave the menu highlights stuck on.  For instance, if one looks at the Camera Raw Preferences, the Adobe Bridge CS6 menu item remains highlighted even after you dismiss the preference pane.
    Edit_2:  The Clear Settings now seems to be working.  I guess, perhaps, it took Bridge some time to update its cache.  It certainly wasn't working right after installation.
    But the various menu highlights still do not turn off when they should, as reported above.
    It seems the menu on/off logic needs a rather general cleaning up.
    grampus45

    None of the issues reported on this forum have been fixed in Camera Raw 7.1, near as I can see.
    The Camera Raw 7.1 software was built on May 15, but Adobe appears to ignore beta feedback unless it's a real show-stopper.  I can only imagine the definition of "show-stopper" must include users' systems actually catching fire or something.
    Camera Raw 7.1 puts columnar color artifacts like this into images, for example:
    Compare the above to the same conversion done with Camera Raw 7.0:
    Plus Adobe has removed several color-fringing reduction features without providing suitable substitutes.
    I recommend eveyone avoid upgrading to this release.
    -Noel

  • DPP won't open in Windows 8

    Hi...
    We can't get  Digital Photo Professional (v3.13.0.1) to open on our Windows 8, 64-bit machine.  We get the following message:
    We've uninstalled and reinstalled a couple of times, made sure the screen resolution is above 1024 x 768, and have tried using the compatibility troubleshooter to change DPP settings to run in 16-bit color, but nothing works.  Help!

    Thumbs up on Light Room. It is leaps and bounds better than DPP.
    But DPP works fine on Win 8 machines so I still suspect you have something set incorrectly. On your Nvidia Control panel you should have a Change Resolution. It is below the 3D Settings.
    Mine is set at 1920x1080, which is the native format, 60hz and 32 bit which is the highest.
    EOS 1Ds Mk III, EOS 1D Mk IV, EF 50mm f1.2 L, EF 24-70mm f2.8 L,
    EF 85mm f1.2 L II USM, EF 70-200mm f2.8 L IS II,
    Sigma 120-300mm f2.8 EX APO, Photoshop CS6, ACR 9, Lightroom 6

  • ACR 7.1 Release Candidate Problem

    I just installed ACR 7.1 RC on a Windows 7 Professional 64 bit system and identified an issue relative to how ACR 7.0 works.  When I select an image that was initially converted using PV2010 (CS5) and click on the "!" on the image to change it to PV2012, make a few adjustments in the Basic panel and then click on the "3 ---" and select "image settings" it changes back to PV2010 with all the settings, but if I then click on the "3---" again to switch back to PV2012 with the settings I made it's already setting in "Custom Settings" and you can't switch between PV2010 and PV2012 using this approach. 
    If you have any other panel than "Basic" selected it allows you to switch between PV2010 and PV2012 by selecting "Image Settings" or "Custom Settings".  You can also switch between PV2010 and PV2012 in the "Basic" panel using this approach if you don't make any changes to the initial PV2012 slider settings. 
    ACR 7 does not have this characteristic. 
    Any comments?

    I have returned to ACR 7.0 and it does not have the issue described above for ACR 7.1 RC.  I am reprocessing images that were already processed with PV2010 and switch between PV2010 version and PV2012 version using the "Image Settings" and "Custom Settings" .  I can do this in ACR 7.0 while in the Basic Panel, but not in ACR 7.1RC.  In ACR 7.1RC I have to switch to something other than the Basic Panel before I switch between PV2012 and PV2010 using "Image Settings" and "Custom Settings", but after I do this one time for an image I can then do this in the Basic Panel. 
    This bug needs fixing before the production release. 

  • ACR 7.1 RC Issue Not Fixed in ACR 7.1

    The issue I identified in ACR 7.1RC is not fixed in the production release of ACR 7.1.  Maybe I did not explain this in enough detail, it's very easy to miss. 
    1. Select a RAW file that was previously adjusted using PV2010.  When you open the file with ACR 7.1 it will open with PV2010 since the xmp file was saved with that process version. 
    2. Click on the "!" next to the image and it changes to PV2012 with suggested slider settings.  Adjust one of the sliders in the Basic Panel - this is very important becasue if you don't adjust a slider the issue does not show up. 
    3.  With the Basic Panel still selected, click on the three dashes to the right of the Basic Panel to get the pop down menu and select "Image Settings".  The image changes back to PV2010 with settings that are saved in the XMP file.  Now click on the three dashed again to get the pop down menu and "Custom Settings" is checked, but the image is displaying PV2010, not PV2012 like it should if "Custom Settings" is checked.  You just lost your PV2012 settings. ACR 7.0 does not have this issue. 
    4. If in #3 above you select another panel before you click "Image Setting"  the first time you can switch between PV2010 and PV2012 by clicking "Image Settings" for PV2010 and "Custom Settings" for PV2012.   After you do this first in a panel other than the Basic Panel for the first time you can then do it in the Basic Panel without the problem occuring. 
    I discovered this while converting images that were adjusted using PV2010 to PV2012 and like to compare the two Process Versions.  I did not have any problems with ACR 7.0, but when I installed ACR 7.1RC the issue occured.  I was hoping it would be resolved in the Production Release of ACR 7.1, but it's still there. 
    I am using Photoshop CS6 on a Windows 7 Professional 64 bit computer, don't know if this same issue exists in Lightroom. 

    None of the issues reported on this forum have been fixed in Camera Raw 7.1, near as I can see.
    The Camera Raw 7.1 software was built on May 15, but Adobe appears to ignore beta feedback unless it's a real show-stopper.  I can only imagine the definition of "show-stopper" must include users' systems actually catching fire or something.
    Camera Raw 7.1 puts columnar color artifacts like this into images, for example:
    Compare the above to the same conversion done with Camera Raw 7.0:
    Plus Adobe has removed several color-fringing reduction features without providing suitable substitutes.
    I recommend eveyone avoid upgrading to this release.
    -Noel

  • Open as "Smart Object" from ACR to PS questions.

    I have 2 questions associated with opening from ACR as a Smart Object in Photoshop. I'm using CS4.
    1. Is there a way to retrieve the original filename (complete with path) using a script or a setting somewhere to do this? I'm currently using Bridge Talk to ask Bridge what the active folder is then adding that to the document's .name property and taking off the " as Smart Object-1" part. Then I add a .psd extension to it and then I have to save it to retain that name unless there's an answer to #2 below.
    2. Is there a way to change the Document's name as described above from "Filename as Smart Object-1" to "Filename.psd" without actually saving it?
    It seems to me there would be a simple way that I might be overlooking here.
    Thanks
    Mike

    Sorry, I guess I need to explain better.
    I wrote a script to do this, but here is this portion of the workflow:
    1. Open CR2 file in ACR and make adjustments.
    2. Open as Smart Object in PS.
    3. Script Events Manager activates this script on Document Open, checks to see if it was opened as a Smart Object. We'll assume it did.
    4. The script asks me if I want to make another layer. I pick yes. The script copies the SO layer, sets an inverted mask, and opens to edit settings in ACR again.
    5. I adjust the settings for that layer in ACR and click OK.
    The script will keep looping between 4 and 5 as long as I pick YES.
    This gives me more local control of areas. If I want to bring out eyes a bit, I can up contrast, saturation, sharpness, brightness, exposure, or whatever looks best for the eyes in ACR, then unmask the eyes as much as I want on that layer in Photoshop. There is more data to pull from in the RAW file vs trying to do the same thing within Photoshop.
    Opening as a regular image file then converting to a SO doesn't give me the same control. I would have to reopen the file separately, make the adjustments in ACR, open to PS then copy that document and paste as a new layer in the original.
    Duplicating the document might work also, but I can also just save as .psd at that point since I'd have to know the path name by then anyway. I'll give that a try, though, and see if it might work better. The only catch with the save part is it slows me down waiting for it to write the file and if I have 5+ SO layers, it takes awhile. Once I unmask where I want, I flatten to a rasterized layer and continue.
    Thanks

  • Switching From Windows To Mac: ACR Database, Bridge Cache Questions

    I am planning to switch from Windows XP to the Mac running Leopard. I am now running CS2 in Windows, but will upgrade to CS3 on the Mac. I am maintaining my RAW file settings in ACR central database and my Bridge cache in a centralized cache file. I've searched the forums but couldn't find answers to my migration questions:<br /><br />1. Can one move the ACR database file from Windows (in folder C:\Documents<br />and Settings\<username>\Application Data\Adobe\CameraRaw) to a folder<br />somewhere on the Mac to preserve the settings on RAW files that are also<br />moved to the Mac? Or does one need to export individual XMP files for the<br />RAW files in Windows and move both the RAW files and their associated XMP<br />files to the Mac?<br /><br />2. I have a similar question for migrating the Bridge cache from Windows XP<br />to the Mac. Can one somehow move the Bridge cache over (I think it's in<br />C:\Documents and Settings\<username>\Application Data\Adobe\Bridge\Cache\Thumbnails\) or do I need to export the cache for<br />each folder and subfolder and move them over along with the folders and<br />subfolders?<br /><br />I would appreciate any help or pointers to any Adobe documents or<br />directions. Thank you.

    Man-Kong,
    Since you said that you were also migrating from CS2 to CS3 I would have said that their cache files were incompatible. That is what I experienced with CS1, CS2, and CS3 in the past. But Thomas indicated it should work. I must be missing something.
    The XMP files move fine for me. The local cache (folder) files have completely different names with each version and I see no evidence that they can be shared. This is also a problem with archived CDs. CS3 always has to rebuild cache if they were archived from CS1 or CS2.
    Since the central cache must have some folder references, and this structure will be completely different on Mac, I dont see how it can work. It doesnt work for scripts or actions either.
    So my humble recommendation is to set your preferences to store cache and XMP files in the local folders where possible. Then simply bite the bullet. Each time you visit a folder for the first time in the new environment, cache will be rebuilt.
    Cheers, Rags :-)

  • ACR PSD files - larger file size and max compatible

    When using ACR > Save As to save a bunch of PSD files from raw files the resulting PSD file sizes are larger.
    for example:
    if I output and save from ACR directly to a folder as a PSD, I'm seeing the file size at 63.1 MB
    If I open the raw file to PS and save it within Photoshop to a PSD file the file size is 56.1 MB ( this is true whether the Max Compatible is turned on or off... probably because it's a flat PSD file)
    why the difference?  same output settings from ACR, bit depth etc.
    Also,
    The file saved out of ACR appears to be "tagged" as a Maximum compatible file even though it is flat, so subsequent saves, even if the PS pref is set to Never for maximum compatibility are disregarded. Whereas the same file that was opened into PS from ACR and then saved with the Never PS pref behaves correctly.
    Is there a preference setting within ACR to not save the PSD's as Maximum compatible?
    thanks
    j
    ACR 6.4
    PS 12.0.4
    10.6.7

    Hi Noel
    I may not have been clear in my post. It's not about PSD v. Raw file size, just comparing PSD files.
    Starting with a raw file ( in this case a 5DmII CR2)
    Using the same settings (mid-bottom of ACR window) when saving a file using the "save image" within ACR or opening the file into PS and then saving. This is where I'm seeing the file size difference.
    The second part of the problem is that PSD files that are saved directly out of ACR using the "save image" (bottom left of ACR window) are all set as Maximum Compatibility. As a result opening these files will always be have the extra data and saving time that files with Maximum Compatibility enabled have. The only way to get around this is to have your PS prefs set to Never or Ask and the "Save As" to overwrite the file.
    I just reprocessed a folder of PSD's that were saved out of ACR by overwriting as above and the 36 files (with layers, retouching etc) went from 6.9GB to 5.6GB, and the save time is also faster.
    This isn't intended to be a discussion about the benefits or disadvantages of the Maximum Compatibiliy "feature", but just a question as to whether it can be turned off in PSDs saved from ACR.
    thanks
    j

  • Changes in ACR Behavior

    Today I was notified of updates to Bridge and Camera RAW when I rebooted in Win7 64, and changes to Camera RAW only in XP 32.
    In Win7 I allowed the updates, and then opened  a file to see what I could see. I was shocked by what I saw.
    Apparently, the update took some xmp data from a file previous to the update, and applied it as a new default setting for my camera, as if I had myself done that, which I can assure you I did not, as I want to be sure my starting place for the evaluation was consistent, even if incorrect for the particular image.
    Here's the changes:
    1) All images now read 2010, including images never before opened anywhere and showed 2003 when first opening these in the current ACR. Ok, I can live with that.
    2) The Detail menu reflects a set of sharpness and noise settings I applied during my most recent runs for a particular ISO value which I had saved. Again these showed up on images from February never before opened anywhere. Not so acceptable at all.
    3) The "Enable Lens Profile Corrections" is now checked...total disagreement here! I have never saved (clicked Done) on any image I used to check the behavior of Lens Corrections.
    So, I reset all to the former defaults and saved as new camera raw defaults.
    I switched to XP CS5 and the notification of the update showed up. It only said Camera raw updates. I did not allow the updates, but went immediately to the same image I used to check the behavior in Win7 64. They all were at my selected defaults...no sharpening, noise or checked "Enable Lens Profile Corrections" IOW business as usual which I had so carefully selected and matched to the Win7 version.
    I ran the updates, and the only change I saw here was that the 2010 now ran without my selecting it, but all the other settings remained at MY default settings.
    I am at a loss to explain or accept. There is, of course, the remote possibility I did change the default settings in ACR Win7 version, but the change in "Enable Lens Profile Corrections" would have been excluded.
    Or my Fairy Godmother decided I  didn't know what the F I am doing and did it for me!
    So, it behooves the user to maintain a check on all default settings when updates are applied. I do that anyway, but I can get lazy or in a schedule conflict and simply run it.
    Note: What I had hoped I would see:  New lens data in ACR is provided including the 18 to 105 is now available. It isn't.
    Lawrence
    I posted this in error in the Lens Correction Creator thread. My bad!

    This is the Lens Profile Creator forum.  You might have better luck with a post like this one in the Camera Raw forum.

  • ACR 4.41 capture sharpening

    Hi I have a question for the experts here. I have XP SP3 PSCS3 ACR 4.41 I am learning Raw with the wonderful Real World Camera Raw with CS3 by Bruce Fraser and Jeff Schewe.
    In the book it is recommended to do my capture sharpening with ACR. Currently I have been using the excellent Photokit Sharpener (1.2.6) plug in for PS,after finishing all of my editing in Raw and converting to PSD. Can anyone suggest equivalent settings in ACR 4.41
    Amount radius, detail masking options.
    for each option in the digital hi-Res capture sharpening set?
    superfine, narrow, medium and wide edge
    I have an idea that Jeff Schewe might be involved in Photokit too??
    Any help is greatly appreciated.
    Kind regards
    Geoff

    >No, there really is no set of settings since it depends on the source capture and the subject matter...the best bet is to make it look "good" at 100%...
    It seems strange to me that useful presets are possible with PKSharpener but not with the new ACR sharpening work flow, since both are based on the same principles: Bruce Fraser's sharpening methods.
    While some degree of fine tuning is always desirable, Jeff does give some suggestions for landscape and portrait sharpening presets, both in the ACR with PSCS3 book (pages 170-184) and in the Camera Raw tutorial. I think these are for Canon 1DsMII resolution.
    In his seminal sharpening book (Image Sharpening with CS2), Bruce Fraser discusses in some detail the settings for source (radius according to camera MP count and amount according to the strength of the blur filter). He also discusses sharpening for subject content in some depth. The OP implied high resolution, so Jeff's suggestions would be a good starting point in building presets for a given camera and subject matter, and the theoretical basis given in Bruce's book goes a long way into how to make rational adjustments.

  • RAW DNG sequence / Edit Original with ACR within Premier

    I need to speak to a Adobe Premier expert. I have a RAW DNG sequence shot on my Canon 5d Mark 3 via Magic Lantern imported into my premier project now. I want to edit the DNG's image settings with ACR (adobe camera raw). So i right click on my DNG sequence / clip and go to Edit - Original . ACR pops up and i make my image modifications. I click ok but the DNG sequence doesnt change, its stays the same.
    Now i can do all this without trouble within After Effects, but it just adds another step to my workflow. When it should be working within Premier. Im still waiting to see if ACR will ever work directly within Premier.

    Maybe whoever answers your question can give me some insight. I imported my DNG sequences to After Effects, because Premier wouldn't import the DNG sequences,  and created a new comp for each of the shots I have. Later in Premier I imported all those AE comps. Now where would be the correct place to color correct and grade this? Straight in Premier? Or will I be loosing the flexibility of the DNGs? Should I do it instead in the AE comps? Or maybe it doesn't matter? Thanks for the help!

  • New Chromatic Aberration tools kills old settings.

    I've just recently found that new chromatic aberration tools kills settings for old chromatic aberration tools.
    Lets say I have a PV2010 photo with adjusted sliders for chromatic aberration reduction and selected defringe "all edges".
    Now I'm importing this photo to LR 4.1.
    Note: I'm not updating process version!
    Photo is automatically updated by Lightroom to new CA controls (note it still PV2010 photo).
    Well, I must say the the results are superb - they are the same as I was achieving with manual sliders, but now with only one click.
    But the problem is - Lightroom says that metadata have been changed, and I am writing back changes to XMP.
    But now XMP contains settings for new CA tools, but settings for old CA tools are LOST.
    So if I want to open this image in ACR 6.6, or send it to someone with older LR version I end up with completely resetted CA settings, because ACR 6.6 does not have new CA tools, and settings for old tools are killed by LR 4.1 - they are just removed from XMP.
    So I am loosing CA removal settings completely when opening image in earlier version of application.
    And I am NOT updating process version!
    Any comments on this?

    Here is screen shot in which you can see that even PV2010 photo has new CA tools and old ones are gone with their settings applied in LR3.
    I have tried to import CR2 files without any settings in the XMP into newly created empty catalog and have same result.
    When I am switching photo to PV2003 or PV2010 only new CA tools are available.
    And saving metadata to file kills old CA settings and writes settings for new tools (even for PV2010 photo) which previous versions does not understand.
    To my opinion this is very serious bug!
    Here is photoshop feedback message created 5 days ago: http://feedback.photoshop.com/photoshop_family/topics/lightroom_new_cromatic_aberration_to ols_kills_old_settings
    Looks like noone cares...
    Can someone at least say do I am the only person having this issue, or you can see this behaviour too.

Maybe you are looking for

  • Excise and delivery channal

    Hi, in a production order operation 20 is sub-contrcating. to send the result material of operation 10 to sub-contractor, we need to prepare excise doc because of cin implemention. for that the mat suppose to be taken into stock. again operation 30 i

  • Data Mismatching in DSO

    Hi Folks, We  have data mismatch issue for one info object ( BASE UOM ) when the data goes from staging DSO to conformance DSO.I will explain the issue here. For one invoice no the Base UOM value dispayed as M2 in the staging DSO.When the data goes f

  • Cue 8.6.6 not transfer to cucm extension

    Hi Expert I have a router 2921 with cue 8.6.6 integrated with CUCM 8.6. My issue is when an incoming calls come to the router from PSTN the AA is playing the welcome message when i try to enter any extension register in cucm is not accepting the dtmf

  • Still no A2DP support in 10.4.7?

    Am I wrong or is there still no A2DP-Bluetooth support for hifi stereo sound in the latest OS X update 10.4.7? I just updated and couldn't see a matching profile. This would not be just disappointing - this feature is a built-in MUST for my next lapt

  • Hi How do I name individual photos in an album?

    Hi How do I name individual photos in an album?