quote:

---

> Hi,
> I'm using Profiler Pro V2.3 to profile my Epson 2200.
>
> In the documentation, it says that during profile creation, the
> working space in Photoshop should be the same
> as the working space that will be used afterwards, while editing and
> printing images. It also says that it is important
> to always use this same working space, because otherwise there will
> be a colour shift. This makes sense - I have read
> elsewhere that profiles are (or can be) to an extent optimised for a
> particular source gamut.
>
> This is all fine, except that what I'm noticing is that the resulting
> profile seems to behave identically, *regardless* of
> the working space I use while building the profile! Has anyone else
> noticed this? Should I tag all the Profiler Pro
> ancilliary images (the images it opens up during the profiling, and
> which are tagged by default with Adobe RGB)
> with my new working space? Should I *convert* them all to my working
> space?
>
> I am in touch with Colorvision support as well, but so far they don't
> even seem to understand what my issue is.

---

quote:

---

> Photoshop is designed to recognize embedded profiles, and honor them for
> printing and display purposes. The end goal of this is consistency, which
> is what you are seeing.

---

quote:

---

> "Mike Russell" <REgeigyMOVE@pacbellTHIS.net> wrote in message
> news:520Ob.11845$re2.3104@newssvr25.news.prodigy.com...
>
> I understand this. When I said "identical results", I mean *exactly* - the
> resulting pixel values are 100% identical. This doesn't make sense to me
> at all. If Colorvision really mean what they say, then when I build two
> different profiles (using two different working spaces during the profile
> creation), I would expect at least the perceptual tables to produce
> slightly different colours, when I switch between the two profiles. It
> appears to me that it makes no difference whatsoever what my working space
> is set to during profile creation - this is contrary to the Profiler Pro
> documentation.

---

quote:

---

> Perhaps the documentation is not correct in this respect.

---

quote:

---

> This is the
> way I see it: First you print a color chart. It shouldn't really matter
> in which color space you opened that chart, because in the end you will
> print it in the *printer color space*.

---

quote:

---

> That's all the printer can do.
> Next you measure the results by scanning that print. You build the
> profile based on that, so I don't see any reason why the profile should
> be different if the color space of the chart is different. As long as
> you do not "Convert to profile" when you open the chart, the RGB values
> you get (and so the RGB-values you sent to the printer) are identical,
> no matter what color space you used.

---

quote:

---

>
> Also, note that other images (two, I think) are opened by Profiler Pro,
> *during* the profile creation. I don't think these images are important -
> I think Profiler Pro just needs *any* image open for certain operations,
> simply because it's a Photoshop plugin. These images are tagged with Adobe
> RGB, and the documentation clearly says not to convert them when opening.
> (i.e, to leave them in Adobe RGB).

---

quote:

---

> By the way, it seems that Profiler Pro works a little differently from
> the one I got. I have PrintFIX and DoctorPRO. PrintFIX doesn't open any
> other image during profile creation.

---

quote:

---

> DoctorPRO does open an image during
> profile correction, but that seems indeed because something has to be
> open (DoctorPRO runs an action, that can't run if there's no open
> document).

---

quote:

---

> "Johan W. Elzenga" <nomail@please.invalid> wrote in message
> news:1g7plvw.ztcnu915f9eq2N%nomail@please.invalid...
>
> FWIW, I've just tried it again, and it opens an image called
> "Colorvision.tif" twice - once when I open the measurements file, and once
> when I click the ok button to generate the profile. The image is the
> colorvision logo.

---

quote:

---

>Greg <nospam@nowhere.com> wrote:
>
>
>I can understand that you shouldn't *convert* anything. That makes
>sense. Let say that the color chart contains a patch with RGB values
>200,200,200. You print this on your printer and next you scan this
>print. The scan will be opened in your default color space, so that will
>be AdobeRGB. Because the original chart was in AdobeRGB as well, the
>software can make a direct comparision: The scanned patch should be
>200,200,200 again, but it won't be. The difference is what is used to
>make the profile. However, if you opened the chart and used "Convert to
>profile" in order to use another color space, the original patch value
>would not be 200,200,200 any longer. It will be converted to something
>else, so you printed something else. Scan this into AdobeRGB, and you
>obviously find a value that is not 200,200,200. Not because of the
>printer, but because the value wasn't 200,200,200 to begin with. The
>result is that your new profile will be off.
>
>By the way, it seems that Profiler Pro works a little differently from
>the one I got. I have PrintFIX and DoctorPRO. PrintFIX doesn't open any
>other image during profile creation. DoctorPRO does open an image during
>profile correction, but that seems indeed because something has to be
>open (DoctorPRO runs an action, that can't run if there's no open
>document).

---

quote:

---

> But if your printer normally expects an sRGB (converted or otherwise
> from Adobe RGB), doesn't it make sense to convert to sRGB anyhing sent
> to the printer first? Of course you could set PS to work in sRGB, but
> that seems counterproductive. Or maybe with Profiler, you just forget
> all that sRGB business and use the profile that it creates?
>
> Do you have a color reflection densitometer? Maybe this could be used
> to verify that your Profiler program is doing what it's supposed to.
> Get a known color reference chart and compare it to the printed
> results from a scanned-in copy. Also there's no guarantee that your
> scanner has perfect color, either--maybe this why Profiler has those
> color tweaks available.

---

quote:

---

> But if your printer normally expects an sRGB (converted or otherwise
> from Adobe RGB), doesn't it make sense to convert to sRGB anyhing sent
> to the printer first? Of course you could set PS to work in sRGB, but
> that seems counterproductive. Or maybe with Profiler, you just forget
> all that sRGB business and use the profile that it creates?

---

quote:

---

> Coulh well be that this is for entertainment only. Personally, I can't
> see why the Colorvision logk would be needed to creite a profile!

---