ledoge

@provanguard The new version is just some UI changes + slight changes in how the color space conversion matrix is calculated. Just re-apply the clamp using that new release.

My first guess would've been that you didn't use the right setting when generating the measurement report, but that doesn't really fit in with what you're seeing on that site....

Thanks, those measurement reports tell the whole story! Both with and without an ICC profile, you're not verifying against Rec.709 but against the display profile itself. What you want to...

Does the `DisplaySettingsChanged` event not fire when the monitor gets put into standby? I assumed it did, but if not then I'll have to look into merging the power broadcast...

It's always there for me no matter what settings I use. Here's what I just did: 1. Check out the latest development branch 2. Delete the DisplayCAL folder under ~/.config...

Interesting, I thought that the monitor ID I'm using as the identifier is per device and not per port... Just to be clear, you're saying that the GUI .exe can't...

I think [this .exe](https://github.com/ledoge/dwm_lut/files/8365366/DwmLutGUI.zip) should fix this, please test it to confirm.

Can you upload the `config.xml` file after each time you assign a LUT to a monitor, using the new build?

OK, I believe the problem is now just caused by the fact that the config, when written, only includes monitors that are currently connected. I'll try to fix that in...

Just pushed a new release, which should handle your use case perfectly now. Please test it and report back!