Nikon D300 imported files not rotated.

When I import vertical (portrait) shots, they appear in landscape (horizontal) mode.  Does anyone know what setting in Lightroom or in the camera I need to set?  I've tried "Rotate Tall both on and off" on the camera to no avail.

In the camera go to Setup Menu (the little wrench) and turn on Auto Image Rotation.

Similar Messages

  • Newbie Q - nikon d300s avi files not recognised - wants codec.

    I have just installed elements 9 and start a new project - i have some nikon d300a avi files on my hard disk and want to create a video. However when I try to import the files the program says this files are not recognised or the codec might be incorrect. What am I supposed to do now? thanks. Phil

    Well, CODEC's are odd little things. Some will work fine in some programs, and some will not.
    This ARTICLE goes into more detail, though cannot cover all possible CODEC's, or all possible NLE programs. When it gets down to why one might work with program ____, but not program ____, I call upon Chief Dan George, "sometimes the magic works, and sometimes it does not."
    Good luck,
    Hunt
    PS - did you install a driver for the Nikon, and/or any software provided? It could well be that Sony's Vegas has an MJPEG CODEC in its installation, but PrE just cannot use that. Normally, if one has the MJPEG CODEC from the camera mfgr. things work OK.

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

  • 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

  • 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

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

  • Bridge 2.1.1.9 problems with Nikon D300 NEF files

    I am getting a few Raw files from my Nikon D300 that will appear properly in Bridge, but the majority either don't show a preview at all or are very pixelated in appearance. The ones that do appear fine can be opened in ACR by right clicking and selecting "open in camera raw". However, the others that don't appear properly don't even show the option to open in camera raw. Yet the files are okay, because I can then open them from within Photoshop and process the files like that. The other odd behavior is that if I right click the thumbnail and rename the file then the thumbnail preview suddenly appears properly. Lastly, the pixel dimensions show incorrectly until the file is renamed.
    I am using Windows XP SP2 with Photoshop CS3. Any suggestions would be appreciated. This has been very frustrating because initially it appears that the file may be corrupt.
    Thanks!

    This might not be helpful as I do not know why but .. I have a D300, and while Bridge is its usual flakey self, it has worked fine with the file formats. I tried all the combinations of compression and 12/14 bit and bridge sees them.
    I do have cache weirdness, where it seems to reprocess them repeatedly, as though it is forgetful, but it does process and resolve them.
    I've experimented with the "high quality previews" on and off, and when off the quality is definitely lower. Secondly if it is processing (or reprocessing) its cache, I see weirdness in the display where it may not display the quality preview either for a very long time, or not at all. But generally I've had no luck getting bridge to be usable while it processes its cache for a directory, I just let it finish and then use it.
    However none of these flaky issues have been D300 specific, and been using it for a couple months now, and also with a D80 from my wife, no difference.

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

  • Imported files not showing up in folders

    I've imported .psd files into a folder of .dng images so I can stack them with their originals. They were all saved with Max Compatibility and LightRoom seems to import them ok, but they don't show up in the grid or filmstrip. Their folder listing has a + sign by the file total and in the folder hierarchy on the filmstrip panel it says that it's showing 82 of 95 photos. How can I get these .psd files to appear?
    If I check the actual folder on the hard disk, the .psd files are there. If I remove them from the folder and try to re-import them, I get a message saying they are already there.
    This hasn't happened every time I've done this action, but a number of my folders show this problem.

    For *.jpg and *.nef (RAW) files the handling is similar:
    If there is a *.nef (RAW) file in the source directory, a *.jpeg with same name will be copied by LR into the destination directory, but the *.jpg will not be included in the LR database.
    The problem is, that LR does not report this to the user. LR should open a popup window after import listing the files not added to the database (as it does for duplicates).
    Personally I'd find it better if LR would import everything to disk AND database. It should perform an automatic stacking for files with same name but different type. The RAW or DNG should be on top of stack of course.

  • Import files not successfully uploading/rendering

    I'm having trouble importing files successfully. Just tried uploading a batch of about 20 clips. Maybe 3 actually successfully rendered and appeard with a corresponding thumbnail in my Event window. The rest appear as an image of a white document icon and yellow caution sign on a red background. I never used to have this issue. Recently I installed OS X Mavericks and have really struggled to succesully import clips. Sometimes I have to upload 5, 6 or even 7 times to get all of the clips I need into the events page.
    Anyone have advice? Thanks!

    Nope. Not a pirate. Admittedly, I have been using this version for some time, and I don't get prompts for software updates. I'll make sure I do this now. Didn't realize the solution was that simple. Thanks for your help.

  • Importing files not in name order

    When importing files from my pmw 200 it wont put them in name order . Hence when selecting them and automating to sequence my footage is all mixed up and is not flowing in the order it should be in  if any one knows whats going on please help ......

    We struggled with this too for awhile, just because we wanted to view the clips as icon (like everyone does) but in the order we took them.
    Depending on which version of Premiere you are using you can now select a sort order in clip bin window itself by clicking on 'Sort Icons' icon at the bottom of the clip bin (next to the zoom bar) and choosing 'List View Sort'. This should give you them in the order that they were taken. It's reverts though everytime you open and close the project, which is a pain.
    Better solution is this though and it works for older versions of the premiere too. First, view the bin as a list view (bottom left icon) which should order them in the order you want or click on the column headers to get the correct order you want them to appear in. Then create a new empty bin, select icon view for this window and then select all the clips and drag them into the new bin. They should retain the correct order but be viewable as icons and they'll stay in that order forever more!

  • Imported files not recognized

    1) I launch iTunes
    2) I plug-in my iPhone
    3) I see the GB application installed on the iPhone
    4) I click on the GB application icon in iTunes
    5) I drag the files from my backup from desktop in to the application window
    6) iTunes is copying the files to my iPhone
    7) iSync my iPhone
    BUT
    the files do not appear on my iPhone when I launch the application
    ??? ... empty ... nothing
    any iDeas ???
    THANK you

    OK ... I need to click the ( + ) icon on iPhone under GB and select "Copy from iTunes Files Sharing"
    gosh ... same procedure for every single file ... and I though sync is sync and then it's synced.
    it's like importing files 2 times ... how godfather complicated!!!

  • Imported files not found

    Hello,
      I am trying to set up Audtion for my students to practice on.  I have loaded the "Sky Cell Tel" files from the Audition "Classroom in a Book."  This is what I have done:
    1. I copied the files from the CD to a folder created specifically for the class using copy/paste in My Computer. I do this so we aren't working with files off the CD, but rather permanently on the harddrive. The files copy over and are  present. A check of the properties show the full file content is present. They also play back in Windows Media Player.
    2. I launch Audition. I click on File, Import and direct the import to the Sky Cell Tel files in the the folder I put them in. The files load into the "Files" tab. I test the files and they all play in Audition using the play button in the files tab.  To give my students a "start from scratch" approach I do not load any files into the timeline.  I save the Session As ... and close Audition.
    3. I then re-open Audition and then open the previously saved Session.  When I do the files that I had previously imported are not present in the Files tab.  Where are they???  I am expecting the saved Session to show the imported files as any other editing program I have used.  Note, if I use a file in the timeline..., THEN it shows in the File tab upon reopening  the saved Session. But files not used in the timeline do not show in the Files tab.
    I think my frustration in obvious.  I  insure the files are permanently on the harddrive. I Import the files. I save the Session. Latter, upon having a student re-open the Session the imported files are not found. Embarrassing and frustrating.
    Any help would be appreciated.
    Thanks, Tom

    I presume we're talking about AA3 here. Yes, a file doesn't get associated with a session until it has actually been used in it - it's always been like that. Normally this isn't an issue (or if it is, nobody's ever mentioned it here before), but I can sort-of understand your frustration. My take on giving students a real-life experience in this situation might perhaps involve a little chat with your network manager, depending upon how you've got your network organised. Give each student their own file storage area that they have to log into, and put copies of the files in each of them, and get them to have the complete experience by loading the files themselves. They'll soon find out what happens to files they don't use...
    I think that the issue with saving sessions having unused files in the file window is that the way the .xml is structured, you only get entries which have time stamps on them. If a file isn't used, then it's not associated with any time stamps and is regarded as not part of the session at save time. It's completely logical, I'm afraid - although frustrating for you!

Maybe you are looking for