From: "shAf" [EMAIL PROTECTED] To: [EMAIL PROTECTED]
Sent: Friday, March 30, 2001 8:23 PM
ALSO ... Ed informs me no transformation takes place at all if the
color space "device RGB" is chosen.
Michael,
What do you mean by this? Is "device RGB" not VS RGB (PCD color space), but
the raw
"Mark Ligtenberg" [EMAIL PROTECTED] wrote:
What do you mean by this? Is "device RGB" not VS RGB (PCD color space),
but
the raw scanner/film RGB?
AIUI, yes. :) I have yet to try this option however...
Rob
Mark writes ...
From: "shAf" [EMAIL PROTECTED] To: [EMAIL PROTECTED]
Sent: Friday, March 30, 2001 8:23 PM
ALSO ... Ed informs me no transformation takes place at all if the
color space "device RGB" is chosen.
What do you mean by this? Is "device RGB" not VS RGB (PCD color space),
but
From: "shAf" [EMAIL PROTECTED] To: [EMAIL PROTECTED]
Sent: Saturday, March 31, 2001 5:22 PM
Mark writes ...
From: "shAf" [EMAIL PROTECTED] To: [EMAIL PROTECTED]
Sent: Friday, March 30, 2001 8:23 PM
ALSO ... Ed informs me no transformation takes place at all if the
color space
On Thu, 29 Mar 2001 08:35:10 -0800 shAf ([EMAIL PROTECTED]) wrote:
That being said, and altho I trust Ed, I know little about PCD RGB,
and there seems to be little available regarding comparisons with the
common working spaces (if comparisons can be made ... some of what
I've found
Richard,
From my reading of info on Vuescan, it does indeed use the PCD
colorspace, and I don't think any violation of anything is occurring.
The color space of PCD could easily include all of the film types you
speak of, regardless of a bias (filter) used during the scanning
process.
Tony writes ...
On Thu, 29 Mar 2001 21:01:09 -0800 shAf
([EMAIL PROTECTED]) wrote:
... so Ektaspace is an easily accepted compromise.
Ektaspace is also respected for its editabilty,
and its wide gamut is very suitable for
highbit editing.
Its gamut is also sufficiently wide for
shAf previously writes ...
Something else has just occurred to me. My "test"
was based on a fresh installation of VS7 while my
LS-2000 is now put away. That is, my test was based
on a previously acquired "raw" scan 64bit TIFF,
and VS7 had no way of knowing which scanner scanned it.
- Original Message -
From: Bob Shomler [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, March 29, 2001 3:28 PM
Subject: RE: filmscanners: Vuescan: "device RGB"
Vuescan has an option to tag files with the selected color space profile
(except for Device RGB, which
- Original Message -
From: Bob Shomler [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, March 29, 2001 3:28 PM
Subject: RE: filmscanners: Vuescan: "device RGB"
Vuescan has an option to tag files with the selected color space profile
(except for Device RGB, which
What color space does Photoshop (6) open a file tagged ProPhoto RGB into?
Depends on the Photoshop 6 Color Settings [Edit Color Settings]. It should act as
set for a profile mismatch. If you have 'ask when opening' checked for profile
mismatches it should present a dialog box on opening the
My point was that I don't find a ProPhoto RGB profile in the Photoshop
dialog. I guess I'll just have to try it.
Bob Wright
- Original Message -
From: Bob Shomler [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Friday, March 30, 2001 3:03 PM
Subject: Re: filmscanners: Vuescan: "devic
"shAf" [EMAIL PROTECTED] wrote:
Rob writes ...
Er, doesn't PS 5.5 allow you to say what profile the
image is coming from when the image is untagged?
Yes ... but it seems to me that list of profiles is particular to
working spaces, excluding device profiles ... or maybe I'm wrong. If
On Wed, 28 Mar 2001 18:39:18 -0800 shAf ([EMAIL PROTECTED]) wrote:
I meant it only in the context of what you seemed to imply ... VS
offering only trismuthus matrix tranformations. It is apparently something
quite rigorous to impliment and tranform 3-dimensional LUT-type device
Tony writes ...
The raw scan is in an unspecified device space,
scanner RGB. Ed's transform, applied during the
production of the Crop file, munges that against
his characterisation and the result is a scan
with altered data values within Vuescan's working
space (which I previously said I
There is a lot that doesn't add up - - regarding PCD "space", and VS
using PhotoCD "space".
1. You will note that you cannot do a profile conversion (profile to
profile) in Photoshop to a PhotoCD (space) profile, of which I have
about 8 of them in my ColorSync folder.
2. PhotoCD format - -
Richard writes ...
There is a lot that doesn't add up - - regarding PCD
"space", and VS using PhotoCD "space".
1. You will note that you cannot do a profile
conversion (profile to profile) in Photoshop ...
2. PhotoCD format - - and their ICC profiles ARE
proprietary, ...
3. If you
8. All Kodak PhotoCD profiles exhibit very unusual gamut profiles, in
either L.a.b., Yxy, or XYZ space. The are all complex. The only thing
you can say is that they universally fit within Kodak ProPhotoRGB
space. I don't know why Ed would even consider these spaces - -
unless for PR reasons.
I guess you will have to ask him exactly what he is using.
The discussion was about PhotoCD embedded profiles. Not standard
spaces, such as AdobeRGB. The "Transforms" you can download from
Kodak - ASFICT are profiles, used to open files formatted in PhotoCD
format. For opening files only.
When you say "all the PCD profiles", wouldn't Ed simply be using the
most appropriate one. And, wouldn't this one offer a standard model
for mathematically converting to from???
They are all different:
pcd4050e.pf for E6
pcd4050k.pf for K-14
pcdcnycc.pf for color negative
pcdekycc.pf
Richard wrote:
And, you can't open a file into "photoCD space", You cannot load any
of the profiles mentioned above as a working "space". If Ed is "doing
this" - somehow - he is not doing this without Kodak's permission,
unless he is licensed and has obtained proprietary authoring
software.
Richard writes ...
Yes it is large. It will encompass Ekta Space (almost), which is the
definition of E6 Ektachrome media, and thus E6 gamut.
I'm posting th results of my little test regarding the capacity of
Vuescan's gamut, "device RGB" (... whatever it is ...)
First ... some
On Tue, 27 Mar 2001 19:15:35 -0800 shAf ([EMAIL PROTECTED]) wrote:
but while we all recognize with kudos the
advantages of VS, we need to also recognize its weakness and lack of
scanner characterization.
Vuescan uses a hard-coded tristimulus transform derived from empirical testing
of
From: "shAf" [EMAIL PROTECTED] To: "Filmscanners"
[EMAIL PROTECTED] Sent: Tuesday, March 27, 2001 10:22 PM
Has anyone figured out how to use this color space option?? VS's
help file implies the resulting color space will be that of the
"device", BUT the profile is not embedded. How would
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Tony Sleep
Sent: Wednesday, March 28, 2001 5:23 AM
To: [EMAIL PROTECTED]
Subject: Re: filmscanners: Vuescan: "device RGB"
On Tue, 27 Mar 2001 19:15:35 -0800 shAf
([EMAIL PROTECT
shAF wrote:
I'm harping about imperceivable effects of one implimentation of CM versus
another more rigorous ...
"Nearly imperceivable effects" are a large part of what makes a picture
"excellent" instead of "good." A little more subtle than the difference
between "lightning" and "a lightning
Mark wrote:
I think it is a nice option. Because you are able to use the scannerprofiles
(neg. and trans.) that came with your scannersoftware when you bought the
scanner.
How do you use scanner profiles with Vuescan?
Rob
Rob Geraghty [EMAIL PROTECTED]
http://wordweb.com
Vuescan uses a hard-coded tristimulus transform derived
from empirical testing of each scanner supported,
though this is presumably not the case for scanners
which happen to be supported just 'cos they understand SCSI
commands for another model.
...
I understand Ed being wary ... At
Rob writes ...
Mark wrote:
I think it is a nice option. Because you are able to use the
scannerprofiles
(neg. and trans.) that came with your scannersoftware when you
bought the
scanner.
How do you use scanner profiles with Vuescan?
Presumably ... the color space option, "device RGB",
On Tue, 27 Mar 2001 11:43:54 -0800 shAf ([EMAIL PROTECTED]) wrote:
I understand Ed being wary ... At one time I was under the impression
he was characterizing the scanners Vuescan supported, but you seem to
claim some scanners are not characterized.
No, part of his adaptation of VS
Tony writes ...
On Tue, 27 Mar 2001 11:43:54 -0800 shAf ([EMAIL PROTECTED]) wrote:
I'm harping about imperceivable effects of one implimentation of CM
versus another more rigorous ...
Last time someone said that of VS, ISTR Ed took exception and pointed out
VS
does no more and no less
Michael wrote:
Rob writes ...
How do you use scanner profiles with Vuescan?
Presumably ... the color space option, "device RGB",
is intended for this ... and you would also need
Photoshop 6 ... for either (1) assigning the scanner
profile of choice ... or (2) opening the scanned
image into
Rob writes ...
Er, doesn't PS 5.5 allow you to say what profile the
image is coming from when the image is untagged?
Yes ... but it seems to me that list of profiles is particular to
working spaces, excluding device profiles ... or maybe I'm wrong. If
so, then it should work for PS5 as
Too bad Ed isn't on the list as he could enlighten us.
Dale
From: "shAf" [EMAIL PROTECTED]
Has anyone figured out how to use this color space option?? VS's
help file implies the resulting color space will be that of the
"device", BUT the profile is not embedded. How would you convert
My understanding is that, though without embedding it, this option uses the
scanner profile as selected in your graphics program in transferring the
image to the graphics program, and the graphics program would than embed
it's default/preferred color space in the image if it embeds such spaces as
Goerf writes ...
shAf wrote:
Has anyone figured out how to use this color space option?? ...
I'm the one who has requested for this space.
Choosing this device space will disable all color space
conversions in Vuescan (like raw) but allows you to
perform the light/heavy/medium
36 matches
Mail list logo
