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.

Similar Messages

  • Nikon d300s .avi files workflow

    I was wondering if anyone else on the forum has ever shot video with a Nikon DSLR and then edited with FCP? If you have, what is your workflow? What I ended up doing is importing my .avi files from my Nikon CF Card onto my external hard drive. I put the files into my scratch disk and then imported them into compressor. I turned them into QT movies and put them BACK into my scratch disks. Then I imported the QT movies into a new FCP Project browser and the files behave properly in the timeline and viewer. Is this an acceptable way to manage these kinds of files? or is there a better, more efficient way?
    I have found a couple of suggestions around the forum about how to mange files from a dSLR, but I would really like to hear from a Nikon shooter who uses FCP. Ultimately, I am going to purchase a dedicated video camera in the future, but have to stick with what I have for right now.

    The D300s files must be converted into an editing codec.
    You can use Compressor, or use MPEG Streamclip.
    Here's a tutorial on how to accomplish this.

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

  • HELP! Premiere CS5 crashes when importing Nikon D300 avi

    Just purchesed CS5. It crashes when importing Nikon D300 avi files (which is why I upgraded from CS4 in the first place.

    vista 64 (home premium)
    8 GB RAM
    Intel quad core CPU 2.66 ghz
    array of 720 drives (800gb free)
    nvidia 9800 dual monitors
    mainconcept codec
    workes fine for CS4
    system crashes instantly when I select a nikon file to import.

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

  • Can I use my Nikon D90 AVI files in Premiere Pro CC on my iMac?

    Hi and thanks in advance to anyone who can lend me a hand. I am new to both Premiere Pro CC and Macs. I have used my Nikon D90 AVI files before with Premiere Elements on my PC with no problem, but the same films aren't working on my new setup with Premiere Pro CC and an iMac.
    I can see and preview the films in the Source window but when I try to drag them onto the sequence window I get a little hand with a "no" sign.
    I am using a version 7.1.0 (141) of PP CC and am on OS X 10.9
    Do I need to transcode the files? If so, to what? And what is the best way to do that?
    Many many thanks for any help!

    Just remember, you will not always get the answer you want right away. Some people will point you to tutorials, some, like me, will attempt to help and still point you to tutorials, and some will just answer the question as best they can.
    Some might insult you, and some merely insult your intelligence. Don't be offended. Do, however, search the forums as best you can in an attempt to find the answer before you post.
    I realize that people don't always have the right words to describe the problem, and therefore have trouble searching. If searching fails you, just ask. It generally works out in the long run. And as you have discovered, sometimes a combination of posts may do the trick.

  • .AVI files not showng when RAW Only selected at import time

    Hi board,
    When I am looking at my SD card from my Nikon D90 in the Import view of Aperture I have the 'Raw Only' option selected for the RAW+JPEG Pairs setting. This results in .AVI files not showing up in the browser. Meaning that when I believed I was importing all my photos in RAW and my movies, my movies were actually not even considered for importing. I realize (now) that RAW Only quite litteraly means RAW Only, but why do I have to select Both when importing to get my movies? Then I would have to weed out any eventual JPEGs that I might have taken but do not want to import.
    I'm simply curious why .AVI are excluded together with .JPEGs. I did not consider this to be intuitive or clear to the user (since the setting is called RAW+JPEG Pairs, not mentioning that it could possibly exclude movies).
    Thanks!

    Same here, with Aperture 3.2.2, OS 10.7.2
    That definitely seems to be a bug to me; if either "JPEG only" or "RAW files only" is selected, the File Types selector is ignored, and no audio or video media are available in the import panel.
    Regards
    Léonie

  • 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

  • Macs and aiff files not recognised by older hi fi.?

    I have burnt audio cds using external burner(itunes 8).They are on the cd as it plays in the mac but will not play on our cd player.Iread something online about macs and aiff files not recognised by older hi fi.
    http://en.wikipedia.org/wiki/AudioInterchange_FileFormat
    any help please

    Several possible issues.
    1) Did you burn the CD as an audio format CD or did you just burn AIFF files to a CD as a data CD? CD players require an audio format CD, not just AIFF files burned to a CD as AIFF files.
    2) Older CD players can have problems reading burned CDs. Sometimes using a different brand CD, a longer burn time (slower burn speed) can help, but sometimes you just have to buy a newer player. CD-RW can present big problems unless it is specified as supported.

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

  • Nikon D40 and RAW files not recognised by Aperture

    Please advise - the RAW files on my D40 are not recognised by Aperture (or i-photo) what to do ? will this be offered in time and if so how long ?
    ARC

    Have a search here. This question has been asked and answered already.

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

  • 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

Maybe you are looking for

  • BPM -- Reprocessing from failed point.

    Hi Friends, I am developing a BPM of 3 send steps. 1st will retrieve the records from a table(using JDBC adapter) and second send step inserts the same records into another table(different system). when insert is done, status is updated into 1st syst

  • Multipage Printing

    Hello, I have to print multiple pages with images, a header and a footer. And I don't know the length of my text and images that will be on the pages. The only thing I do know is that it can be split after each piece of text/image and the pieces will

  • SaxParser problem

    Hi everyone, I am using the SaxParser to parse an xml data. My problem is how to pass a String object directly to the SaxParser? I have little knowledge about this parser but what I have learned so far is that, an xml file should be passed to the par

  • Fcp wont load cause of audio plugins

    Hi. I work on Fcp studio and Logic pro. I have a lot of audio plugins for Logic espescially waves. But now fcp wont load cause it crashes when it gets to a certain plugin. I don't want to use audio plugins in fcp as I do my audio in logic. Why has fc

  • 'assert' in Eclipse @ 1.4

    Hi, I am coding the following line in Eclipse: assert true;The IDE keepsgiving me compile time error: Syntax error on token "assert", AssignmentOperator expected after this token.It does not like the syntax. My Java compile level is at 1.4, and ofcou