D810 users are seeing spots

  • Thread starter Thread starter Loswr
  • Start date Start date
Seems like this issue affects all units in the initial production runs. Good job by Nikon to quickly acknowledge the issue and offer a fix.

http://www.nikonusa.com/en/Service-And-Support/Service-Advisories/hyvanded/Technical-Service-Advisory-for-Users-of-the-Nikon-D810.html

Guess they learned something from the D600 oil/dust spot fiasco.

stan.jpg
 
Nikon D810 Product Advisory

FYI on Nikon's latest postmarket findings:
http://www.thephoblographer.com/2014/08/19/nikon-europe-issues-product-advisory-d810/

I'm on the fence with this one. Dust with the D600 100% should have been caught in evaluation period before launch. But finding an issue that only shows up in crop mode + long exposures might be more of the weird lightning bolt of an issue you don't find until you release it to the masses.

- A
 
Upvote 0
It is amazing how responsive a company can become once a big market flexes its muscles, Nikon and China, GM and the USA.

ahsanford said:
I'm on the fence with this one. Dust with the D600 100% should have been caught in evaluation period before launch. But finding an issue that only shows up in crop mode + long exposures might be more of the weird lightning bolt of an issue you don't find until you release it to the masses.

- A

I'm not, long exposures and crop mode should be covered in even the most basic field trial testing protocols, what the hell are these guys doing? Not saying Canon is often any better, but come on, this is basic stuff. It might not affect many users actual images, but should easily be noticed with an efficient testing strategy.
 
Upvote 0
Re: Nikon D810 Product Advisory

ahsanford said:
FYI on Nikon's latest postmarket findings:
http://www.thephoblographer.com/2014/08/19/nikon-europe-issues-product-advisory-d810/

I'm on the fence with this one. Dust with the D600 100% should have been caught in evaluation period before launch. But finding an issue that only shows up in crop mode + long exposures might be more of the weird lightning bolt of an issue you don't find until you release it to the masses.

- A

The point is that they denied issues with the D600, and recently agreed to replace all D600's in China with D610's. We'll be seeing those D600's on ebay soon.

Hopefully, they have learned to react when a issue is spotted rather than go into denial. That costs them much more than the eventual fix and loss of reputation.
 
Upvote 0
I would never buy a new camera model as soon as it comes out.

With todays manufacturing ethic, it is just two risky.

Same as with the new 7D. I rather other people be the first to buy/find manufacturing and design errors.

It is kinda like walking through a mine field -- I prefer waiting for the other people to go first. LoL
 
Upvote 0
AcutancePhotography said:
I would never buy a new camera model as soon as it comes out.

With todays manufacturing ethic, it is just two risky.

Same as with the new 7D. I rather other people be the first to buy/find manufacturing and design errors.

It is kinda like walking through a mine field -- I prefer waiting for the other people to go first. LoL

Yeah, but Canon has a pretty good track record of making field announcements and repairing affected units free of charge.

With lenses, I wait for consensus in reviews and play the price waiting game. Their lifecycles are much, much longer.

But the shorter the product lifecycle, the earlier you have to get in. So with bodies, I treat it like a new Apple cell phone or laptop offering. I obviously don't buy everything, but when I do make a purchase, I do in on the very first day to maximize the time before the gear is obsoleted or outclassed by something clearly better (not necessarily the next revision, but the game changer new product that forces my hand to upgrade). This is less a matter of 'the pride of owning the coolest new stuff' and more a matter of maximizing the time I can use the item and still have complete support from the manufacturer.

- A
 
Upvote 0
psolberg said:
like the last gen's 1Ds series oily mirrors fiasco on canon's side, nikon learned and that is always good.

There is a quantum difference between oil on a mirror, and oil on the sensor or long exposure hot pixels. Besides my 1Ds MkIII's both had and have oily mirrors and I am not concerned enough to worry about it.

Things that don't affect IQ, like oily mirrors, could hardly be called a fiasco, things that do affect IQ, oily sensors (Nikon), hot pixels on long exposures (Nikon), or intermittent unrepeatable AF inaccuracies (Canon 1D MkIII) could. But it isn't really the issue that classifies anything as a fiasco, it is the way the company deals with that issue, Nikon had to be forced to accept the D600 issues by China banning sales of them!
 
Upvote 0
psolberg said:
like the last gen's 1Ds series oily mirrors fiasco on canon's side, nikon learned and that is always good.

Nikon had to learn the hard way. Did the country with the world's second-largest economy forbid Canon from selling a defective dSLR model in their country?
 
Upvote 0
neuroanatomist said:
Seems like this issue affects all units in the initial production runs. Good job by Nikon to quickly acknowledge the issue and offer a fix.

http://www.nikonusa.com/en/Service-And-Support/Service-Advisories/hyvanded/Technical-Service-Advisory-for-Users-of-the-Nikon-D810.html

Guess they learned something from the D600 oil/dust spot fiasco.

stan.jpg

Who cares about some silly spots? It in no way affects your ability to stroke yourself after intentionally underexposing an image of your cat by five stops, and playing around with the sliders in Lightroom.

I see psolberg has already joined the party. Surely, dilbert can't be far behind ;D
 
Upvote 0
privatebydesign said:
It is amazing how responsive a company can become once a big market flexes its muscles, Nikon and China, GM and the USA.

ahsanford said:
I'm on the fence with this one. Dust with the D600 100% should have been caught in evaluation period before launch. But finding an issue that only shows up in crop mode + long exposures might be more of the weird lightning bolt of an issue you don't find until you release it to the masses.

- A

I'm not, long exposures and crop mode should be covered in even the most basic field trial testing protocols, what the hell are these guys doing? Not saying Canon is often any better, but come on, this is basic stuff. It might not affect many users actual images, but should easily be noticed with an efficient testing strategy.
I'll have to agree with this. It's not like the issue shows up under a magenta moon while you stand on your head and take a 5 minute photo of a black bear in a cave. This is something that a lot of people do on a regular basis otherwise you wouldn't see it so talked about so quickly. And unfortunately, like so many other manufacturers, Nikon finally reacted quickly because of so much recent bad press. Good for them that they did respond but I wonder how much the China 600 ban decision had to do with it.
 
Upvote 0
neuroanatomist said:
Nikon had to learn the hard way.

They don't learn quickly: back in the day, when I shot Nikon, a solution to the D200's horrible banding problem had to be dragged, kicking and screaming, out of the buggers - and it never did really fix it (for me anyway) on either of my D200s.

That camera is why I'm a Canon shooter now.
 
Upvote 0
+1 to that

sek

AcutancePhotography said:
I would never buy a new camera model as soon as it comes out.

With todays manufacturing ethic, it is just two risky.

Same as with the new 7D. I rather other people be the first to buy/find manufacturing and design errors.

It is kinda like walking through a mine field -- I prefer waiting for the other people to go first. LoL
 
Upvote 0
privatebydesign said:
It is amazing how responsive a company can become once a big market flexes its muscles, Nikon and China, GM and the USA.

ahsanford said:
I'm on the fence with this one. Dust with the D600 100% should have been caught in evaluation period before launch. But finding an issue that only shows up in crop mode + long exposures might be more of the weird lightning bolt of an issue you don't find until you release it to the masses.

- A

I'm not, long exposures and crop mode should be covered in even the most basic field trial testing protocols, what the hell are these guys doing? Not saying Canon is often any better, but come on, this is basic stuff. It might not affect many users actual images, but should easily be noticed with an efficient testing strategy.

I would think it's been rushed to market. Quite a few years ago we sold our digital imaging business to Mitsubishi -the owners of Nikon - (and then ended up buying it back) so I know how these guys work. Nikon will be under a lot of pressure to increase margins, profitability per unit, farming production out to cheaper countries etc etc. I have no way of knowing but I would guess that a D810 costs less to produce than a 5DIII. Probably not in the D4s / 1Dx range. Seems to me they are trying to get the D8xx into a guise that will increase its appeal. Adding sRaw is a good start. I just cannot believe that Nikon introduced a 36mp camera without a smaller raw option.

Or perhaps it's intentional because the D820 will be out by Christmas.
 
Upvote 0
dilbert said:
Does anyone here remember how long it took Canon to address issues with the 5D Mark II? It definitely wasn't this quick!

Does anybody remember Canon getting banned from importing or selling a model because of an unacknowledged fault? Nikon were banned from selling the D600 in China.
 
Upvote 0
neuroanatomist said:
dilbert said:
Does anyone here remember how long it took Canon to address issues with the 5D Mark II? It definitely wasn't this quick!

What problems were those? I can't find any Canon Service Notices (firmware updates notwithstanding) for the 5DII...
That's all I remember, a firmware update (quite quick) for some minor "black pixel" issue where under some circumstances a black pixel or halo could be seen around extreme highlights. Maybe that's the "issue" he's referring to. Again, didn't it get a firmware fix in under a month or something of the sort?
 
Upvote 0