Currently Being ModeratedJan 15, 2013 5:32 AM (in response to Fouad Abbasi)
Yes I subscriped the developer program.
Currently Being ModeratedJan 15, 2013 6:18 AM (in response to sonicblue83)
@sonicblue83 : thx for the info, I hope it'll stay like this until the 10.8.3 is golden master !
Currently Being ModeratedJan 15, 2013 6:45 AM (in response to nderambure)
You're welcome. There is no reason why it should change until the golden master. It clearly shows that Apple is aware of the problem and that the problem is software and not hardware based.
Currently Being ModeratedJan 15, 2013 8:13 PM (in response to sonicblue83)
I'm agree with you .. This is software issue.. when I boot in Windows 8 via bootcamp.. The color just fine.. I'm using Mini Display to HDMI. still having issue .. So I think this is not only HDMI port issue. but also The thunderbolt port ..
I hope 10.8.3 will solved the problem .. ThxMac mini (Late 2012), OS X Mountain Lion (10.8.2)
Currently Being ModeratedJan 15, 2013 8:54 PM (in response to UrielGarciaC)
The 10.8.3 update is supposed to address this issue. I'm experiencing it myself and it's quite annoying.
In the meanwhile, rather than mess with calibration (which I find difficult to do due to my own particular physical limitations) or use beta versions of an operating system (not a good idea unless you are actually a dev who needs to be able to test his software in advance of release), I'm using these two free Mac App Store utilities to set the white point "down" enough to make my monitor usable.
They're also great for using a bright monitor in a dark space.
Currently Being ModeratedJan 15, 2013 8:52 PM (in response to John Hammer1)
Hey thanks to sonic
I updated with 10.8.3 beta and the problem is solved
Currently Being ModeratedJan 15, 2013 11:29 PM (in response to John Hammer1)
Apple lists that the newest 10.8.3 beta has "no knows issues", so there's a good chance that the golden master will be the same version. Of course there still could be a bug which Apple still doesn't know, but it's like the same chance that the golden master still includes a bug which nobody found before.
If you get access to the 10.8.3. beta I recommand to install it, so far I didn't had any trouble with it at all. Otherwise the golden master will be released soon I guess.
Currently Being ModeratedJan 16, 2013 5:55 AM (in response to sonicblue83)
If you're lucky, you'll be right most of the time. I don't think anyone on this forum should be recommending developer prereleases to random folks as a solution to a problem, though, as it often results in fairly low-information users taking on tasks and dealing with problems which are potentially well beyond their scope to deal with and worse than the original issue.
Currently Being ModeratedJan 16, 2013 6:19 AM (in response to UrielGarciaC)
Finally.. I solved the problem.. just convert mini display to DVI.. it's working for me..
very happy now..
Currently Being ModeratedJan 16, 2013 7:06 AM (in response to xrmer)
@xrmer : it's not "solved", it's a workaround
I did the same, waiting for the bug fixed.
Currently Being ModeratedJan 17, 2013 4:54 AM (in response to nderambure)
Here is my converter.
MiniDisplay to HDMI. Then I connect HDMI to DVI (include from Apple) Than I Convert DVI To HDMI.sorry for confusing you. here is the pict
this is because. before I buy MiniDisplay to HDMI adapter I found someone on macrumor solved the problem by Convert mini Display to HDMI. and my monitor only has HDMI and VGA port. Unfortunately this not solved.
after looking around on this forum.. I found someone solved by Convert miniDisplay to VGA and miniDisplay to DVI.
when I connect HDMI to DVI converter from apple (without miniDisplay to HDMI) trough macmini. Monitor searching for signal.
it's look messy but it's working.
System Software Overview:
System Version: OS X 10.8.3 (12D50)
Kernel Version: Darwin 12.3.0
Model Name: Mac mini
Processor Name: Intel Core i5
Processor Speed: 2.5 GHz
Boot ROM Version: MM61.0106.B03
Currently Being ModeratedJan 21, 2013 12:37 PM (in response to UrielGarciaC)
I m very happy to find that I m not the only one to have this annoying problem.
So is this problem goes away with the 10.8.3 release? Is officialy answered?