![]() Is it still possible to perform the workaround?įortunately, yes! With one small change. Googling around, I see evidence that people are still trying to force RGB on MacOS 11 (Big Sur), and that the previous version of the workaround no longer works. Comments on the original post suggest that the workaround was necessary and successful on 10.14 (Mojave) and 10.15 (Catalina). ![]() I first encountered the issue on MacOS 10.13 (High Sierra). To help anyone landing here in 2021, I set out to answer a few questions: 1. I no longer have the problematic monitor, but the post still receives a fair amount of traffic, so I wanted to check if the procedure still works. It turned out that my new Mac was using the wrong color space, but there was a workaround to force it back into RGB. BackgroundĪ couple of years ago, I wrote about a strange problem I encountered when I upgraded my Mac: my external display’s image looked terrible. ![]() As of MacOS 11, it’s still possible to override your display’s EDID in order to force RGB mode when you get a problematic YCbCr connection, at least on Intel macs. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |