*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-unbeatable-performance-out-of-the-box/3, 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_identification_data) 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.
:
Andreas, thanks again for assisting with this same process on the u2713HM. Works great.
Hi Andreas, could you upload the file for the HM version as well? Thanks!
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.
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.
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!
Hi, Andreas, Could you please help me to solve this problem for dell u2711 ? Thank you very much
Try running the attached script. Open Terminal and enter "ruby patch-edid.rb". This should give you an override file for your display.
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
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.
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.
You need to run the script while (only) the external display is connected.
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
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
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.
When in RGB mode, set sharpness to 50, this seems to disable any processing. Otherwise the image is blurred or sharpened.
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.
@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
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 :(
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
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=
The only difference is the serial number (different for each display) and the checksum, so it doesn't matter.
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.
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-os-x-to-fix-the-picture-quality-of-an-external-monitor
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.
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.
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.
Oh, I thought that unless you had the same monitor these would be different files.
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.
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
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
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.
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!
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.
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 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.
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.
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.
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.
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.
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
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!
Update: Applied the fix, DP audio still works.
Update2: RGB works now, but annoying flickering with certain websites persists.
Does anyone know if this fix is necessary/works with OSX 10.6.8?
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 :)
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
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
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!
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-os-x-to-fix-the-picture-quality-of-an-external-monitor ...for the less tech savvy among us.
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.
I did it! Had forgotten to copy the folder in the correct directory! Thank Andrews!
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?
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 :-)
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 :)
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.
This script doesn't seem to work with an hp pavilion 23bw. can you help on this one? Thanks
YES YES YES! Worked a treat - shame it doesnt get rid of the ghosting on my DELL U2713H! Thanks so much!
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?
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.
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-os-x-to-fix-the-picture-quality-of-an-external-monitor Any thoughts? Thanks, Karen
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.
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?
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.
Videos I play in the browser also do this. Notice the overlay on just the video, it extends past the player slightly.
I was just about to post the same issue as Ryan - overlay on video players. But had a one last look in the settings and found that turning off Smart Video Enhance gets rid of the overlay. See attachment
great thread... just a heads-up re: mbp retina and U2713HM... Somehow my 2 U2713HMs just fried! The monitors now have 'image burn-in' even after disconnecting the displayport cables, powering down for 5 minutes and powering back up. Found a post on the dell site with another mbp user having similar/same issue. http://en.community.dell.com/support-forums/peripherals/f/3529/t/19495965.aspx Not being an alarmist just a heads-up. Wondered if it could be related to this thread (color mode driving the monitor). I'm off to sort out if there is a factory reset and see what's what. I also had some trouble getting the 2nd monitor to work initially. At first, not detected at all. Then detected (showed up under Displays) but was a blank screen. After unplugging everything, re-plugging and rebooting the mbp the 2nd monitor started working and continued to work until today (4 whole days).
Works great! I noticed my problem but did not know how to solve it. Your solution came to rescue nicely. Thanks
Thanks to GabrielMichael. I too fixed the problem with the display override profile, but was getting the light blue overlay on video content in the browser in OSX 10.8.3 on a rMBP, connected via a cheap mini-DisplayPort to DisplayPort cable. This was fixed, as GabrielMichael says, but turning off Smart Video Enhance. Everything now looks great. Thanks! :-)
Andreas - A newbie question. I have a MacMini with OSX 10.7.5 and want to configure per your script with Dell U2410 to eliminate fuzziness. My questions: 1) Will the script allow the HDMI connection to work, or just DVI, or both? 2) I got the U2410 primarily for photo editing and want to color calibrate it with Spyder4Pro. Will the Spyder4Pro software conflict or limit your script for fuzziness? Thank you!
Hi everyone i have an imac 21.5" and just baught a Dell U2913wm monitor and have the YCbCr issue. i have followed the steps andreas has given and the terminal has created the new folder correctly but i dont have the Displays folder in my library my OS X is in french but there is not such folder or similar folder in the library folder thanks in advance for your help
Hi, I am a MacPro 2009 / Ati HD4870 user looking for a 24"-27" screen to properly work in Adobe RGB gamut. I found this web page looking for info to find a good screen for CGI games and films modelling, worried because of the 8bit (not 10bit) framerate output signal of apple machines. I actually haven't decided any monitor yet, so I don't own any U2713H/HM monitor. Anyway I just wanted to thankyou for making fixes and sharing them with other people, even when some brands which make and sell screens or workstations don't. THANKYOU Andreas Schwarz
update... The 'burnt-in images' dissapated over the course of 5-6 hours. Monitors seem ok now. I found several other references to similar issues with the monitors.
Hi, I am also getting the error mentioned above while running the script: warning: Insecure world writable dir /usr/local in PATH, mode 040777 patch-edid.rb:9: undefined method `[]' for nil:NilClass (NoMethodError) Any Idea? Thanks Oriol
Same error, with my MacBook Air with Lion, and with my MacBook Pro with Mountain Lion... MBAir:Downloads israel$ ruby patch-edid.rb patch-edid.rb:26: undefined method `[]' for nil:NilClass (NoMethodError) Any other option, in other language? I am developer, but zero idea about Ruby, and I can not translate this script to another language...
I have seen why the script gives this error: 202:Downloads israel$ ruby patch-edid.rb patch-edid.rb:26: undefined method `[]' for nil:NilClass (NoMethodError) It's because the "ioreg" command gives its output truncated: +-o AppleDisplay <class AppleDisplay, id 0x100000407, registered, matched, active, busy 0 (2 ms), retain 7> { ... "DisplayProductID" = 22192 "IODisplayEDID" = <00ffffffffffff001e6db0565a38000002130103082f1e78eaaec5a2574a9c25125054a 76b80950f95008180814071$ ... "DisplayVendorID" = 7789 ... } The IODisplayEDID is truncated and has not all the characters it should. It finishes with a $ symbol, not with >. How can I got all the output from this command? Why is it truncating this line?
I updated the script with the change suggested by BugRoger to prevent truncated lines. Please download and try again. http://embdev.net/attachment/168316/patch-edid.rb
So here is an interesting thing I found. I recently purchased a Dell U2713H, and while it worked fine, recently it started going into 1080p mode only. This frustrated me quite a bit, and below are my learnings (how I fixed it). My setup: Macbook Pro Retina 2013 model (two minidisplay ports) Old Apple Cinema Display ADC - Plastic Shell (1600x1024) Dell U2713HM 27" See attached image how I have the graphic hooked up. The Acell cable is for the Dell, the other for the Cinema Display. I tried everything, holding down Option and clicking on "Scaled" in displays, restarting, running funky scripts, connecting only one screen etc. Nothing worked, although it did work at first. Then... THEN!! I accidentally switched MiniDisplay ports. I put Dell's cable where the Cinema was plugged in and vice versa. Presto!! It worked! Now it works right every time, in-sync with the on/off of the rMBP's screen, and when I tried to switch them around (just to test) I was experiencing the problem again. Hope this helps!
Would somebody mind clarifying for me whether it's in fact necessary to run a script? I've simply dragged and dropped the files into the specified directory and now see Dell U2713HM EDID override in System Preferences following reboot. Is that it?
I have just received my DELL U2713HM screen today and connected it up to my 27" iMac using the supplied DVI-D cable and Thunderbolt to DVI connector. I am happy with the colours on the Dell monitor, but my problem is that the Dell does not want to go up to max resolution of 2560x1440 to match my iMac's resolution. Can you point me in the right direction for a solution.
I have the same question related to monitor calibration posted by "Nolan Snook". Using this EDID override, is color calibration still possible with i1Display Pro, Spyder, Lacie and etc? I mainly work with images, so I need the colors to be accurate.
Chase wrote: > Is that it? Yes, that's it. Disgruntled Apple User wrote: > Using this EDID override, is color calibration still possible with > i1Display Pro, Spyder, Lacie and etc? Yes, it has absolutely no effect on color calibration. Mike wrote: > I have just received my DELL U2713HM screen today and connected it up to > my 27" iMac using the supplied DVI-D cable and Thunderbolt to DVI > connector. > I am happy with the colours on the Dell monitor, but my problem is that > the Dell does not want to go up to max resolution of 2560x1440 to match > my iMac's resolution. You are probably using a Single Channel DVI converter or cable, which does not allow the full resolution. Use a (Mini)Displayport cable.
Andreas, thank you so much for providing this fix. I've been searching for a fix for over a year now as I've been plagued by the YPbPr problem with my Dell U3011. Your UPDATE at the start of this thread worked perfectly once I figured out how to run the ruby script inside terminal and where to put the finished file. When calibrating with my Spyder 4 Elite, I now get 95% Adobe 1998 RGB. Fantastic!! Ryan L, if you're still looking for a fix this update worked pefectly with my Dell U3011. (*UPDATE*: see here for a universal fix that works for all monitors: http://embdev.net/topic/284710#3027030 Ryan L wrote: > 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.
I feel like an idiot, as this patch seems to be working for most people. I am unfamiliar with linux and have rarely opened the terminal on my mac. Could someone explain in english (as though they were explaining this to a child) how to use the patch to force my macbook retina to rgb? I opened my terminal and pasted in "ruby patch-edid.rb" but nothing happens. I am also unsure how to get to my home directory via terminal. And then once I do, do I copy and past this code into the terminal? So confused, sorry. Hope someone can help. Thanks.
1 | require 'base64' |
2 | |
3 | data=`ioreg -l -w0 -d0 -r -c AppleDisplay` |
4 | |
5 | edid_hex=data.match(/IODisplayEDID.*?<([a-z0-9]+)>/i)[1] |
6 | vendorid=data.match(/DisplayVendorID.*?([0-9]+)/i)[1].to_i |
7 | productid=data.match(/DisplayProductID.*?([0-9]+)/i)[1].to_i |
8 | |
9 | puts "found display: vendorid #{vendorid}, productid #{productid}, EDID:\n#{edid_hex}" |
10 | |
11 | bytes=edid_hex.scan(/../).map{|x|Integer("0x#{x}")}.flatten |
12 | |
13 | puts "Setting color support to RGB 4:4:4 only" |
14 | bytes[24] &= ~(0b11000) |
15 | |
16 | puts "Number of extension blocks: #{bytes[126]}" |
17 | puts "removing extension block" |
18 | bytes = bytes[0..127] |
19 | bytes[126] = 0 |
20 | |
21 | bytes[127] = (0x100-(bytes[0..126].reduce(:+) % 256)) % 256 |
22 | puts
|
23 | puts "Recalculated checksum: 0x%x" % bytes[127] |
24 | puts "new EDID:\n#{bytes.map{|b|"%02X"%b}.join}" |
25 | |
26 | Dir.mkdir("DisplayVendorID-%x" % vendorid) rescue nil |
27 | f = File.open("DisplayVendorID-%x/DisplayProductID-%x" % [vendorid, productid], 'w') |
28 | f.write '<?xml version="1.0" encoding="UTF-8"?> |
29 | <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
|
30 | <plist version="1.0">'
|
31 | f.write " |
32 | <dict>
|
33 | <key>DisplayProductName</key>
|
34 | <string>Display with forced RGB mode (EDID override)</string>
|
35 | <key>IODisplayEDID</key>
|
36 | <data>#{Base64.encode64(bytes.pack('C*'))}</data> |
37 | <key>DisplayVendorID</key>
|
38 | <integer>#{vendorid}</integer> |
39 | <key>DisplayProductID</key>
|
40 | <integer>#{productid}</integer> |
41 | </dict>
|
42 | </plist>"
|
43 | f.close |
Andreas Schwarz wrote: > You are probably using a Single Channel DVI converter or cable, which > does not allow the full resolution. Use a (Mini)Displayport cable. Thanks Andreas: You were absolutely right. I bought a Mini-Displayport to Displayport cable and now have full 2560x1440 resolution. Yay! Appreciate the help.
Try this Aunt Lucy 1. Open terminal and type in pwd This will tell you what your present working directory is and you should see something like /Users/AuntLucy 2. Open a Finder window and move or copy the patch-edid.rb file from wherever your browser downloaded the file into the the /Users/AuntLucy folder. 3. Back in Terminal, enter "ruby patch-edid.rb". This will create an override file for your display which you will now see in your finder window. It's called DisplayVendorID-10ac 4. Move or copy this folder to /System/Library/Displays/Overrides 5. Restart your machine
Huzzah! Thanks very much for writing this. It's like coming out of a discoloured fog and it also as a side-effect solved a problem I was having where it liked forcing my U2711 into 1080p instead of native res over DisplayPort.
Ah, now it's working. Actually the script didn't work in the terminal until I rebooted the machine first. Thanks again!
Thanks Andreas, can not believe that any computing display device does not default to RGB.
When I enter the "ruby patch-edid.rb" in Terminal nothing happens. What can be the reason for that? My screen still is pink when I change to RGB mode.
In my MBP 2012 with 2713h works your hack like a champ!! Thanks!!!!!
THANK YOU!!! This is tremendously useful. My Dell U2713H was working fine connected to my MacBook Retina, then one day it started showing up as a TV and I couldn't get native resolution. Your fix works like a champ!
Hi Andreas, I use Macbook Pro early 2011 with 10.8.4 Before running script, incoming signal was YCbCr. After I have tried above method, my Dell 2713H completely does not work(blank monitor) with miniDP - DP. However, it's still working DVI-D to HDMI(to miniDP), but with 1920-1080 res. Monitor shows: There is no signal coming from your computer... However, when I tried with MacBook Pro 2009 with 10.8.4 and its absolutely perfectly working with RGB!!! I have no idea, what happened with my MacBook Pro 2011. I have even re-installed whole Mac OS, but problem still exist. Any suggestions? Many thanks!
Andreas Schwarz wrote: > Try running the attached script. Open Terminal and enter "ruby > patch-edid.rb". This should give you an override file for your display. I've clicked this link and it only takes me to another window showing me the script, rather than downloading it. Do you have any idea why this is happening. Could the DL link be dead or something? I really want to fix my monitor issues but it's not letting me. Thanks
This is a great forum thanks everyone, I have a Samsung syncmaster s23b350 I have tried to follow the instructions above coping the file patch edid.rb above into system/library/display/overrides but it didn't work I will really appreciate any help as atm I'm doing assignment and getting blind. Thanks in advance
#update. My problem was in display version 1.2 I changed back to 1.1 and it's working perfectly.
MacUser wrote: > Update2: RGB works now, but annoying flickering with certain > websites > persists. I have the same problem (Dell U2713HM), certain websites with patterned backgrounds causing the display to flicker something terrible (causing migraines), even after the tab for the site(s) has been closed, flicker continues for up to 3 hours afterwards! Before this thread, I was thinking it was a gfx memory problem on my 2012 21.5 iMac Any ideas would be greatly appreciated. Many thanks.
Hi, I am trying to create this override folder for an LG monitor (27ea83), however 1. Chrome wouldn't let me download the file, just opens it as a link, so I have to paste the code into TextEdit then save it as .rtf then rename the file and click use as .rb 2. though the file is in the right folder, when I run the command in terminal it gives me the following error: patch-edid.rb:1: syntax error, unexpected $undefined, expecting '}' {\rtf1\ansi\ansicpg1252\cocoartf1187\cocoasubrtf390 I looked through the code but all { seem to have a }, so I don't quite understand what the issue is. Also, I am completely illiterate when it comes to linux, so not the slightest clue as to what I'm trying to do which makes debugging ever so difficult :) Anyone any thoughts? Is the script being screwed up by me having to save it as rtf first? PS. Andreas, thanks a million for the DELL files, they worked like a charm!!! <rant on> until I had to return one U2713H monitor after another whilst trying to decide which is the bigger pile of dung, DELL quality assurance or their atrocious customer service. A word of advice: don't buy DELL, especially if you're outside of the US, they just get your hopes up with truly amazing colours, then let you down in every other way imaginable. Amazon told me after the second return that they won't even bother replacing it, the whole batch is a waste of space, and that I should order straight from DELL, as they would have the latest versions, which might actually work. Not if I can help it, thank you. <rant off>
Hi. I'm not bright when it comes to running scripts but can you tell me exactly where to / how to run the script that you recommend to over-ride Mac display settings? I clicked on the link and it gave me a page of code - where do I put it before entering the command into the terminal? Really sorry for being a bit thick on the matter!
Fixed the problem with brand new Haswell Air and Dell U2410. Thanks a bunch! --Pasi
Hi, I'm experiencing the same problem with 15" Macbook pro Retina and Dell U2312HM. I've tried the script but the problem remains. Do I need to change something in the script for it to work? thanks!
I'm also using a DELL U2312hm monitor with rMBP15" and applied the script, copied the new folder and chose it in the Color tab under display (in preferences). I'm not sure there's a big difference, the text on Google results is a bit blurry (my eyes are tired after a few minutes of reading). does anyone else experiencing the same? attached: print screen (example) the script output file Please help me.
This fixed the horrible sharpness/haloing I had with my U2913WM when used with my Retina MBP. Thank you so much!
Sam wrote: > Hi, > > I'm experiencing the same problem with 15" Macbook pro Retina and Dell > U2312HM. > I've tried the script but the problem remains. > > Do I need to change something in the script for it to work? > > thanks! You have to run the script, which generated a folder in the same directory it was run from. Then move the folder to /System/Library/Displays/Overrides
Jayphen S. wrote: > Sam wrote: >> Hi, >> >> I'm experiencing the same problem with 15" Macbook pro Retina and Dell >> U2312HM. >> I've tried the script but the problem remains. >> >> Do I need to change something in the script for it to work? >> >> thanks! > > You have to run the script, which generated a folder in the same > directory it was run from. Then move the folder to > /System/Library/Displays/Overrides I've tried it, the fonts on the external display are still very blurry (unless I enlarge the font size by 150%). I've bought a mini display port to display port cable which didn't help either. I'm using U2312hm display, on a windows VM (runs on the rMBP) the fonts are sharp and clear. what can I do?
I've just discovered this thread, as I'm having a similar problem with my HP 22" HDMI monitor. Local Apple store folks spent a total of 2 1/2 hours fiddling and I'm still seeing blurred text on the monitor when connected to my new MacBookPro. The monitor worked fine with my old white Macbook. Main question I have for this list--which I saw raised above, but not answered--is if this fix works with HDMI as well as DVI?
Hi, not trying to derail the thread, but you guys are closest to a solution to my related problem, so maybe you could help. My problem is actually the inverse: my 2010 MBP decides to output full range RGB even though it correctly identifies my TV as a TV, provides overscan slider etc. My TV is capable of reproducing full range RGB and probably correctly advertises this in the EDID. As I have connected multiple devices through an AVR, some of which only output limited range/ycbcr I would however like the Mac to output ycbcr as well. (My gf's MBA running the same version of OSX (10.8.4) outputs ycbcr/limited range btw) What would I need to change in the script to inverse its behaviour, forcing ycbcr output? (I read up on EDID a little bit and think I should set bits 4-3 of byte 24 to "10" but I am neither sure about that, nor how to convert that to the encoding used in the plist nor if I would have to change anything else in order to not break things.) Any help would be highly appreciated!
I just wanted to thank you for making this file available, it's made quite a difference to my dell u2713h display, everything is that more crisp. Again, thank you Patrick
> I've tried it, the fonts on the external display are still very blurry > (unless I enlarge the font size by 150%). > > I've bought a mini display port to display port cable which didn't help > either. > > I'm using U2312hm display, on a windows VM (runs on the rMBP) the fonts > are sharp and clear. > > what can I do? Please, Help!
Hi, Thanks very much for posting this script. I have a Dell U2711 with a 2012 Retina Macbook Pro. I haven't ever noticed any visual/image problems like some people have regarding blurry text or wake for sleep issues but I have always noticed the YPbPr issue. I noticed this script however disables support for audio over the displayport for the monitors, I wondered if it is possible to remove this feature from the script since I do require displayport audio to hook my U2711 up to my external speakers. Thank you very much for this solution. Also I haven't upgraded to 10.8.4 yet, does anyone know if there was an official fix applied?
Alex wrote: > I noticed this script however disables support for audio over the > displayport for the monitors, I wondered if it is possible to remove > this feature from the script since I do require displayport audio to > hook my U2711 up to my external speakers. Try the following steps: 1. remove the existing override file and reboot 2. remove the following lines from the script and run it again:
1 | puts "removing extension block" |
2 | bytes = bytes[0..127] |
3 | bytes[126] = 0 |
4. install the new override file and reboot Please tell me if this has the desired effect.
Hi Andreas, Apologies, I did not fully test the script before posting that reply. I found my audio works fine over Displayport still without modifying the script. It seems to be working fine, I've definitely noticed the change in certain colour's compared to over YPbPr previously. Also I can now use the sRGB feature of the monitor which previously never worked for me on YPbPr. My only question is are there any other 'side effects' from using this script since it has removed extension blocks? Also I ran this script when I had my setup in multiple display mode, the U2711 was my primary display though so I assumed it would pick up the primary display which it has done, does this matter? Thanks again
Hi Andreas, I'm having a different issue that will require the same solution, I fear. I'm attempting to connect a 2009 MBP to an older Mitsubishi projection HDTV via MDP to DVI, OS 10.8.6 keeps forcing the color space to RGB, the TV takes YPrPb DVI signals. I was fiddling around with the code for your patch and I think I only have to change the line that refers to forcing the EDID in to RGB, I'm not exactly a software developer and was wondering if you could direct me on how to convince this Mac to do the opposite of what does for Dell monitor owners? Thanks, Kevin
Try these lines:
1 | puts "Setting color support to RGB+YCbCr" |
2 | bytes[24] |= 0b11000 |
Disabling RGB completely is not possible in EDID, so I'm not sure if this is enough to make OS X use YCbCr. Maybe you need to fiddle something with the EDID extension blocks.
Hello again, I wanted to confirm to anyone searching that the script provided on here (at http://embdev.net/topic/284710#3027030) works like a charm for the Dell U2711. I have been using it for a few weeks now. I did not need to modify anything. It correctly forces my Retina Macbook Pro to use RGB for the display over Displayport instead of YPbPr. This now allows me to use the monitors sRGB feature (which never seemed to work right on YPbPr). I have not noticed any other side effects. Sound over displayport works fine and there has been no issues with waking (I didn't have any before though). I also saw some people mentioning way above about the display having ghosting. Unfortunately this seems to be a downside of the DellU2711 and it does this with whatever it is plugged into (windows, mac, HDMI source etc.). Thanks again for your script. It has saved a lot of my time and has prevented me from buying additional things to fix it, since I do a lot of photography, graphic and web design, colour accuracy is important for me. I would recommended that anyone using a Dell display with a Thunderbolt Macbook downloads this script! Thanks Alex
Thank you Sir! You saved me from having a heart attack.
I'm having a similar problem with EDID and I'm not sure if this will help fix the problem, maybe you can shed some light. Number of Mac Mini's MBP (4 total). Using "Display Port" to VGA adapters IO Gear KVM - "VGA" in/out. My problem is that on my main Mac mini, a mid-2011 which actually uses Thunderbolt instead of a Mini Display port, won't read the EDID of the monitor though the KVM. IOGEAR recognizes the issue, but won't fix it but "recommends" a KVM that is 4 times more expensive. My work around is: 1) Boot Mac mini which shows the right resolution, but it is shifted 4 inches to the right. Detect displays comes back with unknown. 2) Unplug VGA from KVM and put it directly into Mac Mini adapter, Detect displays correctly identifies HP2509 monitor, the image centers on the display. 3) Plug Mini back through KVM everything is good. 4) Turn off sleep and enable screen saver, so it never sleeps - it never loses EDID. An older MacMini, older MBP, mid-2012 MBP don't have any problem recognizing the monitor through the KVM. I've tried swapping adapters, cables, ports but just can't get it to work. I'm hoping I can grab the correct EDID and use the Override to force it to HP2509 when it doesn't think there is anything attached. Thoughts?
Hi, I have MBP Retina 15" connected to Dell U2713H and at first it did not look good at all, especially, the text was fuzzy. For a second I thought I had done a bad deal. I first started out with a HDMI cable that I quickly found out only gives 1080 res. Then the Display Port to Mini display port that came with the screen. Still no result. Probably, it would work with the settings below but I haven't tried it. After that I bought a Mini display port to mini display port cable (11€). Still no result. But I left the cable MDP-MDP and started playing around with the settings and now it looks rather decent: Sharpness: 0 Preset Mode: Paper Brightness: 55 Contrast: 60 Input Color Format: YPbPr Gamma: MAC Color Preferences in MAC: Dell U2713H (LCD Color looks ok too but I prefer Dell). I did not use the script but it looks really good after changing the settings.
After watching hi-res images in Photoshop I changed the settings to: Sharpness: 0 Preset Mode: Color Space => CAL1 Brightness: 50 Contrast: 50 Input Color Format: YPbPr Gamma: MAC And now images, videos and text looks great!
Hi Andreas, first thanks for your support... I run the script and tried to copy the generated folder into Library/Displays/... but I can´t see a Folder called Displays in my Library. Do you know why? What can I do?
I just bought a LG 27EA83R-D monitor and had the same problem. The script fixed it. You're awesome. Apple is a PITA. Thanks for creating a fix!
I am still having the blurry text. I tried everything mentioned in this forum, any help will be very much appreciated
On the U2713H you need to set sharpness to 50% and contrast to 50% to get a pixel-accurate display.
Hello I've tried doing this for the Dell U2711 on OSX 10.8.5 and the issue remains. I tried 3 different times. the screens still flickers at the native resolution 2560x1440 is there anything else I could try specs on the mac are: mac pro mid 2012 12 core version ATI 5779HD 1gb ram video card.
Hi there, Not sure if this will help, but I also had a flickering problem. Quite by chance, I was rearranging my desk and needed to change where things plugged in. I plugged the Dell in to a 'proper' surge protection socket (not a consumer cheap one) and when I switched everything back on the flickering had stopped. So I had a 'dirty' power supply or something. I still get some flickering on visiting certain webpages with fine textures, but 99% of my flickering display seems to have stemmed from the inadequate power supply. I hope this helps.
Sorry that's not the case. I've used different power cords and different outlets and power bars..
mg wrote: > I am still having the blurry text. I tried everything mentioned in this > forum, any help will be very much appreciated I experienced the same problem and adjusted the sharpness setting down to zero and now text is readable.
It turns out to be the cable I was using. I was using a generic canadacomputers.com cable at first and when I switched to a startech cable it started working flawlessly Thanks for all the help in this thread. It helped to weed out the possibilities
Thanks very much for posting this. I am running on MacMini and the EDID override solves my display problem completely. I am trying to get audio over the display port as well - is it possible to do a version with audio enabled? Thanks
Audio should actually still work (at least I can still see the DisplayPort audio device in the audio settings).
Hello Andreas and everyone who can help, I come across this forum as I have a similar problem with my Macbook Air and the Dell U2711 The graphics and the fonts are blurry . I use the external monitor for editing . I am novice with the scripting and making fixes you all discussing here . Could you please guide me trough what to do and what files to download as there is so many of them. What to do step by step after downloading the fix Please guide me trough Thank you in advance Jan
Do you guys know how to fix the blurry fonts problem on external display? fontsmoothing settings doesn't make it better. Does any of you have it too? using a win7 VM produces excellent display (fonts included), OSX doesn't. Thanks!
HI Andreas! Thanks for the awesome script, I have multiple dell u2711 monitors hooked up to my 15 macbook retina. Do you know if this works with multiple monitors? at this point I was only able to get one to work out with the script :( Any ideas? thanks a bunch!
HI there Can this script work with other monitors? I have a new LG 29EA93 running with a brand new Macbook Air (with the G500 GFX card) running at 2560 x 1080 IF you could help with a file for that you would be a bit of a hero to me! Andy
Andy Doyle wrote: > HI there > > Can this script work with other monitors? > > I have a new LG 29EA93 running with a brand new Macbook Air (with the > G500 GFX card) running at 2560 x 1080 > > IF you could help with a file for that you would be a bit of a hero to > me! > > Andy I did run the generic script above and it didnt work for me.
Hi Andreas, I have a mba 2012 and connect to U2713H at home and a "standard" monitor at work. In case I apply the fix script forcing RGB, which fixes the U2713H problem, will it cause a problem with the "standard" monitor? Thanks again Noam
I hope someone will be able to help my problem, blurry fonts on external display. http://apple.stackexchange.com/q/99020/55144
ah crap... with the new mavericks OS X upgrade, its batch, and this script doesn't work. The generated folder even when placed in the correct directory isn't picked up by OS X.
Just upgraded to Mavricks and it reverted to the old "television" color profile for my Monoprice 27. I just ran the script again and it worked great. Thanks!! Mavricks 10.9 2012 Macbook 15
I just installed mavericks and i can't reinstall the patch to fix this issue, error log: found display: vendorid 4268, productid 41004, EDID: 00ffffffffffff0010ac2ca0533437321012010380342078eab325ac5130b426105054a5 4b008180a940714f01010101010101010101283c80a070b023403020360007442100001a 000000ff004a55343336383447323734530a000000fc0044454c4c20323430385746500a 000000fd00384c1e5311000a202020202020013002031bf1489005040302071601230907 0765030c00100083010000023a801871382d40582c450007442100001e011d8018711c16 20582c250007442100009e011d007251d01e206e28550007442100001e8c0ad08a20e02d 10103e960007442100001800000000000000000000000000000000000000000000000000 00000047 Setting color support to RGB 4:4:4 only Number of extension blocks: 1 removing extension block Recalculated checksum: 0x39 new EDID: 00FFFFFFFFFFFF0010AC2CA0533437321012010380342078E2B325AC5130B426105054A5 4B008180A940714F01010101010101010101283C80A070B023403020360007442100001A 000000FF004A55343336383447323734530A000000FC0044454C4C20323430385746500A 000000FD00384C1E5311000A2020202020200039 patch-edid.rb:33:in `initialize': No such file or directory - DisplayVendorID-10ac/DisplayProductID-a02c (Errno::ENOENT) from patch-edid.rb:33:in `open' from patch-edid.rb:33:in `<main>' federicos-mini:Overrides abadfederico$
Just upgraded my 2010 MBA to Mavericks and I immediately thought, "the fonts look funny". Sure enough my EDID override file was gone and my U2713HM was in YPbPr rather than RGB mode. I was able to fix it by simply repeating the steps I had done earlier: copying the DisplayVendorID-10ac folder (which is in a zip file in the very first post in this thread) and placing it in /System/Library/Displays/Overrides. After a reboot, I was back in RGB mode. So at least for the U2713HM, the previous fix still works, but you have to do it again - Mavericks wiped out the old fix. - Mark
Installed Mavericks. Works fine after repatching. Thanks a lot for your patch!!!♥︎♥︎♥︎
just FYI, I was not able to get this to work with mavericks on a u3011, tried reusing the script with no luck
Dell U2713H no good after Mavericks upgrade and reapplying the file. Worked fine on Mountain Lion. :(
The script DID work for my U2413 after upgrading my 2011 MBP to Mavericks, just like on Mountain Lion.
the weird thing for me is after using the script, it is creating a profile but the monitor is still staying on a YCbCr colour space instead of RGB when I navigate through the monitor menus (dell u3011)
ok I think I managed to fix it. Reinstalled mavericks, I disconnected my second monitor (dell 3007WFP), then executed the ruby patch above. Afterwards, I copied it to system/library/displays then rebooted. The monitor was in RGB mode. Re-connected the dell 3007WFP. Rebooted. Monitor stayed in RGB mode. Color was still "off" however I selected the sRGB profile and it looked correct. Never had to select sRGB before... but at least it looks good now.
Just to be clear, here's the process on how I got it to work on Mavericks: 1. I reinstalled a clean OS. Not sure if required. 2. Disconnect all monitors except the one you want modified. 3. execute the ruby patch above. 4. Copy the resultant directory to system/library/displays/overrides/ 5. Reboot. 6. Ensure the new profile is being used, if the colours seem "off" use sRGB profile. The monitor will remain in RGB mode. 7. Reconnect additional monitors. I tested that the monitor remains in RGB even when it's disconnected/reconnected, and it seems to. So should be good to go....
Hey Guys, I have followed the instructions for the script here to get my new Dell S2740L 27" monitor to work properly with my new Mac Mini. The Ruby script seemed to execute nicely but where is the folder placed that it supposed to create? Is that put automatically under /Systems/Library/Displays/Overrides ? So far there appears to be no change even after reboot. Do I need to change something in the system settings under display profiles or something as well? Please advise cause the lack of crisp display is getting to my nervs. Thanks in advance Thomas
In my case of Mavericks upgrade, I have to remove the display profile and then the patch would work. otherwise, my external monitor is not recognized by my MBP. cd /Library/ColorSync/Profiles/Displays/ sudo rm DELL\ U2713H-F0416116-5694-ABA3-1ADB-6E3866AF2A94.icc
After upgrading to Mavericks, i just have to reapply the patch and it's working again. Many thanks for this very helpful solution.
Just dropping a note that placing the original attached files in the /Overrides directory worked for me on a Dell U2713 and a 15" retina MBP experiencing a resolution limit after upgrading to Mavericks. Previously it was running fine at 2560x1440, but the OS upgrade left it limited to 1920x1080 max. I don't see the ghosting that some discuss above, and I was able to dial the colors in nicely with a combination of hardware settings and a new custom Colorsync profile. Many thanks for the easy fix!
i've been using the script w/ my two u2713h displays on my rmbp w/ mDP and out of curiosity attempted to plug a u2713h in via HDMI and was pleasantly surprised that I got 1440p in mavericks with it (read that it couldn't be done with Mountain Lion)... however, it was using YCbCr, so I tried the script with it plugged in via hdmi and it generated an a091 instead of a092 file, and I was optimistic... but when rebooting with that override, colors looked okay but the max screen resolution was 1080p.... removed the profile and rebooted and back to 1440p over hdmi /shrug
Im not technical at all but love photo and would like to get my dell monito and mac book pro to work! Could someone explain for a very stupid person what needs to be done and how. Is it the zip file that should be moved somewhere? Do I need to change anything in the text? Per
I registered just to say thank you for providing this fix. I don't know what I would have done without it.
On mavericks switching which port the cable was plugged into fixed the issue where my monitor was stuck in 1080p. Amazing.
So the patch works super well after a reboot. Thanks a ton for that! Only problem is if I unplug the monitor and plug it back in again, the override doesn't seem to be respected. Anyone found a fix for that?
Thanks Andreas and all that have contributed to this. I'm trying this patch with the Dell U2413 but it doesn't seem to work. Could you advise on how I might edit the patch to work with my monitor please? I'm using a 15'' BMP late 2008, through miniDP to DP on the monitor. Many thanks, Sam
Thanks for the script! I used it to fix my Dell U2413 connected to a mid-2010 Mac Mini via HDMI. (It's also problematic over DisplayPort, and fixed the same way with this script. DVI works fine, but I want to use the DVI input for something else.) I've forked the script on GitHub and added a couple features I really wanted: * Use the monitor name (taken from the EDID data) rather than the generic “Display with forced RGB mode” * Multiple display support — patch the EDID for all connected displays, rather than just the first one. Obviously you only need to install the override file for the problematic display, not all of them. It's available at https://gist.github.com/adaugherity/7435890
Hi All, Just an FYI, used this script on my ASUS PA279Q and PA249Q and it works perfectly....! PS. the Dell and ASUS and Samsung use the same LG AH-IPS Panel. Darin
Hey, I'm having also troubles with my rMBP 15'' and my Dell u2711. I tried to run your script but it still doesn't let me use the RGB mode. The monitor is also still recognized as TV. Is there anything else what i could try?
The same here. Running the 2713h on the MacBook Air 2012 via DP. I am running the new Mavericks - does the patch work with the newest version?
Daniel wrote: > The same here. Running the 2713h on the MacBook Air 2012 via DP. I am > running the new Mavericks - does the patch work with the newest version? Hi Daniel, I'm running mavericks on a new retina Macbook Pro and have successfully run the script and fixed the issues described. Unfortunately, following this thread to try and work out what to do is kinda painful - here are the steps I used: - Download the Ruby script: http://embdev.net/topic/284710#3027030 - Move the script to your desktop - Close the lid on your laptop to force OSX to only see the external monitor - Open Terminal: /Applications/Utilities/Terminal.app - In Terminal, go to the desktop by typing the following command and hitting enter: cd ~/Desktop - Run the Ruby Script by typing and hitting enter: ruby ~/Desktop/patch-edid.rb - Go to your desktop - Check that a new folder was created - something like: "DisplayVendorID-10ac" - Open: /Macintosh HD/System/Library/Displays/Overrides/ - Copy the new folder into the /Overrides directory - Authenticate with your user password (if asked) - Restart your mac For the first few seconds of the restart it will look like nothing has changed but by the time you see the login screen (or your Desktop if you have that off) everything will be sweet. After you've logged in, you can now open the lid of your Macbook Air. Hope that helps. Cheers Ben
:
Edited by User
Retina MacBook pro 15", Dell U2713HM, OS X 10.9. Unfortunately forcing RGB doesn't solve the horrible ghosting my monitor shows. Scrolling is incredibly painful. I have closed the lid of my MBP, run the ruby script, moved the folder to /System/Library/Displays/Overrides , restarted the machine with the lid closed. Still ghosting even if the monitor reports RGB input. Suggestions?
Hi Lucasoldaini, On The Dell Monitor (not OSX), if you go >Main Menu >Menu >Color Settings >Input Color Format Does it say "YPbPr" there?
:
Edited by User
I have run the script and it works fine on my 2011 MBP going to my HP Pavilion 23xi monitor. However, I'm experiencing some issues now with other TV's that I connect to. I'm not sure it is or isn't die to this script forcing RGB but, I would like to know how to reverse the script, delete or disable the changes it made to bring my Macbook back to stock. Any help?
Ben Sciascia wrote: > Hi Lucasoldaini, > > On The Dell Monitor (not OSX), if you go >Main Menu >Menu >Color > Settings >Input Color Format > > Does it say "YPbPr" there? nope, it says RGB. So I guess OS X loads the new profile correctly...
@Ben: Are you sure the Dell shows the info about the mode in this menu? I thought the mode is being displayed in the Syste Settings > Monitor in MacOS. In my case it shows a TV as symbol for the Dell monitor where I thought it should display a monitor instead. Thank you for your detailed procedure. I will check this later today, but I am not quite sure wether I am checking my success against the correct "validation" as explained above. Perhaps the mode is already correct and I should search for another issue for my ghosting issues ;-)
Posting a lucky find for a U2713h on a Macbook Air (2013) with lightning/displayport connection. It worked moderately well at first plug-in but the crispness of the image was awful, giving it the appearance of running at the wrong resolution. Furthermore, the mouse cursor was lurching along as if the computer was struggling. As it turned out, the problem was fixed by simply turning the monitor sharpness down to 0. The image was perfectly clear for general use, and all the issues went away. I suppose that the pixel processing unit in the monitor was struggling with both YPbPr signal decoding and the sharpening algorithm.
Ah this is a great fix. Thank you very much! note * I did not have to close macbook lid for this to work.
Hi there, I was wondering if you could help with my Dell E2414H series? I have dual screen on a Mac Mini (latest model) using mini display port to dvi as well as an hdmi to dvi. It seems to work fine on my md to dvi, but the hdmi to dvi monitor switches from RGB working great, to YPbPr working instead. I want RGB to work... your file didnt work for me. RGB on the other monitor works too. and the one with the issue tends to sometimes not want to wake up. but sometimes it works fine Thanks
Hello, I tried to follow steps to run ruby script, but I get this error, please could somebody help here ? Thanks ! daniels-mbp:Desktop danielreyes$ ruby ~/Desktop/patch-edid.rb /Users/danielreyes/Desktop/patch-edid.rb:1: syntax error, unexpected $undefined, expecting '}' {\rtf1\ansi\ansicpg1252\cocoartf1265 ^ /Users/danielreyes/Desktop/patch-edid.rb:2: syntax error, unexpected $undefined, expecting '}' {\fonttbl\f0\fmodern\fcharset0 Courier;} ^ /Users/danielreyes/Desktop/patch-edid.rb:2: syntax error, unexpected '}', expecting end-of-input daniels-mbp:Desktop danielreyes$
Daniel, I'd guess you didn't download the file correctly. Gist compresses the files when you use the download link, so you'd have to extract the patch from the compressed archive first. If you're on the command line you can just use this command: curl https://gist.github.com/adaugherity/7435890/download | tar -x --strip-components 1 'curl' ("Copy URL" I think) fetches the file and passes it to 'tar' ("Tape ARchive" from the olden times) to extract ('-x') it. --strip-components 1 just makes the file appear in the same place you ran the command from.
When I had previously tried the solution posted here for my Dell U2711 not displaying at full 2560 resolution, it didn't work for me. (I didn't have any color issues as far as I know.) On a whim, I just tried it again, and it worked. Perhaps I did things slightly differently last time. Your mileage might vary, but here's what worked for me: 1) Unplug all other monitors except the problem one and restart 2) Downloaded Andreas' script "patch-edid.rb" from http://embdev.net/attachment/168316/patch-edid.rb 3) Deleted the old color profile in /Library/ColorSync/Profiles/Displays. You'll need to choose the right file for your monitor. For example, I did: sudo rm /Library/ColorSync/Profiles/Displays/DELL\ U2711-000010AC-0000-A057-3145-4A4C00000000.icc 4) Run the script by executing the following command in a terminal window from the directory you downloaded the script to. ruby patch-edid.rb For me, this created a folder called "DisplayVendorID-10ac/" 5) Copy that folder to /System/Library/Displays/Overrides/ sudo mv DisplayVendorID-10ac/ /System/Library/Displays/Overrides/ 6) Restart Not sure if all of the steps are necessary, but that's what worked for me. Thanks, Andreas! Your effort has helped solve yet another person's problem. :)
I have an LG L246WP monitor. Mountain Lion won't let me use it at 1920x1200 without all sorts of craziness, forcing me to use it as a 1080 TV. From what I've read online, the monitor has a hardware write-protect on the EDID, which requires opening up the monitor and detaching a certain pin of a certain chip to disable (enabling the service menu and selecting Agent Mode does not allow EDID writing). I don't know how this fix works, so I don't know if the write-protect would prevent it from working. Anyone know?
mrhooks wrote: > I don't know how this fix works, so I don't know if the write-protect > would prevent it from working. Anyone know? The script does not modify the EDID in the monitor, it just forces the OS to use another EDID of your choice. So in principle the solution still works, however it was never tested with an LG monitor.
Joe Torres wrote: > I have run the script and it works fine on my 2011 MBP going to my HP > Pavilion 23xi monitor. However, I'm experiencing some issues now with > other TV's that I connect to. I'm not sure it is or isn't die to this > script forcing RGB but, I would like to know how to reverse the script, > delete or disable the changes it made to bring my Macbook back to stock. > Any help? hey Joe... Sorry for the comment, but I recently purchased an HP Pavillioin 23xi monitor to connect as an external monitor to my MBP. I'm using an adapter to HDMI to the monitor. I read that this was one of the "best" monitors out there. Not so happy with the dullness of the monitor and then found this thread. If you don't mind, what do I need to do to get this working to its potential. Is this post/thread leading me to find out that I can get a better picture quality on the HP 23xi? Any help would be appreciated. Thank you,
Anthony Vallone wrote: > I just bought a LG 27EA83R-D monitor and had the same problem. The > script fixed it. You're awesome. Apple is a PITA. Thanks for creating a > fix! I have a LG 27EA83D connected to a early 2013 rMBP and never saw this problem with either 10.8 or 10.9. Wonder what the difference is.
Hi All, I have had some success with using my MBP 2013 (running Mavericks) and the Dell U2713. At one point I had a HDMI setup using YPbPr and changing the sharpness down to 0 and I had a pretty clear display. I then tried the script to see if this would improve this further, but it seems to only show the TV resolution 1080p when using HDMI, whilst at some point I had the a higher resolution via HDMI. Does anyone know how to achieve this via HDMI (so I use my DisplayPort for other things)? I have deleted the folder I copied into the Overrides folder hoping that would restore the changes, but it does not unfortunately. I have used both the patch-edt script and the zip download, but the results are the same. Any ideas on what to do apart from using the DisplayPort? Thanks M
great mate definitely the only post here thats easy to understand for people not familiar with terminal and so on. Thanks a lot! works great with aoc 29" 2560x1080
Hello, Have the same problem as everyone here on Mac Mini (end 2012) and Dell U2413f connected with HDMI I have the following error while executing the script: patch-edid.rb:26:in `pack': can't convert MatchData into String (TypeError) from patch-edid.rb:26 from patch-edid.rb:24:in `each' from patch-edid.rb:24 Please, help
If you use the attached folder and put it in the Overrides Folder in your system and use a miniDP to DP cable it works with one screen Dell U2713HM and my iMac 27 in full resolution (2560x1440) on both screens. If you use DVI cable or HDMI it won't. My problem - I did have two Dell U2713HM to connect. First is fine, second connected to second Thunderbolt - all screens go blank. Unplug one -> fine on iMac and one Dell U2713HM. If I change one Dell U2713HM with a Dell U24xx - works with 2 external screens and iMac - but with triple screen setup with two Dell U2713HM the system is crashing. Any clue?
Hey everyone, Unfortunately, i was not able to finde the Displays/Overrides folders in my Library, they simply do not exist. The override files seems to be ok. Is there anything I have to do to make them visible ? Best regards from Germany :)
Hi Christian, Which Library are you looking in? When you go to your Macintosh HD (assuming you haven't changed the name), double click in Finder and you will see a Library folder. DO NOT USE THIS ONE. Double click in System, then in Library, then Displays and you should see the Overrides folder here. So your path is: Macintosh HD/System/Library/Displays/Overrides You should be able to put either downloaded files here or the files created with the patch-edid.rb script here. Make sure (if you are using a Macbook Pro) you close the lid when you restart the MBP so you force your Mac to pass the signal to the external monitor. M
Hi Mike, thank you really much, I was finally able to locate the folders needed. However, even after applying the "patch" colors still look terrific. Does these problem also occur when using a VGA connection ?
Thanks Mazin. I just bought a U2713H, connected it to my Macbook Pro (late 2011 with Maverick), and experienced "grungy" text. Your short guide fixed the issue (y)
Andreas, Just a data point for you. The Ruby script worked beautifully for my HP w2338h display. I just added the folder it generated to the /System/Library/Displays/Overrides/ directory (preserving other contents) and restarted. Presto! Proper resolution. You have saved my programming environment. Thank you! Andrew
Andreas thank you a lot! (Ruby script + mini DP to DP) Ruby script worked great for my Dell U2711 monitor. There was no truble with my old Macbook pro 2.2 from 2007 (osx 10.7.5) and this monitor. Full resolution. Although, sometimes it was a bit to much for him. Very resently I upgrated to a Macbook Pro late 2013 i7 (Osx 10.9.1) and it didn't work. Had a old HDMI cable what didn't work. bought a new one what insured me it was a 1.4 type of cable. Little I know that it didn't work for the max resolution. Also bought a adapter from mini displayport to DVI, because I worked on my old Macbook with only DVI aswell. Max resolution was still 1600x1200 I could force for more with SwitchResX app (trial) but than there was a strange scaling in the monitor. For everytime I switched cables I use the Ruby script. In the proces there was always bad rendered text. Only resolution of 2560x1440 is the best. Anyways, the only way to go is the mini display port to display port cable. I read it in this topic (thanks Ryan L and others). Maybe the dual DVI thing aswell but 100+ euro is to much. Mini DP to DP is not commen in The Netherlands in regular shops. You can find many other adapters. I find this a bit odd. Online no problem and for just 17 bucks incl. post. After this I tried to use my Spyder Pro 4 to calibrate the monitor and although Datacolor didn't support Mavericks (they are in proces) It worked. Looked way better. I'm am a bit of an onion about the whole profile stuff and tried to delete the Ruby script result in 'overrides folder' and rebooted. Just to see... Indeed no RGB in the Monitor and a bit of color with my new profile. Resolution was maxed out and good rendering with the text. Now the file is placed back it is shining. Sort of in my head. One thing what concerns me is the mini display / thunderbold port vs wifi fallout.. Some one spoke about it before, up in this thread. While trying mini DP to DVI there was no wifi connection. There was no trouble with my old laptop having internet via wifi. Now with the mini DP to DP I had ones no connection. Ones trouble finding it but found it and a few good ones... Time will tell I guess. Thanks again Andreas best, sorry for my clumsy English. Hope to help somebody with the same, or around same, setup.
:
Edited by User
Hi Andreas, I did everything according to the instructions from You - and does't work - 2560x1440px resolution . I have dell 2713hm and mini mac with OSX Maverick . I did so : 1. Downloaded "patch- edid.rb" 2. Run the script in terminal 3. Copy DisplayVendorID - 10ac to folder System Library Displays Overrides / And restart I make press button cmd option P / R (reset NVRAM) And still nothing. Please help me!
of course i use to connect mini DP and DVI
Trie mini DP to DP. Please read my post, just before yours and a few others before me. There was no luck for me using mini DP to DVI. Succes!
Works perfectly, any idea how to get it to work as well on Portrait mode?? The monitor at 90degrees is stuck at a max res of 1080x1920. I would like to use the full res 1440x2560 on vertical mode. any ideas or help on how to edit the IODisplayEDID would be appreciated. Cheers,
No sorry. My monitor is not fysical able to do so. So, no experience. And with coding/scripting I feel like an stranger. But maybe when all is set to vertical mode (computer and display) and then you make a profile...? But really, I do have no clue. Interesting it is. Good luck.
Just wanted to comment the files from the first post worked perfectly with my MacBook Pro Retina 15" (2013) and a Dell U2713HM, I now have access to the full resolution and it looks great. Thank you for figuring this out and posting it for all!
thank you so much! I was almost out to buy new cables thinking the old mini-display port to display port cable wasn't good enough. You saved me :) I previously used my Dell U2713H with a macbook pro 15' 2010 and had no problems at all. Then with a mbp mid 2012 (non-retina)with GT 650M and thunderbold everything looked horrible on the Dell. Saved! Thanks again :)
Hi Andrea or anyone else who would have a solution for me! I know I come late and that it's not exactly the topic but i've been looking over the net for an answer to my problem and you are the closest to it. I run rMBP late 2013 with a DELL U2713HM. I don't have any color problems, but a resolution one. None of my tb ports works, i can only have 1920x1080, it doesn't show full res. I am of course using mini display to display port. I really hate not having the full res of my screen especially that the weirdest thing was that it worked in the beginning for a couple days on only one the ports and then nothing. Could it be my cable? I'm not familiar with encoding and such, is there a patch for that too? If you can please help!! Thanks in advance, Julien
Andreas, I am having exactly the same problem as you describe with a NEW Macbook Pro Retina 15 as well as last years model (Don't ask, over excitable dog, glass of water and $3000 that I did not want to spend again). After two days of flipping Thunderbold cables using alternate monitors blah blah blah, It suddenly hit me that I did not see it exhibit the same way in a VM running Windows 7 64bit. That made me search a different way and here I am. I have a few questions...... Why would this not be an issue in windows? Is it perhaps the way that OSx anti aliases text as opposed to Windows ? (I mean when you think about it when you are virtualized on VMWARE on a desktop surely the engine running the VMs is not talking directly to HW. I could understand if it was a bare metal hypervisor.......or is it my lack of understanding? To get practical My monitor is an ASUS VX279Q (how could I afford a fancy Dell monitor after twi Retina Macbooks in a year). Can I go ahead and use the files for the Dell Monitors or do I have to edit them for the ASUS? I do hope not as I could not find an easy listing of Display Vendors, or any pointers from pulling apart windows .inf files........ I would appreciate your thoughts on this Thanks
Please log in before posting. Registration is free and takes only a minute.
Existing account
Do you have a Google/GoogleMail account? No registration required!
Log in with Google account
Log in with Google account
No account? Register here.