Tony, I played with the monitor ICC profile. I could not browse to a file named 'monitor.icc' as my system doesn't seem to have a "monitor.icc" file. I searched the hard drive, and the closest I came up with is a file called
c:\Program Files\Common Files\Polaroid Imaging\Profiles\monitor,pc.icc I tried just leaving that field blank. It really didn't make that much difference but it might be a bit better. Tony Sleep wrote: > On 11/01/2006 [EMAIL PROTECTED] wrote: > >>I favour the suggestion that the colour temperature of his monitor is >>different to that of the lightbox. > > > Something in this area might well account for the perceived different > colour balance between Polascan and Vuescan. > > Adobe Gamma imposes global screen profiling, which will be fine for > Polascan (as fine as AG can be), whereas Vuescan... well, it does full CM, > so setting an explicit monitor profile could likely be introducing double > profiling. AG is already using its custom screen profile within the > Windows environment, everything displayed is controlled by AG. > > I use Optical/Spyder hardware screen profiling which also has a global > effect on the display (loaded at startup, like AG). In VS my settings are > > Monitor Colour Space = 'ICC Profile' > Monitor ICC profile = 'monitor.icc' > > If I set my custom profile instead of 'monitor.icc' I would expect double > profiling. I'd expect similar to happen if Stan is setting his AG profile > there. He should only state an explicit profile if AGLoader is not running > at startup. That would then provide CM of display within VS, but with > AGLoader *and* VS using the profile, it is happening twice. ---------------------------------------------------------------------------------------- Unsubscribe by mail to [EMAIL PROTECTED], with 'unsubscribe filmscanners' or 'unsubscribe filmscanners_digest' (as appropriate) in the message title or body
