before bothering around with darktable profiles use the profile you got to get your system (windows) to use this profile for display.
Then the simply use system default profile in darktable for your display and you‘re fine.
If you’re not that experienced with administrating your system, then better don’t copy stuff into system directories you don’t really know. Windows provides the tools to guide you to do it:
For historgram, workspace etc.pp. stay with the defaults unless you have a specific use case like: preparing output for print services
In the mean time read what you can get on color profiled workflow so you get an idea why you want to deviate from the standards.
Using profiles someone told you without understanding the why is the best way into trouble
That’s good advice and Glen’s document above spells things out pretty clearly… ironically on the display profile I never trust the OS and software. I want to implicitly specify the one I want to use. I use windows so I copied mine to the color\out directory so I can specify the exact profile by name.
I am hoping Santa brings me a calibrator for XMAS
Since I could not calibrate my monitor I always thought best to use the exact profile. However some of those profiles mess a bit with the gamma curve to handle blacks and so when you export in sRGB its not as close as you would like…I found out that actually setting my display profile to DT’s sRGB actually matched my screen/export better than using my display profile…
So I went this route for sometime. I did try the windows screen calibrator just for fun but I wasn’t entirely happy with it…
I am as a stop gap using calibrize now ( https://www.calibrize.com/ ) …simple screen calibrator that will tweak your system profile…make a copy with adjustments and set it as the system…it automates it and you can using the instructions you provided go back and ditch it if you don’t like the results…but I found using it I get a pretty good match for now until Santa come through…
This is why in rawproc I never bothered to figure out how and implement use of the system-specified display profiles - I specify them in rawproc’s properties. Recent rawproc will automatically switch display profiles if you drag the window from one display to another, if you have the two profiles in appropriate properties. Well, 'cept for Wayland, which apparently doesn’t provide the information needed for wxWidgets to know the specific display the application occupies…
