[argyllcms] Re: OS X 10.9 Mavericks has broken LUT manipulation
- From: Martin Diers <martin@xxxxxxxx>
- To: argyllcms@xxxxxxxxxxxxx
- Date: Mon, 21 Oct 2013 09:58:28 -0500
Ding! We have a winner.
○ → ./dispwin -c -D5
Found 2 screens
new_dispwin: CGDisplayGammaTableCapacity = 1024
new_dispwin: found pixel depth 10 bits
new_dispwin: CGDisplayModePixelEncoding = '--------RRRRRRRRGGGGGGGGBBBBBBBB'
Dispwin: Warning - new_dispwin: frame buffer depth 8 != GammaTable depth 10
dispwin_get_ramdac called
dispwin_get_ramdac returning OK
Saved original VideoLUT
new_dispwin: return sucessfully
dispwin_set_ramdac called
Set_ramdac persist
Current profile path =
'/Users/mwdiers/Library/ColorSync/Profiles/display1-427c3e6032c170b8ca110dfa990d74e8.icc'
Renamed current profile
'/Users/mwdiers/Library/ColorSync/Profiles/display1-427c3e6032c170b8ca110dfa990d74e8.icc'
to
'/Users/mwdiers/Library/ColorSync/Profiles/display1-427c3e6032c170b8ca110dfa990d74e8.icc.orig'
Restored
'/Users/mwdiers/Library/ColorSync/Profiles/display1-427c3e6032c170b8ca110dfa990d74e8.icc.orig'
back to
'/Users/mwdiers/Library/ColorSync/Profiles/display1-427c3e6032c170b8ca110dfa990d74e8.icc'
dispwin_set_ramdac returning OK
dispwin_del called
dispwin_set_ramdac called
dispwin_set_ramdac returning OK
dispwin_set_ramdac called
dispwin_set_ramdac returning OK
Restored original ramdac
Now to see if I can use the i1 Display Pro and make this work. I’ll let you
know.
On Oct 20, 2013, at 7:36 PM, Graeme Gill <graeme@xxxxxxxxxxxxx> wrote:
> Martin Diers wrote:
>
>> new_dispwin: CGDisplayModePixelEncoding = '--------RRRRRRRRGGGGGGGGBBBBBBBB'
>> new_dispwin: CGDisplayGammaTableCapacity = 1024
>
> Hmm. Well it seem that 10.9 is giving us contradictory information. On the
> one hand
> it's saying that the frame buffer is 8 BPP, and on the other hand it's saying
> that the VideoLUT tables have 1024 entries. That leaves us guessing as to
> what's actually going on. Is the frame buffer really 8 bits and only 256
> entries of the VideoLUT is being used ? If so, which entries ? The top
> 256, the bottom 256 of something else ? Or is the frame buffer really 10 bits
> deep ??
>
> We're not likely to get any answer from Apple, so we're left with guessing +
> trial
> and error.
>
> I've modified these:
> <http://www.argyllcms.com/disptools_osx64.tgz>
> to believe the VideoLUT depth information. See
> what happens.
>
> Graeme Gill.
>
>
>
Other related posts:
