Why are my RAW files created by Vuescan so dark in Aperture?

I've been scanning images using Vuescan and saving as 16/48 bit RAW images. These images always look great in Vuescan but when I import these images into Aperture, the images are very dark. I need to do an exposure correction of +2 just to start seeing anything in the midtones. Ed Hamrick, the author of Vuescan, says this is because the RAW files have a gamma of 1.0 (coming straight of the CCD). If I save the same scan in TIFF format, the images look pretty much the same in Aperture and Vuescan.
My question is what benefits does saving in RAW bring given the large adjustments that I must make. I know I can automate the adjustments at import which might make this less of an issue but I wonder if saving in TIFF is nearly as good. Some of the pictures have a wide dynamic range with lots of shadow detail.
Any suggestions?
Thanks for any help.
Bob

My frustration has been that I am doing the processing twice which is pointless. I need to choose a workflow. Mind you that if Apple supported the full DNG specification, it would be able to deal automatically with these RAW scanned DNG files (I believe they are linear DNGs) and automatically compensate during import just as Lightroom does. I am using the trial version of Aperture - which I feel really comfortable using - but I think I may take Lightroom for a spin prior to making a final choice of software.
As I tried to clarify, there is no benefit in saving as RAW from a scanner. Just save as a normal 16-bit TIFF and you'll and up with a simplified workflow and no loss of data nor detail. Actually, a DNG is internally just a TIFF.
Mind you that if Apple supported the full DNG specification, it would be able to deal automatically with these RAW scanned DNG files (I believe they are linear DNGs) and automatically compensate during import just as Lightroom does. I am using the trial version of Aperture - which I feel really comfortable using - but I think I may take Lightroom for a spin prior to making a final choice of software.
If Apple fully-supported the DNG specification, then the RAW Fine Tuning adjustment would be available with its auto-exposure button to get a good starting point for tweaking the images.
You could provide Apple with feedback via, Aperture>Provide Aperture Feedback.
If I continue with Aperture, I am thinking that I will save these files as RAW TIFFs and do the gamma adjustment at import. This should streamline the workflow by making it possible to scan two 4x5s at one without the need to tweak each one in the scan and then do all my processing in Aperture (or Lightroom). I will just trust the scanner.
You shouldn't trust your scanner, just as you shouldn't always trust matrix metering or 'I'll fix that in post". Aiming for the best starting material is aiming for the best results. So instead, carefully examine each scan, which will not take you that long BTW.
I will still create the scanner profile of the IT8 target which I should then be able to use as a proofing profile to compensate for any color bias in the Fuji Provia film used. Perhaps I am wrong about this.
Actually, you're wrong on this. The IT8 provides an input profile, and not an output profile or working space. Imagine scanning a slide and printing it. Softproofing for IT8, then you can't softproof for your printer and vice versa.
Your post has allowed me to really think through my workflow and I really appreciate the input I've received in this thread. Now, I just wish I could get Apple to add support for Linear DNG (or whatever format Vuescan RAW DNG is which I know contains three colors per pixel rather then one as in Camera Raw) which would provide the additional tools to deal with these DNGs at import.
Although linear DNG support would indeed be nice for unsupported camera's, it is not necessary here. If Vuescan DNG has three channels, than it is a TIFF. (since demosiacing MUST have been applied, there are no scanners with a Foveon sensor as of yet)
Well to cut a very long story short just use TIFF for scans. It's a necessity for proper colormanagement and will simplify your workflow.

Similar Messages

  • Why are my raw files from my Canon 5D Mark III dim in Lightroom 4.3?

    I am brand new to Lightroom, still reviewing various basic instruction videos, however I am adept in Photoshop CS5 and CS6. I have been able to import and move a file of jpegs but as I shoot jpeg/raw combo, the raw files were left behind in the original file. I can now bring them up, but they are dim and cannot appear to do anything w/them. I would like to move them to the file where I put the accompanying jpegs, but am having no success in finding an answer on how to do this. Nothing seems to activite to let me do this.  Along w/this, I generally tend to work straight from camera raw files, the jpegs are generally not used, thus when LR encourages me to work on the jpegs, I'm not interested. I wish to process my raw files and only move to PS6 if I need to do some more intensive work. Can anyone offer a suggestion?

    Here's my guess, based upon your description.
    When the RAW photos are "dim", you are in the Import Dialog box, and the default operation of the Import is to not let you import a photo if it has been previously imported.
    If that's the case, then you have misunderstood a basic operation of Lightroom. You import your photos once, and from then on, you access them via the Library Module, not the Import dialog. So, go to the Library Module and see if your RAWs are present or not.
    Side comment: your workflow seems to be import then move. This is unneccessary, creating two steps for you when one will suffice. When you do the import, you also tell LR the destination where the photos should wind up (it's on the right hand side of the Import dialog box), and LR will do the import and the move in one step.

  • Why are my raw files being changed?

    If I make changes in the Camera Raw window (i.e. change the exposure) and then "Open" it in Elements from the window, it applys those changes to the raw file, but the manual says "To open a copy of the camera raw image file (with the camera raw settings applied) in Photoshop Elements, click Open. You can edit the image and save it in a Photoshop  Elements-supported format. The original camera raw file remains unaltered" - so why is it altering my original raw file?
    Thankss

    It isn't altering your file. Elements can't write to your raw file; it stores your changes in an xmp sidecar file, not in the original file. But if makes the reasonable assumption that the reason you made changes to your conversion settings is that you want to apply them. If you don't want to keep the changes when you open the file, then undo the ones you don't want to keep before opening the file into the editor. You are never opening your original raw file in PSE, just the converted copy.
    To return to the basic elements conversion settings for the file, in the raw converter click the little lines to the right of where it says Basic in the converter window and choose Image Settings.
    Here:
    That's the mac version, but the location is the same in windows.

  • Why are my RAW files coming over grainy from Lightroom 5 to Photoshop CC

    My images are transferring grainy over the last week.  Any ideas why?

    What camera raw file is it? Can you provide the EXIF data?
    Here's the link to the possible answer:
    Help! My RAW files are VERY grainy! :-(
    I hope this helps.

  • Why are my RAW files so small/ruined?

    I just imported a few hundred photos from my camera into my computer using iphoto version 6.0.6.
    They are now useless little 2x3" jpegs with file sizes of about 16 to 50 kb.
    And of course, I used the convenient 'delete files from camera after import' feature so the originals are gone.
    Please tell me my photo files aren't ruined.
    gg

    Hi, guy. Quite apart from resolving the present problem in iPhoto, two pieces of advice:
    1. Never use the "delete images from camera after importing" option in iPhoto.
    2. If your RAW files are not found anywhere in the iPhoto Library, you can almost certainly recover them from the camera's memory — but ONLY if you haven't written anything to the card since it was erased. So don't use that card again until your pictures are found or recovered. Applications made specifically for data recovery from flash memory cards include:
    PhotoRescue
    MediaRecover
    CardRaider
    There's a demo version of each.

  • Why are my RAW files looking like infrared?

    Hi All,
    I use Aperture frequently for my editing - just recently had a ridiculous problem that results in my RAW files looking infrared.
    Have I enabled only a red channel or something?? Please help!  See pic!

    Wow, what a silly oversight - I knew I had had an update to do, but hadnt bothered with it yet. Thanks a bunch Ernie, I should have thought of us.
    Much appreciated.

  • Why do G3 raw files show as "Unsupported Image Format" in Aperture?

    I am moving towards shooting in raw, and as an experiment I imported some sample raw files from the publicly available text images on the Photography Blog. When I try to look at these images, I get a black screen with a warning triangle and the message "Unsupported Image Format". This happens for all the different raws, including some G3 raw files (.rw2). Oddly, it can read the EXIF metadata and has all the information about shooting settings etc. If I import the same files into iPhoto, it displays the images properly and allows editing, etc.
    I have a workaround, which I've also tried with my Fuji X10 raws (still not supported on MacOSX), of running them through the Adobe DNG converter, and then looking at the dng files which seem to work fine. But it's a pain.
    This has to be one of those simple "D'oh" things, but I can't see what I'm doing wrong!

    Thanks Leonie, the second part revealed that I have been an idiot, although the behaviour is still surprising. The folder has a mix of DMC-G3 raws, Fuji X10 raws, and DNG files produced from both. For the Fuji X10 files, the DNGs produce images and the raws produce the "Unsupported file format" message. The latter is not surprising, the former a little surprising (as I've heard that DNGs only work when the associated raw works). The last two remarks don't directly address my problem (or perceived problem), but they perhaps set the frame for my expectations.
    For the G3 files, when I look at it more closely, the G3 raws DO display correctly, while the G3 DNGs give "Unsupported file format". I had managed to fool myself into thinking it was the other way round (Aperture does rather hide the full file name).
    So I was completely wrong, Aperture does support DMC-G3 raw, it's just it's DNG support that's a bit weird. However, it's on my side if I need to use X10 raws (via the DNG step). In fact so far I've given up the latter, as the noise levels are so much greater than in Fuji's in-camera JPEG conversion.
    So, thanks very much for your help. Now I remember the first rule of system support: never trust what the customer tells you! (I know you're not really customer support, but I guess the same rule applies.) Thanks again

  • Why are some PDF files created in Photoshop not placing in InDesign CS5?

    We are publishers and have used InDesign for over 9 years to create 36+ magazine issues per year.  We are currently using CS5 on 8 MAC stations using OS X Vers 10.8.5.  We are experiencing difficulty placing some supplied PDF files into InDesign documents lately.    We get the following error message when placing the offending PDF file:  "FAILED TO OPEN PDF FILE"
    This is a new error message that has cropped up the last two months or so.   In Acrobat, the file will pre-flight without errors.  The files giving us the errors can be converted to Photoshop PSD, EPS or TIFF files and will place just fine.  Photoshop PDF files, however, will result in the error.
    Can anyone give me an idea what might be causing this issue?  Thanks in advance!

    Bob Levine wrote:
    Try showing options when placing. Sounds like something in the PDF is not compatible with the last settings you used.
    Most likely the crop options.

  • I can no longer import raw files from my Panasonic Lumix LX5 into Aperture 3.3.2 - raw files from my other Canon cameras are fine. Am still running Lion - NOT Mountain Lion. Tried all available software updates - no joy. Any ideas please?

    I can no longer import raw files from my Panasonic Lumix LX5 into Aperture 3.3.2 - raw files from my other Canon cameras are fine. Am still running Lion (10.7.4) - NOT Mountain Lion. Tried all available software updates - all up to date apparently but still no joy. OS X Lion shows the LX5 as a supported file format. I dont want to have to upgrade to Mountain Lion just to see if this solves the problem. Any ideas please.

    Since when did this happen? Directly after you upgraded to Aperture 3.3.2?
    If it happened directly after the upgrade the problem may be, that the raw support for your camera got lost. For some posters it helped to register the raw support again, see this post by Alan Roseman:
    Aperture 3 preview of raw file greenish
    If this does not help, you may need to reinstall Lion to bring back the raw support.
    But if the problem occured independent of a new installation, ypu may have a problem with your camera or the card you are using. Have you tried to use a different card or to reformat the card in the camera?

  • Why are my exported files not going to me email?  I have used 3 different ones.

    Why are my exported files not going to my email (receipts & business card)?  I have used 3 different ones...2 yahoo and 1 hotmail.  I have checked spam box also.

    For the Receipts app I chose to export the info as a PDF file..an email was requested..I entered info and clicked send.  For the Business Card app I chose Send, not Print..an email was requested..I entered info and clicked send.  I haven't received anything, not even in my spam folder.

  • What format are the .tmp files created by hp scanner deskjet f2400?

    What format are the .tmp files created by hp scanner deskjet f2400?  I had a customer get the dreaded "out of space" error after scanning over a hundred pages that she was going to have all in one multipage pdf.  So all that work was gone (each page was a painstaking layout of multiple elements, etc.), except for the hpfAAAA.tmp files. 
    I'm trying to recover the data.  I should say, the data is now recovered, but now I must figure out a way to use it.  How can I open these HP .tmp files?  What format are they saved in?  There is no human-readable header to give me a clue.
    If anyone can help me, it would be much appreciated.  You will be saving a very nice woman many hours of work duplicating what she already did.  Thanks,

    Hi LC475, 
    There would be no way to read the .tmp file. Unfortunately she will need to free up space on her hard drive before attempting to scan the documents again. 
    I am an HP employee.
    Say Thanks by clicking the Kudos Star in the post that helped you.
    Please mark the post that solves your problem as "Accepted Solution"

  • Why are ACR PSD files 10-20 percent larger than the same file resaved in PSD?

    Why are ACR > PSD files 10-20 percent larger than the same file resaved in PSD? I posted this many years ago and never found an answer. Now that my drives fill up quicker, I thought I might chase this question a little bit further.
    Same .CR2 saved within ACR either with cmd-R or open ACR within PSD, the saved file is 34.5mb. Resave that same file (no edits) within PSD either with or without Max-compatible and the file is now 30.7mb. Another file that is 24.5 becomes 19.5MB.
    Why the difference? Is ACR and PSD actually using different compression strategies?
    thanks.
    Mac 10.8.5 / CC / ACR 8.4.1 - but this has been a consistent behavior over many years and versions, CS6 / CC.
    Same .CR2 saved within ACR either with cmd-R or open ACR within PSD, the saved file is 34.5mb. Resave that same file (no edits) within PSD either with or without Max-compatible and the file is now 30.7mb. Another file that is 24.5 becomes 19.5MB.

    Hi Jeff
    If it is RLE it's not as efficient as LZW:
    Saved ACR>PSD = 40.1MB  (sample image this AM)
    opened in PS and resaved as PSD = 30.8MB
    resaved as TIF without LZW = 40.1MB    (this adds to your thought that the ACR>PSD doesn't us any compression)
    resaved as TIF/LZW = 9.6MB
    Jeff Schewe wrote:
    I really think your priorities are a bit off. 10-20% is meaningless...you just need to get bigger....  and quit fussing over a few GB's here or there...
    ???   I hope that the Adobe engineers are fussing over 10-20% efficiencies.
    I'm within arms reach to a rack of 40TB of drives (doesn't include off-site drives), and all 2TB drives are being recycled to 4TB drives, as a result the rack is always growing. Actually the ACR>PSD files don't really make a difference in our long term storage, only for the nightly backups. But anyway, how you save, what you save etc. should all be part of the discussion.
    .... so in my case, throw in an excess MB here and there and all of a sudden you are talking TB's. Plus advantages in backup times, drive life, and energy use.
    Somebody added compression into the PS>PSD format, but it wasn't included in the ACR>PSD format, was it a decision or an oversight? If it's just a matter of making ACR compatible with PS when saving the same PSD format..... then why not?
    regards,
    j

  • Why are 2 identical events created in iCal on my mac when I add event from mail ?

    why are 2 identical events created in iCal on my mac and not on my iPhone when I add event from mail created on a pc using OUTLOOK ?

    Nobody knows? Not even administrators?
    Please it would be really nice to have help on that to take all the benefit of the remote app.
    Thank you very much in advance.

  • Why are there 2 folders created - the photo library and the synced folder

    Why are there 2 folders created on the iPhone during a sync?  The photo library and the synced folder both show up.

    Thanks for your help mate
    This is what I've got, should I modify it?
    Thanks again BDAqua,
    Have a G'day

  • Why does a PDF file created in Pages, attached to e-mail, not get sent?

    Why does a PDF file created in Pages, attached to e-mail, not get sent?  I even blank copied myself and nothing seems to have been sent.  Could it bee the size of the PDF file?

    They send for me, my test document was 3.8 MB.

Maybe you are looking for