Heh, No the profiles work fine when you let the printer driver use them. You want to turn the profiling off when printing the test target. That way you get a sampling of what raw RGB numbers produce ... then the software can make the profile to make them all look good. You can certainly use the ICM profiles produced in the Printer driver too! A lot of people prefer to do the color management in their favorite graphical editing program (PhotoShop - Let PhotoShop handle colors) rather than letting the printer software do it. Does that help? Tom --- In colorvision_group@yahoogroups.com, "mhovie71" <martin@...> wrote: > > Hi! > > I'm new to color calibration and I've just ordered a PrintFix Pro > Suite, which should be delivered in a few days. After reading reviews > and discussions, I'm wondering about the following: > > It seems necessary to disable the ICM profile in the printer driver > and use it in the graphics program instead. But why? Wouldn't it be > more logical and convenient to assign a profile to the printer and not > to all applications using the printer? > > When I create a profile for a monitor, I assign it to the monitor. > When I create one for a scanner, I assign it to the scanner. So why > shouldn't I assign a printer profile to the printer? > > If the profiles created by PrintFix don't work with the printer > driver, can they be converted somehow? > > I want all printing apps to take advantage of the correct profile, not > just Photoshop (or other software supporting profiles). If I assigne > profiles to the input and output devices once, that's much easier and > more convenient compared to assigning it to all applications I use. > Moreover, most apps don't even support custom ICM profiles (e.g. > photocopy programs, etc.) > > What is the point of the "ICM profile" option in the properties of > every printer dirver if it can't be used for anything? This doesn't > make sense to me... > > Regards, > > Martin >
Message
Re: Color profiles in printer driver - why not?
2006-04-11 by Tom
Attachments
- No local attachments were found for this message.