Nikon D90 image files slow down bridge...even more

We are running windows CS3 with ACR 4.6 and all my other Nikon files are fine in bridge, but when myself or a colleague try to use any file type from the D90 bridge comes to a grinding halt. We are trying to get approval to update to CS4 but it takes a while in my company. Is the upgrade to CS4 or Lightroom the only way to fix this? I believe that ACR update 4.6 was the last one for CS3, is this true? Thanks people.

Thanks for your response Curt. Maybe I exaggerated a lttle when i said Bridge comes to a grinding halt, it does display the images clearly and allows me to do pretty much every task i need to do but it takes around 10 times as long as with any other camera file. If i attempt anything clever like batch process or adding metadata to multiple images then it crashes. I know bridge isn't lightening fast but the difference between files from my other camers and the D90 is astounding. No I don't use a card reader, direct upload form the camera to a hard drive. and Yes it has the same effect on the jpgs and nefs. cheers mate

Similar Messages

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

  • Why does Acrobat Pdf converter file slow down my 2003, Windows  Word Program.  I only experience this problem when i convert a pdf file to a doc file.

    Why does Acrobat Pdf converter file slow down my 2003, Windows  Word Program.  I only experience this problem when i convert a pdf file to a doc file.

    Hi Bill -- thanks for your reply!
    When I check the Document Properties on Acrobat I can see that the fonts used in the document (Cambria, Times and Windings) are listed as "Embedded Subset" in the Fonts panel. The machine it was created on did use an earlier version of OS X and an old version of Word, but it seems to have the proper fonts...
    -nick

  • Hi, my iphone 4s shuts down randomly, Apple told me the phone is fine, I did a 2nd restore, deactivated iCloud, and no the frequency of shutting down is even more, any help please ?

    Hi, my iphone 4s ios 6.0.1 shuts down randomly, Apple told me the phone & battery are fine as it holds a charge, I did a 2nd restore, deactivated iCloud, and now the frequency of shutting down is even more, any help please ?

    It's almost impossible to say whether it's the battery or something else.  If you're running 6.0.1 and you've done a restore and set it up as new, there are no other software updates to try.
    If there's no Apple Store near you, contact Apple Care. If  you can't wait for a replacement phone, you may be able to get an express replacement (they ship you the replacement before you ship them yours, but they will put a hold on your credit card until yours is in their hands).
    http://www.apple.com/support/contact/

  • Nikon D90 images not in import screen

    I recently purchased the Nikon D90 and of course I am playing with it this weekend. The images appear fine once imported into Aperture, however, the images do not appear on the import screen. At this point the images are still on the SD card in the camera. Currently they only appear as a grey box. The images will import into Aperture but the images don't appear on the import screen.
    Has any one else had this issue? Had did you do for the photos to appear in the import screen?
    Thanks

    What you describe is IMO a workflow problem because IMO importing original images directly into any images management app is bad practice. IMO Aperture should not even allow direct card-to-Aperture import because it is not safe images handling practice.
    Take a look at the suggested workflow below.
    IMO generally most useful to help keep drives underfilled and fast (drives slow as they fill) is to manage by Reference ("referenced images") as in the workflow outline below where Master images can live anywhere. However with small changes similar workflow could be applied to Managed Masters.
    I feel pretty strongly that card-to-Aperture or even camera-to-Aperture handling of original images puts originals at unnecessary risk. I suggest this workflow, first using the Finder (not Aperture) to copy images from CF card to computer hard drive:
    • Remove the CF card from the camera and insert it into a CF card reader. Faster readers and faster cards are preferable, and Firewire is much preferable to USB2.
    • Finder-copy images from CF to a labeled folder on the intended permanent Masters location hard drive.
    • Eject CF.
    • Burn backup hard drive or DVD copies of the original images (optional recommended backup step).
    • Eject backup hard drive(s) or DVDs.
    • From within Aperture, import images from the hard drive folder into Aperture selecting "Store files in their current location." This is called "referenced images."
    • Review pix for completeness (e.g. a 500-pic shoot has 500 valid images showing).
    • Reformat CF in camera, and archive originals off site on hard drives and/or on DVDs.
    Note that the "eject" steps above are important in order to avoid mistakenly working on removable media.
    Good luck!
    -Allen Wicks

  • Cannot Open Nikon D90 Raw files in Photoshop Elements 7

    Does anyone have advice on how to get Photoshop Elements 7 to read Nikon D90 Camera Raw (.NEF) images? When I try to open one of these Raw images, I get an error message saying that the program does not recognize that file type.

    The D90 was supported as early as ACR 5.1 so you should download the PSE-specific version of ACR 5.6 from http://www.adobe.com/downloads/updates/ via the drop-down list at the top, and following the PSE-specific link and instructions.

  • Why only 10-bit depth dng files from 16-bit Nikon D90 nef files?

    When I convert 16-bit .nef files from my Nikon D90 to DNG I get only 10-bits depth.
    Since the camera should be producing 12-bit depth it seems I am losing information in the conversion, and I don't want that.
    I have installed the 7.1 DNG converter, and I suppose that is what is used when I download from camera memory card through Bridge 5.1 and click dng conversion.
    Same thing if I open the .nef in Photoshop 5.1 , which kicks up CameraRaw converter 6.7.0.339.
    Why is this?
    Can't .dng have more than 10-bit depth?
    Sverk

    Well, according to the user manual and to the review in
    http://www.imaging-resource.com/PRODS/D90/D90A.HTM
    the D90 delivers 12-bit color depth in the .NEF files.
    Of course, I haven't looked at the actual pixel data to find out how finely graded they are.
    What I'm looking at is what Bridge 5.1 (WindowsXP) says about the files in the
    Metadata/ Bit depth entry. 
    In that, the .NEF files are listed as "16-bit" depth (although it will actually hold only 12-bit resolution), but when converted to .DNG it says only  "10-bit",
    and that holds both when the conversion is done automatically during the importing from the camera, and when converting from .nef files afterwards.
    Archiving pictures in the .dng format seems to be a good idea -- but only if no information is lost in the conversion.
    Thus, the "10-bit" info showing in Bridge worries me.
    Might it be that the meaning of bit depth is different in the two file formats?
    Might there be something about the de-mosaicing that necessarily consumes two bits of depth?   Whether in the .dng conversion -- or when saved .nef files are later to be used?
    In other words, for practical purposes, are the formats equivalent in color resolution,
    Or is there indeed a certain loss?
    Maybe a very difficult question, but I'd sure want to have a technical ly definite answer before I dare switch to using the .DNG format all the way.
    Sverk

  • Nikon D90 RAW files

    I just got a Nikon D90 yesterday. I found that Aperture won't open RAW files from the D90. It looks like they changed the format, since RAW files from my D40x worked beautifully.
    I get this "unsupported image format" when I try to view a NEF file.
    Uploaded with plasq's Skitch!
    Message was edited by: mike3k

    Hi, You are not alone. i have a new D700 and have the same problem. Apple service have been very helpful and have informed me that every new camera needs to be manually added to the list of cameras that work with Aperture. They have confirmed support for the D90 and D700 will be in the next update; but when I have no idea. It really is a pathetic updating service - they need to release a small patch within a week of a new cameras release. Canon also have a series of new models being launched in the next couple of weeks. None of them will work!!! Come on Apple you can do better than this!!

  • Camera Raw 5.1 downloaded and unzipped but not working in CS4. Can't open Nikon D90 NEF files.

    Camera Raw 5.1 downloaded and unzipped but not working in CS4. OS Windows 7. Can't open Nikon NEF files. Camera Nikon D90.

    update the adobe program that needs cr 4.6+,  http://www.adobe.com/downloads/updates/

  • How to deal with Nikon D90 AVI files in FCE 4

    I purchased a Nikon D90 digital camera and it records clips stored in AVI format at 1280x720. When I import the video, a red line appears on the video render status line. Why does the video need to be rendered before making any changes?
    Also, why when importing AVCHD video from my Sony camera, no rendering needs to be done?
    Another question. With the AVI video, what is the best way to export in HD so I can post on the web?
    Thanks for any help.

    as far as I know, the D90 (.. what a beast - and the price!!) records in 30fps, 1280x720 square pixel, MotionJpeg, .avi container ..
    which is +a bit off+ the standards, FCE does support.. = rendering
    I had the opportunity to 'play around' for some minutes with the D90.. and made some 'test'-recordings.. it is really breathtaking to use 'photography' techniqués while doing video, esp. FoD...
    but..
    have you seen that movie done with the Canon 5D II?
    http://www.usa.canon.com/dlc/controller?act=GetArticleAct&articleID=2086
    it offers some more practical features, as automatic focus (=Nikon lacks that), and, even more important, the Canon allows to switch off automatic exposure (=in my tests with the D90, the pic 'pulsated' due to diff. light situaation) ...
    ==edit==
    oops, Canon pulled that video.. too much bandwidth
    absolutely brilliant, perfect photography, even in low light condition, ... but 'motion picture' ..

  • Problems importing Nikon D4s NEF files to LR5, Bridge, Photoshop CC / CC2014?

    Is anyone having a problem importing Nikon D4s NEF files into Lightroom 5, Bridge or PhotoshopCC / CC2014 or Photoshop5?
    I am running the latest updates: LR5.5, RAW 8.4, Photoshop CC latest update which, as far as I am aware, are all supposed to support the D4s NEFs but none will read the files; LR5.5 just shows "Preview unavailable for this file", Bridge just shows a blank and Photoshop shows "Photoshop cannot open this file".
    I have tried 14 bit, 12bit uncompressed; but only jpegs show up??
    All running on an iMAC 2.93Ghz Core i7 mid 2010; 16GB Ram and also on a Mid 2011 Macbook pro 2.2Ghz core i7 with 16GB Ram. 
    Is this camera supported fully yet?
    Is anyone else having similar problems?
    Any ideas?

    You probably used Nikon software to transfer the photos to your computer. This causes corruption of the file so taht Adobe Software cannot read it.
    To uncorrupt the files, see Fix Corrupted Nikon NEF Images

  • Flash causes Firefox to slow down and even freeze (and on a gaming laptop, too). How to fix this?

    Every time I use the Flash plug-in (for videos on YouTube or PutLocker or whatever), FireFox just slows down a lot and even freezes. It happens very often now and it's really annoying.
    By the way, I am using a gaming laptop so I am not sure why I am having these problems. My Flash plug-in and firefox are updated to the latest versions, too.
    My specs:
    Windows 7 Home Premium
    Intel i7-2670QM CPU @ 2.20GHZ (8 CPUs)
    nVidia GTX 560m 3GB vRAM dedicated
    16GB RAM

    Okay, so I uninstalled and reinstalled it. That helped only for about ten minutes and it started doing it again.
    I don't know what else to do. :S

  • Nikon D90 RAW files problem

    Recently uploaded and installed the Aperture 2 upgrade which claimed to add RAW capability to the D90 plus other new cameras, but something is amiss - the files appear in browser windows but you can't do a full screen view of them - I get a "loading" message with the spinning wheel then the image shows up by itself on the screen but the same size as the thumbnail image in the browser window. Can't zoom in or anything either. Anyone else having this problem? FYI checked the about Aperture window which says I'm using version 2.1.2 3G13.

    FIGURED OUT A SOLUTION!
    Sorry for shouting, but should others out there run into this problem, here's how I fixed mine:
    Credit goes to Pogster who in another thread gave the link to get the upgrade or RAW support for the D90: http://support.apple.com/downloads/DigitalCamera_Raw_Compatibility_Update2-3
    I had done the upgrade via Apple's Software Update which supposedly should've taken care of this, but perhaps I did it after originally downloading RAW files from my new D90. Regardless, the upgrade has solved future imports and to correct the existing files (thankfully only 30 images) I first created a new project titled "to fix", moved the relevant images into that project, the went into the aperture library and into the "to fix" file in the library (opened the aperture library package contents and "to fix" project file within it by control clicking), then copied the original NEF files onto my desktop and imported them again into a new project. Then just deleted the entire "to fix" project. Now all is good and the images are the proper size. This approach would be a nightmare for 300+ files, but it did work.
    Thanks for the help out there...
    Message was edited by: Tom Macdonald

  • Binary write to file slowing down my program

    I have noticed this more on some types of computers, but I have two threads going.  One that captures 10MB images and queues them, and another thread that dequeues them and appends to a binary file.
    If I disable the write to file, program chugs along well.  Once enabled, I noticed that the image capturing begins to act sluggishly, almost in sync with the writing to hard drive.  I have tried changing the write loop priority to the lowest as well.
    It isn't holding up at the queue/dequeue step either.  Any pointers on what to try?  I'm almost certain that there is a memory sharing issue where one process is writing to 10MB image to memory, while the other is reading a 10MB image from memory, and this is tying things up.

    dre99gsx wrote:
    The main VI which hosts both of these loops is setup as User Interface
    There's the problem, I think. The user interface subsystem is special - it's a single thread. This is required for certain things (interactions with the operating system and user interface, some external DLLs and ActiveX components) that require a single thread. In general, don't run your code in the user interface system unless you have a specific reason to run it there. As an example, property nodes that refer to front-panel items cause a switch to the user interface thread, so if you have VI that uses a lot of references to update the front panel, that VI should run in the UI system. In your case, if you switch your main VI to Standard and leave the subVIs set as Same as Caller, I think you'll see a similar speed improvement. There's more information about LabVIEW threading here, although that information is slightly out of date; if I remember correctly (couldn't find the reference in a quick search) LabVIEW now allocates as many threads per system as there are processor cores in your CPU, but not less than 4 per execution system with the exception of the user interface.

  • Nikon D90 Raw file.

    Hi.
    I have just got CS4. The trouble i am now having is that it does not recognise the raw file from a D90. It will open my old raw files from a D80 as well as all tiffs and jpegs from the D90. I have looked to see if there is an update availiable but can't find one. Can anyone help please?
    Many thanks.
    Mark.

    Update to Adobe Camera RAW 5.5.
    http://www.adobe.com/downloads/updates
    Each new camera needs a new "profile" that Camera RAW must know about, specifically.

Maybe you are looking for