Lightroom confused with NEF + JPG pairs

I moved a directory of NEF+JPG files from directory "A" to "B". And then deleted "A". When I did this, directory "A" disappeared from the library, as expected. But something went wrong. Directory "A" on the hard drive (when viewed with Windows Explorer) still exists, with all the NEF files still there. This is good. But Lightroom is now confused about NEF and JPG files.
All my JPGs now say "xxxx.jpg+jpg" for their names, and the NEFs are no longer in any folders in the library (still in the drive when viewed with Windows Explorer). All my changes are now "attached" to the JPGs. I said, fine, I'll just reimport the NEFs from another directory, but the import command tells me that those NEFs are still in the library, and so won't import them. Try as I may, I cannot find the NEFs anywhere in the library (they're not in the missing files folder). I panicked, and did an optimize database, and then a integration check, and backup. (Thinking back, this was probably a very stupid thing to do.)
My question is this. How do I either import the NEFs into LR (I'm willing to re-do the manipulatinos) or attach the NEFs to the JPGs again?
Any help will be greatly appreciated.
Thanks in advance,
Howard.

I have called Adobe about this. I had to re import the folders. The up side was that the files also still had all the edits done to them still. Big pain. Do you have the XMP files? they will also stay with teh files and they all show up again as NEF and JPEG.

Similar Messages

  • Lightroom 3.6 Camera Raw 6.6 - Issues with NEF files

    Hello all,
    I'm sure I'm not the only person with this problem, I'm a Nikon user and when I view NEF files in Lightroom 3, before the images loads completely it looks like it did on my camera but when the loading phase is done the picture darkens and it changes, sometimes darkens, sometimes changes tones.. What is happening here and is there any way around this with NEF files?  I love Lightroom but if I can't work with NEF the way they look on my camera then I'm going to have to make the switch over to Capture NX 2 and I really don't want to....  In addition I have no problems with JPEG files so I know the issue is isolated to NEF files.  I'm also on a Mac with 10.6.7 if that makes any difference.. not sure it does though.
    Please help!!

    This is not just a characteristic of NEF files.  Adobe software and other third party software does not read the in camera settings, instead it applies default settings.  The initial image you see is probably the stored image that was processed by the camera, but it is replaced by the image rendered using the defaults from Lightroom.  The default camera profile is Adobe Standard, which does not match what you get from the camera.  Adobe has generated Camera matching profiles for Nikon and Canon cameras and a few others.  Go to Camera Calibration and select the same profile you have selected in the camera - it will have a name like Camera Standard, Camera Neutral, etc.  If you have other parameters set to nominal in the camera, this will be a close match to the JPG from the camera.  You can set a new default for Lightroom that will use the setting you select and it will use this when any new NEF files are first opened.  If you want the NEF file to open identical to the JPG from the camera then Nikon software is the only option.  If you were using a Canon, then Canon software would be the only option. 

  • Script to automatically make a stack with a RAW+jpg pair of images

    While on my last trip, I accidently setup my camera to take Raw + small jpg. No big deal, that isn't too much memory, so I didn't really worry about it. When I got home, the jpg files were copied to my hard drive along with the raw files. So, I went to delete the jpgs and I realized something. Bridge runs very fast when it's drawing thumbnails and previews of small jpg images. I got to thinking. Wouldn't it be cool to make a script that would take your raw+jpg from the camera and convert each pair into a stack with the jpg on top. This would enable bridge to run much more quickly since it wouldn't need to render all those raw image thumbs and previews.
    Hmmm....now where to start....I looked around at the scripting language for photoshop. since I have written a little bit of javascript, I thought I would start there, but I can't find where the stack property is kept in metadata or the DOM.
    Any ideas of where I might turn from here?

    Version with some changes.<br />Try fix some bug.<br />Try increase speed.<br /><br />If you found some bug or make changes or fix, please post it to this forum.<br /><br />-== [start of script] ==--<br /><br />///////////////////<br />/// Name: Auto stacking files<br />/// Description: This script enable auto stacking files by name<br />/// Author: Tyzhnenko Dmitry<br />/// E-mail: [email protected]<br />/// Version: 0.32<br />///////////////////<br /><br />/*<br />@@@START_XML@@@<br /><?xml version="1.0" encoding="UTF-8"?><br /><ScriptInfo xmlns:dc="http://purl.org/dc/elements/1.1/" xml:lang="en_US"><br />     <dc:title>Auto stacking files</dc:title><br />     <dc:description>This script enable auto stacing files by name function</dc:description><br /></ScriptInfo><br />@@@END_XML@@@<br />*/<br /><br />function AutomaticStackingFiles()<br />{<br />     /**<br />      The context in which this snippet can run; Bridge must be running.<br />      @type String<br />     */<br />     this.requiredContext = "\tAdobe Bridge CS3 must be running.\n\tExecute against Bridge CS3 as the Target.\n";<br />     $.level = 1; // Debugging level<br />     <br />     this.version = "0.32";<br />     this.author = "Tyzhenenko Dmitry";<br />     <br />     /**<br />      The unique identifier for the new menu item command<br />      @type String<br />     */<br />     //this.menuID = "AutoStackFiles";     <br />     this.menuCommandID = "GoAutoStackingFiles";<br /><br />}<br /><br />function RunAutoStacking()<br />{<br />     var doc = app.document;<br />     var thumb = doc.thumbnail;<br />     var vthumb = doc.visibleThumbnails;<br />     var currSort = doc.sorts;<br />     <br /><br />     function StackPhoto()<br />     {<br />          doc.chooseMenuItem('submenu/Stack');<br />          doc.chooseMenuItem('StackGroup');<br />     }<br /><br />     function CollapseStacks()<br />     {<br />          doc.chooseMenuItem('submenu/Stack');<br />          doc.chooseMenuItem('CollapseAllStacks');<br />     }<br /><br />     function getFileExt( t)<br />     {<br />          var dot = t.name.lastIndexOf ('.');<br />          return t.name.substr(dot,t.name.length);<br />     }<br /><br />     function getFileName( t)<br />     {<br />          var dot = t.name.lastIndexOf ('.');<br />          return t.name.substr(0, dot);<br />     }<br /><br />     CollapseStacks();<br />     <br />     var SortObj = {}; <br />     SortObj.name = "name";<br />     SortObj.type = "string";<br />     SortObj.reverse = false;<br />     var SortsArray = [];<br />     SortsArray.push(SortObj);<br />     doc.sorts = SortsArray;<br /><br />     for (var len = 0; len <  vthumb.length; len++ )<br />     {<br />          doc.deselectAll();<br />          doc.select(vthumb[len]);<br />          doc.reveal(vthumb[len]);<br />          for ( var k = len+1; k < vthumb.length; k++ )<br />          {<br />               //alert(k);<br />               if ( getFileName( vthumb[len] ) == getFileName( vthumb[k]) ) <br />                    doc.select(vthumb[k]);<br />               else <br />               {<br />                    if (doc.selectionLength > 1) <br />                         StackPhoto();<br />                    break;<br />               }<br />               if (k == vthumb.length-1)<br />               {<br />                    if (doc.selectionLength > 1)<br />                         StackPhoto();<br />               }<br />                    <br />               //if (doc.selectionLength > 1) <br />               //     StackPhoto();<br />          }<br />          //delete vthumb;<br />          //var <br />          //vthumb = @doc.visibleThumbnails;<br />     }<br /><br />     doc.sorts = currSort;<br />     doc.reveal(doc.visibleThumbnails[0]);<br /><br />     delete currSort;<br />     delete vthumb;<br />     delete thumb;<br />     delete doc;<br />     <br />}<br /><br />AutomaticStackingFiles.prototype.run = function()<br />{<br />     var retval = true;<br />     if(!this.canRun()) {<br />          retval = false;     <br />          return retval;<br />     }<br />     //app.document.chooseMenuItem('submenu/Stack');<br />     var AutoStackCommand = new MenuElement("command", "Auto stacking", "at the beginning of submenu/Stack", );<br />     AutoStackCommand.onSelect = function(m)<br />     {<br />           //alert('start');<br />           RunAutoStacking();     <br />           //alert('stop');<br />     }<br />}<br /><br />AutomaticStackingFiles.prototype.canRun = function()<br />{     <br />     // Must run in Bridge <br />     if(BridgeTalk.appName == "bridge") <br />     {<br />          // Stop the menu element from being added again if the snippet has already run<br />          if(MenuElement.find(this.menuCommandID))<br />          {<br />               $.writeln("ERROR:: Menu element from AutoStackFiles already exists!\nRestart Bridge to run this snippet again.");<br />               return false;<br />          }<br />          return true;<br />     }<br />     // Fail if these preconditions are not met.  <br />     // Bridge must be running,<br />     // The menu must not already exist.<br />     $.writeln("ERROR:: Cannot run AutomaticStackingFiles");<br />     $.writeln(this.requiredContext);<br />     return false;<br />}<br /><br />if(typeof(AutomaticStackingFiles_unitTest) == "undefined") {<br />    new AutomaticStackingFiles().run();<br />}<br /><br />-== [end of script] ==--

  • Wedding photographer - NEF+JPG?

    Still evaluating LR2... questions:
    I shoot RAW (Nikon, NEF, actually often NEF+JPG) for formals, but only JPG for dancing/action shots (since I shoot tons of these images and rarely need anything larger than a partial album page, and the image quality is fine). I've had no trouble importing the mix, but I'm a bit puzzled about exporting the soted and adjusted batch of images... It seems that the RAW image of a NEF+JPG is the only one visible, correct. (Yes, I know I can set the option to import both as two separate images, but that's not really what I want.)
    What I need to end up with is a JPG of each selected image. So what happens if I export the selected set as JPEGs? The NEF files I guess are converted to JPEGs (or does it simply export the associated JPG file?) and what about the JPEG-only files? Are they siomply copied, or are new JPG files created (thus possibly increasing noise)? I can't seem to find this answer anywhere.... any insights would be greatly appreciated!

    Dorin,
    Thank you for your reply. What are the characteristics of said "high quality embedded JPEG" in the RAW files? Can you elaborate? Are you referring to the previews that LR generates and stores in the Lightroom\Preview folder (but thus can only be read by LR)? Or do RAW files from the camera come with a JPEG embedded?
    One reason I would like to have the JPEG out of the camera is that I feel the JPEGs are often pretty good, especially out of my Olympus E-1 and E-3 and Fuji S5 Pro bodies. In fact, unless there are some exposure problems that I need the RAW files for so I can "rescue" them, a lot of times the JPEG engine in my E-3 and S5 Pro can do just as good a job as I can, if not better (unless I spend a bunch of time flogging the pics in LR). And the bonus is I don't have to spend any time editing them!
    As well, I often like to use the JPEGs as reference. They're usually fairly good out of the camera, so before I edit the RAW pics, I like to check out the JPEG to give me an idea of how it should look according to the camera. That reference point allows me to make my adjustments to the RAW file more quickly, as usually it's at least half way to what the image should look like -- much closer than the RAW file is out of the camera, anyways, and almost always better than what the Auto Tone feature gives me.
    So as you can tell, I do value the OoC JPEGs quite highly for a couple reasons. Does my rationale make sense, or is it fundamentally flawed? But more imporantly, is there any way to have them peacefully coexist in one's workflow? If it's not feasible, then that's the way it is, I guess*.
    * - ( but surely, I can't be alone in this, as I recall reading on other forums debates about using RAW vs JPEG. Several of these debates eventually ended with the conclusion of "why not shoot both? Use JPEGs to save time and RAW when quality is critical or when you have exposure problems". Made perfect sense to me at the time...)

  • Help with NEF files... blown out in Camera raw??

    My Nef files look great until I use the magnify tool in bridge or open them in camera raw. Then all of sudden they instantly brighten and some of them look overexposed!! Please help... is there a default setting I need to change?? I'm using the Nikon d700 Adobe CS5.1

    1) if you are doing a raw conversion using Adobe raw converters (ACR/LR) then you shall not be confused w/ embedded JPGs (written by camera's firmware in your raw files) that you might see temporarily while Adobe software renders some inital preview using your default raw conversion settings (you might change those, including default camera profiles = for Nikon cameras Adobe supplies a standard profile and some profiles to emulate OEM settings, exposure correction, etc)
    2) you are are concerned that you in fact overexpose your raws (clipping in raw channels) then just download a free software = http://www.rawdigger.com/ and see the true raw histogramm (not jpeg based histogram that your camera shows), if your raw channels are not clipped then just dial negative expocorrection in ACR/LR and that is it... in most cases it is good to have raw histogram to be as close as possible (and sometimes even clip unimportant parts of the image - specular highlights for example are in many/most/all cases OK when clipped, because there no details for you in them) to clipping - because then you have a good signal to noise ratio for the most important parts of your image...

  • XMP files remain with NEF files in my folder.  Camera Raw suddenly reset leaving my edits gone.  Will XMP files enable me to resume with those lost edits?

    XMP files remain with NEF files in my folder.  Camera Raw suddenly reset leaving my edits gone.  Will XMP files enable me to resume with those lost edits?

    I never tried this, but I'm pretty sure that with DNG files, Lightroom will ignore xmp files, even when you instruct Lightroom to "Read Metadata from File". Lightroom expects all the metadata to be in the DNG file, not in the xmp file.
    Pick flags, as far as I know, are never written to xmp file; nor are they written to DNG files.
    If you're going to make this transfer procedure work, you need to do it by either (a) embedding the metadata in the DNG file and send those back and forth; or (b) use RAW and xmp and then sending the xmp files back and forth (plus I guess you have to transfer the original RAW once to your editor)

  • FAQ: Will Lightroom work with my camera, or Why won't my raw files open?

    What is a raw file?
      A raw file is the unprocessed data that was captured by your camera sensor when you took your picture. The only settings on your camera that apply to this file are aperture, shutter speed, and ISO. This means that any effects you may have applied to the file, such as white balance or black and white, may not appear in Lightroom. Your camera will create a JPEG copy of your raw file with all current settings applied and save that within the raw file for use as a thumbnail by most applications. When you first view a raw file in Lightroom, you will see this thumbnail, then Lightroom will read the raw data and create its own thumbnail, which may have a different appearance.
    How does Lightroom work with raw camera files?
      Lightroom interprets the raw data and makes image information out of it. But every camera has a unique sensor and thus has a unique form of raw file. Even though camera manufactures may use the same file extension each time (e.g. Nikon raw files are always .NEF), each camera model has a different way of storing information. Because of this, we must continually update Lightroom for new cameras. As we add new cameras to the list (over 300 now) we update our published list of supported cameras.
    Will the raw files from my camera work with Lightroom?
      To determine whether your camera is supported by Lightroom, check this list:
    Supported cameras
      Go to Help > Updates to install the latest release. You can also manually download and install Lightroom updates:
    Macintosh
    Windows
    What if I own a previous version of Lightroom?
    Supposing you have a camera that came out after the release of a newer version of Lightroom, so that your version of Elements is no longer recieving updates, you have two basic options:
    Purchase the latest version of Lightroom that supports your camera.
    Use the latest version of the free DNG Converter (for Macintosh or Windows)
    You can convert your files to the universaly compatible DNG format (the files will work with any version of the Lightroom). See In depth : Digital Negative (DNG) for more information.
      For more assistance on DNG:
    Adobe TV - The Advantages of the DNG File Format
    Adobe TV - On Using DNG in Lightroom
    Adobe TV - DNG Enhancements in Lightroom 4
    Can I perform tethered capture from my camera to Lightroom?
      Lightroom has the ability to automatically import images from your camera, as you shoot, life. To learn more about setting up and useing tethered capture, please see Import photos from a tethered camera. This list shows all the cameras that Lightroom supports for tethered shoooting:
    Tethered camera support | Lightroom 4, 3
      Use this document if you run into trouble when performing tethered shooting:
    Troubleshoot tethered capture | Lightroom 4, 3
      For more assistance on Tethered Shooting:
    Adobe TV - Import photos from a tethered camera
    Will Lightroom help me automatically compensate for the image distortion caused by my camera lens?
      The Develop module of Lightroom includes Lens Correction which can read what lens was used from the metadata. With this information it can pick a profile that will reduce distortion caused by the curvature of the lens. For a list of which lenses are supported by which camera bodies, see this list:
    Lens profile support | Lightroom 4, 3
      If your lens is not currently supported, you have a few options:
    Apply the lens correction manually
    Use the Adobe Lens Profile Downloader (Download: Mac, Win) to see if someone else has created a profile your camera and lens
    Use the Adobe Lens Profile Creator (Download: Mac, Win) to make your own profile for your camera and lens.
      For more assistance on Lens Profile Corrections:
    Adobe TV - Lens Correction & Perspective Correction
    Adobe TV - Create Stunning Images
    Adobe TV - Correcting Perspective
    Adobe TV - Apply Lens Corrections
    Julieanne Kost's Blog - Lens Correction Profiles
    Additional resources
       For more information about Adobe Camera Raw, please check these links:
    Troubleshoot Camera Raw
    Why doesn’t my version of Photoshop or Lightroom support my camera?
    In depth: Camera Raw
    Lightroom Jourrnal (developers blog) about Camera Raw releases
    Julieanne Kost's Camera Raw video tutorials
    Adobe Camera Raw turns 10

    Yes, junky thumb drives pour like rain.   Verify same with another or a good thumb drive.
    Whats the format of the USB stick?
    Use Sandisk or other reliable drives.

  • Re-named NEF & jpg files in CS4 Bridge & they turned into "exec" files!?!? SOS

    SOS!!! I just re-named NEF & jpg files in CS4 Bridge & they turned into "exec" files (& the WEDDING GIG images disappeared!) HELP PLEASE, anyone who knows the solution. I'm desperate.

    God bless you!…I tried it with the 1st 2 files, which were NEFs & it worked. BUT I started with Raw & then shot mostly jpg…cannot "see" anything & am clueless as to which are which / any other ideas?

  • Preview very slow with .nef photos

    My preview works well for .jpg but not .nef.
    Open folder, select 'all' right click, open with 'preview'. Very slow & jerky.
    Used to work fine with .nef in Mt. Lion.
    Any ideas?

    Same issue here, and 10.10.2 brings no solution… Haven't you heard yet, Apple is the new Microsoft?!
    Anyway, here a few tips to speed up Preview at least a bit, so one can use it for work again:
    tip1:
    Delete /Library/Preferences/com.apple.windowserver.plist
    Delete ~/Library/Preferences/ByHost/com.apple.windowserver*.plist
    Shutdown OSX
    Startup, immediately press and hold the P and R keys while holding down the option (⌥) and command (⌘) keys before the gray boot screen appears, which resets the PRAM
    tip2:
    Turn off "Smooth Text and Line Art" in the Preferences. Of course, that's really sad, because PDFs then look terrible, but at least they are easier to work with.
    tip3:
    For just viewing, use QuickLook: in the Finder, select the PDF and hit [SPACE]. Strangely, QuickLook isn't affected by the bug.
    Anyway, those workarounds helped me a bit (thanks to those who posted them), but of course it's no proper solution. The last option would be to go back to Mavericks.
    I heard the problem was reported to Apple when Yosemite was in beta, summer 2014. Nothing happened so far. Apple really has to get its act together…

  • How to replace D750 DNGs with NEFs after 5.7 release?

    Now that LR5.7 has been released, I no longer need the DNGs that are packed with NEFs in them. I know how to run the DNG converter to unpack the NEFs, but how do I get LR to recognize the new NEF as my original files without losing all the edit steps that I've done to the files?

    Most people understand when you say "you can't..", that you mean "I don't know of a way..", whether it be something in Lr native you're not aware, or there is a plugin you're not aware of. I am certainly not aware of everything that is possible, in native Lightroom as well as via plugins. I even forget what some of my own plugins can do!
    Cheers and no prob,
    Rob

  • Problem with NEF files from Nikon D4

    Hi everyone. I find a problem with nef files from my Nikon D4. When files are open in ViewNX2 (free viewer software from Nikon) they are perfect, as shooted... but in ACR they are very different... I use LR4 or CS5 with ACR 6.7 and the difference seems to be linked at D-Lighting function. My impression is that ACR dont read this option and picture are very very dark that original shootings. Anyone have this problem?

    This question used to be answered in the FAQ before they revised it.  So, here we go again.  ViewNX is capable of reading all of the in-camera settings such as, camera profile, saturation, sharpness and other settings.  It is capable of doing this because it is Nikon Software, and they have the ability to program it to read the settings from their raw images.  Lightroom does not read those settings from Nikon cameras or any other brand of camera.  Part of the reason is that different camera makers store those settings differently.
    When I first started using Lightroom I adjusted one of my images that represented what I normally shoot until it looked the way I wanted it.  Then I saved those adjustments as my default settings for the camera.  From that point onward, whenever I import images those settings are automatically applied, and it takes care of the vast majority of my images.  Of course, I still have to make individual adjustments.  But my default settings greatly reduce the amount of how they work that I have to do.
    Active D-lighting is is one of those features that Lightroom does not recognize.  You would be well advised not to use it, or else create a preset to simulate its effect.  It will provide no benefit to your Lightroom work.
    This is a fundamental difference with Lightroom, and something that must be understood and implemented if you are going to use the program effectively.
    I realize this question was asked in the ACR forum and I referenced Lightroom throughout.  But the principle is the same, and the recommended procedure is the same.

  • Can't associate bridge cs5 with nef raw files

    I have been trying to get win 7 to associate the bridge CS5 executable with NEF files.
    It worked fine for CS4 and yes, i am going to file associations and choosing the bridge.exe for cs5 under x86 programs. It just ignores the choice and won't put it in the recommended program area.
    I tried from the exploreer and control panel.
    If i double click the bridge.esxe, it opens properly. it's just the auto associations which don't work.
    Any suggestions?
    thx

    No it can't. It is possible to do but the process requires a using a fair bit of code to create a logo/watermark then using a cutom script to write the logo/watermark, the results are not good unless a background to the logo is used. It does take a fair bit of time to do each one though, so it's not something I would persue or spend time developing.
    Here's one example, cr2 to jpg and text added, done in Bridge only!

  • Lightroom problems opening NEF files

    I used Lighroom 2 and CS4 with no problems for a very long time and then decided to upgrade to Lightroom 3 and CS5 which was a big mistake.
    I have had so many problems and don't know what to do.
    Lightroom has trouble opening NEF files that I would like to edit in photoshop. I have spent so much time with Adobe Tech support with no improvement, tonight a senior tech spent three hours working with the program and cs5 and I still have problems. They make changes, things seem to be fine and when I restart the computer it goes back to the same issue. Tomorrow another tech will call but the days are going by and I'm not getting any work done. A program that is supposed to improve my workflow is turning into a major inconvenience.
    Tonight the program seemed to be working fine for a while, I edited several images and just realized now that they are all corrupted and aren't usable.
    In the past few days we trashed lightroom preferences, cs5 preferences, made sure Lightroom and Photoshop and camera RAW are updated. One night I uninstalled cs5 and installed a fresh copy (didn't install any plug-ins to make suer they are not the ones causing the problem), it was working great then I quit both programs and restarted the computer and back to square one, not being able to open a NEF file.
    If the Adobe technician cannot solve the issue what are my options, should I go back to Lightroom2 or should I try Lightroom 3 with CS4?
    Thanks,
    Barbara

    Barbara,
    The purpose behind setting up a test catalog and new user is to try to find out where things are going wrong.  If you do end up needing a new catalog, there are ways to keep your past work.  You can import from your old catalog into your new catalog.  You can save many of the settings directly into your images (JPEGs or TIFFs) or sidecars (raw files) by using Metadata>Save Metadata to File.  If you do it the second way, you will lose things such as collections that cannot be saved.  But before worrying about that, try the new user and we will work from there.
    You may already know this, but no matter what you do, when you retouch an image in PS, you will be creating a new file.  LR does not modify the originals, so a new TIFF will have to be created to save the retouched image.  There is no way to save the retouching to a raw file.
    As far as the number of catalogs to create, most people will be best served by having only one catalog.  If you have more than one, you have to be organized and careful not to mix them up.  We have seen a lot of problems caused by people accidently importing images into the wrong catalog and then getting concerned when their images disappeared. Also, it is difficult to search for images when they are in multiple catalogs.
    I do use multiple catalogs.  I have to be sure I don't show the wrong images at the wrong times.  I do boudoir and glamour photography that is private and I have to be sure I don't show the images accidently to other clients.  I set up a separate folder for each job and keep the catalog and images in that folder.  After about a year, I burn a DVD of the images and catalog and archive it.  I rarely have to return to a client's file after a year and never have to search across client files.  I also have one large catalog for stock and personal work.  I do need to search across all of those images.  Until you are well-versed and comfortable with using LR, I would recommend keeping it to one catalog.  You can easily split it up later if needed.
    Since I have multiple catalogs I keep each catalog with its images for the sake of organization.  My stock images (and catalog) are on an external drive.  I have another external drive for client work.  Each client job has a separate folder on that drive.  The images and catalog for each job is kept in their job folder.
    John
    John G. Blair Studio
    Occidental, California

  • Why such poor quality saturation and contrast with NEFs?

    Having used Lightroom since the beginning, I'm at my wits end.
    Ever since Lightroom 1, I've noticed that ACR does a really -really, bad job handeling NEFs when you push contrast and saturation, especially in regards to certain colors (reds, yellows, and blues).
    I thought for a long time it was my side, originally using a consumer DSLR (D50), but it affects every NEF I've ever imported, from any Nikon body up to D4.
    The saturation gets chunky with little effort (even after attempting to correct via the Calibration panel), the same when pushing contrast. Not pushing it beyond the files' limits, just a simple s-curve.
    When importing other RAW formats, this is less often the case.
    It's really frustrating to be able to rely on Lightroom doing and adequate job 75% of the time, and it makes me look bad in front of clients.
    Has/ does anyone else run into this? Does anyone have any ideas, or tips as to avoiding this?
    I really hate the UI of C1, but since it has started implementing cataloging I am getting more and more enticed to switch over completely, as even when I push things waaay too contrasty or overly saturated the results are still miles better.
    I'm an unabashed Adobe fanboy with fond memories of the introduction of Levels (Oooooo) back in the day, but I'm feeling I've been pushed to a point where I have to default to whatever program does a better job handeling RAW info, and ACR is not cutting it at a professional level.

    Well, I don't know how to explain it any better, I feel I put it pretty straight forward, however here's an example from a small lookbook. The red is not accurate, everything else is.
    The only thing I've ever come up with is possibly some 'Out of Gamut Warning' option that I haven't found to disable, twenty_one. However, no, I do know Lightroom VERY well, just not 100%, maybe 95%. When Soft proofing for monitor, all colors in the example are within gamut in sRGB, AdobeRGB, and my calibrated monitor color space.
    I've almost exclusively run into this with NEFs, I've used Lightroom with Canon, PhaseOne backs, Leaf backs, Fujis, and more. Oh, and I am a pro, and have worked a wide range of clients from Harper's, Elle, and BEBE, to RED, Playboy and more -not to toot my horn, but to establish I'm not a green.
    I'm on Lightroom 5, current build.
    Typically I stay with the Adobe Standard Profile or Portrait, but none seem to help this particular issue.
    Not sure what sort of NEFs Nikon produced in '76, but I to have been with Adobe since Photoshop 2. I'm viewing on a calibrated monitor in good viewing conditions. I don't print, this is most commonly an issue with lookbooks and catalogs when they need perfect color, the issue remains when viewed on other monitors. I've also tested images on my studio's Eizo CG276 and run into nealry exactly the same results (nearly in that there are pixels of difference, however it's a different size than my normal editing monitor).

  • D300 NEF & JPG in LR

    Just got a D300 and was playing around, taking shots with NEF and JPG fine set. When I import in LR, all I see is the NEF file, not the JPG version. When I look in the folder that contains the images, both NEF and JPG versions are there. How do I get to look at the JPG version in LR? Thanks.

    In the main Preference Dialog under Import check the third item, 'Treat Jpeg files next to raw files as Separate photos.
    That should do it, though you will need do do an import or Synchronize on the Folders.
    Don
    Don Ricklin, MacBook 2Ghz Duo 2 Core running 10.5.1 & Win XP, Pentax *ist D See LR Links list at http://donricklin.blogspot.com for related sites.

Maybe you are looking for