Lost part of a raw image

I opened Lightroom to work on a particular image, found the image in the catalog and selected it. Initially, it loaded the whole image, then a split second after the image displayed on the screen, one third of the image disappeared and turned white. If Lightroom is non destructive and I have not edited the image in any other programs, how can a file apparently get corrupted? I then tried opening it in PSE 9 and the same thing happened. Initially it showed completely and then one third disappeared. Now I only see two thirds of the image no matter what I do. Is this file recoverable? It is a Canon Raw CR2 file. Fortunately I have a jpeg version but I really wanted to work with the original RAW file. I do not have this problem with any other images in my catalog.

Your raw file is corrupt. A raw file has an embedded jpeg image that Lightroom uses as a preview while it is creating a new preview from the raw data. The original jpeg image embedded by your camera is OK, but the raw data is corrupt. Lightroom didn't change that data, the corruption was almost certainly caused by some sort of hardware problem: bad card in your camera, loose or flaky cable when you transferred the image to your computer, flaky disk drive, or even RAM flakiness.
Investigate your hardware. If your disk drive is starting to fail, your troubles will soon be much wider in scope than a corrupt raw image.
Hal

Similar Messages

  • Updated Lightroom and PS in CC and Lost RAW images

    I am very new to CC and all the programs.  When I installed the updates after updating my MAC software to the newest version, I lost all my raw images.  I do not know what happened.  HELP!  All the JPEGS are there but I lost the rest. 

    After an update of OSX it’s best to trash the prefs file so that they get automatically re-built on next launch.
    Quit Lightroom
    Launch Finder and find the user Library by clicking the Go menu whilst holding down the Optn (alt) key (n.b. the library is hidden until you press the optn key) and inside the Library folder select the preferences folder. Then trash the following file:
    com.adobe.Lightroom5.plist
    Quit Finder and re-launch LR5

  • How to get Aperture and iPhoto to use Pentax *ist DL RAW images natively

    Using some techniques that I found in various places in these forums, I am going to give step-by-step instructions to get Aperture and iPhoto to recognize Pentax *ist DL RAW images natively.
    Note: This worked for me using 10.4.6 with the latest iPhoto 06 and Aperture updates. I do NOT know if this will work on older versions of OS X, iPhoto, or Aperture.
    Note: If you also use a Pentax *ist DS camera, these instructions will probably disable support for that particular device due to the modifications made to a system file. Only complete these instructions if you want to use a *ist DL camera.
    ** These instructions involve modifying system level files using a HEX editor. If you are not comfortable with this, do NOT attempt to do this or you could kill your system. Remember, BACKUP BACKUP BACKUP. These steps worked great for me but follow at your own risk!! **
    Ok, lets begin...
    1) Download this great patch by macintosh_tech
    http://idisk.mac.com/macintosh_tech-Public
    This patch contains an updated raw.plist file which includes the RAW information for the *ist DL. This patch also contains an updated libRaw.dylib file and an updated Raw Presets file for Aperture.
    ** Do NOT copy the libRaw.dylib file from this patch to the folder listed in the patch Read_Me. This file did not work on my Intel-based Mac and crashed my system!!
    I was able to modify my original libRaw.dylib file using a HEX editor to get it to work on my system. Instructions for this modification will follow.
    2) Open the .dmg of the patch in a Finder window
    3) Open a new finder window and browse to /System/Library/Frameworks/ApplicationServices.framework/Frameworks/ImageIO.fra mework/Resources
    *4) Backup the libRaw.dylib and Raw.plist files. Copy them to a safe location. For extra safety, you can just copy the whole Resources folder to a safe location (Make sure that you COPY it and dont MOVE it)*
    5) Right-click the libRaw.dylib file and select "Get Info". Look at the bottom of the info window and expand the "Ownership & Permissions" tab. In this section, expand the "Details" tab. If the lock icon is in the locked position, click it to unlock it. Change "Owner" to your user name. If requested, enter your system password at this point. Close the info window. This step lets you modify the libRaw.dylib file.
    6) Complete step 5 for the Raw.plist file.
    7) Copy the Raw.plist file from the "Place In System Folder" folder from the patch to the Resources folder. It will ask you if you wnt to overwrite the existing file. Click "Replace".
    8) Open a new finder window and browse to the /Users/YOURUSERNAME/Library/Application Support/Aperture/ folder.
    * 9) Backup the "Raw Decode Presets.plist" file *
    10) Copy the "Raw Decode Presets.plist" file from the "Place In Home Directory" folder from the patch to the /Users/YOURUSERNAME/Library/Application Support/Aperture/ folder. Click "replace" if it asks you.
    11) Here's the tricky part. Download a HEX editor if you don't have one. I used 0xED. It is free and can be downloaded from
    http://www.versiontracker.com/dyn/moreinfo/macosx/29521
    12) Open the libRaw.dylib file from the Resources folder in your HEX editor.
    Note: This is your original libRaw.dylib file from your /System/Library/...../Resources/ folder, NOT the file from the patch.
    Use the Find function and search for the string "Pentax *ist DS". Make sure you are using "Search Type: Text" (or equivilent in your editor) and that you use proper case. When you find this string, change the "S" in the "DS" to an "L". The string should now look like "Pentax *ist DL". Use the "Find Next" function to find the next instance of "Pentax *ist DS". Again, change the "S" to an "L". There should be two total instances that you need to change. Save the file and exit the editor.
    13) Open Disk Utility and repair permissions. This will set the raw.plist and libRaw.dylib files back to their original permissions.
    14) Reboot the system.
    15) You should now be able to view .PEF files natively in Aperture and iPhoto. I appologize in advance for any typos. Let me know how this works, as this is my first tutorial of this nature.
    Macbook 2.0   Mac OS X (10.4.6)  

    It would appear that my last post was a moot point as the 10.4.7 update adds support for the *ist DL. It's nice to have it biult into the operating system now.

  • Automatically export to JPEG from RAW images

    RAW images are preferred form of shooting for many photographers. And, Lightroom is great at managing and developing these images. However, we increasingly use/view these images outside Lightroom and away from the PC where we do most of the development. For example, I use a DLNA server which shows off my entire image collection to big screen television (which can act as a DLNA client). The same DLNA server is used to send images to our smartphones (my wife loves to show all kid pictures anywhere she - without having to carry the pictures on the phone).
    Most other applications that use these images, do not work on RAW images and JPEG images must be exported manually from Lightroom. This becomes increasingly difficult to manage and keep track of while developing RAW images. How many RAW images need to be exported? How many images did I touch since the last time I exported them?
    Currently, I am using the following process to manage this:
    1. I created a smartlist which contains images that are edited after "a particular date".
    2.  I select all images in this smartlist, and use Lightroom3's export  function to export them all as JPEG, to the same folder as original.
    3. Once the export is completed, I modify the smartlist to change the "particular date" to today's date.
    I plan to repeat this procedure every so often (once a week or so).
    It would be great if Lightroom had a feature such that it always keeps "JPEGs exported" for all RAW images (with the latest development settings of course). This could be a process that could occur in the background or at a user-specified time/event (e.g. when one closes Lightroom). User should be able to specify where the exported JPEG images should be put to and with what name (I prefer in the same folder as RAW but other users may have other preferences). User should be able to select if this is only done for RAW images or also for JPEG and other formats (in which case, should the exported image override the original or not). The exported images should be (optionally) automatically included in the Lightroom catalogue and stacked with the original RAW image.
    Mainly, the entire process should be completely transparent to the user. A collection of JPEG images - corresponding to the latest development settings for the RAW images - should be always available.
    Osho

    I've heard many others raising the issue of an auto-jpeg feature - kinda like auto-write xmp, except auto-write jpeg.
    I agree this would be nice, obviously some sort of "stability" check would be needed so it isnt constantly writing jpegs as you edit. Lightroom employs a form of this already for the xmp - meaning it doesn't update xmp every brush stroke, but accumulates several strokes before updating, so its more efficient...
    If you could define multiple jpegs to keep - with the raws, or a separate tree - even better. That would obsolete all the tree output plugins and publishers.
    The publishing feature was intended to fill this need (albeit manual only), but it suffers from the inability to publish to original directory, and/or an external tree.
    I'd like to see a manual mode too, that accompanies a new "Done for now" function - so when you say "Done for now", it saves xmp, jpeg(s), snapshot, and optionally locks the file so unapproved changes can no longer happen to it. Then if you could define multiple "done for now" presets that include initiating publish service and exports, then the work-flow becomes: 1.import, 2.edit, 3.done for now - and thats it (maybe repeat 2 + 3 in the future). i.e. no more manually initiating the exports, publish services, snapshots, saving of xmp, ..., and whatever else you do when you're done.
    In the mean time, I may make some of this part of an up-n-coming "Sidekick" app + plugin combo when I get to it.
    Presently, I dont use publishing services, and I have ExportManager to consolidate exports (which includes TreeSync), so my workflow is: 1.import, 2.edit, 3.done for now (save xmp+snapshot, and lock via ChangeManager), 4. initiate consolidated exports...
    Rob

  • Loss of thumbnails of RAW images in Photoshop prior to opening them in Camera Raw

    I recently purchased and started using a Canon EOS 7D Mark II.  I found that with my Photoshop CS6 I was unable to open my RAW files in Camera Raw, so I downloaded an update of Camera Raw, viz. version 8.7.1 from the Adobe website.  Now I can open the RAW images from my new camera in Camera Raw.  However, I have lost the capacity to display a thumbnail image of a RAW file when using the open function of the file drop down menu in Photoshop. Now when I single-click on an ID number of a RAW image from the list of images, I see only a blank thumbnail.  I save lots of time using image thumbnails for selecting images for editing in Camera Raw.  Is there some way to restore the ability to see RAW image thumbnails in Photoshop prior to opening images in Camera Raw?

    Which operating system are you using?
    Are the blank thumbnails only for the files from the canon EOS 7D Mark II camera?
    An alternative is to use Bridge CS6 or Mini Bridge to see the photos before you open them in photoshop cs6.

  • Cannot Open Camera Raw Images in PS CR3

    Even though I've been a professional photographer for over 25 years, I finally decided it was time to go digital. Little did I know how overwhelming and frustrating the learning process would be, especially for an old timer like me. Well, the 10 day return period on the digital equipment and software purchase is up, so I have no choice but to move forward in the learning process. :)
    Actually, I'm excited about all the photographic possibilities that digital has to offer over film.
    The first batch of photos were taken with a new Canon 40-D in Raw + JPEG. When I open my picture folder (containing those photos) in Bridge, a CR2 icon appears next to each thumbnail image that was loaded from the camera flash card. The Bridge program is part of Photoshop CS3 that I purchased, and the 40-D has the latest firmware. (If relevant, the computer is a PC using Vista Home Edition.)
    Problem: When I double click on a JPEG image, I am able to load that image into Photoshop. When I double click on the CR2 icon, however, I get a message that says, "Could not complete your request because it is not the right kind of document." What am I overlooking?
    Also, shouldn't a thumbnail Raw image appear along with its corresponding JPEG thumbnail when the content of the picture folder is opened in Bridge? As it stands now, I get only a CR2 icon next to the JPEG thumbnails.
    I would be grateful for any help you could offer.
    Many thanks.
    Bruce

    Bruce,
    When I made the transition to digital some 8 years ago, I had tremendous help from a number of well documented websites, among which:
    http://www.luminous-landscape.com
    I think a lot of stuff there to get you seriously going. Another one is:
    http://www.computer-darkroom.com
    I sold all my film based stuff, except a Nikon F3 and a handful of lenses and a Paterson developing tank.
    The Nikon suspiciously smells like foam mirror damping strips chemically decaying.
    I sold my enlarger over the internet. The word "enlarger" caused me to be on SpamCops blacklist for a while.
    I'm in this since the seventies, and I think you'll be as amazed as I was at the possibilities and control you have. And no more bags with $300 worth of film that's consumed in one shoot.
    Jump in both feet! you won't be sorry. And these forums are the best help you can get.
    Good luck,
    Rob

  • RAW images in Lightroom aren't opening in camera raw in Photoshop.  Instead, I have to open the image in Finder before it will open in Camera Raw in Photoshop.  How can I correct that?

    RAW images in Lightroom aren't opening in camera raw in Photoshop.  Instead, I have to open the image in Finder before it will open in Camera Raw in Photoshop.  How can I correct that?

    Your question is a little unclear. In a "normal" Lightroom/Photoshop workflow the raw images do not open from Lightroom into Camera Raw. Lightroom has all of the Camera Raw functionality in the develop module. When you choose to open an image in Photoshop, and Lightroom and Photoshop are synchronized (i.e. referencing the same version of Camera Raw) then Camera Raw is simply used to interpret the Lightroom adjustments as the image is transferred to Photoshop. If Camera Raw is an older version then Lightroom offers you the choice to open the image or create a PSD or TIF file that includes all of the Lightroom adjustments. But in either case, opening in Camera Raw is not part of the workflow. It is possible to open the image as a smart object or convert the image to the smart object in Photoshop and then open it in Camera Raw. That is done from within Photoshop or is one of the open options in Lightroom. If you choose to go the smart object route the image first has to be opened in Photoshop and then from there you can open it in Camera Raw.

  • Raw Images still Icons only

    After the latest round of updates from Adobe for Windows Bridge (Win7 62 and 34) I have the problem of all raw images showing up as icons in Bridge. The images will open in the converter fortunately but it would be nice to see what the image is before double clicking on it. I have followed all of Adobe's instructions but the problem persists. Deleting and reinstalling the raw plug-in does not fix the problem. I have had every glitch with Adobe Bridge ever reported since the very first version and a few unusual ones that Adobe support, in Microsoft fashion, denied could possibly exist. (Rant about perpetually incompetent Adobe programmers deleted).Apart from a complete program re-install (which is likely pointless as the latest Camera Raw upgrade will still be corrupted) is there a solution for this competely disastrous upgrade from Adobe?

    Sadly: deactivate, uninstall, reinstall. If you have many plug-ins, particularly if they have Aobe-like activation restrictions, that must be considered.
    When Photoshop does what it is supposed to do it is a wonderful tool.
    But.
    It is not clear why Adobe has not been able, or has not tried, to correct the many problems with Bridge since version 1. These are the two most bothersome problems I experience regularly. Adobe says the problems are unique to me but I doubt it since I have had the same issues on at least a dozen machines of all types:
    Bridge tends to freeze if it has been opened for a long time and many images have been opened through Bridge; only rebooting the computer will solve this.
    More often than not after a long sessiion in Bridge/CS-anyversion it is impossible to re-open Bridge, once closed, without rebooting the computer.
    Both these issues exist in Windows XP/Vista/7 in both 32 and 64 bit versions of the OS and Photoshop and in every version of Bridge I have been afflicted with.
    In CS5 I have not lost custom workspace arrangements, a frequent problem in prior versions, but I have lost the ability to preview raw images: which is worse?
    These are not issues with the Windows OS but are specific to Adobe programming  of a $600 program for Windows.
    If I am going to work on a specific image I frequently open it directly from the desktop in order to avoid Bridge entirely because I never know what I am going to get.

  • After using PS CS6 for well over a year, Bridge now will not open RAW images in Camera Raw, although

    After using PS CS6 for well over a year, Bridge now will not open RAW images in Camera Raw, although Photoshop does. When I try to open them in Bridge, I receive a popup message that says that it "requires that a qualifying product has been launched at least once to enable this feature." Obviously, I have done so hundreds of times since installing and activating CS6. What gives, and how do I fix it?

    Things have now become significantly worse!
    Now when I try to open anything from Bridge, or try to open PhotoShop at all, I receive a popup that gives me 2 options: 1) License PS CC, or 2) continue with my trial of PS CC.
    So far as I know, I have not downloaded any trial of anything from Adobe in many months. In fact, I have no interest in PS CC. I wish simply to use PS CS6.
    I have uninstalled my Adobe Creative Suite 6 Design Standard, of which my PS CS is a part, and reinstalled it but I still am blocked from using my properly licensed programs.
    Please advise.
    Mike Hannisian

  • Why doesn't a RAW image placed in a Photoshop Document  pick up changes?

    I have just noticed that if you place a RAW image in a PSD(CS6), then tweak the RAW image using Camera RAW, the changes are not picked up by the PSD.
    I always try and keep my PSDs as open to change as possible and placing is a big part of this. Usually I place an image in a PSD, then if I edit the image outside the PSD, the changes are picked up in the PSD.
    With RAW this doesn't seem to happen. I have the following file-structure:
         -- someFolder
            -- somePSD
            -- someRAWFile
            -- someRAWFIleXMP
    What I'm doing:
    1. I drag the RAW File into the PSD.
    2. I open the RAW File and tweak it.
    3. Photoshop does not reflect the changes
    4. I drag the RAWFile into the PSD
    5. I then have the same placed RAW File with the changes reflected as well as the old placed RAWFile without them.
    So even though both placed images are the same image, they reflect the RAW File at the time it was placed, not at its current state which is surely the whole point of placing a file. It seems that the image is encoded with the RAW settings at the time it is imported, but these are never updated.
    What am I missing? Is this a bug or is there no point placing a RAW file?

    If you need a "non-destructive" alternative, you can import the raw as a Smart Object. You can set this in Camera Raw's Workflow Options, or you can do this 'on the fly' by holding down Shift when you click on Open.
    If you want to change a develop setting after adding the image to a PSD, double-click on the layer thumbnail to reopen the ACR session, and the OK or Cancel when you're finished.
    Thanks Yammer,
    this is very good to know.

  • Photoshop Elements 7 and Panasonic Raw images

    I recently bought a Panasonic Luminex partly in order to shoot RAW images. My research told me that Photoshop Elements 6 and above would accept it. My PE 7 is telling me, however, that it cannot open the image because it is the wrong kind of file. Any guidance?

    What model of Panosonic Lumix is it?
    Unless it's Lumix DMC-GH1, then in all likelihood, you'll need to use the 8.2 dng converter
    to convert your lumix camera raw files to dng copies, which then pse 7 should open.
    8.2 dng converter:
    http://www.adobe.com/support/downloads/detail.jsp?ftpID=5646
    more info on which cameras work in particular versions of camera raw and photoshop elements:
    http://forums.adobe.com/thread/1030798?tstart=0

  • RAW image and preview dramatically different

    I'm using Aperture 2.1 and am recently finding myself extremely unsatisfied with the rendering of my RAW images created with my Nikon D50.
    I am shooting in just RAW (NEF) and sRGB, and am exposing for what I am seeing on the back of my camera. At times I use manual, and others I use the Program setting with a -1.3 exposure compensation since the camera leans too bright; I seem to recall everything exposing correctly until recently. But my memory is shoddy when it comes to how things previously appeared.
    The preview before importing shows much the same image that I intended (exposure-wise), as does the quick preview for a second or so during the import process. Shortly after, my pictures all become dull and dark, lacking color and appearing about 2 stops underexposed.
    I love photography, but am personally baffled by the issue of color profiles, RAW images JPEG previews, and all that jazz. Nothing seems to explain these adequately, which is why I'm reaching out to those more knowledgeable than me. I am unsure if it's my camera, Aperture, color spaces, or just settings within Aperture or my camera.
    Once again, I want to say this is a recent problem, but it may just be that I only noticed recently.

    I have exposed to the image on the LCD before and produced wonderful results. Or, at the very least, results that didn't drive me to post on a discussion board.
    As per your questions:
    --I use 4 different methods to determine how I am exposing my image. In Manual, I use the TTL metering chart in the viewfinder (usually exposing -0.7 to -1.3 so as to compensate for the tendency for the camera's meter to overexpose), the resulting image on the LCD, the histogram, and the in-camera highlights indicator (since, once again, it has a tendency to try and overexpose an image). In Priority modes, I use the camera's exposure compensation setting to set the compensation to -0.7 or -0.1. The resulting JPEG that I see in the pre-import thumbnails and the brief seconds during import are exactly the exposure I want, but when Aperture finishes importing, it's entirely too underexposed. And it's not just that-- the color seems to be worse than it would if it were just simple underexposure... it all feels grey.
    -- I use matrix metering most of the time, with spot metering in the rare instance that requires more precise measurement than just tweaking the aperture or shutter up or down a stop or so. Snow or water pictures are a prime example.
    Just so we're clear, I know how to use a camera. I know how to expose properly, and in the past year with my camera, I feel I've figured out its quirks. It takes a lot to drive me to discussion boards, as I usually figure out problems myself. But, since the lingo and strange things of digital photography (Color Space, EXIF data, RAW conversion engines, etc.) confuses me sometimes, I am looking for more human help. I haven't had this problem (or this dramatic of a problem) in the past.
    The RAW images outside of the last couple of months seem fine (maybe having something to do with the fact that I upgraded to 2.1 from the 1.0 software about 6 months ago and am finally getting back to photography during my summer break). And the JPEGs that I am apparently exposing for are fine as well. It's just after Aperture imports the RAW file that I am having these problems.
    Like I said, I want to continue to use RAW. I want it to work like I thought it was working in the past (that is, without major exposure headaches). But I want the image that I thought I was getting. So how do I make Aperture see the same (or nearly the same) image that I am seeing in the JPEG thumbnail? The difference is just too dramatic to pass it off as quirks and be okay with that. And no, at least as the photography part goes, I do not think it's a short between the floor and the camera.

  • Rendering of RAW images in LR5 vs Canon Digital Photo Professional

    Just as a pre-amble, I love LR and perform 90% of image processing with it (rest in PS). I use a Canon EOS 5D MKIII shooting in RAW, running LR5 on Win7. My monitor is properly calibrated.
    Every so often I view a RAW image with Canon DPP mostly to display the AF point. What I am noticing is that the DPP SW renders the image very different from LR and I tried every LR Profile. In my opinion the DPP rendering is sharper, with less noise and a more natural look. My latest example of the difference in image rendering is from images taken with the Canon 200-400 1.4 zoom lens. This difference in image rendering is after RAW import with no images editing on either application. I just wish there would be a LR profile that yields a similar quality image. Does anybody share my experience on this?

    Panagon-1 wrote:
    it would be of no surprise to me if Canon has some advantage with rendering their own proprietary RAW camera output.
    Canon has been working on their Digic raw->rgb engine whilst Adobe works on their process versions & camera profiles. But, more likely any "advantage" is due more to the defaults&compensations, rather than inside knowledge of sensor behavior - just a guess, but one based on experience, even if no specific inside knowledge (about Canon sensors & software algorithms) of my own..
    Panagon-1 wrote:
    because of animal hair, bird feathers, whiskers, etc.
    If picture is sharp already (i.e. sharp lens, in focus, sufficient shutter speed ... ) then you may prefer a lower radius sharpening, as trshaner was saying.
    But, another approach for such wildlife photos is:
    * instead of sharpening everything (even if relying on sharpening mask to some extent), set global sharpening amount to zero (or 1, at first), then sharpen subject by hand (using locals only). Or, set global low and supplement using locals..
    I acknowledge it takes more time, and you may not want to do it to each of 50 shots in a burst, but it allows you to minimize global (luminance) noise reduction (which tends to smooth feather detail in a way which is hard to recover). And of course Lr5 supports local noise reduction, so you can also clean some stuff up locally.
    Also worth noting: local sharpness = -50 (exactly) eliminates all global sharpening (but does not blur, unless you overlap pins). So if you do decide to sharpen globally to some extent, consider cleaning up some parts locally using:
    * sharpness = -50
    * noise reduction = whatever-ya-need.
    Also, if you do apply some luminance noise reduction, consider cranking luminance noise reduction "detail" way up to preserve feather & hair detail (and keep sharpening detail lower on those high-ISO shots, so you don't need as much lum.NR, which produces better results, IMO). Hint: if you drop sharpening detail down and add lum. NR, you may need higher sharpening amount (and/or radius) to keep from being too soft.
    Rob

  • Canon CR2 raw images are forcibly cropped by Camera Raw

    I posted this on the Photoshop Discussion as I did not realise that Camera Raw has its own - sorry folks!
    Camera raw is cropping my cr2 images even after I have removed the crop in DPP (Digital Photo Professional - Canon's own raw editing software). I have many images cropped by a Canon 5D3 as it forces a 16:9 crop when you take a still while in video mode. The rest of the data is in the raw file, but this is not read by Camera Raw which forces the 16:9 crop. I have removed the crops in DPP, and even re-cropped with a different crop, saved the files and used every way I can imagine to get them into PS short of turning them into tiffs. I do not want to save as a tiff, as I really like the tools in PS Raw, especially the exposure tool (I am no great photographer but I have some very special and irreplaceable pics form fieldwork overseas which are ahem errr not quite correctly exposed).
    My ideal worflow is open folder in DPP - star rate the pics I want to work on. crop them (nice to do this in DPP as it is part of the selection process) then get them into Camera Raw without any more effort, then if an image can be tweaked - do it as a Raw, if it needs more work - get it into PS6 as a tiff and go from there. This seems to minimise effort and minimise file space, at the expense of having two different file types.
    Does anyone else work like this, or is there a better way to review 300 similar pics and get the best selected and processed? Has anyone else encounteres this refusal of Camera Raw to ignore the camera's crop? I bleive that there is a plug-in for lightroom, does anyone know a work around for PS  - I have PS6 with raw 7.3.
    Thanks
    Gor

    Oh can I, thanks . I couldn't see a way to open a tiff in ACR - It only opens when I drag a Raw image into ps6, and it has no file>open to allow me to open a tiff.  In fact it is a rather strange piece of software - it doesn't seem to exist on its own (not as part of production suite anyway).
    This would be a work-around for sure if you could tell me how to do it??
    UPDATE
    FOr anyone else with this problem you can force ps6 to open all tiffs in ACR with a setting in preferences in RAW - automatically open all tiffs. It is still a bit of a pain as i dont really want to automatically open them all, but hey!

  • Automatic adjustements to RAW image?

    Hi,
    I am fairly new to using Lightroom and I wondered if someone might be able to help....
    I notice that when i import RAW images  into Lightroom and open them up, they immediately become dull, less vibrant and very different o the in-camera image. I have tried to find whether there is asetting which applied automatic adjustements to the image but have been unsuccessful.  This doesn't seem to happen when i use the Canon RAW processing software. Any ideas?
    Thanks in advance.

    It might be that a preset is being applied to your photos during import.
    Make sure that no auttone is applied. Go >Edit >Preferences >Presets tab and make sure that <Apply auto tone adjustments> is un-checked. See screen shot:
    When you import images into Lr, on the right side in the Import Dialog under <Apply during Import> make sure that <None> is selected. See screen shot:
    Irrespective of that, your image will look different than on your camera display.
    It is sometimes assumed that the image on camera display must be the "correct" image. That is not so. The camera creates a tiny JPG for display that is not representative of the Raw image. Lr gives you a better rendition of your image.
    If it looks flat and dull - that is not a flaw. Contrast and saturation or vibrancy can always and easily be adjusted. In fact, a flat looking image is easier to work with.
    A "crispy" looking image seems "better" at first. But often the contrast and/or the saturation are too high and detail gets lost. This might not be visible on the screen but becomes apparent when the image is printed.
    Aside from that: Lr can show you the image correctly only when your monitor is calibrated.

Maybe you are looking for