Lightroom 5 Export TIFF tonal change, even without making changes in Photoshop

     Hi there,
I seem to experience a mysterious issue when Lightroom creates an Edit Tiff for external editing. I have this issue only with one picture it seems. I tried to replicate it with another, but it doessn't happen.
So here's what happens. I already had an Edit.tif of a DNG. Then I noticed I wanted to do some final retouching in Photoshop with the healing brush, but I also did some minor adjustments in Lightroom on the Edit.tiff, so I decided to create an Edit-Edit.tif.
Then when I went back to Lightroom, I noticed the Edit-Edit.tif was all of a sudden lighter in the shadows than my Edit.tif.
I tried some trial and error investigation myself, to replicate the issue. I couldn't replicate it with other pictures. But when I tried to do the same thing again, except this time no Photoshop editing to the Edit-Edit.tif (so Photoshop didn't ask me to save), same thing happened. So at least I found out it doesn't have anything to do with Photoshop.
Anyone any idea what this could be? I would greatly appreciate any help! Thanks in advance!
Kind regards,
Dennis

Problem is solved. It turns out, it probably has to do with the interpolation mechanism of Lightroom displaying dark area's with color noise a litte different.
Thanks anyway for reading!

Similar Messages

  • Premiere Pro Won't Export a Stop Motion Video Without Making it a Complete Mess

    I'm having the problem I described in the title.  I can't fix it on my own.

    OK, so what codec are you using when you export?  Does it match the sequence settings?
    It might be a problem with Windows Media Player - try opening the file in a different player (like quicktime) to rule that out.
    Also, what is the image format of the stills in the sequence?  Sometimes Premiere doesn't like jpegs for some reason.
    Finally, there are alternatives - you could use Photoshop or After Effects instead.

  • Lightroom CC exports Jpgs in wrong orientation ONLY when Overwriting WITHOUT WARNING

    This is the first time I post so please bare with me, I will try to explain as much as I can because it is an specific issue.
    The computer I have at work uses Windows 7 pro (Brand New Computer). I import pictures from a network drive, manipulate the pictures and then save them to the same drive. When I see the pictures in the folder browser on windows the pictures have a landscape orientation (even though they should be portraits because they are head shots). Once I import those pictures to LR they appear with the right orientation (portrait), so I play with the pictures and export them to a JPG file. The issue I'm having is when I export with the setting "Overwrite WITHOUT WARNING", I see the picture in the file explorer (Windows) and I can see all the changes I made, but with the old picture's orientation (the wrong one, Landscape) . However, If I choose to create a new file (not overwriting) it will have the orientation I viewed in LR. (The correct one, portrait).  Anyone knows how to export overwriting with the orientation I was seeing in LR?
    Thanks,
    //UPDATE: Also, I just noticed cropping is NOT working when exporting with the same setting "Overwrite WITHOUT WARNING". I had to create new files on a folder and the move and replace in Windows File Browser.

    Yes I have been trying to use my main catalogue, not the back ups - I thought the main catalogue was updated in synch with the latest back up - the reason you can fall back on a back up if all goes pear-shaped. .
    I have managed to resolve the issue as follows:
    I accessed an external hard drive (bootable back up of main computer) and the main Lightroom catalogue. Upon launching Lightroom it gave me the option to use the last saved back up Catalogue and as the default one. This workaround didn't work the same on my main computer as recent image imports and work done were missing.
    I had to delete the main catalogue on my main computer and drag the one from the external back up HD to rectify the situation.
    I have no idea why this has occurred as all I did on my main computer was delete 10 redundant back up folders after which Lightroom failed to launch citing one of the oldest back ups as missing.
    I wonder why Lightroom saved the most recent back-up (upon closing Lightroom) in a Zip folder only? - not noticed this behaviour before.

  • Issue Exporting TIFF Files in Lightroom 3

    When exporting files from Lightroom in a TIFF Format Lightroom is applying specific dimensions to my photos. How do I make this stop so my files maintain the original image size?
    For example. 
    Original Photo - 4256 x 2832, 10.8MB .NEF File shot on D700
    Exported using TIFF Format, No Compression, Pro Photo RGB Colour Space and 16 bit depth. No changes to any part of the original file.
    New exported file - 640 x 426, 1.6MB .TIF File
    Normally I would expect a 16bit TIF export to become a larger file (more MB) yet maintain the original 4256 x 2832 image size.
    This issue is happening for all my images. How can I solve this?

    What have you got selected in this box?

  • ADF Task Flow Binding - Refresh ifNeeded being invoked even WITHOUT any Parameter change

    Using JDeveloper 11.1.1.6.0
    Issue: Task Flow Binding property "refresh = ifNeeded" seems to be triggered even without the mutation of the input parameter.
    As per definition, "ifNeeded: refresh the ADF Region if the value of a task flow binding parameter changes." (Reference: 17.5 Refreshing an ADF Region)
    Now for the setup which reproduces the issue.
    I'll focus at the fragment bounded task flow level and will skip the jspx side.
    taskflow: main-flow.xml
    contains a single fragment mainFgmt.jsff
    has a managed bean defined SampleBean.java as pageFlow scope.
    taskflow: sub-flow.xml
    contains a single fragment subFgmt.jsff
    has an inputParameter SampleBean.java (because it is an input parameter, by default it will be at pageFlow scope)
    !important - has a nested taskflow (task flow call as defined in the component pallete) called inner-flow (see below)
    the nested taskflow is the default activity
    the nested taskflow has an outcome pointing to subFgmt where outcome = "return"
    taskflow: inner-flow.xml
    contains a single fragment called stop.jsff
    has a return activity without outcome = "return"
    stop.jsff has a navigation pointing to the outcome.
    Finally mainFgmt.jsff has a task flow binding (pageDef)
    with id = "sub-flow.xml"
    refresh = "ifNeeded"
    parameter SampleBean being submitted as sub-flow's input parameter. (id=sampleBean, value=#{pageFlowScope.mainSampleBean})
    Assume that code compiles.
    In this scenario where the only tricky condition is the inner nesting (defined by !important), when the inner nesting decides to invoke its outcome to visit sub-flow's fragment, mainFgmt is restarting its taskflow which makes sub-flow start over again.
    Another way of saying it is, if sub-flow starts a nested activity and that nested activity exits out to utilize sub-flow's view. The high level definition which is mainFgmt's refresh ifNeeded is restarting sub-flow.
    In the above example if you notice, the bean (SampleBean) is not really being utilized except that it is completing the purpose of refresh=ifNeeded. This scenario is only to simplify the setup - in practical use this bean will be mutated to be utilized as a refresh mechanism.
    Now interestingly, if I change the pattern a bit then the issue will not happen:
    Don't use the nested taskflow (inner-flow) as the default activity, let a fragment of sub-flow hold the initial view.
    Navigate to the nested flow.
    Exit nested flow.
    Everything works.
    Now in this scenario, it seems like the sub-flow needs to have a view established first for it to be properly be used.
    So my questions are as follows:
    Can I consider the behavior of the refresh=ifNeeded as a bug in this usecase?
    Would it be better to utilize a different way of refreshing (maybe combination of refresh condition) to get around the issue?
    Is the use of the task flow as defined logical or does it cross any boundary or best practice that might be causing this behavior?

    Hi,
    actually you lost me in your description due to complexity. I lived under assumption that sub-flow already is a region on a view in main flow, but then you sad that
    "!important - has a nested taskflow (task flow call as defined in the component pallete) called inner-flow (see below)"
    which then confused me as to I have no idea if inner flow now is the second level nesting or first level nesting (should be second level nesting). If sub-flow is a region then having "has an inputParameter SampleBean.java (because it is an input parameter, by default it will be at pageFlow scope)"  is an unnecessary broad scope because the region wont live longer than view scope.
    Anyway, it seems that a region refresh is triggered by the lifecycle involved, which can be by design or a bug. I suggest you file a Service Request with support and provide a test case as purely from the description, its hard to parse and understand what is going on.
    Frank

  • Export tiff without RichTIFFIPTC tags

    When exporting tiff images I get an error opening them in my custom ImageMagick extension.
    wrong data type 7 for "RichTIFFIPTC"; tag ignored
    Though it says the tag is ignored, the file fails to open.
    When I take those tiffs and resave them as tiffs in GIMP they do not error and open fine.
    Is there a way to save tiffs from photoshop without these tags?

    Both of the scripts in that thread do not work. Image Processor will strip only for a jpg. I need to save as TIFF.
    The other picture processor just doesn't seem to work "PicProcessor is undefined" line 8
    do you know of any other scripts that may accomplish this?

  • Export window format changed, don't know why

    You know aperture is a love/hate relationship. What do I love? I became an advanced user fast, it's intuitive, but the bugs are just maddening and apple has never responded even once to my countless bug and crash reports. Apple has strayed so far from computing as it's central focus... the impression I get is they just don't care about my bug problems or if I stay an apple customer after owning that little baby Duo laptop, PowerPC, ibook and now MacBook Pro. I think that's sad. Just keep pushing the phones and ipods- Steve, and don't worry about me. I'll eventually just go away. That said, the format of the export window changed to first line: export preset, 2nd line: Subfolder Format, 3rd: "Grayed out" customer subfolder name, 4th: Name Format, 5th: Custom Name, 6th: File Name Example. To my knowledge, this new export window format changed without any action on my part. I don't like it because I can no longer just export it to the desk top without it being automatically put in a folder. The old export window format just had an option for tiff, jpg, psd and a name to type in and where it was heading. How do you get back this old export window format? This is baffling like the disappearing library in the trial version every time you shut down and restarted.

    Addressing your final remarks, I don’t see any problem. First: have your current Preset -> Image Export set to what you want in terms of JPEG or PSD etc. Second select the image(s) you want to Export. Select something like File -> Export -> Versions (or whatever you want). The Export panel defaults to the Desktop, and the images will be placed there - no folder is required.
    Maybe I’ve missed your point, but I don’t see any problem.

  • How do I export 72ppi jpegs from InDesign without losing quality?

    I need to export indesign files that I design to 72ppi for web without losing any quality (or as minimal as possible). Countless times I have tried different methods, but alwasy manage to create a workaround, whether it be good quality, or just readable text. ITs really the small text I have the problem with. I explain in the below video my problem in further detail. But basically, I have tried many things such as pasted from indesign to photoshop, exporting to 300ppi jpeg and resizing in photoshop, exporting to 72ppi jpeg and viewing (not good at all), exporting as PDF, opening in photoshop ticking anti alias and inputting my dimensions... how can I get this to work?? Someone please help.. I have battled this problem for to long and my boss is getting annoyed with it. We need to fix this.
    Many people say to export to PDF and then open in photoshop and save as a jpeg from there.. but how can i export a PDF to 72ppi?? Please Adobe fix this issue in future editions of InDesign. Thanks in advance to anyone who can help
    Here is a link to the video if yu can't view it below: http://www.youtube.com/watch?v=0uqsGnhT3gY&feature=youtu.be

    bec-white wrote:
    Many people say to export to PDF and then open in photoshop and save as a jpeg from there.. but how can i export a PDF to 72ppi??
    You have it backwards. You export a PDF, and when you open it in Photoshop, that's when you pick the resolution. Any text in the PDF will likely be vector data, and it will be changed into bitmap data at the resolution you choose. I'll give you an example:
    I placed a 300ppi image (5.7MB Photoshop tiff) into an InDesign page with three captions (12pt, 9pt and 6pt). I exported the page as two different PDFs. One was set to High Quality Print (a1) and the other to Smallest File Size (a2). A1 came in at 446KB and a2 came in at 37KB. When opened in Photoshop, I picked 72ppi as the resolution, flattened and saved as an RGB Jpeg without color profile and quality setting of 12.
    The a1 jpeg was 180kb in size and a2 was 156kb, so not too far apart, considering the difference in file size between the PDF versions. If you open the jpegs in Photoshop, you will see that the size of the letter F at the beginning of the 12pt caption is nine pixels high in each, so if the problem you are having is that small text isn't readable, maybe the text is just too small to be readable at 72ppi.

  • Is the MASTER_IDOC_DISTRIBUTE FM called even without a Custo Distri. Model.

    Hi all
    In have a question dealing with ALE.
    I am trying to send a BOM Change and create IDoc to a XI system.
    My question is :
    Is the MASTER_IDOC_DISTRIBUTE FM called even without a Customer Distribution Model?
    Or to test my scenario do I HAVE to create a CDM, using BD64.
    Please advise.
    specific answers will be appriciated.

    Hi,
    It is required to create a model view..otherwise who is distributing the message to whom can't be rocognised..Hence it is required..
    check the sample code ..
    *& Report ZZ_Program_To_Create_Idoc
    report zz_program_to_create_idoc .
    tables: ekko,ekpo.
    selection-screen skip 3.
    selection-screen begin of block b1 with frame title titl.
    selection-screen skip.
    select-options s_ebeln for ekko-ebeln.
    selection-screen skip.
    selection-screen end of block b1.
    data: header_segment_name like edidd-segnam value 'Z1EKKO',
    item_segment_name like edidd-segnam value 'Z1EKPO',
    idoc_name like edidc-idoctp value 'Z19838IDOC1'.
    data: header_segment_data like z1ekko,
    item_segment_data like z1ekpo.
    data: control_record like edidc.
    data: messagetyp like edmsg-msgtyp value 'ZZ9838MESG1'.
    data: i_communication like edidc occurs 0 with header line,
    i_data like edidd occurs 0 with header line.
    data: begin of i_ekko occurs 0,
    ebeln like ekko-ebeln,
    aedat like ekko-aedat,
    bukrs like ekko-bukrs,
    bsart like ekko-bsart,
    lifnr like ekko-lifnr,
    end of i_ekko.
    data: begin of i_ekpo occurs 0,
    ebelp like ekpo-ebelp,
    matnr like ekpo-matnr,
    menge like ekpo-menge,
    meins like ekpo-meins,
    netpr like ekpo-netpr,
    end of i_ekpo.
    start-of-selection.
    select ebeln aedat bukrs bsart lifnr from ekko
    into table i_ekko where ebeln in s_ebeln.
    select ebelp
    matnr
    menge
    meins
    netpr
    from ekpo
    into table i_ekpo
    where ebeln in s_ebeln.
    control_record-mestyp = messagetyp.
    control_record-rcvprt = 'LS'.
    control_record-idoctp = idoc_name.
    control_record-rcvprn = '0MART800'.
    loop at i_ekko.
    header_segment_data-ebeln = i_ekko-ebeln.
    header_segment_data-aedat = i_ekko-aedat.
    header_segment_data-bukrs = i_ekko-bukrs.
    header_segment_data-bsart = i_ekko-bsart.
    header_segment_data-lifnr = i_ekko-lifnr.
    i_data-segnam = header_segment_name.
    i_data-sdata = header_segment_data.
    append i_data.
    select ebelp
    matnr
    menge
    meins
    netpr
    from ekpo
    into table i_ekpo
    where ebeln = i_ekko-ebeln.
    loop at i_ekpo.
    item_segment_data-ebelp = i_ekpo-ebelp.
    item_segment_data-matnr = i_ekpo-matnr.
    item_segment_data-menge = i_ekpo-menge.
    item_segment_data-meins = i_ekpo-meins.
    item_segment_data-netpr = i_ekpo-netpr.
    i_data-segnam = item_segment_name.
    i_data-sdata = item_segment_data.
    append i_data.
    endloop.
    clear i_ekpo.
    refresh i_ekpo.
    endloop.
    call function 'MASTER_IDOC_DISTRIBUTE'
    exporting
    master_idoc_control = control_record
    OBJ_TYPE = ''
    CHNUM = ''
    tables
    communication_idoc_control = i_communication
    master_idoc_data = i_data
    exceptions
    error_in_idoc_control = 1
    error_writing_idoc_status = 2
    error_in_idoc_data = 3
    sending_logical_system_unknown = 4
    others = 5
    if sy-subrc <> 0.
    message id sy-msgid type sy-msgty number sy-msgno
    with sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
    else.
    loop at i_communication.
    write: 'IDOC GENERATED', i_communication-docnum.
    endloop.
    commit work.
    endif.
    initialization.
    titl = 'ENTER THE PURCHASE ORDER NUMBER'.
    reward  if helpful
    Regards,
    Nagaraj

  • Exporting TIFF with Pages

    Hi everyone. I'm a stranger here and need your help.
    I got a huge problem when I tried to export TIFF images with Pages.
    I use Pages to create documents or issues and export them into TIFF, then send them to printers. Everything is OK with Lion. But since I updated to Mountain Lion, I couldn't do that anymore. When I choose Print/Save PDF to folder as TIFF, I got a warning saying "The action “Render PDF Pages as Images” encountered an error." I've searched on the Internet and got some solutions but they didn't work. I couldn't find any workflows in Library/PDF Services except "Save PDF to Web Receipts Folder" and "Mail PDF" which I don't use. Again, with Lion, I can find those workflows, change the rules or create a new one. But now, with MT, in two Library folders, I can't find those workflows. Oddly enough, they appear on the PDF menu in Pages.
    I can only use Pages to create things, currently I just can't finish my work. I'm very nervous.
    Thank you all!(I'm Chinese, so maybe there're something wrong in that pragraph, SORRY!!)

    The pixels are not the actual measure of quality.
    It is true you need 300dpi or 120lpc for quality output, but OSX may be downgrading the resolution of all or parts of the page and all you are doing is uping the resolution from the lower OSX output.
    More pixels, same information does not improve the quality.
    Are your actual photos in the layout 300dpi images at the size they are used? If so, without any transparency they should stay that resolution in the pdf and final output.
    A pdf file opened in Preview and saved as a tiff allows you to set the resolution anyway. Make sure it is the same as in Pages any change will blur/degrade the images.
    Text should be at a much higher resolution to be sharp (at least 800dpi preferably 1200), and best left as vector graphics in a pdf file.
    Peter

  • When I i open a picture from my Documents it automatically opens in Photoshop.  I want it to open in Lightroom. How do I change this preference?

    When I i open a picture from my Documents it automatically opens in Photoshop.  I want it to open in Lightroom. How do I change this preference?

    You cannot open an image with LR as you would with Photoshop , or Elements. (or a word document, etc)
    The Lightroom program can only open "Catalog" files  (*.LRCAT)   Opening a .LRCAT file will automatically open Lightroom.
    To edit images in LR you must first open the program, then IMPORT the image into the Catalog database (only ever once), then you select the preview thumbnail and go to the Develop module ( press "D")
    Your edits in the Develop module will show on the preview in the library grid.
    Your original image file is not altered, so will not look any different in File Explorer or Finder.
    To get an image file with your Develop edits applied, you must "Export" a derivative file in JPG or TIFF format.

  • Lightroom 6.1 TIFF metadata issue

    I work in Adobe Lightroom to process photos and move them to MediaBin (4.6) to catalog and metatag; this is what my company uses for its photo library. Last week Adobe creative cloud prompted me to upgrade Lightroom; I was using 5.7, and the newest version is 6.1. In doing so, the captions and copyright information that I write in Lightroom are no longer showing up when they come in to MediaBin.
    At first I thought the metadata was getting stripped following being exported from Lightroom (exported as TIFFs), but when looking at the files in photoshop, I can see all of the metadata is present. I then began a series of tests to try and figure this out.
    I first moved a previously exported TIFF file from the previous version of Lightroom into MediaBin, and I could see the data that was embedded. MediaBin was working as it should.
    Next, I took a file exported as a TIFF from the new Lightroom and moved it into MediaBin. I could not see the metadata, as expected. Then I downloaded it from MediaBin- as I would do to fulfill a photo request- and opened it in Photoshop. I was surprised- all the metadata was there! For some reason, MediaBin just couldn’t see it.
    Finally, on a lark, I exported a file from the new Lightroom, but this time made it into a JPEG. When I moved this into MediaBin, I could see the metadata! I tried this with other file formats- DNG, PSD- and only the TIFF files show up minus their metadata.
    What could cause this to happen, and only in TIFF form? I am under the impression that Metadata is just simple text information attached to a file, but I am confused that only in TIFF form do we have an issue.
    Thanks!

    It appears that this is caused by the same problem described here: Lightroom CC: JPEG format tripping up other programs. JPEGs and TIFFs use the same layout of metadata, and I confirmed that your TIFF has the same atypical layout as LR-produced JPEGs.
    The issue is not that LR has a "bug" -- the TIFFs and JPEGs it produces strictly conform to industry standards.  Rather, it's that there are many programs out there, evidently including HP MediaBin, that are buggy and don't conform to the standards and get tripped up by the atypical way that LR writes its metadata.  Of course, Adobe can't change all such non-conforming programs, so LR users would very much prefer that LR go back to using a more typical layout of metadata.
    Please add your vote and opinion (with details) to the bug report linked above.  The more people complain, especially professional and commercial users, the more likely Adobe will prioritize a fix.

  • Exporting tiff to jpeg - loss of light

    Hello,
    Since a couple of days when I export tiff files to jpeg the exported image looks darker. If I reimport it the histogram is evidently changed.
    It looks like something messed up in preferences but I didn't make any changes (at least I didn't do it purposely).
    I upgraded to the 4.4 version after this happened but nothing changed.
    What can I do?
    Thanks for your help,
    Andrea

    I don’t see much difference in the side-by-side thumbnails.  The JPG’s histogram (right one) has a little more black bunched up on the lefthand end and the histogram is vertically scaled to make that higher peak fit so the entire rest of the histogram is shorter, but the entire JPG’s histogram is not shifted left (toward the dark end) very much at all.  Specifically there is a red peak in between the f/11 and 5.0sec indications on both and the green peak is above the 10mm in both cases.  Converting to sRGB will clip things to fit within the sRGB gamut so some difference is expected, I’m just not seeing very much.  Are you seeing more of a difference in Finder/Preview than with the re-imported JPG in LR?
    You could try exporting your TIF as a ProPhotoRGB JPG and re-import that to compare histograms, since LR’s internal workspace is a wide colorspace like ProPhotoRGB is.
    If you think you have accidentally changed something in your LR preferences, you can exit LR and delete the preferences file (or move it somewhere) then restart LR and let it rebuild a new one.  Before doing this you might want to review your LR preferences in case there’s something important that needs set back.
    http://helpx.adobe.com/lightroom/kb/preference-file-locations-lightroom-4.html

  • Problem exporting metadata after changing capture time

    Hello, I've an odd problem with Lightroom (both 1.3 and 1.4).
    I've all my digital camera's photos organised with Lightroom. There was no problem until I tried to change some photo's capture time.
    In the beginning, the capture time shown by Windows' explorer matched with the one in Lightroom.
    But when I changed some photo's capture time, and then saved the new metadata information to the file... the capture time shown by explorer was two hours later than the hour in Lightroom... it's making my crazy.
    In addition I detected some things:
    - If I told Lightroom to read the file's metadata the issue stayed: the computer showing, for example, 14:00, and Lightroom 12:00.
    - If I exported a photo (Lightroom 12:00) the new file also shows 14:00.
    First, I thought it could be a problem caused by the timezone (GMT+1) and the Summer's time in Europe (I live in Spain). (It makes 2 hours...).
    But the big problem arrived when I discovered that, If I add a tag to the photos, the archive in the computer changes [I've marked that metadata is written automatically]... ¡and shows the correct time! So, it seems that, each time I change a photo's time, I'll need to add and then remove a tag...
    Does it have any sense?
    I would be very happy if someone could help me. Thank you very much. And sorry for my english.

    I'm coming completely crazy...
    without changing again the capture time (I won't use that feature again!) now it happens that some of my photos (it seems that they are the last hundreds photos i've taken) show an incorrect time in Lightroom, now one houre more than the real time.
    The time in Lightroom is incorrect, but Windows' file shows a correct time. I've done nothing unusual...
    What should I do? Stop using Lightroom? I liked it...

  • Tonal change between develop and library module

    After having applied some changes in the develop module when I switch back to the library module I am experiencing a sever foreground tonal change? I can add that the foreground in this particular photo had a grad filter applied. The tone shifts from a cool blue to a purple? Shooting with a nikon d5100 with ADL turned off as per other similar problems brought up in this forum. Which by the way I still experience but have learned to live with is that after import of RAW picture looks good for about a second then exposure changes.

    dennis4g1 wrote:
    After having applied some changes in the develop module when I switch back to the library module I am experiencing a sever foreground tonal change? I can add that the foreground in this particular photo had a grad filter applied. The tone shifts from a cool blue to a purple?
    Are you using a calibrated/profiled monitor?  In Develop module, LR displays in ProPhoto colour space, in Library module it's Adobe RGB.  If the monitor doesn't have a proper profile there could be differences in view between Develop and Library.  However I would have thought LR would default to assuming monitors behave like sRGB if there's no profile (or no colour space info in the profile). 
    dennis4g1 wrote:
    ...Which by the way I still experience but have learned to live with is that after import of RAW picture looks good for about a second then exposure changes.
    The usual cause for that is that Adobe can't read Nikon proprietary metadata such as Picture control settings.  If you shoot with the Nikon Picture Control setting (Standard, Portrait or whatever) at default settings, and if you use the corresponding profile in Lightroom's "Camera Calibration" panel (Camera Standard, Camera Portrait etc) then the appearance should be very close to the out-of-camera jpeg preview appearance. 

Maybe you are looking for