hier noch ein Ausschnitt eines Posts:
off you go to the shop, that's what Pierre's demonstration seems to show (minus the banding effects noted, but I think those will be dealt with)
When I do this with my D700 I get lots of noise...
That's because the D700 gives lots of read nosie at 200 ISO - about five times as much as the D7000.
leave it set on 100, give it the exposure that suits and process for the tonal range you want - the effect will be the same as setting the ISO higher, maybe better if your raw processor uses floating point arithmetic.
What's floating point arithmic? I was googling it and got an idea but I would like to hear it explained by you in this context...
OK, the in-camera processor does all its arithmetic using integers (whole numbers) this means that there are rounding errors because the remainders in divisions don't get dealt with properly, and these rounding errors can end up looking much like noise. Floating point arithmetic uses more memory to encode both the integral and fractional part of a number, and so the arithmetic errors are much smaller, and don't display as noise.
NX only recovers 2 stops... Don't force me to ACR please...
As I said somewhere else, the camera manufacturers and raw converter writers haven't caught up with this yet. That is one of the points I make, the camera UI and tools atre still locked into the film paradigm.
The other advantage is that you've always got the full 100 ISO headroom, so you're never going to risk the highlights as you might with a higher ISO.
Of course, if you're working in JPEG, your shots will be dark and not recoverable.
That's clear.
Again, because Nikon has made it that way. If they'd give the option to determine the JPEG brightness after capture, it would take away that problem.
What I find interesting is, when you compare the D7000 with the K-5 and A55, Nikon has clearly deliberately designed the D7000 to be like this, they just haven't quite woken up to the full implications.
Also: Nikon, aufwachen!
