EmbDev.net

Forum: Off Topic Dell U2713H on Mac: forcing RGB mode instead of YCbCr


Author: Andreas Schwarz (andreas) (Admin) Flattr this
Posted on:
Attached files:

Rate this post:
useful
not useful
*UPDATE*: see here for a universal fix that works for all monitors: 
http://embdev.net/topic/284710#3027030

Many Dell monitors (e.g., U2713H, U2713HM, ...) look really bad when 
connected to a Mac (OS X 10.8.2) via DisplayPort, as if some sharpening 
or contrast enhancement was applied. Others have reported the same 
problem 
(http://www.anandtech.com/show/6308/dell-u2713hm-un..., 
http://forums.macrumors.com/showthread.php?t=1481582). The reason is 
that the DisplayPort uses YCbCr colors instead of RGB to drive the 
display, which limits the range of colors and apparently causes the 
display to apply some undesired post processing.

The problem can be solved by overriding the EDID data of the display 
(http://en.wikipedia.org/wiki/Extended_display_iden...) in 
order to tell OS X that the display only supports RGB. This can be done 
by reading the EDID with "ioreg -l", modifying the offending bits (see 
the specification in the Wikipedia article), and creating a display 
config override file for OS X. I have attached such a file for the 
U2713H and U2713HM; just extract it and move the contained folder into 
/System/Library/Displays/Overrides. After a reboot, the monitor should 
show that RGB colors are used. For other monitors with the same problem, 
the files won't work, but in principle the solution is the same.

Changes to the EDID that were made:
- color support: RGB only
- removed CEA extension block (may not be necessary; disables audio
  via Displayport)
- fixed checksum

Tools used:
- text editor
- calculator
- edid-decode (http://cgit.freedesktop.org/xorg/app/edid-decode)
- XCode plist editor

UPDATE: attached file contains fix for U2713HM as well.

Author: Scott (Guest)
Posted on:

Rate this post:
useful
not useful
Andreas, thanks again for assisting with this same process on the 
u2713HM. Works great.

Author: Matthias (Guest)
Posted on:

Rate this post:
useful
not useful
Hi Andreas, could you upload the file for the HM version as well? 
Thanks!

Author: Andreas Schwarz (andreas) (Admin) Flattr this
Posted on:

Rate this post:
useful
not useful
Done.

Author: Ryan L (Guest)
Posted on:

Rate this post:
useful
not useful
Is there any chance you could walk me through this process or upload an 
appropriate file for a Dell U3011?

Having the exact same problem, and it's been a real nightmare. Would be 
eternally greatful!

I'm trying to figure it out on my own but I'm not sure where to look 
within the output from ioreg -l -w -0 > ioreg.txt

Thanks in advance for any help, appreciate it.

Author: Alex Reeve (Guest)
Posted on:
Attached files:

Rate this post:
useful
not useful
Wow, you're a champion for doing this. I've been sporadically trying to 
solve this for almost 2 years!

I managed to work as far as I could by replicating what I imagined your 
steps are – I got everything else figured out except the <data></data> 
tag.

My monitor is a Dell 2709W, and my ioreg -l is attached to this post as 
a .txt file. If you could take a look I'd really appreciate it – or let 
me know how you calculated the <data></data> tag contents so I can do it 
myself!

Thanks again, really appreciated.

Author: Ryan Lucier (ryanl)
Posted on:
Attached files:

Rate this post:
useful
not useful
I kind of hacked my way around and got my Dell U3011 to properly display 
RGB over a mini display port to display port cable! WOOHOO! no need for 
that stupid $150 dual link dvi to mini displayport adapter anymore, 
which was incredibly flakey and sometimes the monitor turned on, and 
sometimes it didn't etc... lots of problems.

but anyways, heres the fix, i've attached a file you unzip into:
/System/Library/Displays/Overrides

It will create a new directory called:
/System/Library/Displays/Overrides/DisplayVendorID-10ac

Then reboot the system, and it should work. Go to system preferences, 
displays, color, and set the display profile to Color LCD.

This will ONLY work for the Dell u3011 and it is completely UNTESTED. 
Use at your OWN RISK. But you should have proper RGB colors after doing 
this.

Good luck!

Author: Vitaliy (Guest)
Posted on:

Rate this post:
useful
not useful
Hi, Andreas,

Could you please help me to solve this problem for dell u2711 ?

Thank you very much

Author: Andreas Schwarz (andreas) (Admin) Flattr this
Posted on:
Attached files:

Rate this post:
useful
not useful
Try running the attached script. Open Terminal and enter "ruby 
patch-edid.rb". This should give you an override file for your display.

Author: Dave (Guest)
Posted on:

Rate this post:
useful
not useful
Hi Andreas,

Many, many thanks for the script. Like Alex I have been struggling with 
this problem ever since I got tried to use a mini-DP to DP cable to 
connect a Thunderbolt MBP to a U2410 monitor (about 2 years ago!). The 
script works fantastically for me.

Interestingly, the same monitor works fine with my original unibody MB 
(i.e. a true mini-DP port), and also works great with my new laptop in 
Windows, so I guess there's a bug in OS X somewhere in relation to 
Thunderbolt and these monitors.

Thanks again!

Dave

Author: David Riek (bodo123)
Posted on:

Rate this post:
useful
not useful
Hi Dave,

yes, I made the same experience.
It is a Thunderbolt problem and OS X.

That's really a bad bug from Apple. I hope they fix it with 10.8.3.

Author: Vitaliy (Guest)
Posted on:
Attached files:

Rate this post:
useful
not useful
Dear Andreas,

There is some problems with run of this script. Probably i am quite 
stupid and did something wrong. Could you please help me with this. I 
attached terminal screen.

Author: Andreas Schwarz (andreas) (Admin) Flattr this
Posted on:

Rate this post:
useful
not useful
You need to run the script while (only) the external display is 
connected.

Author: Vitaliy (Guest)
Posted on:

Rate this post:
useful
not useful
Dear Andreas,

I have tryed all ways to switch off my macbook display and run this 
script with only external display connected: switch it to sleeping mode, 
than to wake it up with keyboard, but still the terminal command to run 
the script doesn't work :(

Probably I am doing something wrong with typing in terminal window.
Should i put this script file in some specific folder?

I will be very appreciate to you if you could help to fix it in "ioreg 
-l" data

+-o AppleDisplay <class AppleDisplay, id 0x1000003be, re$
| | | | | | {
| | | | | | "IOClass" = "AppleDisplay"
| | | | | | "CFBundleIdentifier" = "com.apple.iokit.IOGraphicsF$
| | | | | | "IOProviderClass" = "IODisplayConnect"
| | | | | | "DisplayProductID" = 41047
| | | | | | "IODisplayEDID" = <00ffffffffffff0010ac57a04c353930$
| | | | | | "IODisplayPrefsKey" = "IOService:/AppleACPIPlatform$
| | | | | | "IOPowerManagement" = {"MaxPowerState"=3,"CurrentPo$
| | | | | | "IOProbeScore" = 2000
| | | | | | "IODisplayParameters" = {"bgsc"={"min"=0,"max"=6553$
| | | | | | "IOMatchCategory" = "IODefaultMatchCategory"
| | | | | | "AppleDisplayType" = 2
| | | | | | "IODisplayAttributes" = <676174760000000073676c6600$
| | | | | | "AppleSense" = 37119
| | | | | | "IODisplayConnectFlags" = <c4410000>
| | | | | | "DisplayVendorID" = 4268
| | | | | | "DisplaySerialNumber" = 809055564
| | | | | | }

Thank you

Author: Sebastian (Guest)
Posted on:

Rate this post:
useful
not useful
Hi Andreas,

Thanks for the RGB fix. I'm using the Dell U2713H on a new iMac.
Unfortunately there is a very serious problem with this display and I 
was wondering if you know if that's coming from Apple too:
After Hardware Calibration of the display (or using any other color 
profile besides "Standard") there is heavy green ghosting when I drag a 
window around. It is truly horrible.
Do you know if this is also connected to some Apple to Dell problem and 
how can it be fixed?

Thanks
Sebastian

Author: Kr (Guest)
Posted on:

Rate this post:
useful
not useful
I have Dell U2713H, and 15" rMBP and I filed a support ticket with Apple 
and they sent me a program called TimingSnoop to collect diagnostic 
output. That program seems to collect all EDID information, driver 
details and pretty much all display information. I sent them back the 
output but haven't heard back from them after that.

Forcing RGB seems to make some improvement, but the display is still 
very bad.  There is still some ghosting/fuzzy behavior and it does look 
like some sort of timing/refresh issue. Prior to forcing RGB, I was 
reducing the sharpness levels on the monitor all the way to zero and it 
seemed to make similar improvement.

Author: Andreas Schwarz (andreas) (Admin) Flattr this
Posted on:

Rate this post:
useful
not useful
When in RGB mode, set sharpness to 50, this seems to disable any 
processing. Otherwise the image is blurred or sharpened.

Author: teowood (Guest)
Posted on:

Rate this post:
useful
not useful
Hi,

I just got the Dell U2713H monitor. I connected it with a macbook air 
mid 2011 model (Thunderbolt minidp) using a mini dp to mini dp cable.
I didn't have the YcBcR issue, although OSX system profile reports the 
monitor as "television".
The colors are fine and the Monitor color mode is in RGB as expected
The problem I have is a strange ghosting (probably an RTC overshoot 
issue) when moving windows or scrolling text!

I see Sebastian and Kr have also this specific problem, did you have any 
news from Dell or Apple support?
I have tried the EDID override thing but it doesn't seem to correct the 
"ghosting" issue. I have also tried connecting with several other dp 
cables but the issue is still there.

Has anyone tested this particular monitor with a standard DVI-D PC ?
This is the only test I have not done yet.

Author: Kr (Guest)
Posted on:

Rate this post:
useful
not useful
@andreas, yes I have already set the sharpness to 50 without which the 
display is unbearable but even with this workaround I still think that 
there is some ghosting/clarity issue.

@teowood
Apple closed my support ticket as a duplicate of another ticket and 
Unfortunately I'm not able to see the details in the other ticket.

I also want to test the display with a dual-link DVI connector but 
havent had a chance to do it and Dual Link DVI adapters are expensive

Author: teowood (Guest)
Posted on:

Rate this post:
useful
not useful
Well a pc with a good VGA card should be capable for a dual link DVI, no 
extra adapter needed. I am waiting for my alienware to arrive. I should 
do the test soon.
Meanwhile what i have noticed is that dropping the contrast from the 
default 50 to 40 or 39 almost makes the ghosting go...
I am thinking if i have to live with that or return the monitor :(

Author: Ideas Enabled (ideasenabled)
Posted on:

Rate this post:
useful
not useful
Hi Andreas,
I tried your generic ruby script and could successfully generate the 
file. Just one question: I recognized a slightly different data entry in 
the <data> area for my u2713HM.
The script generated:

AP///////wAQrIBATDk3OSYWAQSlPCJ4Iku1p1ZLoyUKUFSlSwCBALMA0QBxT6lAgYABAQEB 
Vl4AoKCgKVAwIDUAVVAhAAAaAAAA/wBHSzBLRDI5Sjk3OUwKAAAA/ABERUxMIFUyNzEzSE0K 
AAAA/QAxVh1xHgEKICAgICAgAOc=

In your default 2713HM file you have:

AP///////wAQrIBATDAzMyIWAQSlPCJ4Iku1p1ZLoyUKUFSlSwCBALMA0QBxT6lAgYABAQEB 
Vl4AoKCgKVAwIDUAVVAhAAAaAAAA/wBHSzBLRDI4TjMzMEwKAAAA/ABERUxMIFUyNzEzSE0K 
AAAA/QAxVh1xHgEKICAgICAgAA4=

As you can maybe spot, there is a slight difference in the last part:
Oc= vs. A4=

Is this on purpose? What does it mean? And which one to choose now?

Thanks in advance,
chris @ideasenabled

Author: Ideas Enabled (ideasenabled)
Posted on:

Rate this post:
useful
not useful
I just realize there are even more differences in the following order:

1.
Script:
k3OSY

Default:
AzMyI

2.
Script:
5Sjk3OUw

Default:
4TjMzME

3.
Script:
Oc=

Default:
A4=

Author: Andreas Schwarz (andreas) (Admin) Flattr this
Posted on:

Rate this post:
useful
not useful
The only difference is the serial number (different for each display) 
and the checksum, so it doesn't matter.

Author: Andreas Schwarz (andreas) (Admin) Flattr this
Posted on:

Rate this post:
useful
not useful
I also see ghosting on my U2713H, much worse than on my old Eizo S2110W. 
No idea how or whether it can be fixed in software.

Author: Mathew Inkson (coach)
Posted on:

Rate this post:
useful
not useful
Hi Andreas, just joined so that I could thank you for this incredibly 
helpful post. Many of the official and unofficial Apple forums have 
multiple threads about this issue with no solutions, I only found this 
page because I had a hunch that it could be an EDID colorspace issue.

I've posted about it here, let me know if you want me to make any 
changes:
http://ireckon.net/2013/03/force-rgb-mode-in-mac-o...

Author: robin (Guest)
Posted on:

Rate this post:
useful
not useful
Hi All

New to the forum and had high hopes for this fix but alas on my Samsung 
SyncMaster SA350 it seems to have compounded the issue. Now the external 
monitor isn't recognised at all having applied the script.

I (foolishly) didn't backup the initial settings. Can someone tell me 
how to rollback?

Thanks in advance.

Author: Mathew Inkson (coach)
Posted on:

Rate this post:
useful
not useful
robin: in my case I wasn't overriding an existing folder with the same 
name in the Overrides directory, so to rollback I would just delete that 
new folder the script had made.

If you'd overridden an existing folder in the Overrides directory 
without making a backup I'm not sure how best to proceed. However, I 
think it wouldn't hurt to move the folder to somewhere out of the 
Overrides folder (so that there are no overrides for your monitor at 
all), then restart and see if OS X applies the default settings.

Author: Ideas Enabled (ideasenabled)
Posted on:

Rate this post:
useful
not useful
Robin, I have the original files as a backup zip. So let me know in case 
you need them. I need to dig them out but I would do it for you as I was 
in a similar situation like you a month before.
Btw, can you not have a look in time machine? Afaik you should find the 
former stub there.

Author: Mathew Inkson (coach)
Posted on:

Rate this post:
useful
not useful
Oh, I thought that unless you had the same monitor these would be 
different files.

Author: Ideas Enabled (ideasenabled)
Posted on:

Rate this post:
useful
not useful
I was referring to the OS.X "native" ones (without external monitor). 
The ones for the external LCD will be created after the external monitor 
will be attached to the MBP.
So this should work LCD independent.

Author: markjenn (Guest)
Posted on:

Rate this post:
useful
not useful
A quick thanks to Andreas and others you have contributed to this 
thread.  I recently purchased a U2713HM to use with my mid-2010 MBA and 
ran into the expected issues, first with getting the right cable to 
drive it at the full 2560x1440 resolution (mini-displayport to 
displayport is the cheapest solution), then with the issue of "off" 
colors and odd processing artifacts when it is being properly driven in 
YCbCr rather than RGB.  (I think some are not realizing the problem 
because the Mac will report that it is using RGB - you have to use the 
OSD on the monitor to discover what mode is it actually in.)

Anyway, using the attached file solved the problem completely and the 
display looks great.

- Mark

Author: John (Guest)
Posted on:

Rate this post:
useful
not useful
Many, many thanks for this Andreas!  My Dell U2410 worked beautifully on 
my 2006 MacBook Pro and via DVI-to-MiniDP on my new MBP retina, but the 
HDMI output looked lousy.  I had to take up a Thunderbolt port to use 
the monitor, but with this fix I can now use the HDMI and free up the TB 
port for a drive.

Thank you again!

John

Author: Rob M (Guest)
Posted on:

Rate this post:
useful
not useful
Vitaliy,

I had the same problem. I suspect you are using 10.7 as I had the same 
error. Upgrading to OSX 10.8 allowed me to run the ruby with no error. I 
don't know ruby so it was easier for me to get the new OS instead.

Author: say word (skep)
Posted on:

Rate this post:
useful
not useful
Ideas Enabled wrote:
> Robin, I have the original files as a backup zip. So let me know in case
> you need them. I need to dig them out but I would do it for you as I was
> in a similar situation like you a month before.
> Btw, can you not have a look in time machine? Afaik you should find the
> former stub there.

I would be grateful if you could dig up that zip file. I had the default 
folder saved to my desktop, but something happened when i tried to roll 
back. The file is gone. I was testing to see if RGB would look better on 
my TV, but I need to be able to switch between 24 and 60 hz. Now that I 
have "rolled back" it will no longer let me switch and is stuck on 60 
hz. I am not sure if I corrupted a file or something when I copied the 
default settings back in overrides. Please help!

Author: say word (skep)
Posted on:

Rate this post:
useful
not useful
I figured it out. When I switched back, it disabled all of my custom 
switchresx resolutions. It recreated the file when I redid the custom 
profiles.

Author: Katie (Guest)
Posted on:

Rate this post:
useful
not useful
Hi,
I have had the same issue as everyone else with my new Macbook Air 
connected via HDMI to a LG E2260 monitor.

I apologise, but I have absolutely no programming experience. I 
eventually found out how to "open terminal" but when I did enter the 
"ruby patch-edid.rb" into the terminal nothing happened. I suspect that 
I will need an external keyboard and mouse for this to work for the next 
step as I obviously cannot type anything with the macbook lid closed?

Could someone take a dummy through the procedure in simple steps?

Thankyou

Author: Ideas Enabled (ideasenabled)
Posted on:

Rate this post:
useful
not useful
Katie wrote:
> Hi,
> I have had the same issue as everyone else with my new Macbook Air
> connected via HDMI to a LG E2260 monitor.
>
> I apologise, but I have absolutely no programming experience. I
> eventually found out how to "open terminal" but when I did enter the
> "ruby patch-edid.rb" into the terminal nothing happened. I suspect that
> I will need an external keyboard and mouse for this to work for the next
> step as I obviously cannot type anything with the macbook lid closed?
>
> Could someone take a dummy through the procedure in simple steps?
>
> Thankyou

Katie, I am happy to help you out. Skype might be best.

Programming skills are not needed. The script creates a folder. You have 
to copy the folder to a certain place (command line in terminal). 
Restart. Done. You probably need an external keyboard, right. Mouse is 
not required.

Steps are:
- close lid so that you see the external monitor screen only
- open terminal
- run script (folder gets created at your current location: -> type pwd 
(print working dir)
- copy the folder to "/System/Library/Displays/Overrides" via sudo cp -R 
[YOURCURRENTWORKINGDIR]/[CREATEDFOLDERNAME]/ 
System/Library/Displays/Overrides/
- check whether it worked via: ls -la 
/System//Library/Displays/Overrides/
- you should see the RubyScript folder there (see info below)

So for example:
sudo cp -R /Volumes/Free.../RubyScript 
/System/Library/Displays/Overrides/

The command copies what's in the RubyScript folder to the other folder

See info for copy command here: 
http://linux.about.com/od/commands/l/blcmdl1_cp.htm

Hope that helps. ping me at hello AT ideasenabled.com (christian) if you 
need help.

Author: Kr (Guest)
Posted on:

Rate this post:
useful
not useful
I'm not sure if the problems that Katie and some others are reporting in 
this thread are the exact the same issue that we are all discussing 
about.

It is easy to confuse bad display resolution issue with the 
ghosting/fuzziness problem. If you need to drive really large resolution 
like 2440x1560 you need display port/mini-display/Dual Link DVI adapter, 
HDMI/SVGA adapters won't cut it and display wont look sharp with it

The original thread here is about Retina Macbook Pro models driving 
external display with 2440x1560 resolution or higher having two set of 
issues
1) Fuzziness/Ghosting issue on Dell U2713H/HM models
2) Macbook pro recognizing the external display as TV and hence using 
YCbCr instead of RGB mode.

AFAICT, Andreas script only forces RGB mode I don't think it solves the 
display quality problem, atleast not on my Dell U2713H.

FWIW, I removed the display override, tried the Apple Mini DisplayPort 
to Dual-Link DVI adapter to see if it improves the display, it doesn't. 
With Dual Link DVI adapter I do get the RGB mode automatically without 
the override but the display is bad to my eyes and My comparison here is 
the Apple Thunderbolt Display.

I have decided to return the dual LINK DVI adapter, and switch back to 
mini display port adapter. Now I'm not even using the YCbCr override, 
but adjusted the monitor settings (Uniformity Compensation Off, Smar 
Video Enhance off, sharpness set to zero) to get the same display 
quality.

Author: Adrian (Guest)
Posted on:

Rate this post:
useful
not useful
Thanks so much!

This worked for me. I updated my macbook pro retina to 10.8.3 which 
still didnt work.

So downloaded the U2713H override and copied into the folder as stated, 
rebooted and perfect!

New dell ultrasharp u2713h working as it should.

Author: CC (Guest)
Posted on:

Rate this post:
useful
not useful
Hi all,
I am a mac newbie and I am about ready to take it back due to this hdmi 
monitor thing (I have one more day to figure this problem out before I 
can take it back).  I have good color on it, and have downloaded OS X 
10.8.3.  Pictures, etc., look decent, but all text is still blurry. I 
have spent a couple of hours trying to get the display right...still 
nothing.  I am running hdmi-hdmi from my late 2012 mac mini (which I 
have read on other forums that this script works for).  My problem is, I 
don't understand mac coding and I can't get the script to run.  I 
download the script from above by saving the link to downloads.  I then 
open terminal, type in "ruby patch-edid.rb" and the only response I get 
is "command not found".  The process sounds simple as everyone says you 
just type that into the Terminal and a new folder will be created which 
you can then move to systems/library/displays/overide.  Is there 
something I am not doing right?  I really appreciate your help as I 
really like the new mac mini and want to keep it.

Author: TheLuggage (Guest)
Posted on:

Rate this post:
useful
not useful
Hi,

Andreas - you are a genius. Many thanks.

Your script worked fine for my HP LP2475w - I've been searching for a 
fix for ages.

Author: ezz500 (Guest)
Posted on:

Rate this post:
useful
not useful
Apologies for the dum questions, I just came over to MAC OS with the 
purchase of a iMac 27.  I have a dell U2410 attached as a second monitor 
via mini-display to display port. Actually, the colors on the Dell seem 
fine, my problem is text.

Regarding the code you posted as universal fix for forcing external 
monitors to RGB: 1) What kind of file should I copy the code into 2) 
What should I name the file 3) where should I save it in order to run it 
3) How do I run it?

I tried copying the code into apple script editor and running it that 
way, but I get syntax errors.  I also tried just saving into a text file 
called patch-edid.rb and running from terminal, no joy.

Thanks for your help

Author: MacUser (Guest)
Posted on:

Rate this post:
useful
not useful
Hi Andreas,

I use the U2713HM with a MBPr and have a problem with the screen 
flickering completely when scrolling certain websites (fine patterns 
seem to cause this behaviour, play.google.com is such an example, looks 
like a signal processing artefact). My display is also detected as a TV.

I'd like to apply your fix (thanks a lot for sharing your expertise!!!), 
but I use the DP audio output. As you fix removes some extensions, audio 
seems to be broken afterwards.

Is there a way to fix that problem without disabling DP audio?

Thanks in advance!

Author: MacUser (Guest)
Posted on:

Rate this post:
useful
not useful
Update: Applied the fix, DP audio still works.

Author: MacUser (Guest)
Posted on:

Rate this post:
useful
not useful
Update2: RGB works now, but annoying flickering with certain websites 
persists.

Author: Rocky (Guest)
Posted on:

Rate this post:
useful
not useful
Does anyone know if this fix is necessary/works with OSX 10.6.8?

Author: mark (Guest)
Posted on:

Rate this post:
useful
not useful
I have a new 27 inch iMac (2013 spec) on 10.8.3 and a Dell U2713H second 
monitor. I got the mini displayport to display port cable - and the Dell 
picture is clear at full 2500x1440 resolution BUT - the picture looks 
washed out and I cant get the same color balance as the apple.  I am not 
sure if this is just a difference in displays - or is the issue 
discussed in this thread:   When I go through the Dell screen settings - 
if I turn it to RGB - it goes awful - completely NG - so does that mean 
it is receiving YCbCr?
I then tried to follow instructions on this thread but am not familiar 
with terminal etc...

I downloaded "U2713H_U2713HM_Mac_EDID_override.zip" and put it on 
desktop
I opened them both and choose the one with U2713HM in it (and deleted 
the other)
I opened terminal and typed  "ruby patch-edid.rb".
But this came up with an error message ?

So I am stuck - but would greatly appreciate any help :)

Author: Brian Wilson (onthequiet)
Posted on:

Rate this post:
useful
not useful
Thanks for this very useful post Andreas!

I have a U2713h with Macbook Pro Retina 15 2012. The file 
U2713H_U2713HM_Mac_EDID_override.zip fixed the display and made it 
perfect.

I do not have audio out though (I'm using a Startech Mini-Display to 
Display cable).

Just wondering if the file at the very top of this post has been fixed 
to allow audio (ie. U2713H_U2713HM_Mac_EDID_override.zip) or is it the 
other script: patch-edid.rb  ?

Thanks,

/Brian

Author: Dom (Guest)
Posted on:

Rate this post:
useful
not useful
Hi Andreas -

I have the U2713HM, which I have just had replaced due to the following 
issues:

- faint diagonal lines across the whole screen
- image noise when moving windows/scrolling pages
- strange flicker across whole screen if an image on my screen changes 
brightness quickly

The replacement monitor is suffering from the same problems.

I have tried using the Override files you provided but cant tell if this 
has changed anything. How do I see what colour space the monitor is 
using? I have gone into the monitors settings and it appears it is using 
YCbCr. But if I change that to RGB, the screen has a green and red tint 
applied.

The screen is connected to my Macbook Pro Retina via Mini DP to DP.

Any help much appreciated as this is driving me crazy and would really 
like not to have to send it back to Amazon again!

Thanks!

Dom

Author: OnTheQuiet (Guest)
Posted on:

Rate this post:
useful
not useful
Hi Dom,

You can't change it manually: screen goes crazy if you do - I have the 
same setup exactly except I have the H instead of the HM.

You can use either the file at the very top of this page or the script a 
little way down. Either way should leave it that when you look at your 
monitor's settings, it will display RGB (after a reboot). After applying 
the script it should leave it perfect!

Author: Pierre C. (pierre_c)
Posted on:

Rate this post:
useful
not useful
Just thought I'd document my experience with this issue for others that 
may be searching a fix. I'm a photographer running a Macbook Pro Retina 
with an external DELL U2311H monitor for image editing.
Needless to say, suddenly discovering that the Macbook was outputting 
YPbPr only has been a huge frustration to me.
I can confirm that this fix works correctly with the U2311H monitor and 
doesn't interfere with Datacolor calibration.
A huge thanks to Andreas for creating and posting the script. Also to 
Matthew for laying it down in simple steps...
http://ireckon.net/2013/03/force-rgb-mode-in-mac-o...
...for the less tech savvy among us.

Author: Gabriel Alves (Company: Uso Pessoal) (gabrielcardial)
Posted on:
Attached files:

Rate this post:
useful
not useful
Hello Andreas, my name is Gabriel and I live in Brazil.

I bought a Dell U2413 to use with a Macbook Pro Retina 15 ", but the 
image is too bad, because the the Mac sends YPbPr signal to the monitor. 
Forcing the menu to RGB image turns green and pink.

I executed your script only using the monitor (macbook closed), using a 
mouse and wireless keyboard, but nothing happens. What am I doing wrong?

I'm stupid and I must have done something wrong. What should I do?

Look the screenshot on Terminal in attached.

Thank you and sorry for my bad english.

Author: Gabriel Alves (Company: Uso Pessoal) (gabrielcardial)
Posted on:

Rate this post:
useful
not useful
I did it! Had forgotten to copy the folder in the correct directory!

Thank Andrews!

Author: DERYK (Guest)
Posted on:

Rate this post:
useful
not useful
Using MBR with 10.8.3 and Dell U2713HM
I extracted the U2713H_U2713HM_Mac_EDID_override.zip and moved the 
contained folder into /System/Library/Displays/Overrides

I restarted the notebook with the connected U2713HM but this monitor 
stays black. Nothing to see… :-(

What I'am doing wrong?

Author: DERYK (Guest)
Posted on:

Rate this post:
useful
not useful
OK, found the problem - my mistake. You have to set the Input Source at 
the monitor to DisplayPort manually... now it works perfect... thx 
Andreas :-)

Author: BugRoger (Guest)
Posted on:
Attached files:

Rate this post:
useful
not useful
I had to slightly modify the script for it to work with a Dell U3014. 
The EDID was cut off without an additionally "-w 0" parameter to the 
ioreg command.

Attached the updated script. Thanks. Works perfectly now :)

Author: Paul Cryer (Guest)
Posted on:

Rate this post:
useful
not useful
I've got the U241§3 on the non Retina Macbook Pro 2012 model and had 
loads of the issues most people mentioning. Colour being off, not 
looking sharp, basically looking worst than a cheap monitor! Thanks you 
so much for this, the script works perfect and the monitor now looks 
great.

Author: Bruno (Guest)
Posted on:

Rate this post:
useful
not useful
This script doesn't seem to work with an hp pavilion 23bw. can you help 
on this one?

Thanks

Author: Dominic (Guest)
Posted on:

Rate this post:
useful
not useful
YES YES YES! Worked a treat - shame it doesnt get rid of the ghosting on 
my DELL U2713H!

Thanks so much!

Author: tomo (Guest)
Posted on:

Rate this post:
useful
not useful
I'm executing script only with external monitor and got this

/System/Library/Displays/Overrides/patch-edid.rb:9: undefined method 
`[]' for nil:NilClass (NoMethodError)

what I'm doing bad?

Author: Sergey Bulychev (Guest)
Posted on:

Rate this post:
useful
not useful
Thank you so much for your solution. I was sick and tired with DELL 
U2713H changing settings on its own when connected to mac as a secondary 
display.
It was so frustrating to work with photographs in Adobe Lightroom and 
not seeing consistant color and tone, because display was tweeking it 
self for some reason.
I was going to sell it and get another one...
I did as you advised and now it doesn't tweek the color and tone and 
works consistently.

Thank you for your effort to figure this issue out and sharing it with 
the rest of the world. Appreciate it a lot!

Sergey.

Author: Karen Hartman (Company: BAH) (khartman)
Posted on:

Rate this post:
useful
not useful
Hi,

I am also getting the error mentioned above while running the script:
undefined method `[]' for nil:NilClass (NoMethodError)

I followed the advice here to change line 7 and it still didn't work:
http://ireckon.net/2013/03/force-rgb-mode-in-mac-o...

Any thoughts?

Thanks,
Karen

Author: Slvrscoobie (Guest)
Posted on:

Rate this post:
useful
not useful
I have an older 2011 MBP with thunderbolt, and a Dell U2713HM.
Currently connected via a mini -> display port, I dont see too much of a 
problem other than the dell looks vastly less sharp than I would expect 
for such a high res monitor even at 2560x1440. (Sharpness has to be ~75 
to look decent, any higher and I get halos, lower and it looks scaled)
Would this 'hack' help me? Most of the replys are from retnia based 
MBPs.

Author: Rodrigo (Guest)
Posted on:

Rate this post:
useful
not useful
If I don't want to remove the extensions block, should I delete the 
following lines from your script?

puts "Number of extension blocks: #{bytes[126]}"
puts "removing extension block"
bytes = bytes[0..127]
bytes[126] = 0

bytes[127] = (0x100-(bytes[0..126].reduce(:+) % 256)) % 256


Is this correct? Will the checksum be recalculated correctly?

Author: Ryan (Guest)
Posted on:

Rate this post:
useful
not useful
The script that was supposed to work on various models worked fine for 
me on the u3011, with the new u2413 I cannot get it to work properly. 
The sharpness and image is fixed but when editing in Premiere there is a 
purple box the fills the area that the video is being played. As soon as 
I stop playback it returns to normal. Sometimes I have a large purple 
box overlaying the screen thats about 80% the size of my screen. Tried 
for a screenshot, but this is caused by the monitor.

Author: Ryan (Guest)
Posted on:
Attached files:

Rate this post:
useful
not useful
Videos I play in the browser also do this. Notice the overlay on just 
the video, it extends past the player slightly.

Reply

Entering an e-mail address is optional. If you want to receive reply notifications by e-mail, please log in.

Rules — please read before posting

  • Post long source code as attachment, not in the text
  • Posting advertisements is forbidden.

Formatting options

  • [c]C code[/c]
  • [avrasm]AVR assembler code[/avrasm]
  • [code]code in other languages, ASCII drawings[/code]
  • [math]formula (LaTeX syntax)[/math]






webmaster@embdev.netContactAdvertising on EmbDev.net