Re: Newcolor
Re: Newcolor
- Subject: Re: Newcolor
- From: Henrik Holmegaard <email@hidden>
- Date: Sun, 20 Jan 2002 10:16:47 +0100
"publix team" <email@hidden> wrote:
On installation of Newcolor on a win98/winMe system I
get a message that NC runs only on NT4/Win2000 machines.
But on trying to edit a printerprofile .. the changes aren`t saved
into the profile at all. Could this be a flaw with the operating
system? Actually I don't think so.
As my copy of Newcolor was time-limited and expired on December 31, I
sort of don't feel this is my table when it comes to answering, but
still ...
There is only one version of Linocolor. The only version there is is
the latest version there is. Linocolor is the same on any machine
except for the plug-in for the specific scanner. Just like the Mac OS
is the same on any Mac. My version of Linocolor is 6.0.10 but there
may be / probably are later ones.
There are multiple versions of Newcolor which is confusing. These
versions don't have the same functionality which is more confusing.
There is Newcolor 5000 for NT4 (and Win2K, I think). Newcolor 5000 is
the standalone application that replaces Newcolor 4000 which was a
Photoshop plug-in. I know Andrew always wanted and campaigned for a
plug-in approach, but when the Newcolor 4000 blueprint was drawn up
it turned out the then TWAIN API and the then Photoshop API did not
support ICC profiles and the plug-in approach was dropped. You just
cannot build a through-and-through ICC based scanning application
with a non-ICC hand-off mechanism, because it makes no sense at all.
Maybe I should have written this a long time ago.
Newcolor 5000 is / was (?) 8 bit only and had no extended CMYK
editing tools. It only runs on the desktop flatbeds.
Newcolor 7000 version 1 was NT4 only and was released after DRUPA
2000. It does not run on Win2K and it does not run on the desktop
flatbeds, but only on legacy Tangos and legacy Topaz's plus brand new
Primescans and brand new Nexscans. Newcolor 7000 version 1 is 16 bit
/ 8 bit for Lab / RGB / CMYK.
Newcolor 7000 version 2 runs on NT4 and Win2K and appeared last year.
The specs are the same as for version 1 in general, but there now are
a number of features which a professional scanning tool can't well do
without including masks for color correction.
Newcolor 7000 for the Mac is due soon, but I don't know how soon.
Also I don't know what the plans are for the machine park in use by
the old CPS user base or in other words nine out of ten of us. IOW if
the idea is to port Newcolor 5000 to Mac OS replacing Linocolor 6,
then I don't know when that will be.
This is undoubtedly a resource question as is supporting older
scanners. For each older scanner model, somebody has to sit down for
a week or so and write a new driver. There are a good many desktop
models which I suspect won't make it into Newcolor just as there are
a good many Chromagraph models which never made it into Linocolor.
Plus I have absolutely no control over which intents and tables
are edited.
Probably not, so use ProfileMaker 4 instead. But I am not keen on the
idea in the first place since editing makes profiles work one way in
one place in the profile chain and another way in another place which
is confusing, and the rule of thumb is in any case only to edit the
BtoA0 Perceptual table to change your gamut mapping (and arguably
your BtoA1 Relative Colorimetric table, too), but to leave your AtoB
tables alone unless you change the printing process in which case you
need to recharacterize with a new set of test charts and rebuild with
a new profile.
I don't know about this editing stuff, to me it seems that the power
of tools to edit outstrips our understanding of what we are doing to
the workflow when we edit. I seem to remember Steve writing a while
back that he had spent most of his time at a show explaining to
people why they shouldn't be editing when they expressly wanted to be
editing. For instance, there are legitimate reasons for editing such
as a customer without proper viewing lights who rejects a proof as
too flat, so you fix the back transform and produce a proof which the
customer will accept and just use the forward transform, just as
people in analog workflows would create two sets of proofs in similar
circumstances.
Just my ten cents.