On Friday 09 June 2006 09:11, Marti wrote: > Hi Armindo, > > Definitively, the display profile should NOT be taken into account. I don't > know if anybody is doing that, but would be a very bad idea. Ok, good match > to screen may be a goal for the big boys, but, at least for the iniciatives > I've been involved, that is performed by defining suitable viewing > conditions and a setup for the reference monitor, not taking each > workstation monitor profile into account. Many large format printers are > developed with network printing in mind, doing this hack would go against > any color consistency and therefore be contra-producent for the bussiness. > :-) > > I would bet instead for mixed output profile/intents used in each driver, > and maybe double color management. Give a try to the probe profile, I > assure you it would be worth of spent time. > > Regarding the tool to list used profiles, nothing like that on windows > AFAIK. Also, many applications do color management on their own, > completely bypassing ICM. A RIP would be the ultimate solution if > everything else fails, but those are not cheap... > > Regards > Marti. > > > ----- Original Message ----- > From: Armindo > To: Marti ; lcms-user@lists.sourceforge.net > Sent: Thursday, June 08, 2006 5:11 PM > Subject: Re: [Lcms-user] Problem with Printer on Network > > > Hi Marti, > > Nice to ear you. > > The problem may come from photoshop or the Dosplay profile. > Someone told me that to have a very close color between Display and print > outputs, some printer manufacturer take in acount the display profile. Also > this customer has photoshop on every PC and each PC has different > monitors... Do you know what doesn photoshop do if you want to adjust the > display settings (inside adobe product) ? > > Is there a tool that can list all the profiles used by a PC (monitor, > scanner, and each prodile used by each printer) ? > > thanks > > Armindo
On Windows there is a new Color Control Panel applet from Microsoft that allows users to specify what profiles are to be used with each device. One of the nice features is that this allows users to specify profiles for each monitor in multi-monitor setups. Something that you can not do without the applet with most video drivers. In addition the applet will handle VCGT loading so if your profiles have VCGT tag data you no longer need a separate gamma loader program. This applet can be downloaded from Microsoft. This appears to be a backport to XP/2000 from Vista. I have been using this on Windows for about two months now to manage my display profiles and it is a big improvement over what was available before. But I use Windows so little that I don't know how well it works for other devices like printers and scanners and I suspect that this is highly dependent on the printer and twain drivers. I also believe that anyone who wants to do color management on Windows should have this installed. > > > > Hi Armindo, nice to talk with you again :-) > > >When I print some color patches on it from 5 > > different PCs, with EXACTLY the > >same settings and same color profile, > >I see some color difference on the printed results > > Ah, workflow problems. I strongly believe this > is *the* real issue on today's color management. > Double-color management, inconsistent paths, > different profiles... a nightmare. > > Ok, I cannot spot where the problem is, but here > are some clues. Thay have been very useful to > me in past. > > 1) Trust nothing. Check each driver, profile, etc. Even > if the filename and UI look is same, maybe the > profile and driver are different. > > 2) pinpoint the path. This technique is very effective > when one tries to find which profile/intent is being applied. > > ICC gives a "probe profile" here: > > http://www.color.org/probeprofile.html > > This is a fake profile that adds a huge tint, which is of > different color on depending on intent being used. > So, just replace the output profile with this one and do > some prints. If the workflow is configured correctly, every > print should come with same tint color. I guess you will > be surprised by results. > > > 3) Isolate wrong branches. If you have a > colorimeter/spectrophotometer, print some patches and > measure them. Isolate the parts of the network that produces > bad results. If the workflow is complex enough, maybe is not > worth of understanding each step. Remember, you want good > results. A proper setup would be nice, but you final goal are > good results. > > > Hope this helps > > Cheers, > Marti. > > > ----- Original Message ----- > From: Armindo > To: lcms-user@lists.sourceforge.net > Sent: Tuesday, June 06, 2006 2:00 PM > Subject: [Lcms-user] Problem with Printer on Network > > > Hello, > > I don't know if somebody has already had this problem. > > I use a Canon IP4200 printer shared on a Network. > When I print some color patches on it from 5 different PCs, with > EXACTLY the same settings and same color profile, I see some color > difference on the printed results. Any idea of how to solve this ? All the > PC run on Win2K with same driver version. > > Thanks > > Armindo > > > > > > > > > _______________________________________________ > Lcms-user mailing list > Lcms-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/lcms-user > > > > --------------------------------------------------------------------------- >------------ Orange vous informe que cet e-mail a été contrôlé par > l'anti-virus mail. Aucun virus connu à ce jour par nos services n'a été > détecté. > > > > > > > --------------------------------------------------------------------------- >--- > > > > > --------------------------------------------------------------------------- >--- > > > _______________________________________________ > Lcms-user mailing list > Lcms-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/lcms-user _______________________________________________ Lcms-user mailing list Lcms-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lcms-user
