PSE7/ACR 5.6 issue with Canon 7D raw images too dark - solution?

Whenever shooting both jpeg and raw images with my Canon 7D and uploading to PSE7 (where I use ACR 5.6 to convert raw) the raw thumbnails are a stop darker than the jpegs.  When converting a raw 7D image, the exposure needs to be increased by a stop (this needs to be done whether or not jpegs are also shot).  This phenomena does not occur with my Canon 50D using the same raw converter - the jpeg and raw image display the same exposure and raw images do not need the exposure increased.
I have noticed in the raw converter on the Camera Calibration tab that - for the 50D - the Camera Profile contains ACR 4.6, Adobe Standard, and the Canon camera profiles, whereas for the 7D the Camera Profile only has the Adobe Standard and the camera profiles.  The converter does say 7D at the top of the screen, however, so the converter recognizes the 7D.  Is there a 7D Camera Profile that needs to somehow be configured/uploaded, etc.?  ( I did run CameraProfiles.exe)
The 50D and 7D are set up the same, so this is not an ALO or some other camera setup issue - I have done extensive testing in this area.  Also, Canon DPP displays the thumbnails (raw & jpeg) and the raw conversion exposure correctly, which tells me that this issue has something to do with ACR 5.6.
Is this a setup issue in 5.6?  Or, do I need to upgrade to PSE8 and ACR 5.7 or 6.1 to get around this?
Thanks for your assistance.
Ed

Update:
I installed PSE9, which comes with ACR 6.1, and the issue was not resolved.  So, I downloaded ACR 6.2 - same problem: EOS 7D raw images (thumbnails and when opened in raw converter) are 1 stop under-exposed.  As stated above, Canon's DPP doesn't exhibit this problem, nor does FastStone Image Viewer, only ACR.  Anyone else having this issue?  Thanks for any help.
Ed

Similar Messages

  • Canon 1D MkIV images too dark

    Hi there
    Having a problem here. The RAW images from my Canon 1D Mark IV come in a stop too dark!
    When I open them, they lookfine; a second later they switch to a too-dark version. I am using Camera Standard, and no other adjustments.
    It's not just visual: the histogram of the opened file is shifter a stop to the left compared to the same phoito's histogram on the camera.
    Any ideas? This is a major issue for me since I rely on both the 1D MkIV and Lightroom to make a living...
    Many thanks
    Michael
    www.michaelwillems.ca

    Hi M, the question is simple, but the answer is complex. I'll provide an example to try to illustrate. The attached image is a downsampled version of a JPEG from the 1D Mark IV. It's a test picture of a color chart. I've drawn a red circle around the 2nd gray patch in the 4th row. When I take a picture with the 1D Mark IV zoomed into this patch at this exposure, I get a histogram all the way to the right. And indeed, when I open the file in any image editor (e.g., Photoshop, or DPP), and use a color picker / eyedropper to sample the values, the average value of that patch is (255,255,255). So this is like in your example when you say you look at the histogram (e.g., in DPP or on the camera LCD) and it's all the way to the right. In other words, the histogram effectively says this patch is clipped to the max value.
    However, if we look at the average raw values in this example for that patch, they are actually (on an 8-bit scale) about (72, 209, 187). In other words, the actual camera-recorded raw values are still pretty far away from clipping to 255. (I should also mention that the camera-recorded raw values aren't white-balanced, which is why the green value is much higher than the red & blue values, above.)
    So you can see there is a discrepancy between the camera-produced JPEG and the actual raw values. In this example, the camera histogram and JPEG values indicate a clipped patch at (255,255,255). If you are going by that histogram, then you would conclude reasonably that this patch is overexposed and clipped -- when actually it is not.
    More generally, there are always discrepancies / differences between camera-recorded raw values and the histogram shown on the back of the camera (as well as the JPEGs rendered by the camera). This isn't error. This is preference. Cameras and software apply "preset" exposure and tone curve processing (and possibly sharpening, noise reduction, etc.), and the histograms you see on the back of the camera are based on those presets (not the actual raw data). This is why your histogram on the camera will change depending on your in-camera settings of white balance, tone curve, contrast, etc.
    There is nothing wrong with the 1D Mark IV.  Many Canon DSLRs currently leave a lot of highlight headroom, i.e., when metering they will be conservative on the highlight side, and expose a little less. As I recall (don't have my full notes in front of me), the 1D IV spot meters about 3.5 stops below the actual clipping point. In other words, if I had spot-metered that gray patch in the attached example, and started with the meter needle in the middle, I could then increase the exposure by about 3.5 stops before I actually clip that patch. That's quite a lot.
    To summarize: you have to be careful when interpreting camera histograms. In many cases, it is easy to interpret that something is clipped when in fact it is not. If you see a histogram that appears bunched up to the right, the tendency is to decrease the exposure, and therefore make the histogram move to the left (so you aren't overexposing). In reality it is possible the original exposure was fine (without overexposure), and all that's happened is that now the image is even more underexposed.

  • Issue with Oracle LONG RAW data type

    Hi All,
    I am facing some issues with Oracle LONG RAW DATA Type.
    We are using Oracle 9IR2 Database.
    I got a table having LONG RAW column and I need to transfer the same into another table having LONG RAW column.
    When I tried using INSERT INTO SELECT * command (or) CREATE TABLE as select * , it is throwing ORA-00997: illegal use of LONG datatype.
    I have gone through some docs and found we should not use LONG RAW using these operations.
    So I did some basic PLSQL block given below and I was able to insert most of the records. But records where the LONG RAW file is like 7O kb, the inserting is faliling.
    I tried to convert LONG RAW to BLOB and again for the record where the LONG RAW is big in size I am getting (ORA-06502: PL/SQL: numeric or value error) error.
    Appreciate if anyone can help me out here.
    DECLARE
    Y LONG RAW;
    BEGIN
    FOR REC IN (SELECT * FROM TRU_INT.TERRITORY WHERE TERRITORYSEQ=488480 ORDER BY TERRITORYSEQ ) LOOP
    INSERT INTO TRU_CMP.TERRITORY
    BUSINESSUNITSEQ, COMPELEMENTLIFETIMEID, COMPONENTIMAGE, DESCRIPTION, ENDPERIOD, GENERATION, NAME, STARTPERIOD, TERRITORYSEQ
    VALUES
    REC.BUSINESSUNITSEQ, REC.COMPELEMENTLIFETIMEID, REC.COMPONENTIMAGE, REC.DESCRIPTION, REC.ENDPERIOD, REC.GENERATION, REC.NAME,
    REC.STARTPERIOD, REC.TERRITORYSEQ
    END LOOP;
    END;
    /

    Maddy wrote:
    Hi All,
    I am facing some issues with Oracle LONG RAW DATA Type.
    We are using Oracle 9IR2 Database.
    I got a table having LONG RAW column and I need to transfer the same into another table having LONG RAW column.
    When I tried using INSERT INTO SELECT * command (or) CREATE TABLE as select * , it is throwing ORA-00997: illegal use of LONG datatype.
    I have gone through some docs and found we should not use LONG RAW using these operations.
    So I did some basic PLSQL block given below and I was able to insert most of the records. But records where the LONG RAW file is like 7O kb, the inserting is faliling.
    I tried to convert LONG RAW to BLOB and again for the record where the LONG RAW is big in size I am getting (ORA-06502: PL/SQL: numeric or value error) error.
    Appreciate if anyone can help me out here.
    DECLARE
    Y LONG RAW;
    BEGIN
    FOR REC IN (SELECT * FROM TRU_INT.TERRITORY WHERE TERRITORYSEQ=488480 ORDER BY TERRITORYSEQ ) LOOP
    INSERT INTO TRU_CMP.TERRITORY
    BUSINESSUNITSEQ, COMPELEMENTLIFETIMEID, COMPONENTIMAGE, DESCRIPTION, ENDPERIOD, GENERATION, NAME, STARTPERIOD, TERRITORYSEQ
    VALUES
    REC.BUSINESSUNITSEQ, REC.COMPELEMENTLIFETIMEID, REC.COMPONENTIMAGE, REC.DESCRIPTION, REC.ENDPERIOD, REC.GENERATION, REC.NAME,
    REC.STARTPERIOD, REC.TERRITORYSEQ
    END LOOP;
    END;
    /below might work
    12:06:23 SQL> help copy
    COPY
    Copies data from a query to a table in the same or another
    database. COPY supports CHAR, DATE, LONG, NUMBER and VARCHAR2.
    COPY {FROM database | TO database | FROM database TO database}
                {APPEND|CREATE|INSERT|REPLACE} destination_table
                [(column, column, column, ...)] USING query
    where database has the following syntax:
         username[/password]@connect_identifier

  • Canon S120 RAW images not working with iPhoto. Why.

    Canon S120 RAW images why they can't be downloaded to iPhoto and/or when will Apple upgrade iPhoto so they can?

    Raw Support for each model of camera has to be added individually. That's Model not brand. The Raw from an S120 is not the same as the Raw from an S110 and so on. This is a pretty new camera, and the makes don't supply the Raw decoding, so they have to be reverse engineered. Then that will be released as part of an OS or camera raw update.
    Let Apple know you want this camera supported.
    iPhoto Menu -> Provide iPhoto Feedback

  • Can PSE 10 open Canon G16 Raw images?

    I am a professional photographer and educator. I have a client who just purchased a Canon G16. He has PSE 10, and he has contracted with me for some tutoring. I want to include editing G16 Raw images.
    However, I wonder if PSE 10 can open G16 Raw images?
    My client's computer is not powerful enough to upgrade to PSE 12.
    I understand that I can have him convert the Canon G16 Raw images to DNG's using the free Adobe converter and import those into PSE 10, but I was hoping that PSE 10 could use the new 8.2 Raw Converter from Adobe that includes the G16, so it could import the images directly.
    Thanks,
    Russ

    The Camera Raw plug-in for PSE10 was last updated in the spring or summer of 2012.  If the G16 is newer than that (it certainly is), then the DNG Converter is the only route. 
    I see on the list of supported cameras, that the G16 was first supported with ACR 8.2, so you’d need the DNG Converter 8.2 or newer (8.3 ATM):
    http://helpx.adobe.com/creative-suite/kb/camera-raw-plug-supported-cameras.html
    The DNG Converter is available on the Adobe Updates page:
    http://www.adobe.com/downloads/updates/

  • How do I update Lightroom 4.4 to download canon g16 raw images?

    How do I update Lightroom 4.4 to download canon g16 raw images from my camera?

    You cannot read your G16 native raw files with any version of LR 4 so there’s no information, here, about paying to update from LR4 to LR 4.4.  You need LR 5.2 to read G16 raw files natively.  LR 4.x to LR 5.x is a pay-for upgrade.
    Alternatively you can use the DNG Converter 8.2 or newer to convert the G16 raw files to DNG raw files and those will work in your older LR 4 version.
    Adobe updates whatever the current version is with new cameras, so once LR 5 came out LR 4.x ceased to be updated for new cameras.

  • I can not open canon 60d raw images on photoshop CS5.1? can not go to updates either- error?

    I can not open canon 60d raw images on photoshop CS5.1? the same program on stationary mac can open the same raw files, whereas new lap top can not? Why?  can not go to updates either- error, why?

    Which version of mac os x does your new mac have?
    What error do you get when going to Help>Updates in photoshop cs5.1?
    You might try downloading and installing the 6.7 camera raw update from here:
    Adobe - Photoshop : For Macintosh : Camera Raw 6.7 Update
    If you need any other updates, you can find most of them here:
    http://www.adobe.com/downloads/updates.html

  • Can't import Canon G12 RAW images into iPhoto 6.0.6

    unable to import Canon G12 RAW images into iPhoto 6.0.6 (Mac OS-X (10.5.8) - any ideas?

    You'll need to install the Digital Camera RAW Compatibility Update 3.5 - Search the Support/Downloads site for that.
    It still may not work. Iphoto 6 is an elderly piece of software now and predates your camera by several years. If it doesn't work you'll need to update to iPhoto 09 or later.
    Regards
    TD

  • Canon 70D Raw images won't work on my version of Elements 12.

    I know I need to get an update but not sure where to find.

    Thank you!  Worked like a charm.  I just installed elements  tonight and
    appreciate your help.
    Carolyn
    www.carolynkamuda.com (http://www.carolynkamuda.com)
    In a message dated 10/22/2014 10:34:33 P.M. Eastern Daylight Time, 
    [email protected] writes:
    Canon  70D Raw images won't work on my version of Elements 12.
    created by RKelly_ (https://forums.adobe.com/people/R_Kelly)  in 
    Photoshop Elements - View the full  discussion
    (https://forums.adobe.com/message/6858032#6858032)

  • Issue with Canon Legria HF20 and iMovie 09

    I am having an issue with using the Canon Legria HF20 (which is the PAL version of the Canon Vixia HF20) with iMovie 09, and I am trying to confirm whether other people experience the issue.
    I recently purchased the video camera, and while I am having no issues shooting in 25p, I am having an issue with 50i. When I shoot in 50i and import into iMovie at 'Full-Original Size" the footage displays with a horizontal interlaced combing effect, whereby if the camera moves left or right, horizontal lines appear, which causes the edges of things to look jagged. This is difficult to see in the small preview box, but is easy to see if you preview in full screen. I have been told that this shouldn’t occur as iMovie should recognise that the footage is interlaced and adjust the footage when being previewed (thanks Steve Mullen for confirming that). Again, there is no problem with shooting in 25p.
    This link has an example I found on the internet of what I am seeing: http://media.photobucket.com/image/deinterlace%20video/jlatenight/deinterlace.jp g
    Also, when I export the footage from iMovie using 'Export using Quicktime' at either 1080i or 720p, the footage remains interlaced even though I have selected 'Deinterlace Source Video'
    So far I have been unable to get to the bottom of this issue. I have spoken to Apple and they are saying that while the Canon Vixia HF20 (NTSC Version) is on the official list of cameras supported by iMovie, the Canon Legria (PAL Version) isn’t, although they couldn’t say whether this could have something to do with the issue I am having.
    Therefore, I was wondering if anyone could confirm whether they have experienced this issue. Can you please confirm that you are using the Legria version and not the Vixia version of the Camera.
    I would really appreciate your help.
    Message was edited by: Casho3

    Well, it seems to me that it looks the same. I am not an expert here, but it occurs to me that you can either shoot in 25p or de-interlace it from 50i. I think it gives the same quality but the latter is more complicated unless you have the Final Cut.
    Here I got an intersting link on that matter:
    http://www.hv20.com/showthread.php?p=259483
    About de-interlacing in iMovie:
    http://blog.davidglover.org/2009/03/creating-hd-video-with-imovie-09.html

  • Digital camera raw 3.2 issue with Canon 1000d

    Hi all,
    When I install the digital camera raw 3.2 update, Aperture 3 (3.0.3) gives me the indication to reprocess all master files. After that my images become darker and the colours like red, orange and skin tones become very saturated and strange compared with the previous version.
    To solve this problem I revert to the previous version of digital camera raw and everything is ok now.
    Follow the tip in the link above. http://discussions.apple.com/thread.jspa?messageID=11148487&#11148487
    My English isn’t very good, however my experience could save some troubles and time to other users.

    You need to reprocess them in Aperture. Ap3 has a better more advanced raw processor/converter than ap2 It is far superior and the first thing i noticed on ap3. Try on an image you thought was at it's best and could not be improved. I will be surprised if you can not make it better in ap3.
    My suggestion is to process them one at a time, before you want to make some image adjustments.
    Allan

  • Strange colour cast in LR3 with Canon G11 RAW

    Hi all,
    I recently bought Lightroom 3 to work with the RAW output from my Canon G11. The majority of the shots want to process are taken underwater around the UK coast. I'm having an issue with colour casts which I hope someone may be able to shed some light on.
    With these underwater shots LR3 seems to import them with a very strong green colour cast, even though, when diving, I set the manual white balance at regular intervals. By comparison, Canon DPP imports the RAW files correctly (what I consider correct), and I get the same correct results with Raw Therapee, GIMP and Capture 1. PhotoShop Elements gives the same results as LR3, but I assume they both use ACR 6.1.
    I would expect Canon DPP to be correct as it is processing it's own RAW files, but as the other RAW converters match the Canon output, I get the feeling that my problem is with LR3, or possibly ACR. I've scanned both the Adobe LR forum and ACR forum, but can not see any posts where people are having similar issues to me. I did find several post's saying that LR3's support of the Canon G11 was now finished, maybe it has just been tuned for land based shots, not underwater.
    I have tried using Adobe DNG Converter, to no avail, and I have also tried all the white balance pre-sets within LR3. Even the custom white balance picker does not give sensible results, it just changes the shots to a slightly different shade of green.
    Playing around with other setting in LR3 can make slight improvements, but it's a slow, shot by shot process, and still does not produce a usable finished product, or even a reasonable starting point for fine tuning.
    I have found that I can use Canon DPP to output to TIF, which LR3 then opens correctly, but I feel that as I'm not then working with the RAW file, I'm not going to get the best out of LR3's features.
    Is there some particular setting within LR3 or ACR that I have missed ? If not, am I actually loosing detail by converting to TIF before opening LR3 ?
    I've attached example output from LR3 and DPP. Both use white balance of 'As Shot', and neither have had any processing done on them. The LR3 shot looks lees green that it does in LR3, I assume thats because I've saved it as a low res JPG.
    Thanks for any advise people can give.
    LR3 output
    DPP output

    Thanks for that answer, it shows that I may have some settings which need tweaking.
    All the LR3 settings are as standard when first loaded, playing with this bunch of shots (about 20 in all) was the first thing I ever tried in it. I wouldn't even know how to apply split toning even if I wanted to (you probably guessed by now that I'm a new user to this software). All the on land shots I've messed around with import correctly, so it's definitly only the underwater ones.
    One thing that I've just remembered, may be important, when I select shots to import in to LR3, the thumbnails look fine. It's only when the import process has finished the green colour cast appears. It's almost as if something is being applied right at the last minute.
    I haven't tried to white balance the JPEG. I assumed it wouldn't work with the RAW, it would be the same with the JPEG.
    I did process some shots using PS Elements a while ago, and don't remember any stong colour casts in that. They were from shallow fresh water rather than deeper salt water, may make a differeence. I believe the ACR plug in with PSE 8 at the time was in the 5.x range. I did manually upgrade the ACR plug in for PSE 8 to 6.1 after loading LR3. I can try backing that out and seeing if I still get the colour cast.
    Hmmm, it's looking more and more like a problem with ACR 6.1. At a guess I'd say it's not interpreting the 'as shot' information correctly, or completly ignoring it.
    I'll have a go with white balancing the JPEG when I get home. If you can do it, but I can't, it points directly with a setting on my system. I'll also have a look at uploading the RAW file somewhere.
    Cheers

  • Camera Raw 4.4.1 has bug with Canon 40D raw files

    I shoot with the Canon 20D, 30D, 40D, 1DMII, and the Rebel XTI. The Raw processor is showing an anomaly only with the 40D files. When I load raw images, and when the image is displayed, it is shown at one setting. Then in 3 seconds, its updated again at about 1/2 stop brighter. Each time I click on another image on the left column, same thing. The new image is displayed, then 3 seconds later, updated at about 1/2 stop brighter. THe histogram reflects the changes showing the data moving to the right. This only happens with the 40D raw files.
    Whats up?
    It happens regardless if "Auto" or "Default" is selected. I use "default" as a norm, never letting PS do an auto correction.
    How do I stop Camera Raw from doing the second update? This has to stop.
    ...Doug

    Thanks John,
    Now moved to ACR -
    http://www.adobeforums.com/webx/.3bb6a85c.59b53a49

  • CS3: HDR Merge Problem with Canon 50d RAW files

    I recently upgraded from a 20D to a 50D.  I'm running CS3 under WinXPpro with 3GB of RAM.  HDR merge of 3 CR2 files is causing CS3 to generate a program error and crash.  This never happened with my older (smaller) files from the 20D.  Anybody know how to fix this?
    TIA,

    The suggestion was to try an HDR with smaller 50D sRAWs as an *experiment* to see if the size matters more than the camera model.  Another benefit of a 50D would be the 14-bits per pixel instead of 12-bits and an sRAW would have less noise per pixel than a full-size RAW so using smaller sRAW images might work better than a 20D's.
    The "size" being referred to is the dimensions in pixels, not the on-disk size, becasue the in-memory size of an image should be similar whether it comes from a 16-bit TIFF or an 16-bit RAW conversion.
    Merging RAWs will involve ACR during the HDR process, whereas merging TIFFs won't unless you have the setting to prefer ACR for TIFFs, too, which you don't indicate.
    There can be data in the highlights and especially shadows from a RAW that gets thrown away when it's converted to TIFF, so merging RAWs is better than merging from TIFFs.
    I currently have CS4 only on my machine so I forget, but with CS3, does it matter what output size you have set in ACR, when you do an HDR conversion from RAW?  In other words, does HDR using ACR ignore the output size or not?  If not, then perhaps setting a smaller size in ACR (the same area where you set the bit depth and conversion colorspace) would make things work or setting a larger size with 20D images would make them fail.  This is being suggested as a experiment as well, to try to isolate the issue, not necessarily a permanent solution.
    I don't think there is anything inherently wrong with a 50D RAW that would make it not work, but the larger size would use more memory and maybe your machine is getting close to some sort of limit.
    Other suggestions would be to reset your preferences and check your disk(s) with scandisk and/or change your scratch-disk to somewhere else to make sure there's no some corruption keeping the HDR process from working with the larger 50D images, and along those lines, also try purging your ACR cache or moving it to another drive.  You might also try changing the amount of memory available to Photoshop (ram vs scratch-disk) in the Preferences.
    What module does the crash occur in, if the error says?  Is it related to display or something else?

  • Problem with Canon G12 RAW file

    I'm very disappointed because I can't use Lightroom with my new camera! I have this issue since LR 3.3. and CR 6.3 started to support Canon G12's raw file. Any raw file is decoded incorrectly, picture is grained, it has a lot of noise at any ISO (even 80 or 100). The defect is noticeable only at 100% zoom, not at 50% or other sizes.
    I tried to do also a clean installation of LR 3.4.1 and CR 6.4.1 but the problem persists. (I use LR 64 bit on Windows 7 64 bit; with PS 12.1 64 bit I have the same problem)
    Yes, the camera is ok, and with Canon Digital Photo Professional 3.10 all is perfect, the same picture is amazing.
    Is there any solution please?
    Thank you!
    Davide

    It may be that DPP knows how much default noise reduction to apply to your G12's raw images and Lightroom doesn't.
    Can you adjust LR's noise reduction sliders to get a better image? If so, you could make that amount of reduction a default.
    If that doesn't work for you, could you post a sample raw image somewhere that we could bring it into Lightroom and see what you are writing about?
    Hal

Maybe you are looking for

  • Using programs on Macbook

    Hello, I'm a (soon to be)Mac user, and very excited about it. Some things worry me however. I'm looking into buying a 1099$ Macbook + expansion to 1gig ram. For me this is a heavy price to pay... there is no way I can go for the Pro model. However I

  • Autonomous Transactions usage in PL/SQL anonymous block coding

    Hi, I am trying to incorporate Autonomous Transaction for our work. I am using the tables provided below, CREATE TABLE T1 F1 INTEGER, F2 INTEGER CREATE TABLE T2 F1 INTEGER, F2 INTEGER insert into t1(f1, f2) values(20, 0) insert into t2(f1, f2) values

  • Compress the output stream..

    Hello every body.. I have aproject that use the java applet to transmit a vedio and audio over the internet network to do a video conference application with other applet at another computer at the network.. I want to support the application so that

  • Locking invoices with amount over 5%.

    Hi, how locking in MIRO invoices with amounts over 5% of PO amount? Best regards

  • Get session in JSP

    I have got a problem, would like to seek help. thanks in advance:P HttpSession httpsession=request.getSession(true); httpsession.setAttribute("user", getUser(userid));//getUser(userid) will return a user User user=(User)httpsession.getAttribute("user