Discussion:
Nikon's retro DSLR launches and it looks good
(too old to reply)
RichA
2013-11-05 04:47:45 UTC
Permalink
I'd sooner pay $3000 for this than $1800 for a lame D610 body.

http://www.dpreview.com/news/2013/11/05/nikon-df-combines-classic-design-with-modern-technology?utm_campaign=internal-link&utm_source=news-list&utm_medium=text&ref=title_0_2#specs
android
2013-11-05 08:16:07 UTC
Permalink
Post by RichA
I'd sooner pay $3000 for this than $1800 for a lame D610 body.
http://www.dpreview.com/news/2013/11/05/nikon-df-combines-classic-design-with-
modern-technology?utm_campaign=internal-link&utm_source=news-list&utm_medium=t
ext&ref=title_0_2#specs
Kinda cool looks. For the trendy wannabes that can't afford a proper
Leica! ;-) And don't mind having their raw files encrypted...
--
teleportation kills
nospam
2013-11-05 08:56:06 UTC
Permalink
Post by android
And don't mind having their raw files encrypted...
stop spreading misinformation.

the raw files aren't encrypted.

a decade ago, nikon encrypted *just* the white balance. they did *not*
encrypt the entire raw file. it also made no difference to end users.

and it's not just nikon either. just about all camera makers encrypt a
portion. they do not encrypt the entire file.
android
2013-11-05 09:20:49 UTC
Permalink
Post by nospam
Post by android
And don't mind having their raw files encrypted...
stop spreading misinformation.
the raw files aren't encrypted.
According to the source below parts of then are. It could very well be
a waiting game. Do they accept a part now then they might all later.
Post by nospam
a decade ago, nikon encrypted *just* the white balance. they did *not*
encrypt the entire raw file. it also made no difference to end users.
Off course it maters to endusers if the can edit their files with third
party software. It's called futureproofing your workflow.
Post by nospam
and it's not just nikon either. just about all camera makers encrypt a
portion. they do not encrypt the entire file.
http://tinyurl.com/59yf9g
--
teleportation kills
Floyd L. Davidson
2013-11-05 11:23:58 UTC
Permalink
Post by android
Post by nospam
Post by android
And don't mind having their raw files encrypted...
stop spreading misinformation.
the raw files aren't encrypted.
According to the source below parts of then are. It could very well be
a waiting game. Do they accept a part now then they might all later.
You do realize that your "source below" is from April
2005? Shame on the author, Declan MaCullagh, who does
have some real credentials even if he got caught up in
an Adobe attempt to make some hay with PR before the sun
came up and the light showed what was actually going on.

It is true that there are parts of the Nikon NEF file
which are "encryped", and for reasons that I've never
heard. But it's also true, though not mentioned in your
article, that Nikon embedded the encryption key into the
NEF file, thus making it trivial for everyone and anyone
to read the data.
Post by android
Post by nospam
a decade ago, nikon encrypted *just* the white balance. they did *not*
encrypt the entire raw file. it also made no difference to end users.
Off course it maters to endusers if the can edit their files with third
party software. It's called futureproofing your workflow.
Because of the way Nikon did it, there is not and never
has been any problem. I am one who shoots Nikon but has
never used Nikon's software.
Post by android
Post by nospam
and it's not just nikon either. just about all camera makers encrypt a
portion. they do not encrypt the entire file.
http://tinyurl.com/59yf9g--
teleportation kills
--
Floyd L. Davidson http://www.apaflo.com/floyd_davidson
Ukpeagvik (Barrow, Alaska) ***@apaflo.com
android
2013-11-05 11:35:58 UTC
Permalink
Post by Floyd L. Davidson
Post by android
Off course it maters to endusers if the can edit their files with third
party software. It's called futureproofing your workflow.
Because of the way Nikon did it, there is not and never
has been any problem. I am one who shoots Nikon but has
never used Nikon's software.
The reason for Nikon to steal your right to full access to your files
created by you with your equipment is to force you to use their or their
licensees software to get the most out of your creative process and
work. That process has been stalled but Nikon, and others that followed
them has not backed from encrypting some metadata and therefore not
clearly stated that full encryption won't happen in the future. There is
no honest explanation to why encryption of meta data is a benefit to the
owner of the file.
--
teleportation kills
Floyd L. Davidson
2013-11-05 12:40:49 UTC
Permalink
Post by android
Post by Floyd L. Davidson
Post by android
Off course it maters to endusers if the can edit their files with third
party software. It's called futureproofing your workflow.
Because of the way Nikon did it, there is not and never
has been any problem. I am one who shoots Nikon but has
never used Nikon's software.
The reason for Nikon to steal your right to full access to your files
created by you with your equipment is to force you to use their or their
licensees software to get the most out of your creative process and
work. That process has been stalled but Nikon, and others that followed
them has not backed from encrypting some metadata and therefore not
clearly stated that full encryption won't happen in the future. There is
no honest explanation to why encryption of meta data is a benefit to the
owner of the file.
1) The encryption of metadata does not need to be a
benefit to the owner of the file for Nikon or any
other company to use encryption.

2) Your statement that Nikon would "steal your right to
full access" is very bizzare considering that what
Nikon did was *clearly* not meant to deny full
access. As noted previously, which you are ignoring,
Nikon actually embedded the encryption key into the
file to begin with.

3) Nothing you have claimed or ignored either way has
even the slightest effect on the capability of any
camera manufacturere to use encryption of the
metadata in their RAW files. Any and or all of them
could start using encryption tomorrow, whether they
have ever even hinted at it in the past or not.

As noted, I use Nikon cameras (and used a Nikon D2X, one
of the initial cameras that encrypted the White Balance
information), but I have never once even looked at an
image, much less edited one, using any Nikon software.
Your claim that Nikon tried to prevent that is hilarious
on it's face! The idea that what Nikon did in 2005 is
an issue with "futureproofing" my workflow is even more
offbase, given that 8 years down the road there is still
not the slightest significant effort at preventing my
use of non-Nikon software.
--
Floyd L. Davidson http://www.apaflo.com/floyd_davidson
Ukpeagvik (Barrow, Alaska) ***@apaflo.com
J. Clarke
2013-11-05 14:32:32 UTC
Permalink
Post by Floyd L. Davidson
Post by android
Post by Floyd L. Davidson
Post by android
Off course it maters to endusers if the can edit their files with third
party software. It's called futureproofing your workflow.
Because of the way Nikon did it, there is not and never
has been any problem. I am one who shoots Nikon but has
never used Nikon's software.
The reason for Nikon to steal your right to full access to your files
created by you with your equipment is to force you to use their or their
licensees software to get the most out of your creative process and
work. That process has been stalled but Nikon, and others that followed
them has not backed from encrypting some metadata and therefore not
clearly stated that full encryption won't happen in the future. There is
no honest explanation to why encryption of meta data is a benefit to the
owner of the file.
1) The encryption of metadata does not need to be a
benefit to the owner of the file for Nikon or any
other company to use encryption.
2) Your statement that Nikon would "steal your right to
full access" is very bizzare considering that what
Nikon did was *clearly* not meant to deny full
access. As noted previously, which you are ignoring,
Nikon actually embedded the encryption key into the
file to begin with.
3) Nothing you have claimed or ignored either way has
even the slightest effect on the capability of any
camera manufacturere to use encryption of the
metadata in their RAW files. Any and or all of them
could start using encryption tomorrow, whether they
have ever even hinted at it in the past or not.
As noted, I use Nikon cameras (and used a Nikon D2X, one
of the initial cameras that encrypted the White Balance
information), but I have never once even looked at an
image, much less edited one, using any Nikon software.
Your claim that Nikon tried to prevent that is hilarious
on it's face! The idea that what Nikon did in 2005 is
an issue with "futureproofing" my workflow is even more
offbase, given that 8 years down the road there is still
not the slightest significant effort at preventing my
use of non-Nikon software.
However one wonders what the thinking was and by who and whether their
thinking has changed and what their prospects are for rising to a
position of authority in the company.
nospam
2013-11-05 14:59:08 UTC
Permalink
Post by J. Clarke
However one wonders what the thinking was and by who and whether their
thinking has changed and what their prospects are for rising to a
position of authority in the company.
nobody wonders anything and all the companies do it in one way or
another, some more than nikon.

it's not an issue.
android
2013-11-05 15:35:26 UTC
Permalink
Post by nospam
Post by J. Clarke
However one wonders what the thinking was and by who and whether their
thinking has changed and what their prospects are for rising to a
position of authority in the company.
nobody wonders anything and all the companies do it in one way or
another, some more than nikon.
it's not an issue.
You're not replaying to me I've explained in another post why it is.
--
teleportation kills
nospam
2013-11-05 17:58:53 UTC
Permalink
Post by android
Post by nospam
Post by J. Clarke
However one wonders what the thinking was and by who and whether their
thinking has changed and what their prospects are for rising to a
position of authority in the company.
nobody wonders anything and all the companies do it in one way or
another, some more than nikon.
it's not an issue.
You're not replaying to me I've explained in another post why it is.
no, you explained why you *think* it is.

myself and floyd explained that you are wrong.

decoding nikon raws is *not* an issue.
android
2013-11-05 19:21:26 UTC
Permalink
Post by nospam
no, you explained why you *think* it is.
myself and floyd explained that you are wrong.
I have yet to se that explanation...
--
teleportation kills
nospam
2013-11-05 19:41:17 UTC
Permalink
Post by android
Post by nospam
no, you explained why you *think* it is.
myself and floyd explained that you are wrong.
I have yet to se that explanation...
try reading the posts you're replying to before actually replying.
android
2013-11-05 19:59:12 UTC
Permalink
Post by nospam
Post by android
Post by nospam
no, you explained why you *think* it is.
myself and floyd explained that you are wrong.
I have yet to se that explanation...
try reading the posts you're replying to before actually replying.
If there's nothing to se then there's nothing to se...
--
teleportation kills
Floyd L. Davidson
2013-11-05 18:50:22 UTC
Permalink
Post by J. Clarke
Post by Floyd L. Davidson
Post by android
Post by Floyd L. Davidson
Post by android
Off course it maters to endusers if the can edit their files with third
party software. It's called futureproofing your workflow.
Because of the way Nikon did it, there is not and never
has been any problem. I am one who shoots Nikon but has
never used Nikon's software.
The reason for Nikon to steal your right to full access to your files
created by you with your equipment is to force you to use their or their
licensees software to get the most out of your creative process and
work. That process has been stalled but Nikon, and others that followed
them has not backed from encrypting some metadata and therefore not
clearly stated that full encryption won't happen in the future. There is
no honest explanation to why encryption of meta data is a benefit to the
owner of the file.
1) The encryption of metadata does not need to be a
benefit to the owner of the file for Nikon or any
other company to use encryption.
2) Your statement that Nikon would "steal your right to
full access" is very bizzare considering that what
Nikon did was *clearly* not meant to deny full
access. As noted previously, which you are ignoring,
Nikon actually embedded the encryption key into the
file to begin with.
3) Nothing you have claimed or ignored either way has
even the slightest effect on the capability of any
camera manufacturere to use encryption of the
metadata in their RAW files. Any and or all of them
could start using encryption tomorrow, whether they
have ever even hinted at it in the past or not.
As noted, I use Nikon cameras (and used a Nikon D2X, one
of the initial cameras that encrypted the White Balance
information), but I have never once even looked at an
image, much less edited one, using any Nikon software.
Your claim that Nikon tried to prevent that is hilarious
on it's face! The idea that what Nikon did in 2005 is
an issue with "futureproofing" my workflow is even more
offbase, given that 8 years down the road there is still
not the slightest significant effort at preventing my
use of non-Nikon software.
However one wonders what the thinking was and by who and whether their
thinking has changed and what their prospects are for rising to a
position of authority in the company.
Conspiracy theories are not of much value. The first
thing to realize is that Nikon changes the NEF format
for each and every new model of camera they release.
The second thing is that the D2X was very clearly *not*
an attempt to hide the information (the encryption key
is embedded in the NEF file).

If you want to get into where the consiracy is, check
out why Adobe's marketing folks wanted to make a public
fuss about something that wasn't actually a problem!
--
Floyd L. Davidson http://www.apaflo.com/floyd_davidson
Ukpeagvik (Barrow, Alaska) ***@apaflo.com
J. Clarke
2013-11-05 21:33:01 UTC
Permalink
Post by Floyd L. Davidson
Post by J. Clarke
Post by Floyd L. Davidson
Post by android
Post by Floyd L. Davidson
Post by android
Off course it maters to endusers if the can edit their files with third
party software. It's called futureproofing your workflow.
Because of the way Nikon did it, there is not and never
has been any problem. I am one who shoots Nikon but has
never used Nikon's software.
The reason for Nikon to steal your right to full access to your files
created by you with your equipment is to force you to use their or their
licensees software to get the most out of your creative process and
work. That process has been stalled but Nikon, and others that followed
them has not backed from encrypting some metadata and therefore not
clearly stated that full encryption won't happen in the future. There is
no honest explanation to why encryption of meta data is a benefit to the
owner of the file.
1) The encryption of metadata does not need to be a
benefit to the owner of the file for Nikon or any
other company to use encryption.
2) Your statement that Nikon would "steal your right to
full access" is very bizzare considering that what
Nikon did was *clearly* not meant to deny full
access. As noted previously, which you are ignoring,
Nikon actually embedded the encryption key into the
file to begin with.
3) Nothing you have claimed or ignored either way has
even the slightest effect on the capability of any
camera manufacturere to use encryption of the
metadata in their RAW files. Any and or all of them
could start using encryption tomorrow, whether they
have ever even hinted at it in the past or not.
As noted, I use Nikon cameras (and used a Nikon D2X, one
of the initial cameras that encrypted the White Balance
information), but I have never once even looked at an
image, much less edited one, using any Nikon software.
Your claim that Nikon tried to prevent that is hilarious
on it's face! The idea that what Nikon did in 2005 is
an issue with "futureproofing" my workflow is even more
offbase, given that 8 years down the road there is still
not the slightest significant effort at preventing my
use of non-Nikon software.
However one wonders what the thinking was and by who and whether their
thinking has changed and what their prospects are for rising to a
position of authority in the company.
Conspiracy theories are not of much value.
Who said anything about a "conspiracy".
Post by Floyd L. Davidson
The first
thing to realize is that Nikon changes the NEF format
for each and every new model of camera they release.
They do, but how radically?
Post by Floyd L. Davidson
The second thing is that the D2X was very clearly *not*
an attempt to hide the information (the encryption key
is embedded in the NEF file).
You just aren't getting it. If nobody employed by Nikon wanted to hide
the data then WHY ENCRYPT IT TO BEGIN WITH? Obviously _somebody_
thought it was a good idea, equally obviously somebody else didn't. If
"somebody else" retires and "somebody" takes over the department, who's
to say that "somebody" won't get his way in the end and encrypt
everything without providing the key?
Post by Floyd L. Davidson
If you want to get into where the consiracy is, check
out why Adobe's marketing folks wanted to make a public
fuss about something that wasn't actually a problem!
Floyd L. Davidson
2013-11-05 22:02:18 UTC
Permalink
Post by J. Clarke
Post by Floyd L. Davidson
Post by J. Clarke
Post by Floyd L. Davidson
Post by android
Post by Floyd L. Davidson
Post by android
Off course it maters to endusers if the can edit their files with third
party software. It's called futureproofing your workflow.
Because of the way Nikon did it, there is not and never
has been any problem. I am one who shoots Nikon but has
never used Nikon's software.
The reason for Nikon to steal your right to full access to your files
created by you with your equipment is to force you to use their or their
licensees software to get the most out of your creative process and
work. That process has been stalled but Nikon, and others that followed
them has not backed from encrypting some metadata and therefore not
clearly stated that full encryption won't happen in the future. There is
no honest explanation to why encryption of meta data is a benefit to the
owner of the file.
1) The encryption of metadata does not need to be a
benefit to the owner of the file for Nikon or any
other company to use encryption.
2) Your statement that Nikon would "steal your right to
full access" is very bizzare considering that what
Nikon did was *clearly* not meant to deny full
access. As noted previously, which you are ignoring,
Nikon actually embedded the encryption key into the
file to begin with.
3) Nothing you have claimed or ignored either way has
even the slightest effect on the capability of any
camera manufacturere to use encryption of the
metadata in their RAW files. Any and or all of them
could start using encryption tomorrow, whether they
have ever even hinted at it in the past or not.
As noted, I use Nikon cameras (and used a Nikon D2X, one
of the initial cameras that encrypted the White Balance
information), but I have never once even looked at an
image, much less edited one, using any Nikon software.
Your claim that Nikon tried to prevent that is hilarious
on it's face! The idea that what Nikon did in 2005 is
an issue with "futureproofing" my workflow is even more
offbase, given that 8 years down the road there is still
not the slightest significant effort at preventing my
use of non-Nikon software.
However one wonders what the thinking was and by who and whether their
thinking has changed and what their prospects are for rising to a
position of authority in the company.
Conspiracy theories are not of much value.
Who said anything about a "conspiracy".
That is exactly what you described, your conspiracy theory...
Post by J. Clarke
Post by Floyd L. Davidson
The first
thing to realize is that Nikon changes the NEF format
for each and every new model of camera they release.
They do, but how radically?
Enough that until changes are made to existing software
packages, nothing works.
Post by J. Clarke
Post by Floyd L. Davidson
The second thing is that the D2X was very clearly *not*
an attempt to hide the information (the encryption key
is embedded in the NEF file).
You just aren't getting it. If nobody employed by Nikon wanted to hide
the data then WHY ENCRYPT IT TO BEGIN WITH?
You just aren't getting it! We have no idea what Nikon
was doing, but it is rather clear that hiding data can't
be the purpose.
Post by J. Clarke
Obviously _somebody_
thought it was a good idea, equally obviously somebody else didn't. If
"somebody else" retires and "somebody" takes over the department, who's
to say that "somebody" won't get his way in the end and encrypt
everything without providing the key?
That's a rather silly conspiracy theory.

It could be, you know, that the head of Nikon will
decide to dismantle the company, sell off the assets, and
never make another camera again.

You need to worry!
Post by J. Clarke
Post by Floyd L. Davidson
If you want to get into where the consiracy is, check
out why Adobe's marketing folks wanted to make a public
fuss about something that wasn't actually a problem!
Apparently you didn't give any though to the important
points of conspiracy theorizing... ?
--
Floyd L. Davidson http://www.apaflo.com/floyd_davidson
Ukpeagvik (Barrow, Alaska) ***@apaflo.com
J. Clarke
2013-11-05 23:54:56 UTC
Permalink
Post by Floyd L. Davidson
Post by J. Clarke
Post by Floyd L. Davidson
Post by J. Clarke
Post by Floyd L. Davidson
Post by android
Post by Floyd L. Davidson
Post by android
Off course it maters to endusers if the can edit their files with third
party software. It's called futureproofing your workflow.
Because of the way Nikon did it, there is not and never
has been any problem. I am one who shoots Nikon but has
never used Nikon's software.
The reason for Nikon to steal your right to full access to your files
created by you with your equipment is to force you to use their or their
licensees software to get the most out of your creative process and
work. That process has been stalled but Nikon, and others that followed
them has not backed from encrypting some metadata and therefore not
clearly stated that full encryption won't happen in the future. There is
no honest explanation to why encryption of meta data is a benefit to the
owner of the file.
1) The encryption of metadata does not need to be a
benefit to the owner of the file for Nikon or any
other company to use encryption.
2) Your statement that Nikon would "steal your right to
full access" is very bizzare considering that what
Nikon did was *clearly* not meant to deny full
access. As noted previously, which you are ignoring,
Nikon actually embedded the encryption key into the
file to begin with.
3) Nothing you have claimed or ignored either way has
even the slightest effect on the capability of any
camera manufacturere to use encryption of the
metadata in their RAW files. Any and or all of them
could start using encryption tomorrow, whether they
have ever even hinted at it in the past or not.
As noted, I use Nikon cameras (and used a Nikon D2X, one
of the initial cameras that encrypted the White Balance
information), but I have never once even looked at an
image, much less edited one, using any Nikon software.
Your claim that Nikon tried to prevent that is hilarious
on it's face! The idea that what Nikon did in 2005 is
an issue with "futureproofing" my workflow is even more
offbase, given that 8 years down the road there is still
not the slightest significant effort at preventing my
use of non-Nikon software.
However one wonders what the thinking was and by who and whether their
thinking has changed and what their prospects are for rising to a
position of authority in the company.
Conspiracy theories are not of much value.
Who said anything about a "conspiracy".
That is exactly what you described, your conspiracy theory...
I'm sorry, but I did not "describe" _anything_. Wondering what someone
was thinking is not "describing".
Post by Floyd L. Davidson
Post by J. Clarke
Post by Floyd L. Davidson
The first
thing to realize is that Nikon changes the NEF format
for each and every new model of camera they release.
They do, but how radically?
Enough that until changes are made to existing software
packages, nothing works.
Which is not an answer.
Post by Floyd L. Davidson
Post by J. Clarke
Post by Floyd L. Davidson
The second thing is that the D2X was very clearly *not*
an attempt to hide the information (the encryption key
is embedded in the NEF file).
You just aren't getting it. If nobody employed by Nikon wanted to hide
the data then WHY ENCRYPT IT TO BEGIN WITH?
You just aren't getting it! We have no idea what Nikon
was doing, but it is rather clear that hiding data can't
be the purpose.
Whose purpose? Nikon is not an individual, it is a large company with
more than 20,000 employees. Obviously one of those employees decided to
incorporate encryption into part of the system. Did he do that because
someone told him to? Because he was reading a book on encryption and
decided to try it out on company time? Because he found the algorithm
he wanted in a journal and didn't bother to strip out the encryption
part? All kinds of reasons that he could have decided to do it,
including that he personally thinks that everything should be encrypted.
Equally obviously some one of those more than 20,000 employees decided
to provide the encryption key in the software. Was it the same employee
or was it a different employee? Why was the decision made to do it that
way instead of just stripping out the encryption entirely? What
happened to the person who incorported the encryption to begin with? Is
he still with the company? Was he promoted? Disciplined? Transferred
to a different department? What is he doing now?

All of these have bearing on both the reasons for the encryption and the
prospects for it it being tightened in the future.

But instead of recognizing that these are legitimate questions, you
dismiss them as "a conspiracy theory". God help you if you are ever a
project manager because this is the kind of crap you'll have to deal
with all day every day and you won't be able to just say "it's a
conspiracy theory".
Post by Floyd L. Davidson
Post by J. Clarke
Obviously _somebody_
thought it was a good idea, equally obviously somebody else didn't. If
"somebody else" retires and "somebody" takes over the department, who's
to say that "somebody" won't get his way in the end and encrypt
everything without providing the key?
That's a rather silly conspiracy theory.
What's "silly" about it? Have you ever written a line of code in your
life? Encryption does not occur in software unless some human being
wrote the code to put it there. And that human being has a life, that
includes promotions, demotions, lateral transfers, disciplinary action,
and death.
Post by Floyd L. Davidson
It could be, you know, that the head of Nikon will
decide to dismantle the company, sell off the assets, and
never make another camera again.
It could be, however that has no bearing on the fact that somebody put
encryption in the software and nobody saw fit to remove it.
Post by Floyd L. Davidson
You need to worry!
I'm a Canon user, what Nikon does it a matter of crashing indifference
to me.
Post by Floyd L. Davidson
Post by J. Clarke
Post by Floyd L. Davidson
If you want to get into where the consiracy is, check
out why Adobe's marketing folks wanted to make a public
fuss about something that wasn't actually a problem!
Apparently you didn't give any though to the important
points of conspiracy theorizing... ?
Marketing people do what marketing people do. Their voodoo is different
from my voodoo.
nospam
2013-11-06 01:29:13 UTC
Permalink
Post by J. Clarke
Post by Floyd L. Davidson
Post by J. Clarke
Post by Floyd L. Davidson
The second thing is that the D2X was very clearly *not*
an attempt to hide the information (the encryption key
is embedded in the NEF file).
You just aren't getting it. If nobody employed by Nikon wanted to hide
the data then WHY ENCRYPT IT TO BEGIN WITH?
You just aren't getting it! We have no idea what Nikon
was doing, but it is rather clear that hiding data can't
be the purpose.
Whose purpose? Nikon is not an individual, it is a large company with
more than 20,000 employees. Obviously one of those employees decided to
incorporate encryption into part of the system. Did he do that because
someone told him to? Because he was reading a book on encryption and
decided to try it out on company time? Because he found the algorithm
he wanted in a journal and didn't bother to strip out the encryption
part? All kinds of reasons that he could have decided to do it,
including that he personally thinks that everything should be encrypted.
Equally obviously some one of those more than 20,000 employees decided
to provide the encryption key in the software. Was it the same employee
or was it a different employee? Why was the decision made to do it that
way instead of just stripping out the encryption entirely? What
happened to the person who incorported the encryption to begin with? Is
he still with the company? Was he promoted? Disciplined? Transferred
to a different department? What is he doing now?
that one employee must be the same person who got canon and others to
encrypt it too.

not only that, but he has a job at multiple competing companies at the
same time.

and if that isn't enough, he managed to convince everyone else on the
team to agree, including management, right up to the top.

busy guy.
Post by J. Clarke
All of these have bearing on both the reasons for the encryption and the
prospects for it it being tightened in the future.
since this was done 8 years ago and it has not been tightened since
then, there's essentially nothing at all to worry about.

more ignorant fud.
Post by J. Clarke
But instead of recognizing that these are legitimate questions, you
dismiss them as "a conspiracy theory". God help you if you are ever a
project manager because this is the kind of crap you'll have to deal
with all day every day and you won't be able to just say "it's a
conspiracy theory".
what legitimate questions might there be? it doesn't affect end users
at all. it's a little extra work for a developer but it's not really a
big deal.

it is a conspiracy theory.
Post by J. Clarke
Post by Floyd L. Davidson
Post by J. Clarke
Obviously _somebody_
thought it was a good idea, equally obviously somebody else didn't. If
"somebody else" retires and "somebody" takes over the department, who's
to say that "somebody" won't get his way in the end and encrypt
everything without providing the key?
That's a rather silly conspiracy theory.
What's "silly" about it? Have you ever written a line of code in your
life? Encryption does not occur in software unless some human being
wrote the code to put it there. And that human being has a life, that
includes promotions, demotions, lateral transfers, disciplinary action,
and death.
what's silly is your idiotic theory that it's one guy at nikon.

it's multiple people at multiple companies, including canon, what you
say you use.

you're coming up with crazy explanations for a bogus scenario that
never happened.

that's conspiracy.
Post by J. Clarke
Post by Floyd L. Davidson
It could be, you know, that the head of Nikon will
decide to dismantle the company, sell off the assets, and
never make another camera again.
It could be, however that has no bearing on the fact that somebody put
encryption in the software and nobody saw fit to remove it.
maybe they had a good reason to put it there. you are assuming it was
intentionally to hurt the end user.

the bigger question is what exactly would you do with the white balance
info anyway, given that you don't have the chromaticities of the
sensors? also, users usually adjust white balance anyway in raw
processing, so whatever was originally there is ignored.

in other words, encryption doesn't matter one way or the other.
Post by J. Clarke
Post by Floyd L. Davidson
You need to worry!
I'm a Canon user, what Nikon does it a matter of crashing indifference
to me.
apparently, what canon does is also a matter of crashing indifference
to you.

in fact, it's the same thing - white balance:
<http://www.sno.phy.queensu.ca/~phil/exiftool/canon_raw.html>
White sample information with encrypted 8x8 sample data
Post by J. Clarke
Post by Floyd L. Davidson
Post by J. Clarke
Post by Floyd L. Davidson
If you want to get into where the consiracy is, check
out why Adobe's marketing folks wanted to make a public
fuss about something that wasn't actually a problem!
Apparently you didn't give any though to the important
points of conspiracy theorizing... ?
Marketing people do what marketing people do. Their voodoo is different
from my voodoo.
as is your reality.
nospam
2013-11-05 22:02:43 UTC
Permalink
Post by J. Clarke
Post by Floyd L. Davidson
Post by J. Clarke
Post by Floyd L. Davidson
As noted, I use Nikon cameras (and used a Nikon D2X, one
of the initial cameras that encrypted the White Balance
information), but I have never once even looked at an
image, much less edited one, using any Nikon software.
Your claim that Nikon tried to prevent that is hilarious
on it's face! The idea that what Nikon did in 2005 is
an issue with "futureproofing" my workflow is even more
offbase, given that 8 years down the road there is still
not the slightest significant effort at preventing my
use of non-Nikon software.
However one wonders what the thinking was and by who and whether their
thinking has changed and what their prospects are for rising to a
position of authority in the company.
Conspiracy theories are not of much value.
Who said anything about a "conspiracy".
your statement has the makings of one.
Post by J. Clarke
Post by Floyd L. Davidson
The first
thing to realize is that Nikon changes the NEF format
for each and every new model of camera they release.
They do, but how radically?
radically enough for apple, adobe and others to take a month or two to
support it, possibly more, depending on their release cycles.
Post by J. Clarke
Post by Floyd L. Davidson
The second thing is that the D2X was very clearly *not*
an attempt to hide the information (the encryption key
is embedded in the NEF file).
You just aren't getting it. If nobody employed by Nikon wanted to hide
the data then WHY ENCRYPT IT TO BEGIN WITH? Obviously _somebody_
thought it was a good idea, equally obviously somebody else didn't.
others *did*.
Post by J. Clarke
If "somebody else" retires and "somebody" takes over the department, who's
to say that "somebody" won't get his way in the end and encrypt
everything without providing the key?
that somebody must be very busy going from company to company, telling
every company to encrypt something.

it's not one guy at nikon.

other companies do it too and it doesn't matter since what is encrypted
is not critical to raw decoding, other than sigma's cameras and nobody
cares about that.

in the case of nikon, it was white balance, which is ignored by third
party converters and most people don't go with the default anyway so
it's nothing they would have needed.

it's a non-issue.
android
2013-11-05 15:35:31 UTC
Permalink
Post by Floyd L. Davidson
Post by android
Post by Floyd L. Davidson
Post by android
Off course it maters to endusers if the can edit their files with third
party software. It's called futureproofing your workflow.
Because of the way Nikon did it, there is not and never
has been any problem. I am one who shoots Nikon but has
never used Nikon's software.
The reason for Nikon to steal your right to full access to your files
created by you with your equipment is to force you to use their or their
licensees software to get the most out of your creative process and
work. That process has been stalled but Nikon, and others that followed
them has not backed from encrypting some metadata and therefore not
clearly stated that full encryption won't happen in the future. There is
no honest explanation to why encryption of meta data is a benefit to the
owner of the file.
1) The encryption of metadata does not need to be a
benefit to the owner of the file for Nikon or any
other company to use encryption.
2) Your statement that Nikon would "steal your right to
full access" is very bizzare considering that what
Nikon did was *clearly* not meant to deny full
access. As noted previously, which you are ignoring,
Nikon actually embedded the encryption key into the
file to begin with.
3) Nothing you have claimed or ignored either way has
even the slightest effect on the capability of any
camera manufacturere to use encryption of the
metadata in their RAW files. Any and or all of them
could start using encryption tomorrow, whether they
have ever even hinted at it in the past or not.
As noted, I use Nikon cameras (and used a Nikon D2X, one
of the initial cameras that encrypted the White Balance
information), but I have never once even looked at an
image, much less edited one, using any Nikon software.
Your claim that Nikon tried to prevent that is hilarious
on it's face! The idea that what Nikon did in 2005 is
an issue with "futureproofing" my workflow is even more
offbase, given that 8 years down the road there is still
not the slightest significant effort at preventing my
use of non-Nikon software.
You're walking in circles... Get a compass!
--
teleportation kills
Floyd L. Davidson
2013-11-05 18:42:05 UTC
Permalink
Post by android
Post by Floyd L. Davidson
Post by android
Post by Floyd L. Davidson
Post by android
Off course it maters to endusers if the can edit their files with third
party software. It's called futureproofing your workflow.
Because of the way Nikon did it, there is not and never
has been any problem. I am one who shoots Nikon but has
never used Nikon's software.
The reason for Nikon to steal your right to full access to your files
created by you with your equipment is to force you to use their or their
licensees software to get the most out of your creative process and
work. That process has been stalled but Nikon, and others that followed
them has not backed from encrypting some metadata and therefore not
clearly stated that full encryption won't happen in the future. There is
no honest explanation to why encryption of meta data is a benefit to the
owner of the file.
1) The encryption of metadata does not need to be a
benefit to the owner of the file for Nikon or any
other company to use encryption.
2) Your statement that Nikon would "steal your right to
full access" is very bizzare considering that what
Nikon did was *clearly* not meant to deny full
access. As noted previously, which you are ignoring,
Nikon actually embedded the encryption key into the
file to begin with.
3) Nothing you have claimed or ignored either way has
even the slightest effect on the capability of any
camera manufacturere to use encryption of the
metadata in their RAW files. Any and or all of them
could start using encryption tomorrow, whether they
have ever even hinted at it in the past or not.
As noted, I use Nikon cameras (and used a Nikon D2X, one
of the initial cameras that encrypted the White Balance
information), but I have never once even looked at an
image, much less edited one, using any Nikon software.
Your claim that Nikon tried to prevent that is hilarious
on it's face! The idea that what Nikon did in 2005 is
an issue with "futureproofing" my workflow is even more
offbase, given that 8 years down the road there is still
not the slightest significant effort at preventing my
use of non-Nikon software.
You're walking in circles... Get a compass!
You've clearly gotten yourself far more than a bit
confused about how RAW files work and what they are.

Keep in mind that in terms of this so called
"futureproofing" a workflow there is today not one
single raw conversion software package available, free
or proprietary and owned by Nikon or not, that can
decode the RAW file that will be produced by the camera
that will someday replace the current Nikon flagship D4
line of cameras (i.e., the Nikon D5).

Your way of looking at that is to say that the D5 NEF
file format is encrypted, because nobody today can
figure out what it is or how to decode it, and therefore
Nikon is going to steal everyone's right to use other
than Nikon Software when they release a model D5 and
don't bother to tell anyone exactly how to read the new
NEF format!

But that's not the way it works, now or back in April
2005 when there was discussion about how the D2X and D2H
had the White Balance meta data encoded differently than
it had been done in the D1 generation of cameras. Each
camera model (never mind just going from one generation such
as from the D1 to the D2x to the D3 and then the D4) has
had format changes to the NEF file that required unannounced
modifications to the raw conversion software packages
before any of them would work.
--
Floyd L. Davidson http://www.apaflo.com/floyd_davidson
Ukpeagvik (Barrow, Alaska) ***@apaflo.com
android
2013-11-05 19:22:01 UTC
Permalink
Post by Floyd L. Davidson
You've clearly gotten yourself far more than a bit
confused about how RAW files work and what they are.
The raw files consists of raw image data. I E the digitized conversion
of current that the fotosites or pixels produce at exposure and the
associated metadata...
Post by Floyd L. Davidson
Keep in mind that in terms of this so called
"futureproofing" a workflow there is today not one
single raw conversion software package available, free
or proprietary and owned by Nikon or not, that can
decode the RAW file that will be produced by the camera
that will someday replace the current Nikon flagship D4
line of cameras (i.e., the Nikon D5).
Futureproofing is about making your picture files of today available
tomorrow next year and century.
Post by Floyd L. Davidson
Your way of looking at that is to say that the D5 NEF
file format is encrypted, because nobody today can
figure out what it is or how to decode it, and therefore
Nikon is going to steal everyone's right to use other
than Nikon Software when they release a model D5 and
don't bother to tell anyone exactly how to read the new
NEF format!
Nonencrypted rawdata will always be readable through reverse engineering.
--
teleportation kills
nospam
2013-11-05 19:41:19 UTC
Permalink
Post by android
Post by Floyd L. Davidson
You've clearly gotten yourself far more than a bit
confused about how RAW files work and what they are.
The raw files consists of raw image data. I E the digitized conversion
of current that the fotosites or pixels produce at exposure and the
associated metadata...
Post by Floyd L. Davidson
Keep in mind that in terms of this so called
"futureproofing" a workflow there is today not one
single raw conversion software package available, free
or proprietary and owned by Nikon or not, that can
decode the RAW file that will be produced by the camera
that will someday replace the current Nikon flagship D4
line of cameras (i.e., the Nikon D5).
Futureproofing is about making your picture files of today available
tomorrow next year and century.
they're futureproof.

anyone can read raws from a decade ago and there's *no* reason why that
is suddenly going to become impossible.

as long as you can read it at some point, you can read it in the future.
Post by android
Post by Floyd L. Davidson
Your way of looking at that is to say that the D5 NEF
file format is encrypted, because nobody today can
figure out what it is or how to decode it, and therefore
Nikon is going to steal everyone's right to use other
than Nikon Software when they release a model D5 and
don't bother to tell anyone exactly how to read the new
NEF format!
Nonencrypted rawdata will always be readable through reverse engineering.
then what's the problem?
android
2013-11-05 19:58:48 UTC
Permalink
Post by nospam
Post by android
Post by Floyd L. Davidson
You've clearly gotten yourself far more than a bit
confused about how RAW files work and what they are.
The raw files consists of raw image data. I E the digitized conversion
of current that the fotosites or pixels produce at exposure and the
associated metadata...
Post by Floyd L. Davidson
Keep in mind that in terms of this so called
"futureproofing" a workflow there is today not one
single raw conversion software package available, free
or proprietary and owned by Nikon or not, that can
decode the RAW file that will be produced by the camera
that will someday replace the current Nikon flagship D4
line of cameras (i.e., the Nikon D5).
Futureproofing is about making your picture files of today available
tomorrow next year and century.
they're futureproof.
Only if you can guarantee the accessibility of compatible software and
computers.
Post by nospam
anyone can read raws from a decade ago and there's *no* reason why that
is suddenly going to become impossible.
as long as you can read it at some point, you can read it in the future.
The hieroglyphs was easy to read for learned Copts in ancient times.
Modern westerners had to wait for the rosetta stone in order to figure
it out...
Post by nospam
Post by android
Post by Floyd L. Davidson
Your way of looking at that is to say that the D5 NEF
file format is encrypted, because nobody today can
figure out what it is or how to decode it, and therefore
Nikon is going to steal everyone's right to use other
than Nikon Software when they release a model D5 and
don't bother to tell anyone exactly how to read the new
NEF format!
Nonencrypted rawdata will always be readable through reverse engineering.
then what's the problem?
Encryption... Is your head built like a Sinar???
--
teleportation kills
nospam
2013-11-05 20:10:21 UTC
Permalink
Post by android
Post by nospam
Post by android
Post by Floyd L. Davidson
Keep in mind that in terms of this so called
"futureproofing" a workflow there is today not one
single raw conversion software package available, free
or proprietary and owned by Nikon or not, that can
decode the RAW file that will be produced by the camera
that will someday replace the current Nikon flagship D4
line of cameras (i.e., the Nikon D5).
Futureproofing is about making your picture files of today available
tomorrow next year and century.
they're futureproof.
Only if you can guarantee the accessibility of compatible software and
computers.
given that source code exists to read the files, it is guaranteed.

every existing app that can read nikon raw files, which is a *lot* of
apps, will continue to work. they are not going to suddenly stop
working.

a particular app might not run on some future version of mac or
windows, but that doesn't matter. all you need to do is virtualize
whatever system you have now on that future system.

also, raw converters maintain compatibility with older raw files, so
adobe camera raw of the future will read raws of today, as will other
raw processing tools.

it's a non-issue.
android
2013-11-05 20:21:59 UTC
Permalink
Post by nospam
Post by android
Post by nospam
Post by android
Post by Floyd L. Davidson
Keep in mind that in terms of this so called
"futureproofing" a workflow there is today not one
single raw conversion software package available, free
or proprietary and owned by Nikon or not, that can
decode the RAW file that will be produced by the camera
that will someday replace the current Nikon flagship D4
line of cameras (i.e., the Nikon D5).
Futureproofing is about making your picture files of today available
tomorrow next year and century.
they're futureproof.
Only if you can guarantee the accessibility of compatible software and
computers.
given that source code exists to read the files, it is guaranteed.
every existing app that can read nikon raw files, which is a *lot* of
apps, will continue to work. they are not going to suddenly stop
working.
a particular app might not run on some future version of mac or
windows, but that doesn't matter. all you need to do is virtualize
whatever system you have now on that future system.
also, raw converters maintain compatibility with older raw files, so
adobe camera raw of the future will read raws of today, as will other
raw processing tools.
it's a non-issue.
You are not in a position to guarantee the above.

E O L
--
teleportation kills
Floyd L. Davidson
2013-11-05 21:22:48 UTC
Permalink
Post by android
Post by nospam
Post by android
Post by nospam
Post by android
Post by Floyd L. Davidson
Keep in mind that in terms of this so called
"futureproofing" a workflow there is today not one
single raw conversion software package available, free
or proprietary and owned by Nikon or not, that can
decode the RAW file that will be produced by the camera
that will someday replace the current Nikon flagship D4
line of cameras (i.e., the Nikon D5).
Futureproofing is about making your picture files of today available
tomorrow next year and century.
they're futureproof.
Only if you can guarantee the accessibility of compatible software and
computers.
given that source code exists to read the files, it is guaranteed.
every existing app that can read nikon raw files, which is a *lot* of
apps, will continue to work. they are not going to suddenly stop
working.
a particular app might not run on some future version of mac or
windows, but that doesn't matter. all you need to do is virtualize
whatever system you have now on that future system.
also, raw converters maintain compatibility with older raw files, so
adobe camera raw of the future will read raws of today, as will other
raw processing tools.
it's a non-issue.
You are not in a position to guarantee the above.
E O L
Actually he is, and so are many many others.

The source code to DCRAW is freely available, and it is
written in ISO Standard C. That means is it absolutely
is guaranteed to be available literally forever.

No matter what new computer hardware is developed, there
is a prescribed standard for implementing a compiler
than will produce a working DCRAW program that will
convert every NEF format that Nikon has developed to
date.

Unless you think ISO will disappear and all trace of
their current standards will be lost, it really is a
non-issue.
--
Floyd L. Davidson http://www.apaflo.com/floyd_davidson
Ukpeagvik (Barrow, Alaska) ***@apaflo.com
J. Clarke
2013-11-05 21:40:03 UTC
Permalink
Post by Floyd L. Davidson
Post by android
Post by nospam
Post by android
Post by nospam
Post by android
Post by Floyd L. Davidson
Keep in mind that in terms of this so called
"futureproofing" a workflow there is today not one
single raw conversion software package available, free
or proprietary and owned by Nikon or not, that can
decode the RAW file that will be produced by the camera
that will someday replace the current Nikon flagship D4
line of cameras (i.e., the Nikon D5).
Futureproofing is about making your picture files of today available
tomorrow next year and century.
they're futureproof.
Only if you can guarantee the accessibility of compatible software and
computers.
given that source code exists to read the files, it is guaranteed.
every existing app that can read nikon raw files, which is a *lot* of
apps, will continue to work. they are not going to suddenly stop
working.
a particular app might not run on some future version of mac or
windows, but that doesn't matter. all you need to do is virtualize
whatever system you have now on that future system.
also, raw converters maintain compatibility with older raw files, so
adobe camera raw of the future will read raws of today, as will other
raw processing tools.
it's a non-issue.
You are not in a position to guarantee the above.
E O L
Actually he is, and so are many many others.
The source code to DCRAW is freely available, and it is
written in ISO Standard C. That means is it absolutely
is guaranteed to be available literally forever.
And if they decide to change to ECRAW, then what?
Post by Floyd L. Davidson
No matter what new computer hardware is developed, there
is a prescribed standard for implementing a compiler
than will produce a working DCRAW program that will
convert every NEF format that Nikon has developed to
date.
To what date?
Post by Floyd L. Davidson
Unless you think ISO will disappear and all trace of
their current standards will be lost, it really is a
non-issue.
What obligates Nikon to follow any kind of ISO standard? Is the Emperor
going to order them to commit seppuku or something if they don't?
Floyd L. Davidson
2013-11-05 22:10:38 UTC
Permalink
Post by J. Clarke
Post by Floyd L. Davidson
Post by android
Post by nospam
Post by android
Post by nospam
Post by android
Post by Floyd L. Davidson
Keep in mind that in terms of this so called
"futureproofing" a workflow there is today not one
single raw conversion software package available, free
or proprietary and owned by Nikon or not, that can
decode the RAW file that will be produced by the camera
that will someday replace the current Nikon flagship D4
line of cameras (i.e., the Nikon D5).
Futureproofing is about making your picture files of today available
tomorrow next year and century.
they're futureproof.
Only if you can guarantee the accessibility of compatible software and
computers.
given that source code exists to read the files, it is guaranteed.
every existing app that can read nikon raw files, which is a *lot* of
apps, will continue to work. they are not going to suddenly stop
working.
a particular app might not run on some future version of mac or
windows, but that doesn't matter. all you need to do is virtualize
whatever system you have now on that future system.
also, raw converters maintain compatibility with older raw files, so
adobe camera raw of the future will read raws of today, as will other
raw processing tools.
it's a non-issue.
You are not in a position to guarantee the above.
E O L
Actually he is, and so are many many others.
The source code to DCRAW is freely available, and it is
written in ISO Standard C. That means is it absolutely
is guaranteed to be available literally forever.
And if they decide to change to ECRAW, then what?
I assume that is a typo and that you meant change DCRAW.

The code for DCRAW is freely available, and has been archived
all over the world. It isn't going to disappear, nor is there
ever going to be a "new version" that results in the older
versions being unavailable.
Post by J. Clarke
Post by Floyd L. Davidson
No matter what new computer hardware is developed, there
is a prescribed standard for implementing a compiler
than will produce a working DCRAW program that will
convert every NEF format that Nikon has developed to
date.
To what date?
Today. That's what "to date" means.
Post by J. Clarke
Post by Floyd L. Davidson
Unless you think ISO will disappear and all trace of
their current standards will be lost, it really is a
non-issue.
What obligates Nikon to follow any kind of ISO standard? Is the Emperor
going to order them to commit seppuku or something if they don't?
I'm sorry, you don't seem to understand what that means.
The ISO standard is for the C compiler that can compile
the source code to DCRAW. Because it is written in
Standard C there is no possibility that the source code
will ever be unreadable or that there cannot be a
compiler built that will generate the appropriate
program.

That of course has nothing to do with Nikon, nor with
future releases of DCRAW as such. It just means that
what we have now is not going to be lost.
--
Floyd L. Davidson http://www.apaflo.com/floyd_davidson
Ukpeagvik (Barrow, Alaska) ***@apaflo.com
nospam
2013-11-05 22:30:21 UTC
Permalink
Post by Floyd L. Davidson
Post by J. Clarke
Post by Floyd L. Davidson
Unless you think ISO will disappear and all trace of
their current standards will be lost, it really is a
non-issue.
What obligates Nikon to follow any kind of ISO standard? Is the Emperor
going to order them to commit seppuku or something if they don't?
I'm sorry, you don't seem to understand what that means.
The ISO standard is for the C compiler that can compile
the source code to DCRAW. Because it is written in
Standard C there is no possibility that the source code
will ever be unreadable or that there cannot be a
compiler built that will generate the appropriate
program.
and if c were to go away, it could be ported to another language.
J. Clarke
2013-11-06 00:02:48 UTC
Permalink
Post by Floyd L. Davidson
Post by J. Clarke
Post by Floyd L. Davidson
Post by android
Post by nospam
Post by android
Post by nospam
Post by android
Post by Floyd L. Davidson
Keep in mind that in terms of this so called
"futureproofing" a workflow there is today not one
single raw conversion software package available, free
or proprietary and owned by Nikon or not, that can
decode the RAW file that will be produced by the camera
that will someday replace the current Nikon flagship D4
line of cameras (i.e., the Nikon D5).
Futureproofing is about making your picture files of today available
tomorrow next year and century.
they're futureproof.
Only if you can guarantee the accessibility of compatible software and
computers.
given that source code exists to read the files, it is guaranteed.
every existing app that can read nikon raw files, which is a *lot* of
apps, will continue to work. they are not going to suddenly stop
working.
a particular app might not run on some future version of mac or
windows, but that doesn't matter. all you need to do is virtualize
whatever system you have now on that future system.
also, raw converters maintain compatibility with older raw files, so
adobe camera raw of the future will read raws of today, as will other
raw processing tools.
it's a non-issue.
You are not in a position to guarantee the above.
E O L
Actually he is, and so are many many others.
The source code to DCRAW is freely available, and it is
written in ISO Standard C. That means is it absolutely
is guaranteed to be available literally forever.
And if they decide to change to ECRAW, then what?
I assume that is a typo and that you meant change DCRAW.
Nope. What if they decide to produce new closed-source software from
the ground up and call it ECRAW?
Post by Floyd L. Davidson
The code for DCRAW is freely available, and has been archived
all over the world. It isn't going to disappear, nor is there
ever going to be a "new version" that results in the older
versions being unavailable.
Who cares? Do the creators of DCRAW control Nikon? If not then why is
Nikon obligated to use encodings that can be managed by DCRAW?
Post by Floyd L. Davidson
Post by J. Clarke
Post by Floyd L. Davidson
No matter what new computer hardware is developed, there
is a prescribed standard for implementing a compiler
than will produce a working DCRAW program that will
convert every NEF format that Nikon has developed to
date.
To what date?
Today. That's what "to date" means.
And what about future encodings?
Post by Floyd L. Davidson
Post by J. Clarke
Post by Floyd L. Davidson
Unless you think ISO will disappear and all trace of
their current standards will be lost, it really is a
non-issue.
What obligates Nikon to follow any kind of ISO standard? Is the Emperor
going to order them to commit seppuku or something if they don't?
I'm sorry, you don't seem to understand what that means.
What what means?
Post by Floyd L. Davidson
The ISO standard is for the C compiler that can compile
the source code to DCRAW.
And if they write the code in Ada or PL/1 or NTRAN then what?

I'm sorry, but if you think that a standard for a C compiler places some
kind of constraint on the nature of the encodings that can be used by
Nikon or any other company you have no clue what a compiler does.
Post by Floyd L. Davidson
Because it is written in
Standard C there is no possibility that the source code
will ever be unreadable or that there cannot be a
compiler built that will generate the appropriate
program.
So what?
Post by Floyd L. Davidson
That of course has nothing to do with Nikon, nor with
future releases of DCRAW as such. It just means that
what we have now is not going to be lost.
Which has nothing to do with what Nikon might or might not do in the
future.
nospam
2013-11-06 01:29:17 UTC
Permalink
Post by J. Clarke
Post by Floyd L. Davidson
Post by J. Clarke
Post by Floyd L. Davidson
The source code to DCRAW is freely available, and it is
written in ISO Standard C. That means is it absolutely
is guaranteed to be available literally forever.
And if they decide to change to ECRAW, then what?
I assume that is a typo and that you meant change DCRAW.
Nope. What if they decide to produce new closed-source software from
the ground up and call it ECRAW?
unless dave coffin changes his name to eric, it won't be called ecraw.

yet another bogus made up scenario.

if one day he stops updating dcraw, someone else would take over the
code, and if that didn't happen for some reason, what already exists
isn't going to vaporize.

in other words, there will *always* be a way to read nikon raw and
other raws.
Post by J. Clarke
Post by Floyd L. Davidson
The code for DCRAW is freely available, and has been archived
all over the world. It isn't going to disappear, nor is there
ever going to be a "new version" that results in the older
versions being unavailable.
Who cares? Do the creators of DCRAW control Nikon? If not then why is
Nikon obligated to use encodings that can be managed by DCRAW?
they don't have to control anything. whatever nikon and canon and
others do, dcraw and other raw tools come up with code to process it.
it's been this way for years and shows no signs of changing.
Post by J. Clarke
Post by Floyd L. Davidson
Post by J. Clarke
Post by Floyd L. Davidson
No matter what new computer hardware is developed, there
is a prescribed standard for implementing a compiler
than will produce a working DCRAW program that will
convert every NEF format that Nikon has developed to
date.
To what date?
Today. That's what "to date" means.
And what about future encodings?
what about them?

yet another made up scenario.

if a future camera locks down the format, don't buy it.

today's cameras don't lock down the entire image and there's no sign of
any camera maker doing that (other than sigma, who sells so few cameras
that it doesn't matter at all and even that has been cracked).
Post by J. Clarke
Post by Floyd L. Davidson
Post by J. Clarke
Post by Floyd L. Davidson
Unless you think ISO will disappear and all trace of
their current standards will be lost, it really is a
non-issue.
What obligates Nikon to follow any kind of ISO standard? Is the Emperor
going to order them to commit seppuku or something if they don't?
I'm sorry, you don't seem to understand what that means.
What what means?
Post by Floyd L. Davidson
The ISO standard is for the C compiler that can compile
the source code to DCRAW.
And if they write the code in Ada or PL/1 or NTRAN then what?
port dcraw to whatever language you want.

dcraw source is available, as is source to c compilers, so you will
*always* be able to compile it.
Post by J. Clarke
I'm sorry, but if you think that a standard for a C compiler places some
kind of constraint on the nature of the encodings that can be used by
Nikon or any other company you have no clue what a compiler does.
more accurately, you haven't a clue.
Post by J. Clarke
Post by Floyd L. Davidson
Because it is written in
Standard C there is no possibility that the source code
will ever be unreadable or that there cannot be a
compiler built that will generate the appropriate
program.
So what?
it means there will never be a situation where the raw files are
unreadable.

very simple concept.
Post by J. Clarke
Post by Floyd L. Davidson
That of course has nothing to do with Nikon, nor with
future releases of DCRAW as such. It just means that
what we have now is not going to be lost.
Which has nothing to do with what Nikon might or might not do in the
future.
or canon, who encrypts too.

the question *you* need to answer is what will *canon* do in the
future, as they've already shown that they *also* encrypt part of the
raw.

either you're giving a free pass to canon, or you are very, very
ignorant.
Trevor
2013-11-06 06:52:33 UTC
Permalink
Post by Floyd L. Davidson
Post by android
Post by Floyd L. Davidson
Post by android
Off course it maters to endusers if the can edit their files with third
party software. It's called futureproofing your workflow.
Because of the way Nikon did it, there is not and never
has been any problem. I am one who shoots Nikon but has
never used Nikon's software.
The reason for Nikon to steal your right to full access to your files
created by you with your equipment is to force you to use their or their
licensees software to get the most out of your creative process and
work. That process has been stalled but Nikon, and others that followed
them has not backed from encrypting some metadata and therefore not
clearly stated that full encryption won't happen in the future. There is
no honest explanation to why encryption of meta data is a benefit to the
owner of the file.
1) The encryption of metadata does not need to be a
benefit to the owner of the file for Nikon or any
other company to use encryption.
2) Your statement that Nikon would "steal your right to
full access" is very bizzare considering that what
Nikon did was *clearly* not meant to deny full
access. As noted previously, which you are ignoring,
Nikon actually embedded the encryption key into the
file to begin with.
3) Nothing you have claimed or ignored either way has
even the slightest effect on the capability of any
camera manufacturere to use encryption of the
metadata in their RAW files. Any and or all of them
could start using encryption tomorrow, whether they
have ever even hinted at it in the past or not.
As noted, I use Nikon cameras (and used a Nikon D2X, one
of the initial cameras that encrypted the White Balance
information), but I have never once even looked at an
image, much less edited one, using any Nikon software.
Your claim that Nikon tried to prevent that is hilarious
on it's face! The idea that what Nikon did in 2005 is
an issue with "futureproofing" my workflow is even more
offbase, given that 8 years down the road there is still
not the slightest significant effort at preventing my
use of non-Nikon software.
Which begs the question why they think an 'insignificant effort' is
necessary and desirable?
Certainly doesn't provide any benefit to the user that I can see.

Trevor.
Floyd L. Davidson
2013-11-06 13:54:27 UTC
Permalink
Post by Trevor
Post by Floyd L. Davidson
Post by android
Post by Floyd L. Davidson
Post by android
Off course it maters to endusers if the can edit their files with third
party software. It's called futureproofing your workflow.
Because of the way Nikon did it, there is not and never
has been any problem. I am one who shoots Nikon but has
never used Nikon's software.
The reason for Nikon to steal your right to full access to your files
created by you with your equipment is to force you to use their or their
licensees software to get the most out of your creative process and
work. That process has been stalled but Nikon, and others that followed
them has not backed from encrypting some metadata and therefore not
clearly stated that full encryption won't happen in the future. There is
no honest explanation to why encryption of meta data is a benefit to the
owner of the file.
1) The encryption of metadata does not need to be a
benefit to the owner of the file for Nikon or any
other company to use encryption.
2) Your statement that Nikon would "steal your right to
full access" is very bizzare considering that what
Nikon did was *clearly* not meant to deny full
access. As noted previously, which you are ignoring,
Nikon actually embedded the encryption key into the
file to begin with.
3) Nothing you have claimed or ignored either way has
even the slightest effect on the capability of any
camera manufacturere to use encryption of the
metadata in their RAW files. Any and or all of them
could start using encryption tomorrow, whether they
have ever even hinted at it in the past or not.
As noted, I use Nikon cameras (and used a Nikon D2X, one
of the initial cameras that encrypted the White Balance
information), but I have never once even looked at an
image, much less edited one, using any Nikon software.
Your claim that Nikon tried to prevent that is hilarious
on it's face! The idea that what Nikon did in 2005 is
an issue with "futureproofing" my workflow is even more
offbase, given that 8 years down the road there is still
not the slightest significant effort at preventing my
use of non-Nikon software.
Which begs the question why they think an 'insignificant effort' is
necessary and desirable?
Certainly doesn't provide any benefit to the user that I can see.
Trevor.
That doesn't "beg the question" at all. Look up what
that means.

And who says they thought *that* was the purpose? We
don't know at all why, but we do know that almost every
camera manufacturer has done almost exactly the same
thing.

And since when is it necessary for every design aspect
of a camera need to provide benefit, in particular that
*you* can see, to the user? If it provides benefit the
to manufacturer, whether you see what it is or not, they
are very likely to do it.
--
Floyd L. Davidson http://www.apaflo.com/floyd_davidson
Ukpeagvik (Barrow, Alaska) ***@apaflo.com
Trevor
2013-11-08 02:54:00 UTC
Permalink
Post by Floyd L. Davidson
Post by Trevor
Post by Floyd L. Davidson
Post by android
Post by Floyd L. Davidson
Post by android
Off course it maters to endusers if the can edit their files with third
party software. It's called futureproofing your workflow.
Because of the way Nikon did it, there is not and never
has been any problem. I am one who shoots Nikon but has
never used Nikon's software.
The reason for Nikon to steal your right to full access to your files
created by you with your equipment is to force you to use their or their
licensees software to get the most out of your creative process and
work. That process has been stalled but Nikon, and others that followed
them has not backed from encrypting some metadata and therefore not
clearly stated that full encryption won't happen in the future. There is
no honest explanation to why encryption of meta data is a benefit to the
owner of the file.
1) The encryption of metadata does not need to be a
benefit to the owner of the file for Nikon or any
other company to use encryption.
2) Your statement that Nikon would "steal your right to
full access" is very bizzare considering that what
Nikon did was *clearly* not meant to deny full
access. As noted previously, which you are ignoring,
Nikon actually embedded the encryption key into the
file to begin with.
3) Nothing you have claimed or ignored either way has
even the slightest effect on the capability of any
camera manufacturere to use encryption of the
metadata in their RAW files. Any and or all of them
could start using encryption tomorrow, whether they
have ever even hinted at it in the past or not.
As noted, I use Nikon cameras (and used a Nikon D2X, one
of the initial cameras that encrypted the White Balance
information), but I have never once even looked at an
image, much less edited one, using any Nikon software.
Your claim that Nikon tried to prevent that is hilarious
on it's face! The idea that what Nikon did in 2005 is
an issue with "futureproofing" my workflow is even more
offbase, given that 8 years down the road there is still
not the slightest significant effort at preventing my
use of non-Nikon software.
Which begs the question why they think an 'insignificant effort' is
necessary and desirable?
Certainly doesn't provide any benefit to the user that I can see.
That doesn't "beg the question" at all. Look up what
that means.
Look up what being an arse means.
Post by Floyd L. Davidson
And who says they thought *that* was the purpose? We
don't know at all why,
Because they were selling the conversion software at the time, rather than
giving it away in the box like most other manufacturers, had a lot to do
with it I'm certain!
Post by Floyd L. Davidson
but we do know that almost every
camera manufacturer has done almost exactly the same
thing.
Not at all, which is why Adobe had no problems with almost any of them other
than Nikon.
Post by Floyd L. Davidson
And since when is it necessary for every design aspect
of a camera need to provide benefit, in particular that
*you* can see, to the user? If it provides benefit the
to manufacturer, whether you see what it is or not, they
are very likely to do it.
Yep, that's the Apple way too, do what best suits the manufacturer, and as
long as the sheep keep buying, no need to worry what actually suits the
user.
Thankfully I have a choice not to support that business model, just as you
have a choice to do so.
Wasting time defending it though is something I'd want to get paid for!

Trevor.
nospam
2013-11-08 06:18:21 UTC
Permalink
Post by Trevor
Post by Floyd L. Davidson
And who says they thought *that* was the purpose? We
don't know at all why,
Because they were selling the conversion software at the time, rather than
giving it away in the box like most other manufacturers, had a lot to do
with it I'm certain!
wrong.

nikon software was (and still is) *included* with their cameras, just
like other camera makers.

nikon *also* offered more advanced software for sale that had
additional features than what was bundled.

neither of those were required since nikon raws are readable by *many*
non-nikon apps.
Post by Trevor
Post by Floyd L. Davidson
but we do know that almost every
camera manufacturer has done almost exactly the same
thing.
Not at all, which is why Adobe had no problems with almost any of them other
than Nikon.
adobe didn't have a problem with nikon either. adobe camera raw
supports just about every camera out there.
Post by Trevor
Post by Floyd L. Davidson
And since when is it necessary for every design aspect
of a camera need to provide benefit, in particular that
*you* can see, to the user? If it provides benefit the
to manufacturer, whether you see what it is or not, they
are very likely to do it.
Yep, that's the Apple way too, do what best suits the manufacturer, and as
long as the sheep keep buying, no need to worry what actually suits the
user.
nonsense.

apple sticks to open standards, which is the opposite of what microsoft
does.
Post by Trevor
Thankfully I have a choice not to support that business model, just as you
have a choice to do so.
what camera do you have?

because they all encrypt something.

for instance, canon encrypts white balance too, just like nikon does.
David Taylor
2013-11-08 07:49:07 UTC
Permalink
On 08/11/2013 06:18, nospam wrote:
[]
Post by nospam
apple sticks to open standards, which is the opposite of what microsoft
does.
[]

You had me falling off my chair with laughter at that one! Talk about
closed and proprietary - Apple is the prime example!

But if you want to direct your energy somewhere useful, how about
standardising Li-ion batteries so that each manufacturer and each new
camera range requires buying Li-ion batteries again?
--
Cheers,
David
Web: http://www.satsignal.eu
nospam
2013-11-08 08:17:19 UTC
Permalink
Post by David Taylor
Post by nospam
apple sticks to open standards, which is the opposite of what microsoft
does.
You had me falling off my chair with laughter at that one! Talk about
closed and proprietary - Apple is the prime example!
once you climb back on your chair, you ought to check again.

wmv and ntfs are microsoft proprietary. microsoft also invented their
own programming language, c# as well as .net for platform lock-in.
microsoft's visual studio compiler is non-standard and code written
with it, even using standard languages such as c++, was often not
portable to other platforms, intentionally so.

microsoft also created their own non-standard browser extensions and
servers for further lock-in, which is why you get the 'requires
internet explorer' bullshit. fortunately, that is mostly a thing of the
past, as open standards have prevailed.

also, nothing microsoft does is open source. good luck getting the
source code to *any* parts of windows.

meanwhile, apple uses industry standard formats and languages,
including html5, pdf, mp3, aac, mpeg2, mpeg 4, c++ and objective-c.

apple also creates and contributes to open source projects, some of
which are used by several of their competitors, notably webkit. the
kernel of mac os x and ios is open source, as are substantial other
parts of it.

to claim that apple is proprietary is flat out bullshit.
Post by David Taylor
But if you want to direct your energy somewhere useful, how about
standardising Li-ion batteries so that each manufacturer and each new
camera range requires buying Li-ion batteries again?
wont' happen because customers want smaller devices and therefore, each
devices needs its own battery design.
David Taylor
2013-11-08 10:06:25 UTC
Permalink
On 08/11/2013 08:17, nospam wrote:
[]
Post by nospam
to claim that apple is proprietary is flat out bullshit.
In your view - my view differs.

The NTP code which I use compiles equally on FreeBSD (Intel) and on the
Raspberry Pi (ARM), as well as in MS Visual Studio. I don't see Apple's
OS running on the same variety of hardware as does Windows and other
Microsoft programs.

But as this is a photography group, I'll not respond further about this
off-topic deviation.
--
Cheers,
David
Web: http://www.satsignal.eu
nospam
2013-11-08 11:27:28 UTC
Permalink
Post by David Taylor
Post by nospam
to claim that apple is proprietary is flat out bullshit.
In your view - my view differs.
that's fine, but realize it's based on myth, not fact.
Post by David Taylor
The NTP code which I use compiles equally on FreeBSD (Intel) and on the
Raspberry Pi (ARM), as well as in MS Visual Studio. I don't see Apple's
OS running on the same variety of hardware as does Windows and other
Microsoft programs.
ntp isn't microsoft proprietary code, which is why it compiles on
multiple platforms.

let's see you get windows apps running on a raspberry pi or any portion
of windows itself. good luck on that one.

microsoft visual studio is proprietary and not fully standards
compliant, although it's much better than it used to be. most microsoft
programs are nonstandard c#/.net instead of standard c/c++. in other
words, not portable. visual studio is also not free.

apple's os x kernel is open source. feel free to compile it on any
hardware you want. quite a bit of the rest of apple's system is also
open source, available for anyone to use, for whatever purpose they
want.

apple's xcode development environment is completely free, uses open
source compilers (llvm & gcc) and is very standards compliant.
David Taylor
2013-11-08 17:31:19 UTC
Permalink
On 08/11/2013 11:27, nospam wrote:
[]
Post by nospam
that's fine, but realize it's based on myth, not fact.
It's based on over 45 years of experience.
Post by nospam
ntp isn't microsoft proprietary code, which is why it compiles on
multiple platforms.
.. and I'm sure there is Apple proprietary code which won't compile on
other platforms.

I've found no problems processing the images and video from my camera on
Windows platforms, nor with displaying them in the iPad. I'm sure the
same will be true of images from the new Nikon, which is the subject of
this thread.
--
Cheers,
David
Web: http://www.satsignal.eu
nospam
2013-11-08 19:57:19 UTC
Permalink
Post by David Taylor
Post by nospam
that's fine, but realize it's based on myth, not fact.
It's based on over 45 years of experience.
that experience does not include knowing much about apple.

isn't the ipad your first apple product?
Post by David Taylor
Post by nospam
ntp isn't microsoft proprietary code, which is why it compiles on
multiple platforms.
.. and I'm sure there is Apple proprietary code which won't compile on
other platforms.
there is, but there is still quite a bit of open source components and
industry standard format support.

this is in stark contrast to microsoft, who only knows proprietary,
with no open source components and pushes their own proprietary formats
that they created even though there is an existing standard format that
works just as well.
Post by David Taylor
I've found no problems processing the images and video from my camera on
Windows platforms, nor with displaying them in the iPad. I'm sure the
same will be true of images from the new Nikon, which is the subject of
this thread.
that's because nikon, like other cameras, create industry standard jpeg
and the raws can be processed by a wide variety of tools and on just
about any platform, including ipads.

nikon didn't come up with a proprietary format that nobody could read
without paying huge sums of money to nikon, which is what's required
for licensing wma/wmv from microsoft (which really is a *lot* of
money).
sid
2013-11-08 18:57:05 UTC
Permalink
Post by nospam
Post by David Taylor
Post by nospam
apple sticks to open standards, which is the opposite of what microsoft
does.
You had me falling off my chair with laughter at that one! Talk about
closed and proprietary - Apple is the prime example!
once you climb back on your chair, you ought to check again.
microsoft proprietary.
Everyone knows that, so what?
Post by nospam
meanwhile, apple uses industry standard formats and languages,
including html5, pdf, mp3, aac, mpeg2, mpeg 4, c++ and objective-c.
Why wouldn't they, interoperability is good sense plus Apple get those
things without cost.
Post by nospam
apple also creates and contributes to open source projects,
Which ones have they created?
Post by nospam
some of
which are used by several of their competitors, notably webkit.
Which I think you'll find is a fork of KHTML and KJS,
Post by nospam
the
kernel of mac os x and ios is open source,
That is true but of no use to anyone for anything, if it was there would be
a slew of alternative OSs based on those kernels. There isn't.
Post by nospam
as are substantial other
parts of it.
Which other substantial parts are?
Post by nospam
to claim that apple is proprietary is flat out bullshit.
No it's not. What do you think would happen if I cloned the latest OSX,
rebranded it and released it back to the public?
--
sid
nospam
2013-11-08 19:57:24 UTC
Permalink
Post by sid
Post by nospam
Post by David Taylor
Post by nospam
apple sticks to open standards, which is the opposite of what microsoft
does.
You had me falling off my chair with laughter at that one! Talk about
closed and proprietary - Apple is the prime example!
once you climb back on your chair, you ought to check again.
microsoft proprietary.
Everyone knows that, so what?
apparently not everyone because the myth lives on.
Post by sid
Post by nospam
meanwhile, apple uses industry standard formats and languages,
including html5, pdf, mp3, aac, mpeg2, mpeg 4, c++ and objective-c.
Why wouldn't they, interoperability is good sense plus Apple get those
things without cost.
the point is that apple doesn't invent their own formats to lock you
into their platform. they use existing standard formats.

microsoft invents their own proprietary formats for platform lock-in,
such as wma, wmv, c# and many others. microsoft is anything *but*
standard. they also make modifications to existing standards so only
microsoft products work properly, such as what they did with internet
explorer some years ago.
Post by sid
Post by nospam
apple also creates and contributes to open source projects,
Which ones have they created?
webkit and gcd are theirs, and a huge part of llvm is theirs.
Post by sid
Post by nospam
some of
which are used by several of their competitors, notably webkit.
Which I think you'll find is a fork of KHTML and KJS,
originally webkit began as a fork of khtml but it's nothing at all like
it now.

webkit is *far* more capable and way the hell faster than khtml ever
was, with most of the work from apple, and a large part from google.

most of apple's competitors use apple's own webkit, including google,
amazon, blackberry, palm (when they existed), nokia (before they went
windows) and several others.
Post by sid
Post by nospam
the
kernel of mac os x and ios is open source,
That is true but of no use to anyone for anything, if it was there would be
a slew of alternative OSs based on those kernels. There isn't.
at least it's open.

where do you get the windows kernel? oh yea, you don't.
Post by sid
Post by nospam
as are substantial other
parts of it.
Which other substantial parts are?
apache, cups, python, ruby, git, llvm and a shitload more.

<http://opensource.apple.com/release/os-x-109/>

what parts of windows are open source? oh yea, none.
Post by sid
Post by nospam
to claim that apple is proprietary is flat out bullshit.
No it's not. What do you think would happen if I cloned the latest OSX,
rebranded it and released it back to the public?
i didn't say *all* of what apple does is open. some is and some is not.

compare that to microsoft where everything is proprietary and closed.

what i said was that apple is more open than microsoft, and they are,
which you confirm.
sid
2013-11-08 20:58:55 UTC
Permalink
Post by nospam
Post by sid
Post by nospam
microsoft proprietary.
Everyone knows that, so what?
apparently not everyone because the myth lives on.
Eh? What myth? Where is it living on?
Post by nospam
webkit is *far* more capable and way the hell faster than khtml ever
was, with most of the work from apple, and a large part from google.
Well I should hope it is better now than it was when it was forked,
otherwise Apple and Google would have been wasting an awfull lot of time.
Post by nospam
Post by sid
Post by nospam
the
kernel of mac os x and ios is open source,
That is true but of no use to anyone for anything, if it was there would
be a slew of alternative OSs based on those kernels. There isn't.
at least it's open.
The point is it's useless to anyone else so it doesn't matter. It's tuned
for proprietry hardware, to run proprietry software, you would be much
better off using either linux or a bsd kernel if you wanted to actually
develop something. Android is a good example.
Post by nospam
where do you get the windows kernel? oh yea, you don't.
More to the point, why the fcuk would you want to?
Post by nospam
Post by sid
Post by nospam
as are substantial other
parts of it.
Which other substantial parts are?
apache, cups, python, ruby, git, llvm and a shitload more.
Those programs aren't actually part of OSX though are they. They are just
open source programs, mostly either GPL or BSD licensed, that Apple include
with their OS, just the same as countless Linux distros and all the BSDs etc
etc do.
Post by nospam
<http://opensource.apple.com/release/os-x-109/>
what parts of windows are open source? oh yea, none.
The important parts of OSX are not open source either are they?
Post by nospam
Post by sid
Post by nospam
to claim that apple is proprietary is flat out bullshit.
No it's not. What do you think would happen if I cloned the latest OSX,
rebranded it and released it back to the public?
Answer the question and explain why.
Post by nospam
i didn't say *all* of what apple does is open. some is and some is not.
So your "flat out bullshit" bullshit is just bullshit then?
Post by nospam
compare that to microsoft where everything is proprietary and closed.
I'm not disputing that,
--
sid
nospam
2013-11-08 22:43:53 UTC
Permalink
Post by sid
Post by nospam
Post by sid
Post by nospam
microsoft proprietary.
Everyone knows that, so what?
apparently not everyone because the myth lives on.
Eh? What myth? Where is it living on?
the myth that apple is proprietary and microsoft is open. it's actually
the other way around.
Post by sid
Post by nospam
webkit is *far* more capable and way the hell faster than khtml ever
was, with most of the work from apple, and a large part from google.
Well I should hope it is better now than it was when it was forked,
otherwise Apple and Google would have been wasting an awfull lot of time.
you made it seem like it's just a minor change to khtml, when in
reality, it's drastically different that only began as khtml, with
apple and later google running with the ball, and running far.
Post by sid
Post by nospam
Post by sid
Post by nospam
the
kernel of mac os x and ios is open source,
That is true but of no use to anyone for anything, if it was there would
be a slew of alternative OSs based on those kernels. There isn't.
at least it's open.
The point is it's useless to anyone else so it doesn't matter. It's tuned
for proprietry hardware, to run proprietry software, you would be much
better off using either linux or a bsd kernel if you wanted to actually
develop something. Android is a good example.
whether it's useful or useless is irrelevant.

the fact is that it's open source and anyone can modify it as needed,
which is a lot more than you'll ever get out of microsoft.

also, android being open is yet another myth. only a part of android is
open source, just like os x.

the bulk of android is closed source, namely the apps, with more and
more of it becoming closed source. google wants total control over it.
they do not want android licensees modifying it (another part of it not
being open).in fact, google must approve every android device.
Post by sid
Post by nospam
where do you get the windows kernel? oh yea, you don't.
More to the point, why the fcuk would you want to?
doesn't matter whether anyone wants to or not. they *can't*.

however, one reason why someone might want to look at it is if they're
writing a windows app and want to know why something isn't working
properly or even how something works. they can't just look at the
source to see what microsoft is really doing. they can only guess.
Post by sid
Post by nospam
Post by sid
Post by nospam
as are substantial other
parts of it.
Which other substantial parts are?
apache, cups, python, ruby, git, llvm and a shitload more.
Those programs aren't actually part of OSX though are they. They are just
open source programs, mostly either GPL or BSD licensed, that Apple include
with their OS, just the same as countless Linux distros and all the BSDs etc
etc do.
they are all part of os x. for instance, any time you print, you are
using cups. turn on web sharing and you're using apache.

microsoft, on the other hand doesn't use those. they have their own
nonstandard creations.
Post by sid
Post by nospam
<http://opensource.apple.com/release/os-x-109/>
what parts of windows are open source? oh yea, none.
The important parts of OSX are not open source either are they?
depends what you think is important.

all i said was a lot of os x is open source, which is absolutely true.

you're trying to change it into saying the parts that are open source
must be important, which is arbitrary and depends on the user.
Post by sid
Post by nospam
Post by sid
Post by nospam
to claim that apple is proprietary is flat out bullshit.
No it's not. What do you think would happen if I cloned the latest OSX,
rebranded it and released it back to the public?
Answer the question and explain why.
i did answer it.
Post by sid
Post by nospam
i didn't say *all* of what apple does is open. some is and some is not.
So your "flat out bullshit" bullshit is just bullshit then?
it's exactly accurate.

the original claim was that apple was closed and proprietary. that's
bullshit, which you agree.
Post by sid
Post by nospam
compare that to microsoft where everything is proprietary and closed.
I'm not disputing that,
then you agree with me.
sid
2013-11-09 13:51:50 UTC
Permalink
Post by nospam
Post by sid
Post by nospam
Post by sid
Post by nospam
microsoft proprietary.
Everyone knows that, so what?
apparently not everyone because the myth lives on.
Eh? What myth? Where is it living on?
the myth that apple is proprietary and microsoft is open. it's actually
the other way around.
That's not a myth I'm familiar with, are you sure you're not just making it
up as an excuse to get on some high horse or other?
Post by nospam
Post by sid
Post by nospam
webkit is *far* more capable and way the hell faster than khtml ever
was, with most of the work from apple, and a large part from google.
Well I should hope it is better now than it was when it was forked,
otherwise Apple and Google would have been wasting an awfull lot of time.
you made it seem like it's just a minor change to khtml,
Where did I say or imply that?
Post by nospam
when in reality, it's drastically different that only began as khtml, with
apple and later google running with the ball, and running far.
Post by sid
Post by nospam
Post by sid
Post by nospam
the
kernel of mac os x and ios is open source,
That is true but of no use to anyone for anything, if it was there
would be a slew of alternative OSs based on those kernels. There
isn't.
at least it's open.
The point is it's useless to anyone else so it doesn't matter. It's tuned
for proprietry hardware, to run proprietry software, you would be much
better off using either linux or a bsd kernel if you wanted to actually
develop something. Android is a good example.
whether it's useful or useless is irrelevant.
the fact is that it's open source and anyone can modify it as needed,
which is a lot more than you'll ever get out of microsoft.
also, android being open is yet another myth. only a part of android is
open source, just like os x.
I wasn't passing comment on the openess of Android, only on the fact that
they used a linux kernel as the base for their OS rather than either of the
Apple open source kernels.
Post by nospam
Post by sid
Post by nospam
where do you get the windows kernel? oh yea, you don't.
More to the point, why the fcuk would you want to?
doesn't matter whether anyone wants to or not. they *can't*.
however, one reason why someone might want to look at it is if they're
writing a windows app and want to know why something isn't working
properly or even how something works. they can't just look at the
source to see what microsoft is really doing. they can only guess.
I don't write software so I don't know why you'd want to do that, I do
however know that there are thousands and thousands of different programs
that run just fine on windows without having seen the source code.
Post by nospam
Post by sid
Post by nospam
Post by sid
Post by nospam
as are substantial other
parts of it.
Which other substantial parts are?
apache, cups, python, ruby, git, llvm and a shitload more.
Those programs aren't actually part of OSX though are they. They are just
open source programs, mostly either GPL or BSD licensed, that Apple
include with their OS, just the same as countless Linux distros and all
the BSDs etc etc do.
they are all part of os x. for instance, any time you print, you are
using cups. turn on web sharing and you're using apache.
They are not part of OSX, they are all stand alone programs that are free
for Apple to include with their OS.
Post by nospam
microsoft, on the other hand doesn't use those. they have their own
nonstandard creations.
Like Frankensteins monster, over and over again!
Post by nospam
Post by sid
Post by nospam
<http://opensource.apple.com/release/os-x-109/>
what parts of windows are open source? oh yea, none.
The important parts of OSX are not open source either are they?
depends what you think is important.
As a user, a typical user, which bits do you consider to be important?
Post by nospam
all i said was a lot of os x is open source, which is absolutely true.
you're trying to change it into saying the parts that are open source
must be important, which is arbitrary and depends on the user.
I'm not trying to change anything, I'm implying that the important parts are
not open source. The actual user interface and the programs you actually use
to surf the web, read your email etc are all closed source. Proprietry.
Post by nospam
Post by sid
Post by nospam
Post by sid
Post by nospam
to claim that apple is proprietary is flat out bullshit.
No it's not. What do you think would happen if I cloned the latest
OSX, rebranded it and released it back to the public?
Answer the question and explain why.
i did answer it.
You have done no such thing, the following line is not an answer to the
above question. At all.
Post by nospam
Post by sid
Post by nospam
i didn't say *all* of what apple does is open. some is and some is not.
So your "flat out bullshit" bullshit is just bullshit then?
it's exactly accurate.
No it's not
Post by nospam
the original claim was that apple was closed and proprietary.
It is, but it also uses some open source stuff
Post by nospam
that's bullshit, which you agree.
It's not bullshit, I don't agree with you,
Post by nospam
Post by sid
Post by nospam
compare that to microsoft where everything is proprietary and closed.
I'm not disputing that,
then you agree with me.
On the subject of Microsoft, yes.
--
sid
nospam
2013-11-05 14:59:07 UTC
Permalink
Post by android
Post by Floyd L. Davidson
Post by android
Off course it maters to endusers if the can edit their files with third
party software. It's called futureproofing your workflow.
Because of the way Nikon did it, there is not and never
has been any problem. I am one who shoots Nikon but has
never used Nikon's software.
The reason for Nikon to steal your right to full access to your files
created by you with your equipment is to force you to use their or their
licensees software to get the most out of your creative process and
work. That process has been stalled but Nikon, and others that followed
them has not backed from encrypting some metadata and therefore not
clearly stated that full encryption won't happen in the future. There is
no honest explanation to why encryption of meta data is a benefit to the
owner of the file.
nikon is not stealing anyone's rights. you aren't required to use
nikon's software. you are free to choose from among dozens of alternate
raw processing tools, all of which work perfectly fine.

stop spreading lies.
nospam
2013-11-05 14:59:06 UTC
Permalink
Post by android
Post by nospam
Post by android
And don't mind having their raw files encrypted...
stop spreading misinformation.
the raw files aren't encrypted.
According to the source below parts of then are. It could very well be
a waiting game. Do they accept a part now then they might all later.
did you look at the date? it's from 2005.

i also see you are ignoring the fact that nikon isn't the only company
to do so, and actually, they encode much less than some companies.

stop spreading lies.
Post by android
Post by nospam
a decade ago, nikon encrypted *just* the white balance. they did *not*
encrypt the entire raw file. it also made no difference to end users.
Off course it maters to endusers if the can edit their files with third
party software. It's called futureproofing your workflow.
it doesn't matter at all to end users because end users can edit their
raw files with third party software, and do so every single day and
have been doing so for years.

it's *not* a problem.

stop spreading lies.
Post by android
Post by nospam
and it's not just nikon either. just about all camera makers encrypt a
portion. they do not encrypt the entire file.
http://tinyurl.com/59yf9g
android
2013-11-05 15:35:22 UTC
Permalink
Post by nospam
Post by android
Post by nospam
Post by android
And don't mind having their raw files encrypted...
stop spreading misinformation.
the raw files aren't encrypted.
According to the source below parts of then are. It could very well be
a waiting game. Do they accept a part now then they might all later.
did you look at the date? it's from 2005.
Yupp!
Post by nospam
i also see you are ignoring the fact that nikon isn't the only company
to do so, and actually, they encode much less than some companies.
stop spreading lies.
Statements like that should be backed!
Post by nospam
Post by android
Post by nospam
a decade ago, nikon encrypted *just* the white balance. they did *not*
encrypt the entire raw file. it also made no difference to end users.
Off course it maters to endusers if the can edit their files with third
party software. It's called futureproofing your workflow.
it doesn't matter at all to end users because end users can edit their
raw files with third party software, and do so every single day and
have been doing so for years.
it's *not* a problem.
I've expanded on why it is in another post.
Post by nospam
stop spreading lies.
Statements like that should be backed!
Post by nospam
Post by android
Post by nospam
and it's not just nikon either. just about all camera makers encrypt a
portion. they do not encrypt the entire file.
http://tinyurl.com/59yf9g
--
teleportation kills
nospam
2013-11-05 17:58:51 UTC
Permalink
Post by android
Post by nospam
Post by android
Post by nospam
Post by android
And don't mind having their raw files encrypted...
stop spreading misinformation.
the raw files aren't encrypted.
According to the source below parts of then are. It could very well be
a waiting game. Do they accept a part now then they might all later.
did you look at the date? it's from 2005.
Yupp!
so you think it's still relevant??

ever wonder why there hasn't been anyone complaining since that once
instance?

if it was as bad as you claim, certainly someone else would have
pointed it out in the past 8 years...
Post by android
Post by nospam
i also see you are ignoring the fact that nikon isn't the only company
to do so, and actually, they encode much less than some companies.
stop spreading lies.
Statements like that should be backed!
if you can dig up a 8 year old article, you can also dig up *other* 8
year old articles on why it's a non-issue.

here's a start:
<http://www.dpreview.com/news/2005/4/27/davecoffininterview>
This is not a new problem. Phase One, Sony, Foveon, and Canon all
apply some form of encryption to their RAW files. Dcraw decodes them
all -- you can easily find decryption code by searching for the ^
operator.

one in particular, foveon, actually encrypts the entire raw (although i
think some minor stuff like pixel dimensions are in the clear). that's
why anything past the sd14 had no third party support until very
recently (like the past year), which is around 5 years of cameras. it
also isn't as good as sigma's own software.

dcraw stopped supporting foveon because he either couldn't crack the
encryption or there wasn't enough interest to bother. adobe didn't
support recent sigma cameras either, and i don't think they do yet.

not that anyone cares about sigma cameras (they're complete crap), but
sigma definitely encrypts just about everything, forcing you to use
their super-crappy raw converter. even sigma fanbois hate the sigma
software and want alternatives, which aren't as good because they don't
know the 'secret sauce'.

anyway, back to nikon. there are a *lot* of apps that can process nikon
raw files, many of which don't touch nikon's own code because it's not
particularly good.

adobe and apple both wrote their own raw converters from scratch as did
some other companies. dcraw processes nikon raw and is the basis of
additional raw converters from companies who don't want to write their
own.

claiming nikon locks you into only their software is flat out bullshit.

so like i said, stop spreading lies.
Post by android
Post by nospam
Post by android
Post by nospam
a decade ago, nikon encrypted *just* the white balance. they did *not*
encrypt the entire raw file. it also made no difference to end users.
Off course it maters to endusers if the can edit their files with third
party software. It's called futureproofing your workflow.
it doesn't matter at all to end users because end users can edit their
raw files with third party software, and do so every single day and
have been doing so for years.
it's *not* a problem.
I've expanded on why it is in another post.
expand all you want. you're wrong.
android
2013-11-05 19:21:20 UTC
Permalink
Post by nospam
claiming nikon locks you into only their software is flat out bullshit.
The reason for Nikon to steal your right to full access to your files
created by you with your equipment is to force you to use their or their
licensees software to get the most out of your creative process and
work. That process has been stalled but Nikon, and others that followed
them has not backed from encrypting some metadata and therefore not
clearly stated that full encryption won't happen in the future. There is
no honest explanation to why encryption of meta data is a benefit to the
owner of the file."
so like i said, stop spreading lies.
Who's lying? I'm not!
--
teleportation kills
nospam
2013-11-05 19:41:16 UTC
Permalink
Post by nospam
claiming nikon locks you into only their software is flat out bullshit.
I have not .
yes you did.
Post by nospam
The reason for Nikon to steal your right to full access to your files
created by you with your equipment is to force you to use their or their
licensees software to get the most out of your creative process and
work. That process has been stalled but Nikon, and others that followed
them has not backed from encrypting some metadata and therefore not
clearly stated that full encryption won't happen in the future. There is
no honest explanation to why encryption of meta data is a benefit to the
owner of the file."
that's bullshit.

nobody is forced to use nikon's software nor has anything been stalled.
Post by nospam
so like i said, stop spreading lies.
Who's lying? I'm not!
you are saying things that are not true. i'd call that lying.
android
2013-11-05 19:58:41 UTC
Permalink
Post by nospam
Post by nospam
claiming nikon locks you into only their software is flat out bullshit.
I have not .
yes you did.
Post by nospam
The reason for Nikon to steal your right to full access to your files
created by you with your equipment is to force you to use their or their
licensees software to get the most out of your creative process and
work. That process has been stalled but Nikon, and others that followed
them has not backed from encrypting some metadata and therefore not
clearly stated that full encryption won't happen in the future. There is
no honest explanation to why encryption of meta data is a benefit to the
owner of the file."
that's bullshit.
nobody is forced to use nikon's software nor has anything been stalled.
Post by nospam
so like i said, stop spreading lies.
Who's lying? I'm not!
you are saying things that are not true. i'd call that lying.
The first is an unsubstantiated statement. The second slander.
--
teleportation kills
nospam
2013-11-05 20:10:19 UTC
Permalink
Post by android
Post by nospam
Post by android
Post by nospam
so like i said, stop spreading lies.
Who's lying? I'm not!
you are saying things that are not true. i'd call that lying.
The first is an unsubstantiated statement.
incorrect.
Post by android
The second slander.
not when it's true.
android
2013-11-05 20:21:52 UTC
Permalink
Post by nospam
Post by android
Post by nospam
Post by android
Post by nospam
so like i said, stop spreading lies.
Who's lying? I'm not!
you are saying things that are not true. i'd call that lying.
The first is an unsubstantiated statement.
incorrect.
Post by android
The second slander.
not when it's true.
Snipping the context's your only way out?

E O L
--
teleportation kills
nospam
2013-11-05 21:54:14 UTC
Permalink
Post by android
Post by nospam
Post by android
Post by nospam
Post by android
Post by nospam
so like i said, stop spreading lies.
Who's lying? I'm not!
you are saying things that are not true. i'd call that lying.
The first is an unsubstantiated statement.
incorrect.
Post by android
The second slander.
not when it's true.
Snipping the context's your only way out?
it's not a way out.

what you have said is false, therefore i cannot be slandering you.
android
2013-11-05 19:21:31 UTC
Permalink
Post by nospam
if you can dig up a 8 year old article, you can also dig up *other* 8
year old articles on why it's a non-issue.
<http://www.dpreview.com/news/2005/4/27/davecoffininterview>
This is not a new problem. Phase One, Sony, Foveon, and Canon all
apply some form of encryption to their RAW files. Dcraw decodes them
all -- you can easily find decryption code by searching for the ^
operator.
Surly thats the way it's gonna stay forever...
--
teleportation kills
nospam
2013-11-05 19:41:20 UTC
Permalink
Post by android
Post by nospam
if you can dig up a 8 year old article, you can also dig up *other* 8
year old articles on why it's a non-issue.
<http://www.dpreview.com/news/2005/4/27/davecoffininterview>
This is not a new problem. Phase One, Sony, Foveon, and Canon all
apply some form of encryption to their RAW files. Dcraw decodes them
all -- you can easily find decryption code by searching for the ^
operator.
Surly thats the way it's gonna stay forever...
nobody knows what the future will be, but it's been that way for a
decade with no sign of changing.
android
2013-11-05 19:59:02 UTC
Permalink
Post by nospam
Post by android
Post by nospam
if you can dig up a 8 year old article, you can also dig up *other* 8
year old articles on why it's a non-issue.
<http://www.dpreview.com/news/2005/4/27/davecoffininterview>
This is not a new problem. Phase One, Sony, Foveon, and Canon all
apply some form of encryption to their RAW files. Dcraw decodes them
all -- you can easily find decryption code by searching for the ^
operator.
Surly thats the way it's gonna stay forever...
nobody knows what the future will be, but it's been that way for a
decade with no sign of changing.
As one would expect in a waiting game...
--
teleportation kills
Savageduck
2013-11-06 20:31:10 UTC
Permalink
Post by android
Post by nospam
Post by android
And don't mind having their raw files encrypted...
stop spreading misinformation.
the raw files aren't encrypted.
According to the source below parts of then are. It could very well be
a waiting game. Do they accept a part now then they might all later.
Post by nospam
a decade ago, nikon encrypted *just* the white balance. they did *not*
encrypt the entire raw file. it also made no difference to end users.
Off course it maters to endusers if the can edit their files with third
party software. It's called futureproofing your workflow.
Post by nospam
and it's not just nikon either. just about all camera makers encrypt a
portion. they do not encrypt the entire file.
http://tinyurl.com/59yf9g
A biased opinion from 2005, written by an obvious DMCA pseudo-expert.
--
Regards,

Savageduck
RichA
2013-11-05 20:21:59 UTC
Permalink
Post by android
Post by RichA
I'd sooner pay $3000 for this than $1800 for a lame D610 body.
http://www.dpreview.com/news/2013/11/05/nikon-df-combines-classic-design-with-
modern-technology?utm_campaign=internal-link&utm_source=news-list&utm_medium=t
ext&ref=title_0_2#specs
Kinda cool looks. For the trendy wannabes that can't afford a proper
Leica! ;-) And don't mind having their raw files encrypted...
N. Americans tend to be very stodgy when it comes to new designs of anything, photogs prefer 12 year old standard DSLR designs. But I think the camera will do well.
android
2013-11-05 20:33:04 UTC
Permalink
Post by RichA
Post by android
Post by RichA
I'd sooner pay $3000 for this than $1800 for a lame D610 body.
http://www.dpreview.com/news/2013/11/05/nikon-df-combines-classic-design-w
ith-
modern-technology?utm_campaign=internal-link&utm_source=news-list&utm_medi
um=t
ext&ref=title_0_2#specs
Kinda cool looks. For the trendy wannabes that can't afford a proper
Leica! ;-) And don't mind having their raw files encrypted...
N. Americans tend to be very stodgy when it comes to new designs of anything,
photogs prefer 12 year old standard DSLR designs. But I think the camera will
do well.
Some folks think that their glovesize is some indicator of sorts. And
that big gadgets is in indicator of their err "glovesize". ;-)
--
teleportation kills
David Taylor
2013-11-05 08:49:12 UTC
Permalink
Post by RichA
I'd sooner pay $3000 for this than $1800 for a lame D610 body.
http://www.dpreview.com/news/2013/11/05/nikon-df-combines-classic-design-with-modern-technology?utm_campaign=internal-link&utm_source=news-list&utm_medium=text&ref=title_0_2#specs
Strange, really. I suppose it will appeal to some folk, but what a
price! Too many dials!


http://www.wexphotographic.com/buy-nikon-df-digital-slr-camera-with-50mm-lens-silver/p1544998&go=kits_bundles?cm_mmc=exacttarget-_-marketing-_-lm_1708660-_-http%3a%2f%2fwww.wexphotographic.com%2fbuy-nikon-df-digital-slr-camera-with-50mm-lens-silver%2fp1544998%26go%3dkits_bundles&utm_source=exacttarget&utm_medium=1708660&utm_campaign=http%3a%2f%2fwww.wexphotographic.com%2fbuy-nikon-df-digital-slr-camera-with-50mm-lens-silver%2fp1544998%26go%3dkits_bundles
--
Cheers,
David
Web: http://www.satsignal.eu
Me
2013-11-05 10:03:12 UTC
Permalink
Post by David Taylor
Post by RichA
I'd sooner pay $3000 for this than $1800 for a lame D610 body.
Strange, really. I suppose it will appeal to some folk, but what a
price! Too many dials!
It's large, pointless, and overpriced.
D610 is a much better camera, or for the same retail price as the DF, a
D800 kills it in every way.
Michael
2013-11-06 04:39:41 UTC
Permalink
Post by Me
Post by David Taylor
Post by RichA
I'd sooner pay $3000 for this than $1800 for a lame D610 body.
Strange, really. I suppose it will appeal to some folk, but what a
price! Too many dials!
It's large, pointless, and overpriced.
D610 is a much better camera, or for the same retail price as the DF, a
D800 kills it in every way.
Unlike many Nikon D's, this one specifically works with all the old (I
mean OLD) lenses- the pre-AI manual lenses with the coupling forks. One
reason I bought my (DX format) D5000 was that it could do that also,
but when I found it too tedious to use those lenses fully manually, and
I wasn't taking 35mm film anymore (I still take 120), I sold my entire
Nikon F system to KEH when they came up to my city on one of their
traveling buying trips. I got decent money for it. But now those lenses
would be useful on the DF, if I could figure out a good reason to drop
nearly $3000 on yet another camera. All that said, for those of us who
grew up loving the Nikon F, this camera looks like a camera again.
--
Michael
John A.
2013-11-12 19:17:01 UTC
Permalink
Post by Michael
Post by Me
Post by David Taylor
Post by RichA
I'd sooner pay $3000 for this than $1800 for a lame D610 body.
Strange, really. I suppose it will appeal to some folk, but what a
price! Too many dials!
It's large, pointless, and overpriced.
D610 is a much better camera, or for the same retail price as the DF, a
D800 kills it in every way.
Unlike many Nikon D's, this one specifically works with all the old (I
mean OLD) lenses- the pre-AI manual lenses with the coupling forks. One
reason I bought my (DX format) D5000 was that it could do that also,
but when I found it too tedious to use those lenses fully manually, and
I wasn't taking 35mm film anymore (I still take 120), I sold my entire
Nikon F system to KEH when they came up to my city on one of their
traveling buying trips. I got decent money for it. But now those lenses
would be useful on the DF, if I could figure out a good reason to drop
nearly $3000 on yet another camera. All that said, for those of us who
grew up loving the Nikon F, this camera looks like a camera again.
If only this were real... http://re35.net/

Back before I bought my first DSLR I did in fact look around to see if
something like that was available.

Maybe this will come to fruition some day...
http://nikonrumors.com/2012/12/17/nikon-patents-a-digital-back-for-35mm-film-slr-cameras.aspx/

JA
Usenet Account
2013-11-12 20:04:17 UTC
Permalink
Post by John A.
Post by Michael
Post by Me
Post by David Taylor
Post by RichA
I'd sooner pay $3000 for this than $1800 for a lame D610 body.
Strange, really. I suppose it will appeal to some folk, but what a
price! Too many dials!
It's large, pointless, and overpriced.
D610 is a much better camera, or for the same retail price as the DF, a
D800 kills it in every way.
Unlike many Nikon D's, this one specifically works with all the old (I
mean OLD) lenses- the pre-AI manual lenses with the coupling forks. One
reason I bought my (DX format) D5000 was that it could do that also,
but when I found it too tedious to use those lenses fully manually, and
I wasn't taking 35mm film anymore (I still take 120), I sold my entire
Nikon F system to KEH when they came up to my city on one of their
traveling buying trips. I got decent money for it. But now those lenses
would be useful on the DF, if I could figure out a good reason to drop
nearly $3000 on yet another camera. All that said, for those of us who
grew up loving the Nikon F, this camera looks like a camera again.
If only this were real... http://re35.net/
Back before I bought my first DSLR I did in fact look around to see if
something like that was available.
Maybe this will come to fruition some day...
http://nikonrumors.com/2012/12/17/nikon-patents-a-digital-back-for-35mm-film-slr-cameras.aspx/
JA
I recall a company back in 1997 Imagek later renamed SiliconFilm that
was pushing that concept. But seemed more like investment baiting scam.

Never fielded a working model for anyone to examine.
--
Men make their own history, but they do not make it as they please; they
do not make it under self-selected circumstances, but under
circumstances existing already, given and transmitted from the past.
nospam
2013-11-12 20:27:50 UTC
Permalink
Post by Usenet Account
Post by John A.
Maybe this will come to fruition some day...
http://nikonrumors.com/2012/12/17/nikon-patents-a-digital-back-for-35mm-film-
slr-cameras.aspx/
I recall a company back in 1997 Imagek later renamed SiliconFilm that
was pushing that concept. But seemed more like investment baiting scam.
a scam is exactly what it was.
Post by Usenet Account
Never fielded a working model for anyone to examine.
of course there wasn't a working model. such a device is not possible.
Savageduck
2013-11-12 20:55:17 UTC
Permalink
Post by John A.
Post by Michael
Post by Me
Post by David Taylor
Post by RichA
I'd sooner pay $3000 for this than $1800 for a lame D610 body.
Strange, really. I suppose it will appeal to some folk, but what a
price! Too many dials!
It's large, pointless, and overpriced.
D610 is a much better camera, or for the same retail price as the DF, a
D800 kills it in every way.
Unlike many Nikon D's, this one specifically works with all the old (I
mean OLD) lenses- the pre-AI manual lenses with the coupling forks. One
reason I bought my (DX format) D5000 was that it could do that also,
but when I found it too tedious to use those lenses fully manually, and
I wasn't taking 35mm film anymore (I still take 120), I sold my entire
Nikon F system to KEH when they came up to my city on one of their
traveling buying trips. I got decent money for it. But now those lenses
would be useful on the DF, if I could figure out a good reason to drop
nearly $3000 on yet another camera. All that said, for those of us who
grew up loving the Nikon F, this camera looks like a camera again.
If only this were real... http://re35.net/
Back before I bought my first DSLR I did in fact look around to see if
something like that was available.
Maybe this will come to fruition some day...
http://nikonrumors.com/2012/12/17/nikon-patents-a-digital-back-for-35mm-film-slr-cameras.aspx/
JA


I
recall a company back in 1997 Imagek later renamed SiliconFilm that was
pushing that concept. But seemed more like investment baiting scam.
Never fielded a working model for anyone to examine.
I believe that either Hoodman or Delkin had a short lived concept at
about the same time. Ultimately it wouldn't even be able to keep pace
with the least of the P&S of the day. I seem to remember they were
talking about 1.7MB.
--
Regards,

Savageduck
J. Clarke
2013-11-12 21:16:23 UTC
Permalink
Post by Usenet Account
Post by John A.
Post by Michael
Post by Me
Post by David Taylor
Post by RichA
I'd sooner pay $3000 for this than $1800 for a lame D610 body.
Strange, really. I suppose it will appeal to some folk, but what a
price! Too many dials!
It's large, pointless, and overpriced.
D610 is a much better camera, or for the same retail price as the DF, a
D800 kills it in every way.
Unlike many Nikon D's, this one specifically works with all the old (I
mean OLD) lenses- the pre-AI manual lenses with the coupling forks. One
reason I bought my (DX format) D5000 was that it could do that also,
but when I found it too tedious to use those lenses fully manually, and
I wasn't taking 35mm film anymore (I still take 120), I sold my entire
Nikon F system to KEH when they came up to my city on one of their
traveling buying trips. I got decent money for it. But now those lenses
would be useful on the DF, if I could figure out a good reason to drop
nearly $3000 on yet another camera. All that said, for those of us who
grew up loving the Nikon F, this camera looks like a camera again.
If only this were real... http://re35.net/
Back before I bought my first DSLR I did in fact look around to see if
something like that was available.
Maybe this will come to fruition some day...
http://nikonrumors.com/2012/12/17/nikon-patents-a-digital-back-for-35mm-film-slr-cameras.aspx/
JA
I recall a company back in 1997 Imagek later renamed SiliconFilm that
was pushing that concept. But seemed more like investment baiting scam.
Never fielded a working model for anyone to examine.
It's a nice idea but until someone figures out a way to make a sensor
thin enough to fit into the film-plane of a 35mm SLR and durable enough
to survive handling, I think it's pie in the sky.

I suspect that eventually it will be done, as a laboratory exercise if
nothing else, but I also suspect that by the time it happens film will
have been out of use so long that nobody pays much attention.
nospam
2013-11-12 23:28:19 UTC
Permalink
Post by J. Clarke
Post by Usenet Account
I recall a company back in 1997 Imagek later renamed SiliconFilm that
was pushing that concept. But seemed more like investment baiting scam.
Never fielded a working model for anyone to examine.
It's a nice idea but until someone figures out a way to make a sensor
thin enough to fit into the film-plane of a 35mm SLR and durable enough
to survive handling, I think it's pie in the sky.
that's minor. the pressure plate has some flex to it.

there are many other issues that are far bigger obstacles.
Savageduck
2013-11-12 20:43:24 UTC
Permalink
Post by John A.
Post by Michael
Post by Me
Post by David Taylor
Post by RichA
I'd sooner pay $3000 for this than $1800 for a lame D610 body.
Strange, really. I suppose it will appeal to some folk, but what a
price! Too many dials!
It's large, pointless, and overpriced.
D610 is a much better camera, or for the same retail price as the DF, a
D800 kills it in every way.
Unlike many Nikon D's, this one specifically works with all the old (I
mean OLD) lenses- the pre-AI manual lenses with the coupling forks. One
reason I bought my (DX format) D5000 was that it could do that also,
but when I found it too tedious to use those lenses fully manually, and
I wasn't taking 35mm film anymore (I still take 120), I sold my entire
Nikon F system to KEH when they came up to my city on one of their
traveling buying trips. I got decent money for it. But now those lenses
would be useful on the DF, if I could figure out a good reason to drop
nearly $3000 on yet another camera. All that said, for those of us who
grew up loving the Nikon F, this camera looks like a camera again.
If only this were real... http://re35.net/
Yup! That was an April fool's day prank from a year or two back.

There was a siilar idea which flew for a few months and the proved to
not be viable.
Post by John A.
Back before I bought my first DSLR I did in fact look around to see if
something like that was available.
Maybe this will come to fruition some day...
http://nikonrumors.com/2012/12/17/nikon-patents-a-digital-back-for-35mm-film-slr-cameras.aspx/
I
seriously doubt that that is much more than wishful thinking.
--
Regards,

Savageduck
J. Clarke
2013-11-12 21:18:14 UTC
Permalink
Post by Savageduck
Post by John A.
Post by Michael
Post by Me
Post by David Taylor
Post by RichA
I'd sooner pay $3000 for this than $1800 for a lame D610 body.
Strange, really. I suppose it will appeal to some folk, but what a
price! Too many dials!
It's large, pointless, and overpriced.
D610 is a much better camera, or for the same retail price as the DF, a
D800 kills it in every way.
Unlike many Nikon D's, this one specifically works with all the old (I
mean OLD) lenses- the pre-AI manual lenses with the coupling forks. One
reason I bought my (DX format) D5000 was that it could do that also,
but when I found it too tedious to use those lenses fully manually, and
I wasn't taking 35mm film anymore (I still take 120), I sold my entire
Nikon F system to KEH when they came up to my city on one of their
traveling buying trips. I got decent money for it. But now those lenses
would be useful on the DF, if I could figure out a good reason to drop
nearly $3000 on yet another camera. All that said, for those of us who
grew up loving the Nikon F, this camera looks like a camera again.
If only this were real... http://re35.net/
Yup! That was an April fool's day prank from a year or two back.
There was a siilar idea which flew for a few months and the proved to
not be viable.
Post by John A.
Back before I bought my first DSLR I did in fact look around to see if
something like that was available.
Maybe this will come to fruition some day...
http://nikonrumors.com/2012/12/17/nikon-patents-a-digital-back-for-35mm-film-slr-cameras.aspx/
I
seriously doubt that that is much more than wishful thinking.
I suspect it will be invalidated on the basis of prior art--Leica
actually sold such a product, the "Digital Modul R" for the R9.
John A.
2013-11-13 01:32:47 UTC
Permalink
On Tue, 12 Nov 2013 16:18:14 -0500, "J. Clarke"
Post by J. Clarke
Post by Savageduck
Post by John A.
Post by Michael
Post by Me
Post by David Taylor
Post by RichA
I'd sooner pay $3000 for this than $1800 for a lame D610 body.
Strange, really. I suppose it will appeal to some folk, but what a
price! Too many dials!
It's large, pointless, and overpriced.
D610 is a much better camera, or for the same retail price as the DF, a
D800 kills it in every way.
Unlike many Nikon D's, this one specifically works with all the old (I
mean OLD) lenses- the pre-AI manual lenses with the coupling forks. One
reason I bought my (DX format) D5000 was that it could do that also,
but when I found it too tedious to use those lenses fully manually, and
I wasn't taking 35mm film anymore (I still take 120), I sold my entire
Nikon F system to KEH when they came up to my city on one of their
traveling buying trips. I got decent money for it. But now those lenses
would be useful on the DF, if I could figure out a good reason to drop
nearly $3000 on yet another camera. All that said, for those of us who
grew up loving the Nikon F, this camera looks like a camera again.
If only this were real... http://re35.net/
Yup! That was an April fool's day prank from a year or two back.
There was a siilar idea which flew for a few months and the proved to
not be viable.
Post by John A.
Back before I bought my first DSLR I did in fact look around to see if
something like that was available.
Maybe this will come to fruition some day...
http://nikonrumors.com/2012/12/17/nikon-patents-a-digital-back-for-35mm-film-slr-cameras.aspx/
I
seriously doubt that that is much more than wishful thinking.
I suspect it will be invalidated on the basis of prior art--Leica
actually sold such a product, the "Digital Modul R" for the R9.
Plus IIRC there are/were digital replacement backs for at least some
MF cameras.

And I've always thought these large-format scanning backs were pretty
cool. http://www.betterlight.com/

JA
nospam
2013-11-13 01:44:42 UTC
Permalink
Post by John A.
Plus IIRC there are/were digital replacement backs for at least some
MF cameras.
that's a very different situation, since mf cameras were designed to
have interchangeable backs.
Post by John A.
And I've always thought these large-format scanning backs were pretty
cool. http://www.betterlight.com/
for still life, sure. not so useful for moving subjects.
PeterN
2013-11-13 13:28:36 UTC
Permalink
Post by nospam
Post by John A.
Plus IIRC there are/were digital replacement backs for at least some
MF cameras.
that's a very different situation, since mf cameras were designed to
have interchangeable backs.
Post by John A.
And I've always thought these large-format scanning backs were pretty
cool. http://www.betterlight.com/
for still life, sure. not so useful for moving subjects.
OMG! I can't believe that we pretty much agree. ;-p

The scanning backs are also good for some landscape photography, where
wind is not a factor.
IIRC A few months before the Nikon D1 came out, some now defunct company
called Kodak, was making a digital back for the Nikon F3. I was told the
cost would be between 8 @ 15 k depending on the ISO sensitivity I
wanted. Oh yes, it would have almost 1 million pixels.
--
PeterN
John Turco
2014-02-21 01:10:05 UTC
Permalink
Post by PeterN
Post by nospam
Post by John A.
Plus IIRC there are/were digital replacement backs for at least some
MF cameras.
that's a very different situation, since mf cameras were designed to
have interchangeable backs.
Post by John A.
And I've always thought these large-format scanning backs were pretty
cool. http://www.betterlight.com/
for still life, sure. not so useful for moving subjects.
OMG! I can't believe that we pretty much agree. ;-p
The scanning backs are also good for some landscape photography, where
wind is not a factor.
IIRC A few months before the Nikon D1 came out, some now defunct company
called Kodak, was making a digital back for the Nikon F3. I was told the
wanted. Oh yes, it would have almost 1 million pixels.
Hey, Peter, haven't you heard? Kodak <http://www.kodak.com> is
still around!

Kodak/News Releases - Kodak Rings Opening Bell at NYSE
<http://www.kodak.com/ek/US/en/Kodak_Rings_Opening_Bell_at_NYSE.htm>

"Wednesday, January 08, 2014"

"Following the company's emergence from reorganization on Sept.
3, Kodak common shares began trading on the NYSE – by far
the world's largest stock exchange – on Nov. 1 under the new
'KODK' symbol."

John
PeterN
2014-02-22 13:50:25 UTC
Permalink
Post by John Turco
Post by PeterN
Post by nospam
Post by John A.
Plus IIRC there are/were digital replacement backs for at least some
MF cameras.
that's a very different situation, since mf cameras were designed to
have interchangeable backs.
Post by John A.
And I've always thought these large-format scanning backs were pretty
cool. http://www.betterlight.com/
for still life, sure. not so useful for moving subjects.
OMG! I can't believe that we pretty much agree. ;-p
The scanning backs are also good for some landscape photography, where
wind is not a factor.
IIRC A few months before the Nikon D1 came out, some now defunct company
called Kodak, was making a digital back for the Nikon F3. I was told the
wanted. Oh yes, it would have almost 1 million pixels.
Hey, Peter, haven't you heard? Kodak <http://www.kodak.com> is
still around!
Kodak/News Releases - Kodak Rings Opening Bell at NYSE
<http://www.kodak.com/ek/US/en/Kodak_Rings_Opening_Bell_at_NYSE.htm>
"Wednesday, January 08, 2014"
"Following the company's emergence from reorganization on Sept.
3, Kodak common shares began trading on the NYSE – by far
the world's largest stock exchange – on Nov. 1 under the new
'KODK' symbol."
It would take a lot to convince me to either extend them credit, or
invest in their stock.
--
PeterN
John Turco
2014-02-23 02:23:13 UTC
Permalink
Post by PeterN
Post by John Turco
Post by PeterN
Post by nospam
Post by John A.
Plus IIRC there are/were digital replacement backs for at least some
MF cameras.
that's a very different situation, since mf cameras were designed to
have interchangeable backs.
Post by John A.
And I've always thought these large-format scanning backs were pretty
cool. http://www.betterlight.com/
for still life, sure. not so useful for moving subjects.
OMG! I can't believe that we pretty much agree. ;-p
The scanning backs are also good for some landscape photography, where
wind is not a factor.
IIRC A few months before the Nikon D1 came out, some now defunct company
called Kodak, was making a digital back for the Nikon F3. I was told the
wanted. Oh yes, it would have almost 1 million pixels.
Hey, Peter, haven't you heard? Kodak <http://www.kodak.com> is
still around!
Kodak/News Releases - Kodak Rings Opening Bell at NYSE
<http://www.kodak.com/ek/US/en/Kodak_Rings_Opening_Bell_at_NYSE.htm>
"Wednesday, January 08, 2014"
"Following the company's emergence from reorganization on Sept.
3, Kodak common shares began trading on the NYSE – by far
the world's largest stock exchange – on Nov. 1 under the new
'KODK' symbol."
It would take a lot to convince me to either extend them credit, or
invest in their stock.
C'mon, man; try to be more positive about Kodak, please.

John
nospam
2014-02-23 03:48:51 UTC
Permalink
Post by John Turco
Post by PeterN
Post by John Turco
"Following the company's emergence from reorganization on Sept.
3, Kodak common shares began trading on the NYSE – by far
the world's largest stock exchange – on Nov. 1 under the new
'KODK' symbol."
It would take a lot to convince me to either extend them credit, or
invest in their stock.
C'mon, man; try to be more positive about Kodak, please.
how?

their ship has sailed.
John Turco
2014-02-23 07:51:49 UTC
Permalink
Post by nospam
Post by John Turco
Post by PeterN
Post by John Turco
"Following the company's emergence from reorganization on Sept.
3, Kodak common shares began trading on the NYSE – by far
the world's largest stock exchange – on Nov. 1 under the new
'KODK' symbol."
It would take a lot to convince me to either extend them credit, or
invest in their stock.
C'mon, man; try to be more positive about Kodak, please.
how?
Just have a little faith.
Post by nospam
their ship has sailed.
Nay, I say! Kodak's "ship" was a submarine, and it has now resurfaced.

John
PeterN
2014-02-23 17:45:02 UTC
Permalink
Post by John Turco
Post by John Turco
Post by PeterN
Post by John Turco
"Following the company's emergence from reorganization on Sept.
3, Kodak common shares began trading on the NYSE – by far
the world's largest stock exchange – on Nov. 1 under the new
'KODK' symbol."
It would take a lot to convince me to either extend them credit, or
invest in their stock.
C'mon, man; try to be more positive about Kodak, please.
how?
Just have a little faith.
Well John, I do have a little faith. Very little. ;-p
--
PeterN
nospam
2014-02-23 19:40:19 UTC
Permalink
Post by John Turco
Post by nospam
Post by John Turco
C'mon, man; try to be more positive about Kodak, please.
how?
Just have a little faith.
in what?

what can kodak bring to the table? seriously.
Post by John Turco
Post by nospam
their ship has sailed.
Nay, I say! Kodak's "ship" was a submarine, and it has now resurfaced.
the problem is that nobody wants submarines anymore.

kodak was king of film but film is for all intents, dead.

they may have pioneered digital and had the first dslrs, but they
weren't a market leader, which is why they went bankrupt. their digital
cameras were crap.
John Turco
2014-02-24 23:47:55 UTC
Permalink
Post by nospam
Post by John Turco
Post by nospam
Post by John Turco
C'mon, man; try to be more positive about Kodak, please.
how?
Just have a little faith.
in what?
what can kodak bring to the table? seriously.
Post by John Turco
Post by nospam
their ship has sailed.
Nay, I say! Kodak's "ship" was a submarine, and it has now resurfaced.
the problem is that nobody wants submarines anymore.
kodak was king of film but film is for all intents, dead.
they may have pioneered digital and had the first dslrs, but they
weren't a market leader, which is why they went bankrupt. their digital
cameras were crap.
Yeah, that same, old myth keeps being regurgitated: "Kodak was slow to
commit to digital photography."

This conveniently omits the fact Kodak was the earliest company to
introduce DSLR's, and had an extensive line of "EasyShare" P&S models.

If any outfit is behind the times, it's FujiFilm -- it still has the
word "film" in its very name!

John
nospam
2014-02-25 00:15:24 UTC
Permalink
Post by John Turco
Post by nospam
Post by John Turco
Nay, I say! Kodak's "ship" was a submarine, and it has now resurfaced.
the problem is that nobody wants submarines anymore.
kodak was king of film but film is for all intents, dead.
they may have pioneered digital and had the first dslrs, but they
weren't a market leader, which is why they went bankrupt. their digital
cameras were crap.
Yeah, that same, old myth keeps being regurgitated: "Kodak was slow to
commit to digital photography."
This conveniently omits the fact Kodak was the earliest company to
introduce DSLR's,
it doesn't omit anything nor is what i said a myth.

read what i wrote. i said they pioneered digital and that they also
failed to succeed in the market.

kodak's early slrs were hybrids made by nikon/canon, with additional
kodak electronics. they could never be competitive with that strategy.

kodak then tried again with the 14n and slr/n (which were built from
nikon parts) and the slr/c (which was made by sigma). they were all
horrible and that's being kind.

nikon/canon and other companies made much better slrs for less money.
kodak lost.
Post by John Turco
and had an extensive line of "EasyShare" P&S models.
easyshare was crap, something i also said.

when a company sells crap that nobody buys, they often go bankrupt.

some companies do manage to succeed by selling crap, but kodak wasn't
one of them. it's also not a very good strategy.
Post by John Turco
If any outfit is behind the times, it's FujiFilm -- it still has the
word "film" in its very name!
big deal. if that's the only thing they get wrong then they're doing
pretty good.
PeterN
2014-02-25 11:25:05 UTC
Permalink
Post by nospam
Post by John Turco
Post by nospam
Post by John Turco
Nay, I say! Kodak's "ship" was a submarine, and it has now resurfaced.
the problem is that nobody wants submarines anymore.
kodak was king of film but film is for all intents, dead.
they may have pioneered digital and had the first dslrs, but they
weren't a market leader, which is why they went bankrupt. their digital
cameras were crap.
Yeah, that same, old myth keeps being regurgitated: "Kodak was slow to
commit to digital photography."
This conveniently omits the fact Kodak was the earliest company to
introduce DSLR's,
it doesn't omit anything nor is what i said a myth.
read what i wrote. i said they pioneered digital and that they also
failed to succeed in the market.
kodak's early slrs were hybrids made by nikon/canon, with additional
kodak electronics. they could never be competitive with that strategy.
kodak then tried again with the 14n and slr/n (which were built from
nikon parts) and the slr/c (which was made by sigma). they were all
horrible and that's being kind.
nikon/canon and other companies made much better slrs for less money.
kodak lost.
Post by John Turco
and had an extensive line of "EasyShare" P&S models.
easyshare was crap, something i also said.
when a company sells crap that nobody buys, they often go bankrupt.
Think Aston-Martin; Rolls Royce, etc
As usual your statements don't stand up. But there is no reason to give
you a business lesson.

However, Kodak went out partially because of exactly the opposite
mentality. the refused to adopt the current mentality of "make it, sell
it, fix it. We all know you will never admit being wrong, but Iam
posting this authoritative link, written by somone who knos a lot more
about business than you.

<http://www.economist.com/node/21542796>
Post by nospam
some companies do manage to succeed by selling crap, but kodak wasn't
one of them. it's also not a very good strategy.
Post by John Turco
If any outfit is behind the times, it's FujiFilm -- it still has the
word "film" in its very name!
big deal. if that's the only thing they get wrong then they're doing
pretty good.
--
PeterN
nospam
2014-02-25 16:45:26 UTC
Permalink
Post by PeterN
Post by nospam
Post by John Turco
This conveniently omits the fact Kodak was the earliest company to
introduce DSLR's,
it doesn't omit anything nor is what i said a myth.
read what i wrote. i said they pioneered digital and that they also
failed to succeed in the market.
kodak's early slrs were hybrids made by nikon/canon, with additional
kodak electronics. they could never be competitive with that strategy.
kodak then tried again with the 14n and slr/n (which were built from
nikon parts) and the slr/c (which was made by sigma). they were all
horrible and that's being kind.
nikon/canon and other companies made much better slrs for less money.
kodak lost.
Post by John Turco
and had an extensive line of "EasyShare" P&S models.
easyshare was crap, something i also said.
when a company sells crap that nobody buys, they often go bankrupt.
Think Aston-Martin; Rolls Royce, etc
aston martin and rolls royce are crap?

where do you come up with this shit? seriously, wtf?

i hope you're not suggesting kodak should have made ultra-high end
cameras, because that would have been very, very stupid.

ask hasselblad how well that worked out for them.
Post by PeterN
As usual your statements don't stand up. But there is no reason to give
you a business lesson.
However, Kodak went out partially because of exactly the opposite
mentality. the refused to adopt the current mentality of "make it, sell
it, fix it. We all know you will never admit being wrong, but Iam
posting this authoritative link, written by somone who knos a lot more
about business than you.
<http://www.economist.com/node/21542796>
further proof you are a nothing more than an argumentative idiot.

that link is just one person's opinion, but regardless, it basically
says the same thing i did, but with some additional details. i summed
it up in a couple of lines. that link is many, many paragraphs. here's
a snippet:

Kodak sold cheap cameras and relied on customers buying lots of
expensive film. (Just as Gillette makes money on the blades, not the
razors.) That model obviously does not work with digital cameras.

and with even fewer words:

move to where the puck is going. not to where was.

and apparently i know more about business than those who ran kodak,
because i know that selling at a loss is not sustainable:
<http://www.hindustantimes.com/business-news/kodak-what-led-to-bankruptc
y/article1-800633.aspx>
Kodak was losing $60 for every digital camera it sold by 2001 and it
was trying to quell a war that had erupted between its digital and
film staff, according to the Harvard case study.
John Turco
2014-02-25 21:31:22 UTC
Permalink
Post by nospam
Post by John Turco
Post by nospam
Post by John Turco
Nay, I say! Kodak's "ship" was a submarine, and it has now resurfaced.
the problem is that nobody wants submarines anymore.
kodak was king of film but film is for all intents, dead.
they may have pioneered digital and had the first dslrs, but they
weren't a market leader, which is why they went bankrupt. their digital
cameras were crap.
Yeah, that same, old myth keeps being regurgitated: "Kodak was slow to
commit to digital photography."
This conveniently omits the fact Kodak was the earliest company to
introduce DSLR's,
it doesn't omit anything nor is what i said a myth.
read what i wrote. i said they pioneered digital and that they also
failed to succeed in the market.
It's a wrong to say that Kodak ignored digital technology. It was a
major player in the P&S market and also, had already paved the way
for Canon and Nikon, where DSLR's were concerned.
Post by nospam
kodak's early slrs were hybrids made by nikon/canon, with additional
kodak electronics. they could never be competitive with that strategy.
kodak then tried again with the 14n and slr/n (which were built from
nikon parts) and the slr/c (which was made by sigma). they were all
horrible and that's being kind.
nikon/canon and other companies made much better slrs for less money.
kodak lost.
Kodak was never a manufacturer of SLR bodies or lenses, naturally.
Post by nospam
Post by John Turco
and had an extensive line of "EasyShare" P&S models.
easyshare was crap, something i also said.
Not crap, and I own quite a few EasyShare cameras.
Post by nospam
when a company sells crap that nobody buys, they often go bankrupt.
Then, using a frequent target of your scorn (i.e., "Sigma"), why hasn't
that questionable firm folded, yet?
Post by nospam
some companies do manage to succeed by selling crap, but kodak wasn't
one of them. it's also not a very good strategy.
It works for Sigma, does it not?
Post by nospam
Post by John Turco
If any outfit is behind the times, it's FujiFilm -- it still has the
word "film" in its very name!
big deal. if that's the only thing they get wrong then they're doing
pretty good.
They get a lot of things wrong (e.g., qualty control), it seems.

John
Joe Makowiec
2014-02-25 22:02:29 UTC
Permalink
Post by John Turco
Kodak was never a manufacturer of SLR bodies or lenses, naturally.
They did, from 1957 - 1967:

http://camerapedia.wikia.com/wiki/Kodak_Retina_Reflex

A cousin had one. I was contemplating buying it from him when I was
looking for my first camera around 1973. (I wound up with an FTb.) Note
the rapid wind lever on the bottom of the body!
--
Joe Makowiec
http://makowiec.org/
Email: http://makowiec.org/contact/?Joe
Usenet Improvement Project: http://twovoyagers.com/improve-usenet.org/
nospam
2014-02-25 23:06:06 UTC
Permalink
Post by Joe Makowiec
Post by John Turco
Kodak was never a manufacturer of SLR bodies or lenses, naturally.
http://camerapedia.wikia.com/wiki/Kodak_Retina_Reflex
A cousin had one. I was contemplating buying it from him when I was
looking for my first camera around 1973. (I wound up with an FTb.) Note
the rapid wind lever on the bottom of the body!
which is an incredibly dumb place to put it.
nospam
2014-02-25 23:36:42 UTC
Permalink
Post by John Turco
Post by nospam
Post by John Turco
This conveniently omits the fact Kodak was the earliest company to
introduce DSLR's,
it doesn't omit anything nor is what i said a myth.
read what i wrote. i said they pioneered digital and that they also
failed to succeed in the market.
It's a wrong to say that Kodak ignored digital technology.
what's wrong is to say i said that, because i didn't say anything close
to that.
Post by John Turco
It was a
major player in the P&S market
not really.

early on they had a reasonable share, but that didn't last all that
long.

other companies made more compelling products and their share dwindled.

i gave a link in another post that kodak was losing $60 per camera
sold. that's almost never a good idea.
Post by John Turco
and also, had already paved the way
for Canon and Nikon, where DSLR's were concerned.
and then kodak wasted a shitload of money on the 14n, slr/n and slr/c.
those were *awful*.

complete waste of money.
Post by John Turco
Post by nospam
kodak's early slrs were hybrids made by nikon/canon, with additional
kodak electronics. they could never be competitive with that strategy.
kodak then tried again with the 14n and slr/n (which were built from
nikon parts) and the slr/c (which was made by sigma). they were all
horrible and that's being kind.
nikon/canon and other companies made much better slrs for less money.
kodak lost.
Kodak was never a manufacturer of SLR bodies or lenses, naturally.
incorrect.

kodak made film slrs long ago, such as the retina reflex, which was not
particularly good.

then there was the instamatic slr, a *really* dumb idea. the film in an
instamatic cartridge could not be kept flat enough to obtain the full
quality of an slr.

<http://www.bvipirate.com/Kodak/IReflex-1.html>

kodak was trying to push instamatic film, which might have been fine
for the consumer market, but it certainly was not for the slr market.
whose bright idea was that??

more recently, the kodak 14n and slr/n were built by kodak using nikon
parts. it was mostly a nikon n80 but not entirely so. what kodak didn't
do with those was buy a nikon shell and stuff kodak electronics into
it, as they did with earlier cameras.

the slr/c version of the slr/n, however, was outsourced to sigma, of
all people. yet another mistake.
Post by John Turco
Post by nospam
Post by John Turco
and had an extensive line of "EasyShare" P&S models.
easyshare was crap, something i also said.
Not crap, and I own quite a few EasyShare cameras.
they were crap compared to other options available. the user interface
was not particularly good, they didn't offer anything compelling over
other cameras, most of which cost less, and the sharing thing was
bizarre.

they were trying to target a specific niche, with a commodity product.
Post by John Turco
Post by nospam
when a company sells crap that nobody buys, they often go bankrupt.
Then, using a frequent target of your scorn (i.e., "Sigma"), why hasn't
that questionable firm folded, yet?
because sigma makes a shitload of money on lenses and their lenses
aren't complete crap. they're certainly not as good as nikon/canon, but
they're not total junk.

sigma's older lenses, the ones that used cellophane tape to hold them
together (no joke) were crap, but they don't do that anymore.

the problem i have with sigma is that they are one of the sleaziest
companies around, intentionally lying about the foveon sensor to the
point of violating the laws of physics and mathematics. who wants to do
business with liars?

anyway, if you want crap lenses, look no further than this gem:
<Loading Image...>

notice how well it maintains a parallel axis when extended. if that
camera were any heavier, it would probably snap right off.

the difference with that company is that they sell a *lot* of products,
so a couple of crappy ones aren't a big deal. they're not betting the
farm on that type of product, which is what kodak was doing.
Post by John Turco
Post by nospam
some companies do manage to succeed by selling crap, but kodak wasn't
one of them. it's also not a very good strategy.
It works for Sigma, does it not?
not a good analogy.

sigma's lens sales aren't going away the way film was for kodak.

if sigma's main source of revenue was going away to be replaced by
their cameras, then sigma would have a serious problem. their camera
division loses a lot of money, which means if they were relying on it,
sigma would ultimately go away.

with kodak, film was going away (and kodak knew it), but their cameras
weren't good enough to replace it, especially when they were losing
money on them.
Post by John Turco
Post by nospam
Post by John Turco
If any outfit is behind the times, it's FujiFilm -- it still has the
word "film" in its very name!
big deal. if that's the only thing they get wrong then they're doing
pretty good.
They get a lot of things wrong (e.g., qualty control), it seems.
not really.

Trevor
2014-02-24 03:28:32 UTC
Permalink
Post by John Turco
Post by nospam
their ship has sailed.
Nay, I say! Kodak's "ship" was a submarine, and it has now resurfaced.
Nah, it's still full of holes.

Trevor.
J. Clarke
2013-11-13 02:27:32 UTC
Permalink
Post by John A.
On Tue, 12 Nov 2013 16:18:14 -0500, "J. Clarke"
Post by J. Clarke
Post by Savageduck
Post by John A.
Post by Michael
Post by Me
Post by David Taylor
Post by RichA
I'd sooner pay $3000 for this than $1800 for a lame D610 body.
Strange, really. I suppose it will appeal to some folk, but what a
price! Too many dials!
It's large, pointless, and overpriced.
D610 is a much better camera, or for the same retail price as the DF, a
D800 kills it in every way.
Unlike many Nikon D's, this one specifically works with all the old (I
mean OLD) lenses- the pre-AI manual lenses with the coupling forks. One
reason I bought my (DX format) D5000 was that it could do that also,
but when I found it too tedious to use those lenses fully manually, and
I wasn't taking 35mm film anymore (I still take 120), I sold my entire
Nikon F system to KEH when they came up to my city on one of their
traveling buying trips. I got decent money for it. But now those lenses
would be useful on the DF, if I could figure out a good reason to drop
nearly $3000 on yet another camera. All that said, for those of us who
grew up loving the Nikon F, this camera looks like a camera again.
If only this were real... http://re35.net/
Yup! That was an April fool's day prank from a year or two back.
There was a siilar idea which flew for a few months and the proved to
not be viable.
Post by John A.
Back before I bought my first DSLR I did in fact look around to see if
something like that was available.
Maybe this will come to fruition some day...
http://nikonrumors.com/2012/12/17/nikon-patents-a-digital-back-for-35mm-film-slr-cameras.aspx/
I
seriously doubt that that is much more than wishful thinking.
I suspect it will be invalidated on the basis of prior art--Leica
actually sold such a product, the "Digital Modul R" for the R9.
Plus IIRC there are/were digital replacement backs for at least some
MF cameras.
And I've always thought these large-format scanning backs were pretty
cool. http://www.betterlight.com/
Yep. Although a scanning back doesn't serve quite the same function.
PeterN
2013-11-05 13:05:20 UTC
Permalink
Post by RichA
I'd sooner pay $3000 for this than $1800 for a lame D610 body.
http://www.dpreview.com/news/2013/11/05/nikon-df-combines-classic-design-with-modern-technology?utm_campaign=internal-link&utm_source=news-list&utm_medium=text&ref=title_0_2#specs
That body does nothing for me. If Nikon wanted to really go retro, it
could have used in interchangeable viewfinder, so we could use a waist
level finder.
--
PeterN
Alan Browne
2013-11-05 21:36:32 UTC
Permalink
Post by RichA
I'd sooner pay $3000 for this than $1800 for a lame D610 body.
http://www.dpreview.com/news/2013/11/05/nikon-df-combines-classic-design-with-modern-technology?utm_campaign=internal-link&utm_source=news-list&utm_medium=text&ref=title_0_2#specs
Looks like something the well heeled or showboater would buy as a
conversation piece.

That said, I like the knobs (as long as they provide access to useful
functions - I miss that from my Maxxum 7D (esp. exp. comp knobs on left
side)).

So it seems silly that there's an LCD display on top that shows (1/125
in this case) shutter speed when the speed dial is selecting "1/3 STEP"
while the exposure mode is "M" (manual). What's that all about? 1/2 or
1/3 steps are usually a finer setting somewhere in the menus - so not
needed on a knob. Strange indeed.

This implies that the user is using the function wheel to select speed
and/or aperture or both. So why bother with the knob?

On the other end, wasting a knob for something as specific as ISO seems
strange - though I suppose it could be used quickly in changing light
conditions.

I also suspect the buttons atop the knobs are control locks. Horrible
things to have.

The FF over 16 Mpix is very nice - should yield very low noise images at
higher ISO.
--
"Quotation, n: The act of repeating erroneously the words of another."
-Ambrose Bierce
RichA
2013-11-05 23:48:45 UTC
Permalink
Post by Alan Browne
Post by RichA
I'd sooner pay $3000 for this than $1800 for a lame D610 body.
http://www.dpreview.com/news/2013/11/05/nikon-df-combines-classic-design-with-modern-technology?utm_campaign=internal-link&utm_source=news-list&utm_medium=text&ref=title_0_2#specs
Looks like something the well heeled or showboater would buy as a
conversation piece.
That said, I like the knobs (as long as they provide access to useful
functions - I miss that from my Maxxum 7D (esp. exp. comp knobs on left
side)).
So it seems silly that there's an LCD display on top that shows (1/125
in this case) shutter speed when the speed dial is selecting "1/3 STEP"
while the exposure mode is "M" (manual). What's that all about? 1/2 or
1/3 steps are usually a finer setting somewhere in the menus - so not
needed on a knob. Strange indeed.
This implies that the user is using the function wheel to select speed
and/or aperture or both. So why bother with the knob?
On the other end, wasting a knob for something as specific as ISO seems
strange - though I suppose it could be used quickly in changing light
conditions.
I also suspect the buttons atop the knobs are control locks. Horrible
things to have.
The FF over 16 Mpix is very nice - should yield very low noise images at
higher ISO.
Personally, I like control options as buttons and knobs, even though I'm (having used a lot of Olympus and Panasonic) well-used to using menus. Control locks came about due to the rough use SLR's used to be put through in professional situations, I haven't seen them in some time, but I figure I'll be able to get used to them. I can certainly attest to actuating features by accident because I don't baby cameras when I use them.
Bowser
2013-11-05 22:10:03 UTC
Permalink
Post by RichA
I'd sooner pay $3000 for this than $1800 for a lame D610 body.
http://www.dpreview.com/news/2013/11/05/nikon-df-combines-classic-design-with-modern-technology?utm_campaign=internal-link&utm_source=news-list&utm_medium=text&ref=title_0_2#specs
I'm not an AARP member, so I don't think it's for me.
Kingpin
2013-11-11 05:53:22 UTC
Permalink
Post by RichA
I'd sooner pay $3000 for this than $1800 for a lame D610 body.
http://www.dpreview.com/news/2013/11/05/nikon-df-combines-classic-design-with-modern-technology?utm_campaign=internal-link&utm_source=news-list&utm_medium=text&ref=title_0_2#specs
I'm waiting for the Box Brownie version.
Loading...