- This topic has 4 replies, 2 voices, and was last updated 11 months, 1 week ago by
.
-
Posts
-
Just got a new 5k display and using the 5k resolution. However Win 11 text is microscopic and I set scaling to 200% for text, apps etc. After doing this, display call won’t start when I manually launch the app. It gives me multiple python errors. If I leave it like this, will displaycal not load use the profile? I did do a restart of the PC and the icon in the taskbar does show it as being loaded.
I’m using display cal ver 3.9.16 with Windows 11 home 24H2 release with an Nvidia 3060 video card with the latest studio drivers.
Try DisplayCal 3.8.9.3. If your meter is supported it is ok to use Argyii the old version the old displaycal loads during install. The new one needs to be fixed. Bug reports go to the new site. 3.8.9.3 works fine in Windows 11. Windows 11 24h2 does have its new auto color that needs to be off for calibrators and try not to use Windows profile loader. Disable it in the Windows Color management. Have to go to admin defaults and set it to unchecked. The default Windows profile from data from hardware device actually worked and improved in measurements from a hardware calibration using HCFR and useing Displaycal for reports on the current settings for it display profile. Displaycal is deep. Research is needed.
I do wish the new Displaycal worked to try to calibrate from 0 to 254 instead of 0 to 255. 255 makes my tv clip except the windows hardware profile does not. Even a displaycal profile useing as measured for everything since it is calibrated but needs a profile for color managed apps.
Try DisplayCal 3.8.9.3. If your meter is supported it is ok to use Argyii the old version the old displaycal loads during install. The new one needs to be fixed. Bug reports go to the new site. 3.8.9.3 works fine in Windows 11. Windows 11 24h2 does have its new auto color that needs to be off for calibrators and try not to use Windows profile loader. Disable it in the Windows Color management. Have to go to admin defaults and set it to unchecked. The default Windows profile from data from hardware device actually worked and improved in measurements from a hardware calibration using HCFR and useing Displaycal for reports on the current settings for it display profile. Displaycal is deep. Research is needed.
I do wish the new Displaycal worked to try to calibrate from 0 to 254 instead of 0 to 255. 255 makes my tv clip except the windows hardware profile does not. Even a displaycal profile useing as measured for everything since it is calibrated but needs a profile for color managed apps.
Thanks! I think I’ll remove the current displaycal and revert to the 6 year old version. Before I run the calibration with the old version, I’ll ensure the built in Windows OS calibration is disabled. But overall, display cal is so deep and I’m pretty sure I’m in over my head. There seem to be hundreds of esoteric settings that can break an accurate monitor profile for newbs. I really don’t want to spend ~$300 for a new hardware calibrator and using their calibration software. But at a certain point it might be worth it. I’m already on my 4th calibration and different results every time. Now onto my 5th….
Your brightness on 100%? 50% is a lot better on the hardware and it is more stable. They do warm up and it takes more than 30 minutes to warm up. After being on for a long time they stabilize but the peak brightness goes down a little. It changes everything. Got to use HCFR to see what changes over time and settings. Adjusting the controls on the display will change things.
Your brightness on 100%? 50% is a lot better on the hardware and it is more stable. They do warm up and it takes more than 30 minutes to warm up. After being on for a long time they stabilize but the peak brightness goes down a little. It changes everything. Got to use HCFR to see what changes over time and settings. Adjusting the controls on the display will change things.
I have brightness set to 25% (and displaycal shows 120 cdm) and the monitor and spyder warm up for at least an hr before running any measurements.
