RAW-TIFF and Photobooks

I am using a 10.5.8, on an 2.4 Intel Core 2 Duo and iPhoto 08, (version 7.1.5) and I have a mix of RAW and jpgs in a Photobook I created, but haven't yet ordered. I have in my preferences under Advanced --->RAW Save Edits as 16 bit TIFFs. All of the files have had some edits to them, so the question is.
Can I order the book and get closely what I see on my monitor?
And a second question....If I just used RAW files and made no edits to the images can I make a book and order it? Or is some conversion needed.
Thanks in advance and hope I can order this as is but hesitant to do so until a brain greater then mine fills me in. I would hate to order it and fine the color totally out of wack or that its a blank box because it was a RAW file.
Thanks again

Terence,
They are originally RAW files, but I have under Preferences ---> Advanced--->>RAW Photos-->> Save edits as 16-bit TIFF files.........they have all been edited. Since they have been edited aren't they now TIFF files and therefore able to be sent and printed properly?
They have been edited, so I presume they are TIFF files but when I look at them within the context of the book they still are tagged as RAW files. I understand what the RAW files are that is why I am asking, as what point do they cease being RAW and able to be used for a book.
The way I read it, since they have been edited, they are TIFFs and can be sent, but I don't want to make a costly mistake.
Will the Preview method send in the other response tell me 100% that it will be printable or not?
Thanks

Similar Messages

  • The availability of color space in RAW, TIFF and JPEG files

    This is useful if your new to DSLR photography.
    This is Nikon response on my question in the discussion: View photo metadata
    I'm assuming that you know that Adobe RGB shows about 50% and sRGB 35% of CIELAB color space.
    In a DSLR camera like the Nikon D800 you can select a color space (Adobe RGB or sRGB) in the shooting menu.
    In Adobe Lightroom 4.3 the RAW metadata shows no color space info. Therefore I asked why not?
    In the (Dutch) Nikon D800 manual on page 84 (about RAW) and 274 (about color space) and Nikon FAQ website there is no descripton about the color space availability/behavior in RAW, JPEG and TIFF files.
    In the book "Mastering the Nikon D800 by Darrel Young" on page 125 - 126 is written: "If you shoot in RAW format a lot, you may want to consider using Adobe RGB....."
    All experts on this forum answered: color space does not apply/affect the RAW data file or RAW files have no color space.
    The respone of Nikon Europe Support (Robert Vermeulen) was: In Nikon D800 NEF RAW files both color spaces (Adobe RGB and sRGB) are always physically available. In JPEG and TIFF files only the in the shooting menu selected color space is physically available. So the forum experts gave the correct answer!
    Of course you can convert afterwards a JPEG or TIFF file with sRGB color space to Adobe RGB but you don't get more colors.
    When you install the Microsoft Camera Codec Pack or FastPictureViewer Codec Pack they only show color space metadata for JPEG and TIFF files and nothing for RAW because color space "doesn't exist". I thought the codec packs removed the color space metadata for my RAW files.
    Adobe Lightroom also can not show color space for RAW files because that "doesn't exist".

    Van-Paul wrote:
    The respone of Nikon Europe Support (Robert Vermeulen) was: In Nikon D800 NEF RAW files both color spaces (Adobe RGB and sRGB) are physically available. In JPEG and TIFF files only the in the shooting menu selected color space is physically available.
    I still think this is an evasive answer that doesn't really pinpoint the exact chain of events that take place. They are:
    1. The raw file contains the naked data captured by the sensor. This is just a very dark grayscale image.
    2. In the raw converter it is encoded into a working color space to process the information. In Lightroom this is known as "Melissa RGB", or linear gamma Prophoto. It is also demosaiced to bring back the color information.
    3. From Lightroom it can be exported to one of the familiar color spaces like sRGB or Adobe RGB. This is, in principle at least, a normal profile conversion.
    These three steps are what the camera does to produce a jpeg. So the basic steps are the same, the camera is just doing it automatically (and usually butchering the image in the process...).
    This Darrell Young is, I'm sure, an excellent photographer, but in this he is seriously confused and just propagating a common myth. Anyway, thanks for bringing up this discussion, hope you didn't object too much to the tone of the answers... Our only concern here was to get this right and with no room for misunderstanding.

  • Difference in TIFF and RAW import with ACR (how to fix)?

    I'm experimenting with a workflow, so whilst this may seem like an odd thing to want to make work, I have a geniune reason for doing what's described below:
    I have Canon CR2 RAW files from a 7D, Photoshop CS6 13.01 64bit, with ACR 7.1.0.354, running on Windows 7 64bit.
    1. I import a CR2 image via ACR, with no changes to any sliders; opening it as Adobe RGB (1998); 16bit
    2. I then save the image as a TIFF file, leaving "ICC Profile: Abode RGB (1998)" selected in the Color section of the file save dialog
    3. If I then close all files, and reopen the CR2 and TIFF image, they (as expected) appear to be identical
    4. After closing all files again, I then open the CR2 and make an exposure adjustment (e.g. -1.00)
    5. Using Bridge, I select the TIFF file, right click and select Open in Camera Raw. I make the same exposure adjustment as for the CR2
    6. Now, the adjusted CR2 and adjusted TIFF are different. A colour shift is noticable, and for a severe exposure change (i.e. +4.00) the shadow detail in the CR2 is a lot lighter
    Here are two cropped areas from the files (with a 4 stop push), showing some branch/leaf and grass detail respectively. The TIFF has a greener colour cast for the grass, but much darker shadows:
    TIFF
    RAW
    I appreciate that the CR2 is still a RAW file, and as such has the original Bayer pattern data, but is there any way I can make ACR adjustments to a TIFF (taken from a CR2) to behave in the same way as the original CR2?

    ssprengel, Jeff, JJMack - thanks for the constructive replies
    station_two - after your use of mildly aggressive language ("What seems to escape your grasp") in your first post, I had money that your subsequent response(s) would be on the lines of "I'm too busy to explain it to people like you". Thankyou for confirming my expectations (sometimes I wonder if some people engage in forum discussions for the sole purpose of trying to get themselves [and possibly others] riled)
    So... back to trying to find a construcive solution: If the algorthirms for the adjustments in ACR do operate directly on the Bayer data (before demosiacing to RGB per pixel) then operating on the TIFF (or any other demosaiced RGB data) will indeed be a non-starter. Without (probably unlikely) input from an Adobe developer however, we can't know for sure.
    > So RAW numbers after debayering to RGB are linear with numbers of photons within a particular color (R, G or B), while TIF numbers are assumed to be linear with human-vision sensitivity
    Understood (I'm familiar with gamma, camera sensor behaviour, exposing to the right etc). Ultimately though, it should be possible to produce an RGB file that is also linear (i.e. not adjusted for human vision) to then bring back into ACR. However, if that's simply not possible with ACR, then that's also a non-starter (and wouldn't help anyway if the adjustments operate on the Bayer data directly).
    I did look briefly into opening the RAW as a smart object, but sadly I didn't think that'd help. The goal I'm trying to achieve is an experimental idea to blend parts of images together from multiple exposures; but to achieve a single RAW file with that data as if it came from the camera (thus it could be brought into ACR to get the benefit of - from my point of view - the useful and intuitive adjustment sliders). Clearly that would require reverse engineering the particular RAW format for the camera being used (and each and every camera you'd want to support) - thus, it's not really practical.
    I'd hoped to be able to convert (without edits) the RAW images into TIFF (or some other lossless RGB container that I can read programmatically), do the blending to produce a single TIFF, and then bring that back into ACR.
    Whilst it's more convoluted, I suppose it might be possible to generate the unedited TIFF files purely for the purposes for getting data about the images, then using that to create a set of masks. Then, as Jeff suggests, perform adjustments to the RAW files in ACR, and use the masks to blend the imported (and now corrected) RAWs into one image. Not ideal, but perhaps worthy of more experimentation.

  • Photo Stream only supports JPEG, PNG, TIFF and RAW files.

    I'm using Panasonic LX3 with its RAW format (a supported RAW format since sometimes with iPhoto '09 already)
    When I choose to Photo Stream my images after import with iPhoto '11, it says "Photo Stream only supports JPEG, PNG, TIFF and RAW files."
    My files are RAW formats so why can't I photo stream it?!
    Is there something I can get around or need to wait for Apple to support this?!

    You don;t have a preset set. What you are seeing is normal behavior when importing Raw files.
    What you see at first is the camera produced JPG preview imbedded in the Raw file. Aperture puts this up while it decodes the actual Raw data. This JPG has all the special settings and enhancements set on the camera and is basically the image that would be produced if you were shooting JPG.
    As a rule none of the settings on the camera (apart from the basics) are applied to the Raw file though some of the newer cameras have settings that could affect the data stored in the Raw file.
    This is a often asked question by those just getting into Raw and you can search the discussions here for other answers to this question.
    Given the capability of today's cameras, especially the high-end ones, a lot of users have decided to abandon Raw as unnecessary  if they are happy with the images the camera produces. It's all a matter of personal needs.
    regards

  • Jpeg, TIFF and Raw files in iphoto

    I have all three types of files in my iphoto library. I need to sort them so I can export Raw files and some TIFF files to Elements 3 for conversion and/or editing. I need to convert some Tiffs to Jpeg to save space.
    Is there some way I can sort my 3000 files so that I can find all of a type in order to, for instance, do a Batch Rename in Elements? Is there a way to do that sort of conversion within iphoto?
    imac g5 1gig   Mac OS X (10.4.5)   300 gig external HD
      Mac OS X (10.4.5)  

    To sort your pictures by file types, create Smart Folders where Filename Contains .tif or .tiff, .jpg or jpeg, etc.
    Once you have created the Smart Folders, you can export the contents of the Smart Folders to folders on your Desktop or elsewhere and then batch convert the files in Elements.
    I don't think there's a way to batch convert the files within iPhoto, but you can ask about that in this iPhoto forum.

  • I have an iPad 2 and a Nikon DSLR. How can I transfer RAW/Tiff images using a compact flash card

    I have an iPad 2 and a Nikon DSLR. How can I transfer RAW/Tiff images using a compact flash card? Plugging in the camera at the ipad connector doesn't seem to work, possibly due to lack of power.

    This may apply.
    Fix (for Nikon D800)
    http://www.georgewheelhouse.com/blog/2012/10/ipad-ios-6-update---camera-connecti on-kit-fix
    Are you using an SD, SDHC, or SDXC card? And what capacity?
     Vheers, Tom

  • 10.4.11 autoupdate killed tiffs and raw files - REPAIRMENT HOW?

    Hi there!
    I got big problems when I was updating from os 10.4.10 to 10.4.11 - everything crashed and I had to install everything new - I decided to take a new harddisk as well, but when I copied the rest of the stuff from the old one, I had to realise that several tiffs and raw files were damaged in a way that "preview" can handle them, but no other programm (no photoshop, or capture one). Is there any possibility to get those stuff back working well?
    Thank you for all your help!!!
    Yours,
    Joerg

    Thanks for that,
    I downloaded RPP and it does indeed open the RAW files and lets me convert them into TIFFs or JPGs which I can then import into Photoshop to play with.  However I'm still confused about why I can't open them in Photoshop directly.  My other camera is a SLR saving to a SanDisk Extreme lll Compact Flash card and I can open RAW files off that on the same computer with no problem using a Photoshop RAW converter plug-in.

  • Output sharpening in Adobe Camera Raw (ACR) and Photoshop CS5

    Output sharpening in Adobe Camera Raw (ACR) and Photoshop CS5
    I want to do two-pass sharpening - capture and output - with output capture done just before I print. I do the initial (capture) sharpening in the ACR Detail/Sharpening panel, with Amount slider set to, for example, 100.  Then, I open the image to PS CS5 as a Smart Object, and use layers and masks for further editting.
    My question is, can I go back to ACR for the final (output) sharpening pass?  When I re-open the file in ACR, the Sharpening Amount slider is back to zero, but the other three sliders are still at the settings I used at the start of the process, i.e., the capture sharpening.  If I again set the Amount slider to a positive value, then again open the image in PS for printing, will my second pass through the ACR Sharpening panel take effect - will it accumulate on top of the initial sharpening?
    By the way, the reason I want do output sharpening in ACR rather than, say, PS Unsharp Mask, is so I can use the Masking slider in ACR, which is much easier than the comparable techniques available in PS.  I am aware that some say you should not do any masking for the output sharpening. I'd like to though.
    Thanks for ideas.

    This is pretty much the way I do it, and I also always found ACR sharpening superior to anything in Photoshop. There is the "sharpen for output" in ACR, but you have little control over it.
    The tricky part is feeding the file through ACR a second time. I don't think re-opening the Smart Object will do anything more than you could have done the first time. I do it with a rendered TIFF, and have an intricate set of actions that I run in the Image Processor Pro. It's a mess, and you don't want to know.
    The frustrating part is how to action ACR. I just can't figure it out. It'll work, and then I have to change some setting and the action stops working. I suspect you need a script, but so far I haven't found any.
    So I've come to a compromise: I first process to TIFF in a temp folder, then I bulk open them in ACR to sharpen, then a second process to finish up.
    For less critical files I have a sharpening action that comes close, involving edge masks and blend ifs, using smart sharpen which tends to preserve edges better than unsharp mask, and with less accumulation of noise.
    Bottom line: I'm also very interested in further comments to this. BTW, I recently bought Lightroom 4, so maybe there is a posibility using that in a mixed workflow.

  • Editing in Photoshop Elements 9 (tiff and tif)

    Last week at the end I moved to Aperture. Now I've some problem when I edit with Photoshop Elements 9.
    I've setted Aperture to transfer a 8 bit tiff to photoshop now Aperture tranfer a .tiff file to photoshop and when i save (not save as) photoshop save back a .tif file that obvisioly Aperture don't see..
    There is a way in Aperture to set to export a .tif or in photoshop to save a .tiff; I know it is just a matter to remember to add an "f" before saving but it is so easy to forgot....

    Only your camera can save as NEF. It's not even a file, really, a Raw is just the dump of the data from your camera sensor.
    When you process (or edit) a Raw it has to be saved as something else - in this case a Jpeg.
    You can choose tiff in the Preferences if you prefer.
    But there is no way to edit a raw file and then send it, as a raw, to another editor on any system.
    You can also process your Raw with a 3rd Party app like ACR or Photoshop. But iPhoto does not handle this gracefully and it's a bit of a kludge.
    First off set your preferred app as an external editor in iPhoto:
    You can set Photoshop (or any image editor) as an external editor in iPhoto. (Preferences -> General -> Edit Photo: Choose from the Drop Down Menu.) This way, when you double click a pic to edit in iPhoto it will open automatically in Photoshop or your Image Editor, and when you save it it's sent back to iPhoto automatically. This is the only way that edits made in another application will be displayed in iPhoto.
    Note that iPhoto sends a copy+ of the file to Photoshop, so when you save be sure to use the Save command, not Save As... If you use Save As then you're creating a new file and iPhoto has no way of knowing about this new file. iPhoto is preserving your original anyway.
    Next: In the iPhoto Preferences -> Advanced, elect to use Raw with your External editor:
    Uploaded with plasq's Skitch!
    Now when you go to edit the Raw it will be sent to your external editor.
    Now for the kludge:
    You cannot save a Raw. The work you do must be output to a new file, in a new format (jepg, tiff, whatever). However, as the External Editor is making this new file iPhoto has no knowledge of its existence. Therefore you *must save it to the desktop and then import it back to iPhoto as a new file*.
    This means that you will have your Original Raw and the processed version in iPhoto but they will not be recognised as version and original. iPhoto will see them as two separate shots.
    Regards
    TD

  • Include Develop settings in metadata inside JPEG, TIFF, and PSD files ignored when unchecked

    In the Catalog Settings under the Metadata tab, I have unchecked the option 'Include Develop settings in metadata inside JPEG, TIFF and PSD files'.
    I then selected a JPEG photograph in the Library module and chose Metadata/Save Metatdata to File.  I wanted to save the metadata that I had added (keywords, IPTC, rating, etc), but not the develop settings.
    I then imported the jpeg back into another catalog.  The metadata I had added was there as expected, but so are the develop settings.  This I did not expect or want.
    Have I got something wrong here?  My understanding is that turning off the 'Include Develop settings in metadata inside JPEG, TIFF and PSD files' option means that develop settings are not written to the xmp area in non raw files such as jpegs.
    Looks like a bug to me.
    Tony

    Hello all,
    I have investigated this problem further and now have the answer.  It is not that the option "Include Develop settings in metadata inside JPEG, TIFF, and PSD files" is ignored, but it appears that the LR catalog is not properly updated when this option is turned off.
    Here are steps to test and illustrate the problem:
    1. Create a new folder and place a copy of an original jpeg image (original from camera) in the new folder.  Make sure you keep the original safe and only work on copies.
    2. Create a new catalog in Lightroom 2.3.
    3. Import the jpeg image from the new folder.
    4. Add some metadata (keywords, ratings, title, caption, IPTC data, etc).
    5. Make some Develop adjustments to the image.
    6. Open "Catalogue Settings" from the Edit menu and check (enable) the option "Include Develop settings in metadata inside JPEG, TIFF, and PSD files".  Uncheck (disable)  the "Automatically write changes into XMP" option.
    7. Select "Save Metadata to File".
    8. Delete the jpeg image from the Library module, then re-import it.
    9. Copy the original image back to the new folder, replacing the updated jpeg (once again, the jpeg image now contains no metadata from Lightroom).  At this stage, Lightroom fails to recognize that the metadata in the LR catalog doesn’t match the metadata content in the jpeg file.  I would have though that it should.
    10. Open "Catalogue Settings" from the Edit menu and uncheck (turn off) the option "Include Develop settings in metadata inside JPEG, TIFF, and PSD files".
    11. Reset the Develop settings.
    12. You now need to make a change to the metadata like increase or decrease the rating (otherwise LR won’t save any metadata to the jpeg file - LR is being too smart and thinks it’s already up to date, so does nothing when you do the next step).
    12. Select "Save Metadata to File".
    13. Delete the jpeg image from the Library module again, then re-import it again.
    14. Look at the develop settings (that you specifically did not want saved within the jpeg file in step 10).
    Although the Develop settings were Reset in step 11, you have ended up with the original Develop settings from step 5.  It is true that LR has not saved the reset develop settings, but it also hasn’t removed the old develop settings that are still stored in the catalog.  This must be considered a bug (oversight).  Note that it has also saved an Import snapshot as well.
    For the more technically minded (and the LR developers if you are listening), the field "xmp" in the table "Adobe_AdditionalMetadata" is not updated (old camera raw settings and snapshot settings are left behind) when the "Include Develop settings in metadata inside JPEG, TIFF, and PSD files" option is unchecked (disabled) and it seems that this is the data that is written to the jpeg file when you select "Save Metadata to File".  Note that the state of "Automatically write changes into XMP" has not effect on this process - I tried it on and off.
    Hope that this might be of some help to others one day.
    Tony

  • Capture One RAW Tiffs not previewing properly in Aperture

    We just wrapped a big photoshoot and the photographer was using Capture One Pro. He gave me all of the raw files, but Capture creates RAW Tiffs. I imported them all to my Aperture, but now it's only showing me low-res jpeg previews. We switched computers mid-way and some of the previews are bigger than others, so I realize it's probably a setting in Capture One, but I want Aperture to show me the real file.
    any suggestions?
    thanks,
    -A

    euroskip wrote:
    thanks, but i have to say, that's pretty weak on Apple's end. it was from a Phase One back and if apple wants to get into the pro game, they better get on board with what most pros are using at the moment.
    thanks for the response, hopefully they fix that stat.
    what's that lightroom? you wanna play? ok.
    I agree that they need to add Phase One support, no question. They've got Leaf and Hasselblad. It's a huge oversight for them not to have Phase One.
    That said, if this was a "big proshoot" as you say and the photographer gave you all of his raws why are you bouncing around between programs? You are not a digital tech or you'd already know what was up. If you're thinking that you can hit the ground running, fresh from an assignment, with no experience in any of these programs (Aperture, Lightroom, ACR, Capture One, etc.) then you've got a learning curve ahead of you.
    It would probably be much more efficient for you to have the photographer process the raws for you (I don't know of any pro's who would hand off their raw files - it's just assuming too much on the client's end) or outsourcing to a digital tech who's knows how to work the files.
    Jon Roemer
    http://www.jonroemer.com/

  • What does "Include develop settings metadata inside JPEG, TIFF, and PSD files" do?

    I am wondering what the option "Include develop settings metadata inside JPEG, TIFF, and PSD files" found in catalog settings/metadata does?  what happens if you uncheck it?

    Bob12312321 wrote:
    also when this is unchecked will lightroom still save keyword changes to raw(nef) files?  thank you!
    Metadata ("real" metadata like keyowords nor develop adjustments) are never saved into non-DNG Raw files (like .nef, .cr2) directly. With these files, there is always a so called sidecar file (with the extension .xmp) created to hold the XMP information.
    And yes, if the option is unchecked, LR will save the keywords to the XMP sidecars, when you perform "Write Metadata to File" or have the autowrite option active.
    Beat

  • External Editor only TIFF and PSD

    I want to edit my photos in Photoshop but in the Preferences there are only the TIFF's and PSD formats supported - since my original files come as JPEG's it would be sufficient to safe the files as high quality JPEG's. Is there a possibility to edit a PLIST file in Aperture, that this option gets visible in the Preferences?

    my qustion is would not this be the perfect job for a
    DNG file in
    a future V. of apeture ?
    I can state this would not be a good way at all to handle this situation. The problem is this - you have been working on color and other adjustments based on the Aperture RAW conversion (which itself you have probably carefully tweaked as to sharpness and noise reduction).
    Using DNG and going to some other program to edit, you are relying now on the ability of that other program to do exactly the same RAW conversion and also do all of the adjustments Aperture did in exactly the same way. As you might imagine, no other program has a hope of doing the conversion and adjustments exactly as Aperture does them, for they are not Aperture. Thus when you did sharpening or some other adjustment in that other program it would be based on a different RAW conversion that may well not have the exact same combination of RAW adjustments applied.
    That is why when moving to other programs to continue editing a rendered format (such as TIFF) is the way to go, because it exactly preserves all of the editing you have done to that point.
    As to the posters original question it would not actually be that great an idea to send a JPG over to the external editor because it would have to be a brand new JPG with your adjustments applied, and then when you saved it from the external editor you'd have a 3rd generation JPG file and every time you edited it after you'd have yet another generation of JPG loss.
    What you can do to conserve some space is to select PSD for external editing, and then in Photoshop (or whatever you open the file in) convert to 8-bit mode (by default it's 16).
    Just think of ti this way - that JPG is no longer a JPG, it's your new master! Preserve quality at all costs (well at least space costs).
    Messing with the plist file may give you an 8-bit PSD file directly, I have not messed with those settings after 1.1.1 came out.

  • How to save metadatas in RAW files (and not in external .XMP sidecar file)

    Hello,
    I would like to save metadatas (for example keywords) inside the RAW files, and not in external .XMP sidecar file.
    How to do this in Lightroom ?
    Thanks
    Josh
    PS: is XMP a file format (= .XMP files) or a metadata format that can be embedded either in a .XMP sidecar file or in the RAW itself ?

    MarvinFoster wrote:
    It's a horridly named catalog setting since if you are using DNG you don't have XMP files but it does the same thing, it updates the dng with the catalog settings.
    XMP does not mean XMP FILES per se.
    XMP is a metadata format/standard. so it´s not horrible named but simply missunderstood. 
    http://en.wikipedia.org/wiki/Extensible_Metadata_Platform
    XMP can be used in several file formats such as PDF, JPEG, JPEG 2000, JPEG XR, GIF, PNG, HTML, TIFF, Adobe Illustrator, PSD, MP3, MP4, Audio Video Interleave, WAV, RF64, Audio Interchange File Format, PostScript, Encapsulated PostScript, and proposed for DjVu. In a typical edited JPEG file, XMP information is typically included alongside Exif and IPTC Information Interchange Model data.

  • RAW NoiseNinja and HDR - what workflow ?

    Here's what I want to do :
    1. Open Nikon D300 NEF files
    2. Remove chromatic aberration (in Camera RAW 5.5)
    3. Remove noise using NoiseNinja PS plugin
    4. Merge to HDR
    My problem is between stages 3 and 4, as I can't save the files to RAW in order to move on.
    Any ideas gratefully received
    Thanks !

    Victor Burgin wrote:
    Thanks again. I'm further enlightened (and now understand the value of keeping the metadata as a separate file), but you earlier seemed to suggest that if I leave Noise Ninja out of the equation, and do both defringing and noise reduction in ACR, then I can use the resulting file (which I appreciate is no longer strictly a RAW file) in Merge to HDR – which I can, but only after being warned that I have lost valuable tonal data.
    Who says you lose any tonal data at all when you convert (open) a raw file and save it as a PSD or TIFF file?     If that were the case, there would be no purpose to shooting raw. 
    Or is your issue that you need raw files to convert to HDR?  Forgive me for that over-simplistic question, but never having seen an HDR image that I have even remotely liked, I have not played with that feature much.  When faced with a scene with extreme dynamic range, I combine multiple exposures (or multiple renditions of one or more raw files) in Photoshop, manually and judiciously as needed, and obtain infinitely better results than the HDR merge function can provide for me.
    Victor Burgin wrote:
    Summary : For optimum results, Merge to HDR will work only on an unaltered RAW file – but if "unaltered" by definition means that the file is marred by chromatic aberration and noise, then Merge to HDR is a completely useless component of CS4. Am I missing something ? 
       Again a misconception.  Any Merge function (to HDR or as a panorama) cannot possibly work on a raw image.  Instead the Merge function needs to call upon Camera Raw (in the background) to convert and cook the raw image data on the fly by opening it, and the conversion process will include any adjustments you have applied to its metadata, such as ACR Color Aberration correction, ACR Noise Reduction, spot adjustments, sharpening, vibrance, saturation, exposure, etc.  That's why the metadata is there, to be applied during the conversion.
    A raw file is a very, very dark grayscale image without anything that a human being can interpret as color, although there is color information to be used by the raw converter (in this case Adobe Camera Raw).  That's why the raw file must be converted before it can processed in any way.
    My apologies if my previous posts were unclear.  I hope this one is better crafted.
    Wo Tai Lao Le
    我太老了

Maybe you are looking for