I may have to see if I can get this up and running. It will be an upgrade from the xserver/WSL2 work around to get Linux GUI running on the Windows 10 desktop…darktable ran fine there so it should even be smoother here…
Nice to see it’s making progress - although the requirements for a Windows Insider build mean it’s going to be another 2-3 years before I see this as an option in my primary Windows use cases.
Heck, as it is, I’m still considered a “beta tester” for 1909 rollout on my work laptop
(Although strangely, they rolled out 20H2 to someone which REALLY surprised me… But that person is located in a different site that has their own local IT staff who might not have properly communicated with the mothership)
I’d be really really surprised if color management works at all with WSL, under the hood it is RDP any Wayland.
I just got 21H1…the WSLg should come this fall I think to non insiders. I did lapse my insider membership as I was away on an extended trip an number of years back and my version expired…it basically meant my PC was bricked…
Yeah, in my case, my main use case for WSL is on a corporate machine, and corporate IT departments typically wait quite a while.
As I said - 1909 is literally still in beta test here.
Color management under Windows is handled by the application. When you load a profile (either through something like the DisplayCal profile loader or the native way), the VCT tables are loaded into the videocard. The matrix/lut/‘other’ part of the profile is then handled by the application. The desktop is not color managed at all.
So you need to tell darktable to use the exact same profile, and you have a very good chance for it to work OK. Time will tell though.
I’m very interested in this, and they seem to set it up pretty well (probably OpenCL acceleration might even be possible) but I’m not turning my work machine into an Insiders machine just to get early access. I’ll wait patiently to have a play with it :P.
Ya they posted some virtual GPU numbers and they are not bad… I am not sure of the metric but the number for native was around 500 and 350 for vGPU and like 5 for no vGPU so not too bad. If the intent is to support linux development I think they will have to make it work well or it will be a big bust…being able to easily go between the OS will be nice.
Its more about the underlying technologies. I don’t know if RDP is color managed and some quick searching didn’t reveal any answers. I’d suspect because of its age and intended uss that it is not capable of being color managed.
They are also using Wayland, which currently has no color managent support, so unless Microsoft adds this, it won’t work.
But rdp doesn’t need to be color managed… the applications you run inside of it must be. The same goes for Wayland… darktable itself must be able to map its working space to the display profile, and as far as I know it can (it does under windows ).
Windows doesn’t have do any color management. It only allows applications to request the profile that is chosen for a certain display. Its then up to the applications to do something with that profile (the reason why you have applications that are not color managed at all under windows… on a Mac, the os is doing (some) of the mapping).
So as long as you say to darktable 'this is my display profile to use I see no reason why it won’t work.
Maybe different profiles for different monitors will be an issue, but I could live with that.
Please let me know when you have it working in practice!