Calibrated with i1Display Pro in basiCColor Display and i1Profiler too.
Lightroom Classic version: 7.0 [ 1140024 ] License: Creative Cloud Operating system: Mac OS 10 Version: 10.13 [0] Application architecture: x64 Logical processor count: 8 Processor speed: 3,5 GHz Built-in memory: 16 384,0 MB Real memory available to Lightroom: 16 384,0 MB Real memory used by Lightroom: 1 735,2 MB (10,5%) Virtual memory used by Lightroom: 5 485,6 MB Memory cache size: 82,4MB Maximum thread count used by Camera Raw: 5 Camera Raw SIMD optimization: SSE2,AVX,AVX2 Camera Raw virtual memory: 1095MB / 8191MB (13%) Camera Raw real memory: 1130MB / 16384MB (6%) Displays: 1) 2560x1440
Cheers Simon - all sorted now, and cheers Ad for the correct folder location to drop Simons config.lua file. It's the same location under El Cap 10.11.6 for those of us on Apples abandoned machines.
I tried tip #2 on https://helpx.adobe.com/lightroom/kb/crash-gpu-directx-enabled.html. The location to place the file is not valid when Lr is configured to store presets with the catalog, still showing "Metal: ..." for the GPU checkbox and no flags reported in system info.
When placing the config.lua in /Users/<user name>/Library/Application Support/Adobe/Lightroom/ (macOS Sierra), the GPU checkbox states "OpenGL", the setting is reported in system info and no more blocked-up shadows.
Thank you for confirming that your issue is reproducible in the Photoshop's ACR and Bridge.
You can try the possible Lr Classic workaround that I suggested to Andy to see if that works. If not, then the short term workaround is to turn off the GPU acceleration from the Lightroom and ACR's preference dialog until we can confirm and fix the issue.
For people who has the issue, please attached the ICC color profile of your primary Lightroom display (monitor) to this thread.
Also can you report if you have a multiple monitor setup. If so, what happens if you disconnect your secondary display, does the color discrepancy between library and develop still appear.
Metal is actually Apples API. it allows for more direct access to the graphics hardware so that is actually a good thing. The issue appears to be because Adobe is not using their own color management when the GPU is enabled.
The problem is a combo of Apple and Adobe. Apple for years now has been unable to properly support calibrated table based profiles. This is an issue with OS level stuff like Safari, image preview, etc.... Its not an issue with pro software because it uses its own built in color management.
I've now been able to reproduce this problem in Photoshop's ACR and Bridge. This is 100% unacceptable. Apple has no near term plans to fix this issue and Adobe has been aware of it for years. To not provide *AT LEAST* an option to choose whether you use Adobe's color management or Apple's is a joke. (DaVinci Resolve provides this option)
I'm curious to see what any other staff member has to say regarding this because quite frankly at this point my patience has run thin. Previous LR versions have had a host of performance problems and now this.
Theres other competition on the market perhaps its time to just give up.
A
Anonymous
October 20, 2017
Simon, just uploaded a video here https://youtu.be/N1YuSTt8MLc that illustrates the problem, and also that the problem did NOT exist before the upgrade from the last itteration of CC2015.
Is there any way to force Lr Classic to use/see OpenGL instead of this 'Metal' - what ever that is?