Nikon D300s and LR 2

I have recently purchased a D300s and have tried import the raw files into LR but this fails with error "The files appear to be unsupported or damaged (1) " . I am OK with Jpegs and have been OK with other Nikon Raw files (D80).
I can see the files in windows so I suspect that I am missing something or am doing something wrong. Can you help ?

Download and install version 2.6 from here, and you'll be fine.
Hal

Similar Messages

  • Nikon D300 and chromatic aberration

    I've noticed quite pronounced fringing in raw files brought into Lightroom 1.4 from a Nikon D300 and it can't be adequately fixed using the Lens Correction controls.
    Creating jpegs in-camera using RAW+jpeg gives jpegs with far better fringe reduction than I can get in Lightroom. It seems that Nikon Capture NX can give the same treatment to NEFs that the camera gives to jpegs, but it's not available in Lightroom.
    That benefit is powerful enough to make me consider switching to NX rather than upgrading to Lightroom 2 (which doesn't appear have this feature either).
    Alas, I've been allowing Lightroom to convert my NEFs to DNGs, so I imagine I've lost the metadata that NX uses to fix the CA on all my old files.
    Has anybody got any useful info on any of this?

    Nikon uses a software algorithm in the body and in NX to correct for lateral CA live. It does it for ANY lense you attach to the body. For RAW files, the info is written as metadata in the RAW file, which NX reads and uses as a first guess. Canon does the same in their DPP software. The math that Lightroom does in the lens correction section is the same. It just doesn't automatically determine the right settings. I have over time developed a set of presets that I will apply to files from certain lenses at certain focal lengths and this works OK, but not as good as the automatic fitting of the parameters that NX does. I had asked for something like this in the beta period, but it is probably not very high on the list of priorities. We'll see when and if it materializes. The algorithms to do this are simple (there is no reason to build a database, this is straightforward image processing stuff) but they are patent protected, so Adobe might not go there at all.

  • Nikon D300 and Aperture2

    I just bought a Nikon D300 and seem to be having some problems with the RAW conversion. From what I can tell, the D300 should be compatible with Aperture2 and Leopard. Sometimes when I make an adjustment to a photo, even the slightest adjustment will turn the whole picture black and UNDO doesn't fix the problem.
    Also, some of the picures show up with UNSUPPORTED FILE FORMAT.
    HELP!!
    Thanks,
    Mark

    I'm having the same problem with images from my D300 as well as my old D200, although i don't think it has to do with the camera based on other reports i've read on the internet. The levels almost always don't display and as soon as i adjust it, the image goes black. Even if i select another image and come back to that one, the image is still black. The only way to get it back is if i re-adjust the image size which makes it appear again. But if i adjust the levels again, it repeats.
    I am unable to adjust the levels on ANY image now - even ones that came from my D200.
    I haven't found a permanent fix to this.

  • Nikon D300 and D70 RAW support broken

    I am an Aperture 1.5 user that recently upgraded to 2.x due to my purchase of a D300. I was shooting a D70 before.
    I am just sort of getting my Aperture library back in shape (sold my G5 and moved completely to MBP until there is a Sub 2k machine that takes two external monitors and/or apple offers matte displays). I started importing some pictures from my D300 which were made with firmware 1.1. The first thing I noticed is that the autostack on import wasn't working. Moving the time domain slider over does nothing until I reach the far right hand side when it stacks the whole flash card full of files together.
    The other odd thing I noticed right off is that it does not auto-rotate shots done in portrait. After noticing that, I changed the import view to the "spreadsheet" format and all of the metadata was blank. Another side effect was that I imported some photos and had aperture place them on a network drive using the year/month of the pictures as the directory structure. This resulted in all of the shots going into a folder structure of 2000/1/ which is completely incorrect as the shots were taken last month and have a correct date/time stamp in the exif header in the files as well as on the actual files themselves.
    I though, perhaps I need to have the 1.10 firmware upgrade on my D300, so I applied that and shot some test pictures with the same result, autostack broken, autorotate broken, no metadata at import. I checked the picture post-import and the metadata seemed to all be there (F-stop, picture orientation, lens data, etc...). I though this might be a bug with the D300 format or using 12bit RAW+Jpeg Fine so I took a few shots with my trusty D70 in RAW and had the exact same issues.
    I finally gave up and took a series of shots with the D300 in Jpeg Fine. All of the above features worked perfectly this time. I repeated the test with the D70 Jpeg files which also worked perfectly.
    The issue only seems to present itself on import. RAW files that are already in my library seem to be fine.
    There is some horrible bug in the handling of Nikon raw files from at least two camera bodies. I looked around and there are some other threads on the discussion groups here citing inability to import and some other camera makes and models and I wanted to get a thread started about the core of these issues as I was able to cross-check with two bodies. I have access to a D80 and a D90 body as well to test with but didn't bother as the D70 support should be well baked at this point.
    Here are the numbers:
    Hardware: MBP 17" 2.4 "Santa Rosa" 4 gig ram
    OS: 10.5.5
    Aperture: 2.1.2
    RAW Support: 2.3 update
    Flash Media: Sandisk Ultra II and Extreme III 30mb/sec
    Flash Reader: Sandisk "14 in 1" OSX compatible (supposedly)
    D300 Firmware: 1.01 and 1.10 tested
    D300 image format: 12 bit RAW (.NEf) + Jpeg large/fine
    D70 Firmware: 2.0
    D70 image format: RAW (.NEF)
    So when can we expect a fix for this issue and will this require an export and re-import of all of the shots I have already imported?
    This is pretty serious as RAW file handling is the #1 feature of Aperture and Nikon is one of the top two brands of camera. This bug has broken multiple features in the software which should have set off red flags. This also broke support for an extremely old body. This is telling me that Apple has a QA problem in their test rig for Aperture.
    This is serious for me personally as this is a heavy use time of year for me and I'm not feeling good about this software. I'm a 1.0 user that upgraded so I have $400 into aperture at this point and I'm not certain it's worth it.
    Thanks

    mindedc wrote:
    Was your aperture a clean install or an upgrade like mine?
    Yes upgraded from 1.5.6 to 2.0 and now 2.1.2
    If an upgrade, did you move an old aperture library or did you export all of your pictures as projects and re-import them to a clean aperture library as I did?
    Library was upgraded when the Aperture opened it in V2.0 - no did not bother to do what you did.
    Did you purchase your Aperture 2.0 some time ago (when it first came out?) or in the last month as I did?
    When it first came out. If you purchased it last month, it should have most, if not all of the updates.
    Are you on PPC or Intel as I am?
    On Intel - in fact on MBP like you, just 15" instead of 17"
    Are you on a platform with a GPU or integrated graphics like I am (Shouldn't make a difference for this but...)?
    To be clear, MBP has a dedicated GPU and not integrated graphics like MB.
    Do you have the D300/D200 write something into the exif headers using the copyright or image comment as I do?
    No image comment but Copyright, new feature since firmware 1.1, on D300.
    Do you keep your machine meticulously clean or do you have lots of software installed like I do (xcode, office 2008, vmware, macports)?
    I try to keep it clean as much as possible. Meaning that I clean out temp and cache out and try to keep the system up to date. As for apps, yes, yes, Parallels instead, and no, respectively. Have lots of other sw installed.
    Do you have other pro apps like I do (final cut)?
    No final cut.
    Do you have iLife 08 installed like I do?
    Yes. Also iWork.
    Would you be willing to swap a raw image from your D300 with a raw image I have and try to cross-import into each others libraries to prove beyond a shadow of a doubt that this is related to unique aperture installations (mine being a "bad" one) or that it is a setting/configuration issue on a per camera basis?
    Actually, this test does not do anything. I don't recall the exact thread but it is here in the Aperture Forum, that stated that if you use a card reader (which is what I do), then there are no issues importing D300 nef files. But if you hook up the camera direct, then the issues you have articulated exists.
    That might explain why some people are troubled by this and others are not.
    Btw, I have D70 as well and have no issue with the nef files from that camera as well.
    It seems to me that there is an issue. But there is also work around if you import via card reader. I realize one should be able to do whichever and not encounter any problems but I do believe it is not a major issue or deal breaker so to speak.
    Cheers

  • Nikon D300 and Mac OS_X 10.4.11 and Elements 4.0 and iPhoto 6.0.6

    I have updated Elements with the Camera Raw plugin to handle the D300. My understanding is that iPhoto 6.0.6 does not support RAW and the D300. Please suggest a workflow to get RAW image from my camera into iPhoto----I assume I would somehow import RAW data to Elements and then convert the finished product to jpeg to send to iPhoto....or can I have iPhoto point to the RAW image in Elements. Assume I am as ignorant as this question may be.

    Mark,
    Download the free Adobe DNG Converter 5.2 and convert your Nikon raw files to raw DNGs first, before running them to through ACR hosted by
    Elements. All versions of ACR starting with 2.4 will open raw DNG files.
    I can't help with iPhoto. I only launched it once, years ago. You may have a reason for running it.
    Don't forget to download the Adobe DNG Converter version
    5.2
    or even the Release Candidate 5.3. The Adobe DNG Converter 5.2 is a stand-alone application that you run independently of any other program.

  • When will there be ACR/LR support for Nikon D300 and D3?

    Sorry, could not resist.

    ACR/LR are hardwired to be unable to support any Nikon camera that has a "3" in the name. It would take a massive rewrite of the code to circumvent this limitation.

  • Photoshop CS3 and Nikon D300s = BUYER BEWARE

    I recently purchased a Nikon D300s and noticed an error message when I try to open RAW files in Photoshop CS3. I checked for an upgrade to the Camera Raw plugin and guess what? The upgrade that includes the D300s is only available for Photoshop CS4.
    I called Adobe and they confirmed not only that I have to upgrade Photoshop but that because I purchased the Adobe Creative Suite, I have to upgrade the ENTIRE suite and CANNOT upgrade just Photoshop.
    I'm not a programmer but it seems to me that when they upgrade Camera Raw (which they've done several times in CS3) all they do is add support for new cameras. I doubt there is so much programming being done that this pluging update cannot be supported by CS3. It's a complete rip off.

    I doubt there is so much programming being done that this pluging update cannot be supported by CS3.
    Oh, so the engine from 2010 Prius can be fitted into your 73 pinto without any problems?
    Yeah, it's sorta like that.

  • 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

  • New Nikon D3, D300, and D700 "Camera" v3 beta profiles

    Hi everyone,
    I have posted a zip file containing updated "Camera" color profiles (Camera Standard, Camera Neutral, etc.) for the Nikon D3, Nikon D300, and Nikon D700. The zip file contains a copy of the readme, but I'll post it here for convenience, too:
    For lack of a better name, I am calling these "v3" beta profiles.
    BETA RELEASE NOTES
    Overview
    These updated Camera v3 beta profiles for the Nikon D3, Nikon D300, and Nikon D700 are designed to reduce banding and highlight color artifacts. They also address the "too bright" tone curve issues with the previous "v2" version of the D3 and D700 profiles.
    IMPORTANT NOTE: When using these v3 beta profiles, if you wish to match the default tonality of Nikon's Picture Controls (e.g., match View NX / Capture NX), you must set the Exposure slider in Camera Raw / Lightroom to -0.5.
    Of course, feel free to adjust Exposure to make your image brighter or darker as you like. But in terms of matching Nikon's default tonality, you must set the Exposure slider to -0.5, or the default will be too bright.
    For workflow convenience, you can use presets in Camera Raw / Lightroom to take care of both (e.g., simultaneously set the profile to "Camera Standard" and set Exposure to -0.5).
    Installation
    If you are on Mac OS X, drag the "Camera v3 beta" folder to:
        /Library/Application Support/Adobe/CameraRaw/CameraProfiles
    If you are on Windows XP, drag the "Camera v3 beta" folder to:
        C:\Documents and Settings\All Users\Application Data\Adobe\CameraRaw\CameraProfiles
    If you are on Windows Vista or Windows 7, drag the "Camera v3 beta" folder to:
        C:\ProgramData\Adobe\CameraRaw\CameraProfiles
    Note that the above path on Windows Vista and Windows 7 may be hidden by default. Check your folder settings.
    Feedback
    The profiles are currently in beta status. Please provide feedback via the online Adobe user-to-user forums here:
    http://forums.adobe.com/community/cameraraw
    http://forums.adobe.com/community/lightroom
    Thank you!

    Vit Novak wrote:
    It's because ACR assumes that exposure slider at 0 actually means exposure correction of +0.5 EV for this camera model, so with expsure slider at 0, upper 0.5 EV of histogram is clipped
    If this bothers you, there is a workaround - convert NEF to DNG, then change BaselineExposure tag in a dng from 0.5 to 0. There are several utilities for this
    Or wait for some future version of ACR where this will be solved
    The BaselineExposure used by the DNG spec and ACR can complicate ETTR exposure. A uniformly lit surface, when exposed as determined by the standard ISO light meter, should result in 0.18/sqrt(2) or 12.7% saturation of the sensor according to the ISO 12232 saturation standard. This is the standard used by DXO and it allows 0.5 EV highlight headroom. For ETTR exposure, no (or minimum) headroom is desired and mid-gray (18% reflection) is 2.5 stops below 100%.
    For example, I exposed a gray card according to the camera light meter reading with the Nikon D3. The resulting 12 bit data number was 497 and the saturation is 497/4095 = 12.1 % saturation, which is very close to the expected value of 12.7%, confirming that the light meter and sensor are properly calibrated. The corresponding pixel value in 8 bit sRGB is 99.8 as shown.
    The raw file can be rendered into sRGB with in camera processing or Nikon NX2, which closely approximates in camera processing. With the Standard Picture Control, the camera sRGB value is 150. This is a hot tone curve and the a highlight with 100% reflectance would be clipped. The table below shows the results with ACR and various presets. If one uses the Adobe Standard camera profile, the sRGB value is 162 rather than the expected 99.8 Other combinations are shown. To get the proper value for mid-gray one must use a linear tone curve (sliders on main tab set to zero and a linear point curve) and an exposure correction of -0.5 EV to compensate for the +0.5 EV BaselineExposure. With no exposure correction and a linear TRC, the sRGB value would be 116, very close to the calculated sRGB value of 117 for mid-gray (18%). However, the linear TRC gives a flat appearing image.
    The take home point is that if you use Adobe Standard with no exposure compensation with ETTR, your images will appear overexposed and lead to cutting back on the camera expoure. The raw file highlights will have values well under sensor saturation.

  • Some Nikon D300 NEF files don't appear in Bridge CS3 (Mac)

    Hi all,
    I'm using a Nikon D300 and just upgraded to CS3 on my MAC in no small part because the D300 was not supported by CS2. I am running into a problem though.
    I always shoot in both JPEG and RAW modes. When I open Bridge I always see each JPEG version of a shot.
    However, only about 50% of the time can I see the NEF (RAW) version of the thumbnail. The rest of the time I only see a generic "RAW" thumbnail with no image. This sporadic NEF viewability carries over to the preview pane when I select such a NEF file.
    Furthermore, Camera Raw cannot open the NEF files that are not visible in Bridge. When I try opening them I get a message saying "Could not complete your request because Photoshop does not recognize this file type."
    I have tried purging the Cache (through Tools) as some indicated in other forums threads but this has not helped. I have also downloaded the ACR 4.4 plugin and installed it in the correct library location.
    Has anyone else experienced this (whether on a Nikon or other camera)? Any advice?
    Thanks

    I've finally solved the problem with having only some of my NikonD300 NEF files viewable in Bridge/readable by Photoshop! Jon Michael Riley had said he was having similar problems so I wanted to make sure he and anyone else has the info on what worked for me.
    The issue does not have anything to do with purging the thumbnail cache or installing the latest version of Camera RAW 4.4.1. While they were good suggestions (offered by Adobe's Technical support people also), they do not resolve this particular issue.
    I read that an earlier version of what Jon described as "Nikon's clunky software" had corruption issues when images were first transfered from the camera via Nikon PictureProject Transfer. It looks like the latest incarnation has the same issues. Nikon products can see the transfered images without a problem. HOWEVER, Adobe Bridge/Photoshop cannot rectify the corruption issue caused by transferring photos using Nikon's utility.
    So here's the solution: DO NOT use Nikon PictureProject Transfer! It is a piece of garbage! Instead, make ADOBE PHOTO DOWNLOADER the default tool to transfer images from the camera. To make it default do the following:
    Open Bridge, pull down the Bridge CS3 Preferences. Select the "General" preferences set. On this screen you will see "Behavior". The first clickable box reads "When a camera is connected launch Adobe Photo Downloader". Select this box to render this the default transfer tool.
    If you still have the pictures on your memory cards you can re-transfer them using Adobe Photo Downloader. All your NEF files should now be readable by Bridge/Photoshop. I've told Adobe Tech Support about this problem with Nikon's software. Hopefully they'll be able to check this as an option if others call in with similar problems.
    Unfortunately I have not figured out how to repair the corruption in the files I transfered earlier using Nikon's piece of garbage software. Since I don't have the images on memory cards anymore I can't just re-transfer them. Does anyone have any thoughts on how to do this? Will I ever be able to access my earlier NEF shots?
    Cheers,
    Greg
    Thanks to everyone for trying to help resolve these issues.

  • How can i import raw files into iphoto from my Nikon D300?

    Just got a Nikon D300, and it will import jpg and tff, but not raw (nef) files-i prefer iphoto to their software- Nikon says to try talking to apple to find a way to do it- does anyone know any info that can help? I need to decide if I am keeping the camera-from other posts it doesn't look like buying aperture will help either- thanks.

    I would not ditch a camera because of this! If you like the camera, there will always be a way to import Canikon RAW files, though you may need to do some upgrading, and it may take some time for Apple to support a new camera.
    Message was edited by: Keith Barkley

  • Nikon D300S Unsupported Images

    Just purchased the new Nikon D300s and on attempting to load images (.Nef Files Camera Raw Format ) aperture tells me the its an unsupported image - I have a Nikon D200 and its no problem with .Nef Files/
    Any ideas folks?

    That's really not accurate at all, since there are many programs that can do RAW conversion without any special support from the OS. Lightroom can convert D300s nefs, as can capture nx2, and several others, all on Leopard or Snow Leopard OS. The fact that Apple usually (but not always) adds new cameras to its RAW support through an OS update doesn't make it an OS function -- sometimes they've had camera raw updates all by themselves. When they do add in raw support for a new camera, their raw support applies all of Apple's programs. But then, when Adobe adds a new camera to its RAW support, that support flows through to all the Adobe programs, like Bridge, Photoshop, Elements, Lightroom, etc. In any event, it's certainly no excuse at all to say that it's harder for Apple to add in a new camera because it's "OS level" while every other developer can add it in much faster. Perhaps a better excuse is that they want to get it right, but that's no comfort to those waiting months or even years (Leica DLUX4/Panasonic LX3) for raw support.
    On another note, Aperture is hailed as a pro photographer's tool. But pros today often buy new high-end cameras, and this makes it difficult to stick with Aperture as your pro tool when you have no idea when your RAW files will be supported. Nikon's new D3s is out now, pros and amateures are buying them, and none can use Aperture for the raw files. And who knows when Apple will support it.
    Just my two cents.

  • Ap Crashes after connecting camera (Nikon D300) to computer for Tethering..

    Using Aperture in a "tethered" photo shoot, I connected a Nikon D300 and it was working fine. I hade to do a battery change on teh camera and when I turned the camera back on Aperture crashed. Restared computer twice, Aperture lauched just fine, BUT afte connecting the Nikon D300 to the computer Aperture was not responding. However I would disconnect the camera and Aperture was fine. Bottom line I had to cancel the Tethered shooting because aperture continued to stall when I connected the camera. Any thought? Please advice.

    Something I forgot to mention was that I shot 2,616 pictures yesterday when this happen. It crashed at like picture 2,245. I was shooting models and it was one shot after the other for like 13 hours straight.
    However, today I decided to trash some older pictures to make room for part 2 of the shoot this coming weekend. I got home and I tried tethering again and wallah, it worked. I tried another camera as well a D60 and it worked. So can we say that it was a system overload? Would that be a good assumption?
    Should I go in to the preferences and dump prefs? Any thoughts on this would be good.
    P.s Prior to the deleting of my older stuff I have like 9gigs available in the hard drive, after deleting I had 27 gigs left.. Just a note!
    Thanks in advance!

  • Using Aperture with an external Hard Drive and my new camera (Nikon D300s)

    I have an older MacBook pro- basically had option upgrade comp or camera- went with the new Nikon D300s... my pro was maxed out so a friend helped me transfer my library to my external Harddrive (had a tra- after transfer of my library looking at only 721mb left (just a few photos)) but here is the issue- we have it set up when i load my cards that they go right to the external- but two things happen- my raw photos show as 'unsupported format' AND I can't figure out how to edit.... seriously so frustrated I am ready to go with a micro-puker computer and photoshop... this is NUTS! any help... o and I run AP 2 and I ain't dumping any more money in apple until they can show me they are working again... this is eating my profits!

    Well... I am going to say I am not ashamed to admit that I am not 100% sure. I basically gave my computer to my friend who is a computer guru as I was trying to download my first shoot with my new camera and I got a "not enough memory" message- and kinda freaked out.
    I have a WD external HD so it is mac friendly-
    I don't know how he moved it-- I know he said when he set it up to transfer it took close to 14 hours as it is USB (I know I can and should get a firewire port for it) - and to be truthful I don't know if it is referenced or managed. I know that I plug in the external and make sure it shows in on my computer then plug in my card reader and when i plug in my CF card... aperture opens and I set up a new project and it saves to the hard drive... yet is still showing on my aperture lib- so I am confused... and of course my "free" apple care ran out 6 months ago so I can't just call them or drive to denver and have them show me the solution... and I need one as I have a HUGE photo job in like 4 days

  • Nikon D300 Raw Images and Lightroom 1.4.1

    My updated 1.4.1 Lightroom and 4.4.1 Camera Raw are not reading the raw images from my new Nikon D300. I have read several strings of conversation from other folks who are having this problem, and from what I am reading, my 1.4.1 Lightroom should be recognizing them, but it's not. Any help would be MOST appreciated.
    Frank Leonard
    [email protected]

    Before you even answered I transferred the files from my camera card to my hard drive, and presto bingo, they are now importing beautifully into lightroom. THANK YOU LEE JAY!!!!! Frank Leonard - [email protected]

Maybe you are looking for