Am I stuck using ViewNX2 for .nef files ?

I have CS2, my camera is a Nikon D7100, the .nef files will not open in Cs2. I have tried the Camera Raw 3.7 update, and the DNG converter,
but that still has not solved the problem, doe's any one have a solution ?, or am I stuck using ViewNX2 ?

That's what I supposed. That seems to confuse every new user of the DNG converter. Notice the prompt; it is asking for the FOLDER. Choose the folder but don't open the folder. After you have selected the folder and set your other options appropriately, click on the Convert button. Then you will see a list of your files and be able to monitor the progress of the conversion. If you want to convert individual files, drag/drop the file on to the DNG converter icon before you start the program.

Similar Messages

Camera-raw plugin for NEF files, made with the new Nikon D7200

Hi, does anyone know when there will be a camera-raw plugin for NEF files made with the new Nikon D7200?

I think that camera is too new. Even the DNG converter will not support it. If you have Nikon software with the camera, you could convert to tiff and then use the tiff files in Elements whilst awaiting the next Camera Raw update for PSE13.

Framemaker uses $filename for short file name, can we edit this to change appearance? We do not want the short file name of long filename to include the .fm extension can this be removed or modified to make this happen?

Framemaker uses <$filename> for short file name, can we edit this to change appearance? We do not want the short file name of long filename to include the .fm extension can this be removed or modified to make this happen? In compiling our books it would be helpful to not have this extension appear as it then requires us to create extra files without them.

See: System Variables

Sender file adapter - Can I use *.xml for the file name

Hi Gurus,
I have some interfaces where I need to pick the file from a directory. The name of the file will have Data<i>time stamp</i> as the naming convention. Can I use *.xml to pick up my files from this directory?
The help.sap.com documentation says that we can use this naming convention.
<b>
● File Name
Specify the name of the file that you want to process. The name can contain placeholders (*, ? (placeholders for exactly one character)) so that you can select a list of files for processing.
</b>
I tried using *.xml for my file name in the communication channel, XI is not picking up this file.
Please let me know if you have the solution.
Thanks
Kalyan

Murthy,
Thanks for the reply.
I am using GuildFTP tool as my FTP server. In this tool, all the permissions were given for the file to pick up.
The status of the file is good.
Where in the file adapter configuration I have to select 'Read-only'?
The file adapter is working perfect with the exact name of the file.
Thanks
Kalyan

Using Log4j for writing files

Hello,
Is possible to use log4j for writing files?
For example:
I have an application that produce several report txt files is possible at runtime produce them using log4j features?
Thanks

Did you ever got an answer for this??? I'm starting a new project with ORACLE 9i and the site have a NAS. It will be very helpfull to know if it's possible and how can it be done.
Thank you,
Ulises Feliciano Troche
GIS Analyst
GMT

Preview not Available for NEF files

It is my first time using LR and also my first time trying to download NEF files from my new D750. I removed the card from the camera and inserted it into my computer (MacBook Pro) I can see previews of the images shot in JPEG format, but those shot in RAW format are appearing as boxes with "Preview not available". The D750 came with Nikon ViewNX2 software, which I downloaded, and I can see the previews on that. Any suggestions/ideas on what might be the problem?

Lightroom does not support the Nikon D750 RAW photos at this time.
Please read this thread:
Support for Nikon D750
Just released (see the message 49 of that thread) is a DNG converter that should allow you to convert the NEF to DNG and import those into Lightroom.

Thumbnails for Nef files with upated exposure in Capture NX2 revert to original exposure

I did a batch processing in Nikon Capture NX2 to update the exposure for all Nef files in a folder.
When displayed in Bridge (CS6) the thumbnails at first show the thumbnail with the updated exposure, then slowly updates all the thumbnails to the original exposure.
How do I get Bridge to display the thumbnails with the updated exposure and keep bridge from reverting back to the original exposure?

You can set different default parameters for Adobe Camera RAW, but they are still default parameters and this is what Camera RAW uses to render the RAW file instead of the parameters saved in the RAW file by either the camera or Capture NX2.
The camera saves a low quality jpg image in the NEF file (you can't change this) and if you edit the NEF file with Capture NX2 or View NX2 it saves a high quality jpg image in the NEF file, which increases file size by a considerable amount.
I process everything from the RAW file using Photoshop CS6 Adobe Camera RAW. I have all in camera parameters set to nominal, active D Lighting off, and use Camera Neutral with a custom tone curve that was generated using the Picture Control editor. In Camera RAW I use Camera Neutral v4 with the same custom tone curve as I used in modification of the Picture control profile. My Camera RAW default is set using the modified Camera Netural v4 profile and I get excellent agreemnet between the Camera jpg and Camera RAW.

White balance values for NEF file

Hello
I'm using Ligthroom 1.2 with nikon raw files (NEF) taken with D80 camera (firmware 1.01).
The white balance is most of the time set to 5300K on my camera. But in LR, it always shows 4950K, with tint set to -1.
I know there is some compatibility problems between LR and NEF files, but does anyone know if there is a solution (except of course applying systematically the right temperature in LR during import.)?
Thanks
Erwann

I believe the issue is actually that Nikon encrypts the white balance in NEF files of recent cameras. If you
google for it you'll find lots of links to all the problems this caused. Adobe and other RAW software developers have had to reengineer the encryption of this value in order to get a reasonable value and in order to not break the DMCA (draconian US anti-piracy law). Apparently, for some cameras the algorithm is not so good. The alternative for Adobe would have been to use Nikon's RAW rendering library, which for obvious reasons will never happen. The only software I am aware of that correctly reads NEF white balance for cameras after the D2X without using Nikon's libraries is dcraw/ufraw, but they can get away with cracking the encryption. This really is one of the dumber things Nikon ever did.

Is Bridge supporting 16 Bit for NEF files?

Hi to all!
I'm a longtime Aperture user, but I'm considering to use it in future more for all my selecting and ordering of my files, and would like to do the Raw conversion in Adobe Camera Raw.
My files used in Aperture are 'referenced', so only the edits etc. will be stored as an extra file in Aperture Library. So I can work on the NEF files within Aperture, but also within CS4 (which gives me the edits as an extra file beside the photo file, it seems not to disturb Aperture).
So far so good. But now I noticed that Aperture is converting my 14 Bit NEF files before working on it into a 16 Bit file. I also can export it as a 16 bit file, but not as a NEF anymore. If I open the same NEF file in Camera Raw it appears to be only a 8 Bit file.
Is there a way that Adobe could change it into a 16 Bit. Or is this not important during that converting in Camera RAW?
Thanks for any advise

Thank you so much Buko!
I didn't notice that those info's were 'clickable'.
Super easy, and cool. Also the OPTION to choose the resolution is great.
You were much of a help!

Using an * for all file extensions in a class selection parser

Using iFS 1.1.9....
I have successfully gotten a custom document class created using
xml. I have used the following code to set up the parser, etc.
If I use a specific file extension like txt the parser will
upload the file as my custom class. However, if I use * for all
file extensions the parser uploads all files as Document class.
Here is what I am using:
<?xml version='1.0' standalone = 'yes'?>

<PropertyBundle>
<Update
Reftype='ValueDefault'>ParserLookupbyfileExtension</Update>
<Properties>
<Property Action = 'add'>
<Name>*</Name>
<Value Datatyupe = 'String'>
oracle.ifs.beans.parsers.ClassSelectionParser
</Value>
</Property>
</Properties>
</Propertybundle>
When the above is uploaded I can go into iFS Manager and see
that the parser has been registered with * as the file extention.
I then upload this:
<?xml version='1.0' standalone = 'yes'?>

<PropertyBundle>
<Update
Reftype='ValueDefault'>IFS.PARSER.ObjectTypeLookpByFileExtension
</Update>
<Properties>
<Property Action = 'add'>
<Name>*</Name>
<Value Datatype='String'>QualDocument</Value>
</Property>
</Properties>
</PropertyBundle>
If I have txt or some other extension for the Name in place of
the * and upload a document it will put the class as
QualDocument. If I have the * it defaults to Document.
Is there a way to have the parser make all uploaded documents
QualDocument instead of Document without doing this for each and
every possible file extension?
Thanks.

Using iFS 1.1.9....
I have successfully gotten a custom document class created using
xml. I have used the following code to set up the parser, etc.
If I use a specific file extension like txt the parser will
upload the file as my custom class. However, if I use * for all
file extensions the parser uploads all files as Document class.
Here is what I am using:
<?xml version='1.0' standalone = 'yes'?>

<PropertyBundle>
<Update
Reftype='ValueDefault'>ParserLookupbyfileExtension</Update>
<Properties>
<Property Action = 'add'>
<Name>*</Name>
<Value Datatyupe = 'String'>
oracle.ifs.beans.parsers.ClassSelectionParser
</Value>
</Property>
</Properties>
</Propertybundle>
When the above is uploaded I can go into iFS Manager and see
that the parser has been registered with * as the file extention.
I then upload this:
<?xml version='1.0' standalone = 'yes'?>

<PropertyBundle>
<Update
Reftype='ValueDefault'>IFS.PARSER.ObjectTypeLookpByFileExtension
</Update>
<Properties>
<Property Action = 'add'>
<Name>*</Name>
<Value Datatype='String'>QualDocument</Value>
</Property>
</Properties>
</PropertyBundle>
If I have txt or some other extension for the Name in place of
the * and upload a document it will put the class as
QualDocument. If I have the * it defaults to Document.
Is there a way to have the parser make all uploaded documents
QualDocument instead of Document without doing this for each and
every possible file extension?
Thanks.

Camera raw plug in for NEF files from nikon d800

How can I open a NEF file from NikonD800 in photoshop CS5 Windows, camera raw plug in version 6.7.0.339? same problem for CS5 MAC, camera raw plug in version 7.0.0.308?

Hi there! Because the forum you originally posted in is for beginners trying to learn the basics of Photoshop, I moved your question to the Photoshop General Discussion forum, where you'll get more specialized help.

Plug in for NEF files

I am on CS5 and cannot open NEF files. Have updated my RAW plugin but will not work.It installed the the DNG converter but still can't read NEF extension. I read the conversation for Noelle on her extension update but can't find an application manager. Any suggestions on what to try next?

Is the DNG converter version 8.4? If not update. If you want to read NEF directly with PS you will have to update to CS6 or subscribe to CC.
This should solve problem.

Photoshop disk error on latest update for NEF files

Since the last update of Photoshop CC, photoshop refuses to open my NEF files Nikon format) quoting disk error.
The same file is opened in another mac with the photoshop version not updated to the latest CC update.
The same file is opened on the computer with photoshop troubles with other photo programs
What is the issue?

If you are still having/have had issues, you can open an active case file with Apple. Log the issue with a tech on the phone, so that you know you've reported it, so if anything gets worse in the future, you have a point of reference to come back to.
This is essential in the even that your warranty expires. So if you know you've had a problem from an outset, and if it turns out to be hardware related, you have case for a replacement because you've reported it.
Kind regards,
Gopha.

Photoshop CS and RAW support for NEF files...

I just purchased a Nikon camera and was wondering if anyone has seen a plug in for the D80 NEF files in Photoshop CS. They have created one for the CS2 program but not the CS... while apple has already created an update for D80 NEF support.
Thanks.
Daryn

No body helped

I have a passport external hard. previously, I used it on windows, then I changed my laptop to mac. Now, It's only read. How can I use it for copying files on it on mac? I don wanna use it on windows again.

I have a passport external hard. previously, I used it on windows, then I changed my laptop to mac. Now, It's only read. How can I use it on my mac for copying files on my passport? I don wanna use it on windows again.

If you're not going to use the drive on a Windows machine, you should use Disk Utility (Applications>Utilities folder) to erase the drive and format it as "Mac OS Extended (Journaled)" with a single GUID partition (default):
Good luck,
Clinton

Am I stuck using ViewNX2 for .nef files ?

Similar Messages

Maybe you are looking for