My main monitor is hardware calibrated to AdobeRGB and sRGB colour space (built-in cal device, ColorNavigator7), each with different colour temperatures – and communicates with Win10 ‘on-the-fly’, – yes, the difference is visible ( otherwise nobody would care / spend money … ) The other manages 100% sRGB – yes (and suppose some more) – FastPictureViewer has to be set manually to the correct screen profile,ĭoes PL5 do anything about the current ICM profile, when a window moves from A to B – IrfanView can be set to automatically choose the current profile (like PL),īut not with moving the active window to the other screen apart from that I use different viewers.– I tried this with old LR 5.7 (main Window) and it looks like it does – that only works if PL would have an ‘autosensing’ feature, what I doubtĪdobe applications take into account on-the-fly-changes Moving the main window to the other monitor – so that’s what it does, when starting on one of them PL5 is configured to automatically choose the current profile Yes, two monitors, both calibrated / profiled There are standard Windows API functions to do this enumeration once at program start in order to add those profiles to the drop-down list of ICM profiles in the program’s “Display” options.Ĭan’t give a profound answer, just a few ideas. One simple workaround would be the ability to change the ICM profile used by Photolab 5 on-the-fly to another ICM monitor profile enumerated among the profiles already active on connected monitors. In my particular case, one monitor covers 100% of the AdobeRGB gamut, while the other only manages 100% of the sRGB gamut, so the visual difference is readily observable in the more saturated colours. Microsoft’s Windows API has an elaborate system of callbacks that allow programs to react to changes in window status items (size, visibility, etc.), of which one is the current colour transformation (or ICM profile) attached to a window, and there are others which do the same for the current screen on which a window may have been moved to.Īs far as I know, Adobe applications all take into account on-the-fly changes in colour management when moving windows among monitors, and I believe most serious Windows photo editing software does the same thing.ĭoes Photolab 5 do anything about the current ICM profile when a window moves between screens? What happens when I move the main window (or the detached image browser window) to the other monitor? When Photolab starts, it’s configured to use the system profile, presumably using one of the Windows API functions that yield the ICM colour profile assigned to the monitor on which Photolab has started. I have two monitors, both calibrated and profiled individually, with the profiles installed and configured in Windows 11 for each monitor.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |