Barry Pearson
Veteran Member
James O'Neill wrote:
[snip]
[snip]
Furthermore, if camera manufacturers could be persuaded to cooperate, there were cheaper ways of achieving cost reductions, such as getting specifications and camera details under NDA. (If a particular camera manufacturer couldn't be persuaded to provide such details, why expect them to switch to DNG?)
[snip]
[snip]
[snip]
It makes business sense for Adobe to develop and promote DNG, but not because they intend to make money out of DNG itself. Adobe works well in an industry structured with clean interfaces. They are not a total system supplier, so can't hope to lock-in people in the way that Nikon attempt. But in a structured industry, photographers have a need for well-considered workflows populated by inter-working tools, and Adobe can thrive there.
[snip]
Chuckle! I suddenly guessed that sometime after I posted.Oops. Too many Barries Error. I was talking to you as if you were
Barry F who I assume hadn't read any of it.
[snip]
True. I was making a point that they had more in mind than just avoiding reverse-engineering costs, not that it was comparable in cost to a commercial product development. (Although they must have spent something on brand management as well, with a name, abbreviation, file-extension, logo, etc). When they started on DNG about 3 years ago, they must have known that it would involve ongoing cost for a long time, certainly several years. Yet it would also be several years before they would see a significant reduction in reverse-engineering costs, if at all.Bottom line, although what they've spent is a some of money you or
I would cross the street to pick up, for a company of their size,
it's small change.
Furthermore, if camera manufacturers could be persuaded to cooperate, there were cheaper ways of achieving cost reductions, such as getting specifications and camera details under NDA. (If a particular camera manufacturer couldn't be persuaded to provide such details, why expect them to switch to DNG?)
[snip]
Gosh! I used to be fast, but not that fast. Certainly not making code of releasable quality.I had a look at it, and to be honest if I compare it with Microsoft
SDKs I know about there is less in it than some of those, including
one I know which probably took only 2 man months of effort.
[snip]
True. I don't think they ever felt they could guarantee that. It was a "strategic" investment to transform part of an industry in a way that would suit them.There's no guarantee that they'll get their money back.
[snip]
What else could we expect from a company where the directors sacrifice and eat a puppy during each board meeting?Hmmm. We've had various people saying their objectives are this
that the other - just stopping short of saying they want
photographers to sell their children to buy monopoly Adobe software.
This is the point. That mess is inhibiting the take up of raw shooting. It sounds geeky, and the complications (visible in these forums) put some people off. I think Adobe want people to "shoot DNG" not "shoot raw", and have DNG work as smoothly as JPEG, although with the need for post-processing where they could sell product. (The menu in the Leica M8 doesn't have a "raw" option, just a "DNG" option. But that would make particular sense for a camera following a line of film cameras!)The fact that RAW is a mess right now is bad for everyone doing
image processing software; it's in Adobe's best interests to make
life simpler. Adobe is the the only company who's standards might
get followed. And if a standard emerges that's good for everyone.
It makes business sense for Adobe to develop and promote DNG, but not because they intend to make money out of DNG itself. Adobe works well in an industry structured with clean interfaces. They are not a total system supplier, so can't hope to lock-in people in the way that Nikon attempt. But in a structured industry, photographers have a need for well-considered workflows populated by inter-working tools, and Adobe can thrive there.