Will LR 5.3 read Nikon picture controls applied to RAW files in-camera?

I've never used picture controls on my D4 because my understanding was that, even though they're embedded in RAW files in-camera, only Nikon software will read the data. Can anyone verify this condition for me? If my LR software will read these settings, then I would start experimenting a bit!

As Andrew said, Lightroom won't read Nikon picture controls, so if you want similar picture style as shot, you need to either:
* manually select camera emulation profile (you can make presets or defaults as you prefer) - see camera calibration section.
* use a plugin like ISO Detailer to select camera emulation profile automatically based on camera setting.
To be clear: *any* software can read any metadata in a NEF (or NRW) that it wants to (there is no legal or technical reason that is prohibitive). Still, it is proprietary, which means "subject to change without notice", which means you have to change your software if Nikon decides to change proprietary metadata around. In practice that almost NEVER happens, since it's defined by camera firmware which, once debugged, isn't "enhanced". (right: they could do a newer model differently, but that doesn't affect the code which supports older models).
Rob

Similar Messages

A3 reading Nikon Picture Controls

Research on the internet suggests that only Nikon conversion software will read Picture Control settings in Nikons. I had trouble telling the difference between diferent Controls in test shots I did with the d7000. I'm now thinking there probably wasn't if A3 doesn't recognise this facility. Anyway, I'm quite interested in using Picture Controls so would appreciate any help on this. Cheers, jp

Thanks DiploStrat. I may not have explained myself very well but I do agree with you. I've always shot in RAW. And to be honest I thought Picture Controls were something for the "point and shoot" mindset (and Ken Rockwell). And in answer to Frank, the overwhelming reason to shoot in Raw is the flexibility it gives me with post processing. Which is your point DiploStrat - all the picture control stuff can be done here.
I presumed that the effect of the photos you intensely dislike the look of (no sitting on the fence here - an admirable trait) was done with PS or simlar software. However, as I've mentioned, my weekend workshop tutor said try picture controls, which obviously work for her. I learned a lot from the workshop but somebody has yet to convince me why I should use Picture Controls. So, at present I'm with you DiploStrat, and learning the editing formulae is the way to go.
Not a futile discussion though, I've learned a bit (discovered Rob Boyer) and feel more comfortable that Picture Controls are not something I need to worry about.
Thanks for the below info - I'll check it out. Cheers, jp
-- Run your images through Capture NX first and then import the TIFF into Aperture, or,
-- Take a look at Catapult: http://brushedpixel.com/
Best wishes,
DiploStrat

Generally when creating a Word file from either a Mac or Win7 pc and opening it on two different machines (either one first) it always prompts that the file is open and will be opened as read only. However opening a CSS file does not prompt that it is alr

Generally when creating a Word file from either a Mac or Win7 pc and opening it on two different machines (either one first) it always prompts that the file is open and will be opened as read only.
However opening a CSS file does not prompt that it is already open on or from any machine which is causing code edits to be lost.
What we found from out testing:
- The file can be saved from one user to the server and WILL NOT PROMPT on other machines until the saving machine has the Dreamweaver program closed completely
- The file can be closed and Dreamweaver minimised to the launch bar but it still will not register on other machines that it has been changed.
- Also, until the Dreamweaver program is closed on the machines, it will continue to open it's saved version of the file.
Example Scenario:
- User 1 opens test.css (which is 2000 lines) and adds some code to the end of the file to bring it up to 2500 lines
- Meanwhile User 2 opens test.css as well (opens as 2000 lines as User 1’s edits have not yet been saved) and adds in code to bring it to 2300 lines
- User 1 saves his file and closes it - but Dreamweaver is still open.
- User 2 also saves his file and leaves Dreamweaver open.
- The server will report the size and last edit of the file the same as User 2 as he was the last person to save it (and if you open from the Win7 Machine it will show as User 2’s 2300 line version)
- If User 1 then open's the file again (from either the 'recent' in Dreamweaver OR clicking on the file directly in Finder...which version opens.... The version that User 1 saved! Not the true version on the server, but the version that User 1 edited and saved with 2500 lines in it.
- Same for User 2, he will open 'his' version with 2300 lines in.
Other information:
- Files are opened directly from the server
- Sometimes the users will save incrementally and re-open
- Most of the time users will save incrementally and keep the files open
- The users will never not save incrementally and just save when closing the file once finished
- The users are usually working on the files all day
- It is always the bottom lines of code that are lost. It could be a case of the two versions being mixed up and cutting off the newly added lines based on the line count (possibly).
It is as if Dreamweaver is holding a cache of the version locally and then only properly looking back to the server when it has been completely closed. It is very difficult to see how the server is causing such an impact on these files, there are very few logs which are giving any indication to the root cause of the problems.
Anyone know if this is a known issue?
Is there a way that there can be a featured implemented on the server that doesn't allow another user to open a file if it is already open on another machine?
Thanks

Your server file handling has nothing, and really nothing to do with Adobe software. If files don't get locked for (over-)writing and/or lose connection to the program opening them, then your server is misconfigured. It's as plain and simple and that. Anything from "known file types"/ file associations not being set correctly, MIME types being botched, crooked user privileges and file permissions, missing Mac server extensions, delayed file writing on the server, generic network timeout issues and what have you. Either way, you have written a longwinded post with no real value since you haven't bothered to provide any proper technical info, most notably about the alleged server. Either way, the only way you can "fix" it is by straightening out your server and network configuration, not some magic switch in Adobe's software.
Mylenium

Why I cannot open camera raw files from camera Nikon 3200 through Adobe Bridge and/or Photoshop?

Why I cannot open raw files (NEF) from camera Nikon D3200 through Adobe Bridge and/or Photoshop ?

Thanks for the tip. It worked out perfectly.
De: ssprengel [email protected]
Enviada em: terça-feira, 14 de janeiro de 2014 19:14
Para: Aecio Paes Leme
Assunto: Why I cannot open camera raw files from camera Nikon 3200 through Adobe Bridge and/or Photoshop?
Re: Why I cannot open camera raw files from camera Nikon 3200 through Adobe Bridge and/or Photoshop?
created by ssprengel <http://forums.adobe.com/people/ssprengel> in Adobe Camera Raw - View the full discussion <http://forums.adobe.com/message/6012775#6012775

Will there ever be support in Lightroom 4 for Olympus raw files

Will there ever be support in Lightroom 4 for Olympus raw files?

Which camera exactly?
Support varies camera by camera.
Supported cameras
Camera Raw plug-in | Supported cameras
Compatible Adobe software
Camera Raw-compatible Adobe applications

Will Photoshop Elements 11 and Lightroom 4 support conversation of RAW files from a Nikon D800?

I'm currently using Photoshop Elements 9 and must convert RAW files from my Nikon D800 to .dng files before processing using a added converted. I'm considering upgrading to either Elements 11 or Lightroom 4 but want to know if either of these programs will support the nikon D800 RAW files without having to go through this extra cumbersome step. Additionally, if I do go with Lightroom 4, will the transition be easy or difficult and what problems might I encounter?

Yes the D800 is fully supported in both applications.
You would certainly benefit in processing your 36mp raw files using Lightroom if you have a 64bit PC or Mac with additional memory (RAM). The Lightroom develop module is where you do all the editing and you get the benefit of the full CS6 raw engine in an intuitive interface.
If you regularly use the Elements Organizer you should understand Lightroom quite easily.
Why not download the free trial of LR4 and test for 30 days.
http://success.adobe.com/en/uk/sem/products/lightroom.html?kw=p&skwcid=TC|23077|lightroom| |S|b|21212135254
P.S.
There is a good video tutorial from Adobe’s Julieanne Kost - Create Stunning Images.
http://tv.adobe.com/watch/getting-started-with-adobe-photoshop-lightroom-4/lightroom-4-cre ate-stunning-images/

Why does lightroom 5 do not read or can't find my raw files when I'm trying to import my images from my camera to light room

It just started happening out of the ordinary. I had a photo shoot done today. I came home plugged my camera usb to my mac lap top and tried to import my raw files as i usually do into light room 5 to edit my images. This time the same error message popped up stating it couldn't read or my files weren't found over and over again. Neither the new ones nor the old pictures was able to import them. Please Help!

I just bought Lightroom and have the same problem - MacBook Pro with OS X 10.10.1. LR actually displays the photos properly when previewing but fails when starting the import. Also, a couple of times it would start but would hang up. I think it may be a Yosemite problem. I was having trouble importing with Aperture too. The fail message from LR was:
The following files were not imported because they could not be read. (6)
    IMGP7941.JPG
    IMGP7942.JPG
    IMGP7944.JPG
    IMGP7943.JPG
    IMGP7945.JPG
    IMGP7946.JPG
I can copy the folder from the camera to my desktop and then import. That works but of course I shouldn't have to do that.

Importing nikon d610 files and presets are applying to raw files?

I just picked up a nikon d610 and every time I import photos several presets are applied to my Raw images. White balance, contrast, Vibrance, saturation, and sharpening. It's like an import preset is set but I don't have anything selected. This only happens on my D610, my D800 and D7000 import raw files in with no settings applied. Running LR5.5 on a Mac OS 10
Anyone experience this before?
Thanks

You mention an older camera, which opens the door to the possibility of older software. There are histories of older versions of Nikon Transfer doing bad things to files from newer cameras. Check to see that you have the most recent version of Nikon Transfer. If not, do the upgrade then transfer the files again from the card(s).

Lightroom 4.4 cannot partly read Nikon Capture NX2 changes in NEF files

Good Morning,
if I improve a NEF-File in capture NX2 and save it as a NEF-file and afterwards will import these files into LR, then the changes are available on the LR Importscreen (great), but during the import-process in LR the changes - embedded in the NEF-file - disappear, and I just see the original NEF-file before the changes. Looking to learn how to solve this problem.

Nikon Capture NX2 uses its own proprietory process to render the raw data and produce a viewable image file which Lightroom cannot use.
Lightroom has its own process and profiles developed for your camera model, it uses these to render the raw data and produces a viewable image file. The view you see on the import screen are the thumbnail jpeg's created by your camera which enable you to view the image on your camera's screen.
Adobe may have created aditional profiles for you camera to emulate the look of your camera, in the develop module these are located in the Camera Calibration and can be choosen there (Camera standard, camera landscape, camera portrait etc.). There are also tools for you to create your own profile and look for your camera if you wish.

Can't open Nikon D300 raw files in camera raw in CS3

Is there a solution to this?

The D300 is supported in CS3. The last version of Camera Raw that is compatible with CS3 is 4.6. If you have it installed correctly you should have no problems. Your camera was supported in at least one previous version, I didn't check real closely. But you should install and use 4.6.

ACR 4.6 Picture Controls

I am confused about what is happening. Any help would be appreciated.
I understand that Nikon Picture Controls can be used to change the color balance which may give better color.
I am running CS3 in a 64 bit Vista Ulimate operating system
What I am trying to understand is how the Camera Profile works in the Camera Calibration tab in ACR. I am currently shooting a Nikon D200 and a D300. I understand that Nikon picture controls can be available in the Camera Profile of the Camera Calibration tab
I went to http://www.adobe.com/support/downloads/thankyou.jsp?ftpID=4040&fileID=3754 and downloaded ACR 4.6. I then unzipped and installed.
After installing ACR 4.6 I downloaded and installed GND 5.5 at http://www.adobe.com/support/downloads/thankyou.jsp?ftpID=4576&fileID=4244
The Title bar in ACR shows Camera Raw 4.6. The Camera Profiles in the ACR Camera Calibration tab shows ACR 4.4 and 4.3. After installing GND 5.5 the Nikon Picture Controls (NPC) appear in Camera Profiles. When I click on one of the NPC it seems to work but the Shadows, Red green and Blue Primaries are not changed.
When I go to the DNG 5.5 DNG Converter in the compatibility section of the preferences section it says that it should work for 4.6 and later.
My confusion relates to the fact that my Camera profile in the Camera Profile shows ACR 4.3 and 4.4 – not 4.6 and the DNG converter preferences says 4.6 and later. Someone that I know who downloaded and installed ACR 4.6 and DNG at the same time has the camera profile showing 4.6.
Do I have a problem or am I spinning my wheels? If I have a problem how do I correct the Problem?

Forums #1 wrote:
My confusion relates to the fact that my Camera profile in the Camera Profile shows ACR 4.3 and 4.4 – not 4.6 and the DNG converter preferences says 4.6 and later. Someone that I know who downloaded and installed ACR 4.6 and DNG at the same time has the camera profile showing 4.6.
The fact that there are two older profile versions (4.3 & 4.4) simply mean that the FIRST version to support your camera model was 4.3. The fact that 4.4 is there as well means the profile was modified (improved) for ACR 4.4. the reason both are there are for legacy reasons...
Looking at the Profile drop-down is NOT the way you determine the current version of Camera Raw you have loaded...the ONLY way is using the "About Plug-ins" menu item or looking at the main ACR title bar in the window (as long as you aren't at full screen).
If you have the Adobe Standard and the vender looks profiles loaded, you're good to go...as to what those profile will or won't do to and for your image...well, that's for you to decide. I tend to use Adobe Standard.

Examples of scenes rendered by the new LV 3D picture control (2)

According to NI News august 6, 2004, there is a new :
8. Download LabVIEW 3D Picture Control Evaluation Software With the new LabVIEW 3D Picture Control evaluation software for LabVIEW 7.1, you can model and render basic 3D scenes for advanced visualization in LabVIEW. Download the software at:
http://digital.ni.com/express.nsf/bycode/nn0804a08
I've downloaded it for evaluation, but couldn't install since I run LV 7.0 Express, so I stated the previous request for some samples of scenes
Any help would be appreciated

Unfortunately the dedicated topic for the 3D Picture Control tools was lost in the transition. The old forums had the concept of a "topic", which was different from a typical question or other thread, and they were not migrated.
One of most useful parts of that thread was a link to the download page for the tools, which I will post here.
LabVIEW 3D Picture Control Evaluation Software
Additionally, I have created a new dedicated forum post for these items. The new dedicated forum for these 3D tools is here.

Save content of picture control as .jpg into excel file?

Is it possible to save the contents shown of a picture control as a jpeg file into an excel file along with other data? Is this possible without using ActiveX? If I have to use ActiveX how do I use this?
Thanks

Hello AndyBE,
ActiveX is definitely going to be your best bet. I�ve attached an example that should meet your needs. Let me know if this works for you.
Have a nice day!
Robert Mortensen
Applications Engineer
National Instruments
Robert Mortensen
Software Engineer
National Instruments
Attachments:
Picture_To_XL_(6i).vi ‏133 KB

Nikon D300 Raw files for 64bit windows vista machine not appearing in Photoshop CS3 raw

I purchased a new 64bit computer running Vista. I have installed Photoshop CS3 including the latest updates and the 4.6 (Camera Raw.8bi) raw update file. I included the raw file in C:\Program Files (x86)\Common Files\Adobe\Plug-Ins\CS3\File Formats. I have purged cache in Bridge and I still cannot view the raw files in Bridge. I only see a gray square with a Blue NEF. I can open the files in Photoshop however. What can I do to see the files in Bridge?

Nikon encrypts RAW file data
ByMichael R. Tomkins, The Imaging Resource
(Wednesday, April 20, 2005 - 02:16 EDT)
A news item posted on Sunday by PhotoshopNews.com reports on comments from Thomas Knoll, one of the original authors of Adobe Photoshop, relating to the RAW file format used in Nikon's D2X and D2Hs digital SLRs.
<IFRAME src="http://208.43.255.194/cgi-bin/advertpro/banners.fpl?region=112&keyword=NULL" height="250" width="300" marginwidth="0" marginheight="0" vspace="0" hspace="0" frameborder="0" align="middle" scrolling="no"> <A href="http://208.43.255.194/cgi-bin/advertpro/blink.fpl?region=112&slot=1" target="_blank"> <IMG src="http://208.43.255.194/cgi-bin/advertpro/bimg.fpl?region=112&slot=1&keyword=NULL" border="0" width="300" height="250" alt="Click Here!"> </A> </IFRAME>
Thomas Knoll is currently the chief engineer for Adobe Camera Raw, the company's RAW file conversion software. The PhotoshopNews item references a forum thread started by Mr. Knoll in Adobe's official user forums, where he reveals that .NEF RAW files from the latest Nikon digital SLRs encrypt data relating to the white balance setting the photo was shot with.
RAW file formats vary significantly between digital camera manufacturers (and often, between different models in a manufacturer's lineup), and the manufacturers generally won't publicly disclose the specification for the RAW file format(s) they use. Some will offer plugins or software development kits (SDKs) that enable their RAW files to be opened in third-party applications, but these generally have some limitations attached to their use.
In addition, the companies generally offer RAW file conversion software of their own, either as part of their camera bundles or as an added-cost option. Nikon offer their pro SLRs with PictureProject software that includes limited control over the RAW file conversion process, and then offer the more feature-rich Nikon Capture conversion software for an added cost. In a recent publication on the company's Nikon Pro website, it suggested that it feels Nikon Capture is better-suited to photographers, while Adobe's Photoshop is more suited to graphic artists. Still, different photographers have different workflow preferences, and for this reason third parties such as Adobe often reverse engineer the RAW file formats, allowing them to be opened in their own software - sometimes with even better image quality than the original manufacturer's software.
In a way, it is understandable that companies would want to encrypt RAW file data from their products - it allows them to pick and choose which competitors are able to open RAW files shot with their products, and allows them to generate new revenue streams from the sale of their own RAW file conversion software (or, if they choose, the sale of licenses allowing competitor programs to access their RAW file data). Nikon is not the first company we're aware of to encrypt data in RAW files; Sony's Cyber-shot DSC-F828 RAW files contain encrypted data. In that instance, however, Sony granted permission for Adobe to decrypt the data in their software. At the current time, Mr. Knoll states that while Adobe has signed a non-disclosure agreement that grants them access to use Nikon's SDK, they have not received any response to requests from Adobe that the company be allowed to decrypt the white balance data, which would allow closer integration with their software than is possible with the SDK.
The fact that Nikon has chosen to encrypt a portion of the RAW file data would not be particularly problematic for third parties to overcome, were it not for certain laws enacted around the world in recent years. One such law is the United States' "Digital Millennium Copyright Act", often referred to as the DMCA, which makes it illegal to produce technology that can circumvent measures designed to protect copyright. One could argue that Nikon's encryption of the white balance data is just such a measure - which would make it an offense for a third party without permission to make software that could decrypt the original white balance setting used by the camera when the photo was shot. One could equally argue, however, that the copyright over the RAW file belongs to the photographer who captured the image - and hence the choice over what is done with that copyrighted work is entirely up to the photographer.
Unfortunately, there's no clear-cut answer, and short of a company or programmer finding themselves in court for having cracked the encryption, there isn't likely to be such an answer any time soon. This presents a problem for third parties attempting to make their own RAW file conversion routines for the D2X and D2Hs, as if they don't want to risk opening themselves up to legal action, they aren't able to determine the original white balance setting. Hence, they must either request the white balance setting from the user as the RAW file is converted, or attempt to determine an appropriate white balance setting automatically (which would not necessarily be the same as that determined by the camera itself).
Nikon hasn't communicated their reasons for encrypting the white balance information in their latest NEF formats, but we have to say it doesn't sound like a very good idea. While Nikon Capture does indeed offer excellent capabilities for people to manipulate images saved in NEF formats, many photographers and organizations have already established workflows based on Adobe's RAW plugin for Photoshop and other image-processing tools. The biggest consequence of this move on Nikon's part seems likely to be to push more photographers onto other camera platforms. It's hard to imagine that increased sales of Nikon Capture will make up the revenue lost from camera and lens sales going forward.

Unable to open Raw files from Nikon D800 in Photoshop CC [was:raw updates with creative cloud?]

i have a d800, bridge or photoshop do not seem to support the raw files, i am using CC and bridge will not bring up the thumbnails and photoshop will not open the files at all, can anyone help?

[Moved from Cloud forum to Camera Raw forum]
ACR = Adobe Camera Raw.
ACR is the plugin used by Photoshop to read and process Raw files from cameras. It must be updated every time a new camera comes on to the market.
The Nikon D800 has been fully supported since ACR7.1
http://helpx.adobe.com/creative-suite/kb/camera-raw-plug-supported-cameras.html
ACR7.1 is compatible with Photoshop CS6 and later
http://helpx.adobe.com/x-productkb/global/camera-raw-compatible-applications.html
So, if you are in fact using Photoshop CC, there should be no reason that Raw files cannot be opened.
In Photoshop, click:
Windows: Help > About Plug-In > Camera Raw
Mac: Photoshop > About Plug-In > Camera Raw
Which version number is shown?
Are you using Nikon transfer software to get the Raw files from your camera to your computer?

Will LR 5.3 read Nikon picture controls applied to RAW files in-camera?

Similar Messages

Maybe you are looking for