Closed goldenx86 closed 3 months ago
Before opening ARC Control:
After opening ARC Control:
Both pics were taken with a 4000k white balance, 50 ISO, and 1/10 shutter speed to normalize them.
Hi @goldenx86 thanks for this.
when you mention " 24H2 solves it by opening the color profile settings." are you saying the latest update of windows, fixes your issue?
Hi. Yes and no, it's not guaranteed to work after some several attempts. When it works, just going to Windows Configure > Display > Color profile solves it. Other times, it still needs a system reboot/log-off to solve it.
@goldenx86
So, checkout my testing video: https://youtu.be/3HPAXTKymJY
Am i doing everything right here? I used your profile and did not notice much of anything. Tried leaving for an hour and then coming back and re-did all the steps. Still did not see the reverting back after launching arc control.
What monitors are you using? It could very well be thr monitor specific issue.
Could you tell me the following:
-Muji
For 23H2, you have to set the profile as system wide for the change to take effect, which is what my laptop's driver does. This is in Color Management, Advanced tab, at the bottom left, Change system defaults, and then set the profile for the display there. On 24H2 this is just done from Configure > Devices > Screen Color profiles.
Make sure to test this locally and not over remote, as it won't show up on recordings, the profiles only affect the output of the display, not the actual frames.
The specific display shouldn't matter, but just in case, this Asus laptop comes with a BOE 0903, it's just the integrated display. From the Intel Discord server, at least 3 people are affected from what I could find, all with different configurations. I'll try if DDU helps with the latest driver.
Oh nice, I now tested it on the integrated graphics (not a remote device). and followed your instructions.
can you tell me if I did everything right here? https://youtu.be/H2tmGKVM2FE I couldnt see any difference in the behavior of resetting it to srgb when opening arc control.
how about this, can you record your desktop going from step 1 to the failure you mentioned? I want to see how the profile changes to srgb
Yeah, LGTM. I wonder if it is the fact that it's installed for the specific device instead of loading the profile manually. I didn't have any luck with DDU, the issue is still reproducible on my end.
yeah, this is interesting to me. Do you have the link to the post on discord? I wonder if they all use the same exact model of the laptop/display.
Actually, I found the post on discord. I have a similar laptop as the other user. I'm going to test it on that one and come back with the results.
I'm going to follow the exact same procedure to test it on another system.
When you say "it's installed for the device vs manually loading" what do you mean by that? You mean the default the device came with was the profile you shared vs how I am manually loading it to apply as default?
-Muji
Yeah by default (the stock Windows install), or if you manually install the "driver" responsible for adding the system level profile, you don't need to go yourself through what you did on the videos. But since those drivers look for the vendor and panel IDs, it's basically useless unless you have my same laptop. I can pass the installer, I just extracted the profile from there so I can also use it on Linux too: https://dlcdnets.asus.com/pub/ASUS/nb/Image/Software/SoftwareandUtility/15070/MyASUSSplendid_ASUS_Z_V6.0.0.487_15070.exe?model=X1502ZA
Yeah could be specific to that brand of device since I couldn't reproduce it on other desktops. However, I still have to test on the system one discord person tasted since I have the similar if not the exact one. Will keep you in the loop.
Btw, if you can get in touch with the manufacturer regarding this and letting them know it doesn't happen anywhere else, could be helpful as well since it could very well be something from the manufacturer driver setup that's causing this weird conflict.
I can try at least. Asus is not the greatest, but it's worth mentioning it to them.
Hey @goldenx86 so we had the i7-14700HX lenovo legion pro 5i model ordered and I tested on that with both IGPU and only Nvidia dgpu. Did not notice any resetting of the color management profile after opening up arc
-Muji
Pretty slippery one.
So yeah, I suspect this issue is related to your system and the best course of action would to be get in touch with the manufacturer. I mean you could try our latest graphics driver released two days ago. But if that doesn't do the trick, then the manufacturer route would be the ideal choice in this scenario.
Hey @goldenx86
Okay, so this the game plan:
Does this sound good to you?
Will do and confirm with you here. Guess it's the last to do before the incoming EoL. Thanks.
Ill go ahead and close the ticket, if you have questions you can refer back to this ticket, sounds good?
Sounds good to me, thank you for your time.
Appreciate it. Thank you for reaching out.
Found the cause, ARC Control has a brightness default of 30 instead of the proper value of 50. Resetting that solves the problem.
Checklist [README]
Application [Required]
Intel ARC Control
Processor / Processor Number [Required]
i5 1240P
Graphic Card [Required]
Iris Xe
GPU Driver Version [Required]
32.0.101.5762
Other GPU Driver version
No response
Rendering API [Required]
Windows Build [Required]
Windows 11 23H2
Other Windows build
At least 23H2 and 24H2
Intel System Support Utility report
intel.txt
Description and steps to reproduce [Required]
If a system-wide color profile is configured, opening Intel ARC Control resets it back to sRGB, making some monitors display wrong colors. The only way to revert this on 23H2 is to disable ARC Control from startup and log off. 24H2 solves it by opening the color profile settings.
Tested system is an ASUS Vivobook X1502ZA, i5 1240P, Iris Xe. Both Windows 11 23H2 and 24H2 are affected. I'm attaching the profile my display needs as an example. X1502ZA_8086_E5090903.zip
Device / Platform
Asus Vivobook X1502ZA
Crash dumps [Required, if applicable]
No response
Application / Windows logs
No response