AppleCLCD2
instead of AppleDisplay
for AS Macs.ioreg
will not return EDID for AppleCLCD2
, instead it will decode the edid to properties like the following:"Chromaticity"={"Red"={"X"=43200,"Y"=21888},"Green"={"X"=19712,"Y"=41856},"Blue"={"X"=9792,"Y"=2816}},"DefaultWhitePoint"={"X"=20544,"Y"=21568,"Gamma"=144179}
I tried to run the script on my old 2014 Macbook Pro 15 inch with DP port to the monitor and then copied the output file to M1 Mac mini. It doesn't work. It seems that the monitor can't recognize the patch file.The display "driver" for M1 Macs is different, and the display class name is nowAppleCLCD2
instead ofAppleDisplay
for AS Macs.
ioreg
will not return EDID forAppleCLCD2
, instead it will decode the edid to properties like the following:
Code:"Chromaticity"={"Red"={"X"=43200,"Y"=21888},"Green"={"X"=19712,"Y"=41856},"Blue"={"X"=9792,"Y"=2816}},"DefaultWhitePoint"={"X"=20544,"Y"=21568,"Gamma"=144179}
Therefore current scripts cannot work.
But the chance is that someone can create that patch using an Intel Mac, and copy that to M1 Mac to see if it will work, if that's the case, we can obtain the edid string using something other than ioreg and manually apply the patch.
If this is the case we will need to start over for a new way could work on M1 Macs.I tried to run the script on my old 2014 Macbook Pro 15 inch with DP port to the monitor and then copied the output file to M1 Mac mini. It doesn't work. It seems that the monitor can't recognize the patch file.
The display "driver" for M1 Macs is different, and the display class name is nowAppleCLCD2
instead ofAppleDisplay
for AS Macs.
ioreg
will not return EDID forAppleCLCD2
, instead it will decode the edid to properties like the following:
Code:"Chromaticity"={"Red"={"X"=43200,"Y"=21888},"Green"={"X"=19712,"Y"=41856},"Blue"={"X"=9792,"Y"=2816}},"DefaultWhitePoint"={"X"=20544,"Y"=21568,"Gamma"=144179}
Therefore current scripts cannot work.
But the chance is that someone can create that patch using an Intel Mac, and copy that to M1 Mac to see if it will work, if that's the case, we can obtain the edid string using something other than ioreg and manually apply the patch.
In very old days YPbPr will gave a very terrible quality that you cannot even see the text clearly.Same here, on a Dell u3219q. iPad Pro also connects as YPbPr. But in all cases it looks great, so does it really matter? Or does RGB look better?
I copied the patch file from a 2018 Mac Mini to M1 Mini. No luck though. My Dell U2518D monitor still connects as YPbPr instead of RGB.
Where did you copy to? There are reports saying you have to copy to the “/Library” directory, instead of the “/System/Library” on Big Sur to make it work.copied the output file to M1
"/Library/Displays/Contents/Resources/Overrides"Where did you copy to? There are reports saying you have to copy to the “/Library” directory, instead of the “/System/Library” on Big Sur to make it work.
It is harder to make / rw, you have to disable signed system volume."/Library/Displays/Contents/Resources/Overrides"
The "System/Library" is not writable on M1 Mac even disable SIP(fail to run command "sudo mount -uw /")
YcbCr mode is the $5 mode. It takes an otherwise great and expensive monitor and turns it into a $5 monitor you could find at the thrift shop. It's a terrible waste of technology.Same here, on a Dell u3219q. iPad Pro also connects as YPbPr. But in all cases it looks great, so does it really matter? Or does RGB look better?
Where did you copy to? There are reports saying you have to copy to the “/Library” directory, instead of the “/System/Library” on Big Sur to make it work.
Depends on the monitor. Go through its menus. On a Dell it’s under the Color section.how can you check what mode your monitor is running in?
It was in the old days, not quite nowadays.YcbCr mode is the $5 mode.
Has anyone tried copying a file from one Intel Mac to another, instead of Intel to M1?It doesn't work. It seems that the monitor can't recognize the patch file.
YPbPr made my U3219Q looked "wrong" in a way I couldn't put my finger on. Especially text. To the point where I was considering a return.Same here, on a Dell u3219q. iPad Pro also connects as YPbPr. But in all cases it looks great, so does it really matter? Or does RGB look better?
Apple should really fix this themselves; I filed feedback FB8946046 and suggest you dupe it with a description of the issue.Copied to /Library/Displays/Contents/Resources/Overrides
Display property correctly shows the modified name (~EDID override) but doesn’t actually enforce the RGB mode.
Hoping someone can create an updated patch with new syntax and commands for M1 Macs.