Skip navigation

Incredibly slow rendering when editing raws from the new Nikon D800

4520 Views 22 Replies Latest reply: Sep 16, 2012 2:53 PM by vdrummer RSS
  • CalxOddity Level 3 Level 3 (680 points)

    Hi,

       I had the same experience when changing from my Nikon D40 to a D5100.  The raw image file went from 5MB to 20MB and the responsiveness of brushed in adjustments declined noticeably.  It's still usable, but there are more page outs happening than there used to be.

     

    Maybe do some benchmarking of a D800 raw versus another camera raw versus a similar sized tiff????

  • motomongrel Calculating status...

    I don't know how relevant you will find this info about my workflow but here goes. After purchasing my D800 I discovered that I could not use the cd to process the raw files because the 10.4.1 os of my iMac was too old.

    My macBook has os 10.6.8 and could not use that either. Both have 2gb of ram. Not being able to spend more money on any type of upgrade of hardware, I decided to use Adobe DNG converter. There was a version I could use on the macBook, so I downloaded that.

    So the workflow is like this:

    1. Download from card to folder on desktop of macBook.

    2. Do DNG conversion in a  folder in USB external hard attached to macBook. This doesn't take as long as I thought it would. Btwn 10-15 mins for 100 or so raw images.

    3. After conversion, I'm able to work on either computer using Aperture. Processing goes fairly quickly with no real issues, only an occasional "spinning ball of death".

     

    I don't think that this is the ideal way to do work, but it didn't cost me anything. I do believe however that the conversion to DNG is not as color accurate as being able to dump everything into Aperture. But I can live with this and make the necessary adjustments. Creating the new tiff files to me my client's requirements (400 ppi) at native size results in files over 100mbs.

    There is a fair amount of moving files around and I had to get rid of a lot of old apps that were taking up space, but didn't gain as much hard drive memory as I would have liked.

    The take away here is that I found a way to make it all work. A interesting observation is that the .dng files seem to cause less lags in processing than the native .nef.

     

    I hope that this helps some of you out there. If anyone has a suggestion that might improve all of this, I'm all ears.

  • motomongrel Level 1 Level 1 (0 points)

    I don't know how relevant you will find this info about my workflow but here goes. After purchasing my D800 I discovered that I could not use the cd to process the raw files because the 10.4.1 os of my iMac was too old.

    My macBook has os 10.6.8 and could not use that either. Both have 2gb of ram. Not being able to spend more money on any type of upgrade of hardware, I decided to use Adobe DNG converter. There was a version I could use on the macBook, so I downloaded that.

    So the workflow is like this:

    1. Download from card to folder on desktop of macBook.

    2. Do DNG conversion in a  folder in USB external hard attached to macBook. This doesn't take as long as I thought it would. Btwn 10-15 mins for 100 or so raw images.

    3. After conversion, I'm able to work on either computer using Aperture. Processing goes fairly quickly with no real issues, only an occasional "spinning ball of death".

     

    I don't think that this is the ideal way to do work, but it didn't cost me anything. I do believe however that the conversion to DNG is not as color accurate as being able to dump everything into Aperture. But I can live with this and make the necessary adjustments. Creating the new tiff files to me my client's requirements (400 ppi) at native size results in files over 100mbs.

    There is a fair amount of moving files around and I had to get rid of a lot of old apps that were taking up space, but didn't gain as much hard drive memory as I would have liked.

    The take away here is that I found a way to make it all work. A interesting observation is that the .dng files seem to cause less lags in processing than the native .nef.

     

    I hope that this helps some of you out there. If anyone has a suggestion that might improve all of this, I'm all ears.

  • SierraDragon Level 4 Level 4 (2,665 points)

    OP: Have you performed the (simple) test for RAM page outs that I described? If so what were the results?

     

    -Allen

  • toby snelgrove Calculating status...

    Welcome to huge MB files ... I am on lighroom and often make a coffee while rendering images ... Photomatics and PS are also slow ... 8 gig of ram 10.7.4

    It is all about file size.

    I am thinking computer up-grade soon ... or take up sailing ... just a slow.

    Cheers.

    Toby

  • vdrummer Calculating status...

    Once I have Aperture 3.3.2 loaded and project selected, my D800E RAW files finish loading in about 3-5 seconds, as I click from one image to another.  D800 files aren't really taking much longer to load or work with than D700 NEF files.  Editing with Nik plug ins might be a little slower.

     

    Results are always about the same with three different systems:

    late-2011 macbook pro, 8Gb ram; libraries on internal SSD and external thunderbolt

    spring-2012 macbook air, 8Gb ram, library on internal SSD

    early 2008 macpro, 10Gb ram, library on internal RAID drives

  • SierraDragon Level 4 Level 4 (2,665 points)

    vdrummer-

     

    What are your experiences with the D800e? Do you find significant moiré or artifacts that you have to deal with in post-processing?

     

    Cash is tight and I am debating whether the e version is worth the extra money to me. If cost was no object I would say it is, but cost is a big deal so I guess I am looking for excuses not to pay the extra 10%... 

     

    Thanks.

     

    -Allen

  • vdrummer Level 1 Level 1 (0 points)

    haven't seen any moiré at all - up to about 2,000+ images, mostly all landscapes.

1 2 Previous Next

Actions

More Like This

  • Retrieving data ...

Bookmarked By (1)

Legend

  • This solved my question - 10 points
  • This helped me - 5 points
This site contains user submitted content, comments and opinions and is for informational purposes only. Apple disclaims any and all liability for the acts, omissions and conduct of any third parties in connection with or related to your use of the site. All postings and use of the content on this site are subject to the Apple Support Communities Terms of Use.