Hello, I think I may be experiencing a bug with ST.2084 custom spaces in ColourSpace CMS 126.96.36.1998.
If I create a custom ST.2084 space with a custom maximum nits level (such as 700 nits, so I can verify PQ tracking on an LG OLED), upon loading the space in the profiling window the maximum nits appears to get overridden to 10000 nits. If ColourSpace CMS is restarted, the custom space will read 700 nits again. So it appears the space is being saved correctly on disk, but the profiling window is forcing it to 10000 in that session.
Windows 10 21H2, ColourSpace is installed for "all users", LTE license.