darktable 3.0.1 released

danny · March 18, 2020, 10:09pm

This regression in master with input color profiles seems to be now also affecting 3.0.1 on windows

In addition to

github.com/darktable-org/darktable

Windows: incorrect colors on secondary monitor

opened 09:21AM - 29 Nov 19 UTC

Dannny1

scope: color management scope: OS support bug: pending no-issue-activity

**Describe the bug** When darktable opens on secondary monitor(1) and the main …display is (2), it displays wrong colors. It probaly uses the display profile of the main (2) display. It shows correct colors on (1), if the (1) is set as main display. darktable 2.6 wasn't affected by this issue When dt is opened it seems also to show for very short moment small window on the main display, before it opens darktable window on the other monitor, it may be related. **To Reproduce** Steps to reproduce the behavior: 1. Have 2 monitors calibrated 2. Set darktable to open on secondary display 3. Open image in darktable **Expected behavior** it should use profile of the monitor where it's open and display corect colors as 2.6 did **Platform (please complete the following information):** - OS: Windows 8.1 - dt version: 3.0rc1 and rc2 Edit 2.9.2023: - dt version: Retested and issue present with with all releases including 4.4 Present with current nightly darktable-4.5.0+445 - OS: Windows 11 - HW: tested with nvidia rtx2070, and also different hw with 4080m