Skip to main content
Participating Frequently
December 14, 2015

P: Color lookup turns black and no start screen

  • December 14, 2015
  • 50 replies
  • 1025 views

-PS cc2015.1 (dutch version) can't see new start screen, check box is on.
-Color lookup few filters turn image black (bleach bypass and a few other)

I work with new iMac and El Capitan, color lookup works normal with older mac and Yosemite.

This topic has been closed for replies.

50 replies

Inspiring
March 16, 2017
> The application of a Color Lookup adjustment layer selecting a profile with .look extension results in a completely black image. The application of Color Lookup adjustment layers selecting .3dl and .cube profiles works.>

Do I understand you're stating that you can't use .look files on your Mac? You're using the .look files that come with Photoshop? Or trying to open one from Speed Grade? As I recall, that's the app that creates .look files. As it happens, I have 2015 still installed, and all of the LUT files that ship, including .look, work just fine on my MBP running El Capitan. They also work in Yosemite, and in CC 2017. The LUT files I've created work in PS just fine, too.

My video card is an Nvidia GT 750M, if that makes any difference to the display.
RosaPerry
Inspiring
March 16, 2017
Hi Jeffrey,

Just confirming, after another Windows update last evening I am still not able to use certain LUTs. I'm not going to uninstall this update especially as Windows announced another major update in the coming weeks - Windows 10 Create - which is supposed to give us enhanced 'graphic abilities'.
Rosa
Legend
March 15, 2017
Hi Denny, I am not able to reproduce this issue. I can open an 8-bit or 16-bit RGB image, create a Color Lookup adjustment, and select "2Strip.look"

The image doesn't turn black.
davescm
Community Expert
Community Expert
March 15, 2017

Hi Jeffrey
Yes the look LUT  issue still exists and still comes up from users on the Photoshop Forums which is how I got to see it. I'm happy to carry out any testing you want me to try.
What I have found out is that going into CC2015.5 and applying the LUT then saving as a *.cube file enables me to apply the LUT in 2017.0.1. so as a workaround that works although it is awkward.

System details : Win 10 Pro;  i7 3930k ; Motherboard P9X79Pro; 64GB RAM; 500GB SSD + 3x2TB drives; Graphics AMD 7970 3GB  ;3xHPZR2240W monitors ; M-Audio Profire2626 audio.

Dave

Red Aqua Media
Known Participant
March 15, 2017
Today my operating system installed the security update KB890830. Then Color Lookup did not work again.

Just uninstalled this. Then it works again. Windows want to install the update KB4013429 after uninstalling KB890830, but I blocked it.

Well done Adobe! We still have a vulnerable operating system since December 2016 and you still did not fix this little issue.
Legend
March 15, 2017
Hi David, I'm not able to reproduce this issue in CC 2017.0.1. Are you still having this issue? If so, we'll need to dig in more to find out if there's something special different about your set-up/steps.
Known Participant
March 15, 2017


The application of a Color Lookup adjustment layer selecting a profile with .look extension results in a completely black image. 

The application of Color Lookup adjustment layers selecting .3dl and .cube profiles works.

System datas:
OS X El Capitan 10.11.5 (15F34) - Macbook Pro Retina 15"
Photoshop CC 2015.1.2
davescm
Community Expert
Community Expert
March 15, 2017


Problem :

Open a file

Apply a color look up adjustment layer

Pick "2Strip.look"

Result - black screen



Expected result – application of LUT as in CC2015.5 which works correctly

Note the same issue applies in most, but not
all,  *.look tables. Copying the table
from CC2015 does not resolve the issue

Participant
March 15, 2017


When I select a color lookup, I get a black Image.

Photoshop CC 2015.1

Red Aqua Media
Known Participant
January 30, 2017
Thanks for the info, Carlos 🙂 I will wait for the next Photoshop update and hope Adobe keep their promise.
If not, then I will use the compatibility mode, because I don't want to block the further Windows 10 updates. You know, it's not really safe 😉