D800E User Thread


daredevil123 said:
Yup.. RAM and processor is key...

You will really feel it when doing lots of cloning/healing in Lightroom.

For me, my PP machine is workstation.. not laptop.. running 16GB ram and i7-3770. Smooth as butter.. but then again, I am not using D800/e. LOL.

Woah! Your machine must be blazing fast!
 

ok only la. The SSD that runs the OS and key software really helps with the speed.

Things that's will increase image processing speed, in order of importance:

Enough RAM. I think 8GB is where you should start. I have a 64GB desktop.

SSD instead oh Hard Disk Drive. Disk I/O is a huge bottleneck. SSDs are 10-100X faster than hard drives.

Processor. Last on the list. Unless you have enough RAM and an SSD, the processor will mostly be idly waiting for I/O operations to complete.
 

Things that's will increase image processing speed, in order of importance:

Enough RAM. I think 8GB is where you should start. I have a 64GB desktop.

SSD instead oh Hard Disk Drive. Disk I/O is a huge bottleneck. SSDs are 10-100X faster than hard drives.

Processor. Last on the list. Unless you have enough RAM and an SSD, the processor will mostly be idly waiting for I/O operations to complete.

As for SSD, it really depends on the processing software. For software like Photoshop CS6, where a scratch disk is used for swapping and state change saving, the use of a SSD will greatly improve processing speeds. For something like Lightroom, where the display image is rendered, and the actual changes are only executed on export, RAM matters a lot more when working on the edits. Only during the export phase, will SSD really kick in to help with the speeds. But during LR exports, most people usually let it run and go for a coffee.
 

Last edited:
avsquare said:
I see. I haven't done any stitching before, but how much RAM does it usually eat while doing a typical 9-16 frames stitch? What's your processor now, is the bottle neck the processor or really the RAM?

+\- 24-25gb of ram for 9-16 stitches on full sized tiff file...
 

Faber Arising Redux


Faber Arising Redux by Scintt, on Flickr​

I'm running on 8gb ram on an i5 processor. Stitching in Autopano takes about 3gb of physical memory, or what's left. Taxes the CPU though.

The above is a 3-image vertorama, by the way.
 

Last edited:
Faber Arising Redux


Faber Arising Redux by Scintt, on Flickr​

I'm running on 8gb ram on an i5 processor. Stitching in Autopano takes about 3gb of physical memory, or what's left. Taxes the CPU though.

The above is a 3-image vertorama, by the way.

fantastic shot!!
Great effort on the details in post!! especially the trees!
 

fantastic shot!!
Great effort on the details in post!! especially the trees!

Thanks mate! I'm still flabbergasted at how much detail I can pull with D800 files. There's this DSTA building in the far left of the horizon and the camera even resolves the letters!
 

+\- 24-25gb of ram for 9-16 stitches on full sized tiff file...

:o



I'm running on 8gb ram on an i5 processor. Stitching in Autopano takes about 3gb of physical memory, or what's left. Taxes the CPU though.

The above is a 3-image vertorama, by the way.​


you're stitching on RAW, DNG or full TIFF?​
 

:o



you're stitching on RAW, DNG or full TIFF?

Ah, I'm stitching tiff files. I think Autopano is more efficient at stitching than Photoshop though, renders relatively fast even on my old i5 laptop.
 

Ah, I'm stitching tiff files. I think Autopano is more efficient at stitching than Photoshop though, renders relatively fast even on my old i5 laptop.

Ah I see. As I don't stitch, I don't use Autopano, but I know PS is a snail processing full sized TIFFs.. My 2nd gen i7 will lag sometimes if I'm processing like 1GB of TIFF files.
 

From what I read your posts.. it sounds more like user error... It is not the LCD.. it is probably the picture styles settings your friend's D700/7000 and his work.

If you don't spend the time to do a once over to set up your cam to the way you want it, why even bother raising an issue here now?

Yes, it's most probably. I own both the D700, 7000 & this is an addition on top of my film camera collection but I have to admit that I don't have much time these days to indulge in photography so could only spend about 15-30mins or so to set up the menus etc. I just find it surprising that colour renditions are not as spot on as my D700.

Some of you are sounding quite defensive. It is just my observation on my particular camera & asking for feedback that's all. If it's a lemon so be it, NSC should fix it or simply move on to another body.

My PC is running on i5 8gb ram but if I were to edit raw files out of the D800E, it does slow down somewhat but a trip to fellow pc shop & $950 of upgrade gives me a new motherboard, 1Tb HD & 16 or 32Gb ram which should solve it.
 

That's the most ridiculous thing I've read here. Are you saying that you bought the D800E not knowing it was going to produce bigger files than the D700? You are disappointed with a Lamborghini because its going too fast for your reflexes.

I'm editing my photos with "readily available" MBP with no issues.

And we have a Mr know all here? I enjoy your architectural images but replies are less than friendly.

FYI, I track my Lamborghinis, Porsches & Ferraris in Sepang and also do a bit of rally in Italy, thank goodness I never crashed them (fingers crossed :D) but I do agree that modern exotics are very very fast just like modern cameras. It's just a matter of getting used to them but takes a bit of time.

Anyway, thanks all for your replies.
 

Maybe some of us do not understand that file size increase geometrically with megapixels, not linear. Hence out of expectations.
 

Maybe some of us do not understand that file size increase geometrically with megapixels, not linear. Hence out of expectations.

File size increases linearly with respect to the increase in number of pixels.
 

First photo of 2013 for me... almost on the hour.

D800E, Zeiss 21/2.8

8415102435_610bfb81bc_b.jpg


http://www.flickr.com/photos/tnndrw/8415102435/in/photostream
 

Last edited:
Back
Top