Nikon D300 raw files, unable to retrieve the camera serial number!

Hi all,
I have just downloaded some D300 NEF files (camera firmware v. 1.2) onto my PC, and both Bridge and Camera Raw display NO camera serial number in all the shots! :-( And when I convert them in DNG, I still don't have any info on the nikon camera serial no. , why!? :-(
I opened them with EXIF tool and I tested that the camera serial is there in all the NEF's (and also JPEG) files.
I tried the NEF files from a Nikon D2X camera and, this time, the camera serial is read perfectly from both Bridge, Camera Raw and Lightroom (v. 1.4.1) too. Does someone have any hints!?
Thanks in advance! ;)
GL

>then it's either a bug in the application or an application that ignores some very basic rules.
For as long as Photoshop has been around, any plug-in, with or without an extension will try to be loaded by Photoshop (as well as Bridge). Normal renaming of a plug-in or removing an extension will NOT eliminate Photoshop's ability to load them at startup.
There are certain symbols you can add to the front of a file name to prevent loading the plug-in. If you want to disable a plug-in on startup you'll need to add ¬ symbol as a leading character and that plug-in will be disabled.
This is neither a bug nor a failure of the application...it's a special situation that is a standard cross-platform method that Adobe apps have used for years (at least 18 years at this point with Photoshop).
So, while it may be obscure and obtuse, it's not the problem of Photoshop/Bridge since it's behaving as designed.
In testing various versions, I often have up to 1/2 dozen different versions of Camera Raw installed at one time. I use the ¬ symbol to disable all the version I don't want to load and make sure only 1 version is named normally.

Similar Messages

  • Bridge won 't recognize nikon d300 raw files

    What is it with Adobe?  Every time I attempt to use their product I hit another road block.  First it was using LR and PS on a high resolution screen.  Then I purchased their monthly subscription and got multiple versions of PS, not knowing which is the newest and correct version to use.  Is Photoshop CC or Photoshop CS5 the newest version. Now I can't get Bridge CS5 to recognize my Nikon D300 raw files.  Has Adobe lost it's footing?   I am extemely frustrated with Adobe products and apparently so are thousands, if not million of other customers

    Not possible in CS5
    Camera Raw plug-in | Supported cameras
    Camera Raw-compatible Adobe applications
    You can use the DNG converter to workaround this problem.

  • Aperture suddenly displaying "unsupported format" for Nikon D300s RAW files

    I am using Aperture 3.1.3 on my iMac 24 with Snow Leopard 10.6.8.   A couple of days ago I applied an update for Aperture RAW files that was in my update list, even though I don't use any of the cameras involved. 
    After that update Aperture gives me an "unsupported format" error on all my Nikon D300s RAW files. Every RAW file in the library.  I have never had a problem with this at any time over the last 2+ years of using Aperture.
    I have tried using time machine and rolling Aperture back to the end of July (my most recent backup) along with rolling back the RAW file plist. I then did a repair permissions, and reimported the photos after this.  I have rebooted numerous times.  All to no avail.  I have not yet tried a library rebuild that would be next if I must.
    I use a Referenced library, so I was able to check out individual RAW files with Adobe Camera RAW.   They open fine so there is no file corruption issue. 
    Any thoughts on what might be happening?  Any other file(s) associated with RAW conversion that I might need to roll back?   I do not see any mention of a problem like this when searching the web or the forum (although I may have missed something by not searching the correct terms).
    Any help would be greatly appreciated!

    The raw camera bundle is  /System/Library/CoreServices/RawCamera.bundle
    Go to /System/Library/CoreServices with the Finder, locate the the RawCamera.bundle package, select it and then do a File->Get Info on the package. You should have version 3.8.0, that is the latest and the one that you should have downloaded last week. If it is not 3.8.0 stop here and post back what version you do have, something isn't right.
    Assuming you have 3.8.0  use the Finder to navigate to /System/Library/CoreServices and then delete the RawCamera.bundle package. The Finder will ask you to authorize the delete.
    Then go to Digital Camera RAW Compatibility Update 3.7 download and install it. That will put you back to the last CameraRaw update before this one.
    See if that fixes your problem.
    As always when messing around with system files it is possible to mess things up so make sure you have a good backup before proceeding, And if any of these instructions make you nervous you might want to hold off doing them.
    good luck

  • Lightroom5 not recognising Nikon D300s RAW files

    Hi,  I have recently upgraded to a new iMac running OSx Mavericks.  Lightroom 5 is not recognising my Nikon d300s raw files (NEF).  According to everything I have read on the net it should as Lightroom is brand new and up to date.
    Any advice.?
    Thanks

    They all show up in the preview view finder but then I get the error message "The following files were not imported because they could not be read" with a list of the files underneath.
    This is the first time I have used Lightroom 5 with the D300s... having just changed computers and upgraded from Lightroom 4. I have also now found out I can't download JPegs either!?!?!? You know that feeling when you think "if it isn't broken don't fix it" that's how I'm feeling right now about buying the new computer and software!!

  • 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.

  • Error opening New Nikon D300 RAW files on Iphoto and Preview

    hi,
    I've a new Nikon D300 and I've had problems when i try to import the RAW (.NEF) photos to my iphoto... it says that the file is unreadable either on Iphoto or Preview or even on Apple Aperture. How can i solve this problem? is there any update that i can do for that or Apple didn't upgrade the iPhoto yet? I l know the camera can take 14-bit Raw format photos but i'm not sure if it is taking them in 12-bit because it can take both. I have a Nikon D200 too and i've never had any problem uploading my Raw photos to iphoto. the only program that opens the photos yet is Photoshop CS3.
    hope, someone can help me.
    Many Thanks:
    Gonçalo Rendeiro

    hope this 10.5.2 solved the problem
    http://docs.info.apple.com/article.html?artnum=306835

  • 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.

  • Nikon D3s RAW files are underexposed by Lightroom / Camera RAW

    I'm used to shot RAW files only.
    I recently bought a D3s, alongside with my D700 and I noticed D3s files were darker than D700 ones, by about 1/2 or even 2/3 stop. Initially I thought the problem was one of the cameras, but after some tests I found the problem is my RAW converter. Infact this happens only with NEF (RAW) files, and if I shot a RAW+JPG image, the D3s RAW file opened in Lightroom 4 (or Camera RAW) is underexposed if compared with its JPG on-camera version.
    I think no camera setting is affecting this behaviour. I reset either the D3s and the D700. No D-Lighting is set on-camera. This happens only with the D3s and only with Camera RAW and Lightroom.
    Other RAW converters display the D3s RAW file correctly exposed, the same as its JPG version, and the same as the D700 RAW and JPG. I tested so far Capture One, DxO Pro Optics and Raw Therapee.
    Color profile used is custom, but I tried using Adobe Standard and the result is the same.
    Default develop settings affect only color profile and sharpening, and I got the same problem on a fresh new installation of Lightroom where no default develop settings are set.
    If anybody with a D3s can check if his NEFs are underexposed if compared to their JPG versions when opened in LR or Camera RAW, I would appreciate that much.
    Any idea about the origins of my problem would be great.
    Thank you.

    alessandroavenali wrote:
    I know, DdeGannes, but a different rendition of 2 pro cameras at the same settings is a bit frustrating.
    Would it be better to underexpose the D700 while shooting, or setting a default -0,5EV on every imported picture, if the problem goes on?
    Moreover, seems the Nikon D3s ISOs need to be pushed +2/3 to obtain the same exposure as the D700 in LR workflow. So the advantage of this great sensor could be lost.
    I'd like to know more about D700 and D3s rendition comparison in LR/ACR at same settings.
    It's not unusual for two camera bodies of even the same exact make and model to have Exposure differences of up to 1/3 EV, which is very noticeable. Ditto for  White Balance differences. For Example:
    Camera 1 is +1/3 EV and Camera 2 is -1/3 EV = 2/3 EV Difference
    Camera 1 White Balance is -500KTemp and Camera 2 is +500K Temp = 1000K Difference
    Tack on minor differences between the LR Camera Profiles and it will get much worse if heading in opposite directions, as above.
    The only way to compare the raw NEF files from two cameras is to use a RAW converter that applies NO profiles, NO Gamma Correction, or any other modifications to the raw pixel data. See may post here for information on 'Rawnalyze:'
    http://forums.adobe.com/message/3952812#3952812
    You can download it here:
    http://dave-anderson-photo.com/files/software/Rawnalyze/Rawnalyze_2.10.4.0.zip
    Online manual here:
    http://www.oitregor.com/numeric/Rawnalyze/Rawnalyse_doc/datas/RawnalyzeGuide.htm
    None of the external links in the manual work, but nothing to worry about. If you have any questions on how to use it let me know.
    I believe the Nikon D700, D3, and D3s cameras are supported in Rawnalyze 2.10.4.0. If not you can convert the NEF to DNG.

  • Aperture Nikon D300 RAW: 4304×2852 instead of 4288 × 2848?

    Aperture 2.0 seems to squeeze extra pixels out of my Nikon D300 RAW files compared to Capture NX.
    This messes up Apertures "+auto detection & import+" of RAW+JPG sets when you generate the JPGs using Capture NX. No problem when using the JPGs the camera created: Aperture silently imports those JPGs alongside the RAWs so you can "Generate Version from Master JPG"
    Where do these extra pixels come from, and is this "feature" unique to decoding of D300 files?

    Well both a pain and a blessing
    I used to shoot RAW+JPG and whenever I felt my JPGs were good I just used 'New Version From Master JPG' and select that one as the pick.
    I just imported a bunch of RAWs from a directory in which I also placed the batched Capture JPGs and Aperture was able to 'auto-stack' them by 2. A pitty the order of the first image isn't always the JPG...
    I'm not sure which RAW+JPG workflow is better at the moment

  • How to import Nikon Nef (raw Files) ?

    Hello
    I'm having problems importing Nikon Nef Raw files, PSE9 is displaying the message The file is damaged or file format
    cannot be included. Any suggestions please.

    You are going to need Adobe Camera Raw 6.3, but the only version that has been released is the Version 6.3 Release Candidate, which I don't think can be installed with PSE. You will have to wait until the final version of Adobe Camera Raw 6.3 is released.
    The only workaround is to use the Version 6.3RC DNG Converter to convert your RAW files to DNG files, which can then be accessed by PSE.

  • Retrieval of 'original serial number'

    My MacBook Pro2,1 (OS 10.5.8) has just come back from repairs at the local Apple Store/Genius Bar. I'm finding that as I launch each application, I'm required to re-enter serial numbers.
    The wrinkle is wth the attempt to launch FCP 5.1.4 - after successfully entering the upgrade serial number, the next dialog requests the 'original serial number'. Oops - that goes well back. I was careful to do a backup of my home folder before sending this venerable computer out for repairs.
    Is it going to be possible to retrieve the orig serial number from the home folder backup?

    Thanks Shane. Thinking back, I think my first version of FCP was 3.0, and I would have recycled all of that at the end of 2006, when I upgraded to 5.1.4
    For some reason, with all the operations my (same) computer has been through since then, I've never been required to key that original code information back in.
    I remember having trouble installing the serial number for 5.1.4 the first time after buying it - I went back to the store and watched as a staff member retrieved the code from inside the software. By cutting and pasting it directly into the dialog, he avoided any possible typos.
    I think the Genius folks will be happy to help with this, and I have the original purchase records for the v 3.0 on file. Shane, do you think Time Machine is a way to drill down into the pre-repaired state of the computer, and find the serial number there?
    GP

  • Are selfmade DNG profiles referred to the cameras serial nr. (et al.)?

    Need a quick help, because I'm just writing an article about the DNG profile editor...
    When I make my own DNG profile with the DNG PE, is this profile referred to the cameras serial#? If you have more than one camera of the same model, you should be able to make a separate profile for every body. If you have different profiles for different cameras of the same model - are the right profiles automatically referred to the corresponding camera in ACR? Or do I have to use different profile names to select them manually?
    When I have assigned the different profiles to the corresponding cameras in ACR and I fix this as a standard ("Save new camera raw standard"), will the right profiles be assigned correctly by ACR from now on? Only if "Align standards at the cameras serial number" in the ACRs settings is active? (Sorry, I don't know the correct option names in english, because I only have the german version of PS...)
    Unfortunately I can't try this by myself, because I own some digital cameras, but not two of the same model... :-(
    Is there anybody who knows this? Or is there an owner of "camera tweens" who can figure this out for me?
    Another question: If I have already made a camera calibration with ACR (modified the red, green and blue primaries), can I transfer these values (without change) to the DNG profile editor to save and use this calibration as a profile? (I know I have to set the calibration to 0 in ACR in this case, because instead it is applied twice.) My question is: Do same values of the calibration in ACR and PE produce exactly the same result?
    I just tried this: It is not the case. Why not? I compared the two results with the difference-mode, they are not exactly equal (differences up to six 8-bit integer values).
    What about the "Hue (dark tones)" slider in ACRs camera calibration? Why is it missing in the PEs Color Matrices window?
    Thx a lot for your answers
    Marius

    So far as I am aware, DNG camera profiles do not store camera serial numbers, only camera model. Application can, if they want, associate a particular profile to a camera with a particular serial number.
    As regards differences between PE and ACR calibration sliders - I don't think the Adobe people have ever had it as a design goal for PE and ACR to be exactly the same in that regard. But only someone on the inside like Eric Chan would know for sure.
    Sandy

  • Nikon Df RAW (NEF) files will not load previews into Lightroom 5.4. Nikon d300s RAW (NEF) files load just fine. Df files do not.

    Nikon Df RAW (NEF) files will not load previews into Lightroom 5.4. Nikon d300s RAW (NEF) files load just fine. Df files do not.

    Thank you for your response.
    I have loaded directly into Lightroom using import and via Nikon Capture NX2. RAW files display fine in Capture.
    In Lightroom, blank previews are created for each available image, with the message "Preview unavailable for this file."

  • I need to find the download for ACR 7.3 to use my nikon d600 raw files. i have cs5 running on macboo

    i need to find the download for ACR 7.3 to use my nikon d600 raw files. i have cs5 running on macbook pro with mountain lion OS.

    Hi,
    Unfortunatly the 7.x series of camera raw plugin is not compatible with photoshop cs5.
    You could download the 7.4 DNG Converter and convert your d600 files to dng copies which then photoshop cs5 will open.
    http://www.adobe.com/support/downloads/detail.jsp?ftpID=5568

  • When opening a nikon raw file in cs5, ACR, the sky turns red, but is not red in thumbnail

    when opening a nikon raw file in cs5, ACR, the sky turns red, but is not red in thumbnail

    You most likely have the clipping indicator on that shows you blown out areas.  Click the little triangle in the upper right of the histogram to turn it on or off.

Maybe you are looking for

  • Finder won't open - continually crashes and asks me if I want to reopen windows

    I have no idea how to fix this. It began right after I installed Mavericks on my 2010 Macbook Pro 13". Finder will not open. It keeps crashing with a pop-up window that tells me that Finder isn't working and asking if I want to try to reopen windows

  • DVD burned from iDVD skips on TV not computer

    Help! I create a graduation DVD every year for the 8th grade at my daughters' school. It is created in iMovie and is made of pictures and music - basically a slideshow. After I create it in iMovie, I pull it into Garage Band to chapter it, then send

  • Monitoring with Server Manager?

    I start Server Manager in an xterm window with command svrmgrl and log in with system account. However, when trying to monitor the database, the following message appears (interpreted by oerr): [oracle@rxo log]$ oerr MGR 4501 4501, 0, "monitors are n

  • Smart Mailbox When Using The Subject Condition

    Hi Apologies if this is already a know issue. I created the following Smart Mailbox to find mails with attachments, but to exclude those that were related to iCards... [] Contains Attachments [] Subject Does not contain iCard This appeared to work un

  • FaceTime (and Photo Booth) do not recognize my internal camera

    I don't believe I have made any substantive changes to my system but my camera is no longer recognized on my iMac (late 2009, 10.8.2).  Facetime is working on my MacAir and iPhone.  It isn't working on the computer as I tried another account.  It jus