Pages: 1 ... 4 5 [6]   Go Down

Author Topic: LAB COLOR  (Read 30220 times)

Mark D Segal

  • Contributor
  • Sr. Member
  • *
  • Offline Offline
  • Posts: 7791
« Reply #100 on: December 07, 2007, 02:26:58 PM »

Just stating what I heard him say (and that I don't agree with).
[a href=\"index.php?act=findpost&pid=159028\"][{POST_SNAPBACK}][/a]

Ahah - the part in brackets was missing. Now *I hear you*.

Mark D Segal (formerly MarkDS)
Author: "Scanning Workflows with SilverFast 8....."


  • Sr. Member
  • ****
  • Offline Offline
  • Posts: 10628
« Reply #101 on: December 07, 2007, 03:25:47 PM »

What's ironic, if that's the right term, is he is just making the Lab move to build a luminosity layer set to Screen (which makes the image in Lab look butt ugly). He could have duplicated the original image, converted to Lab, built the layer and shift dragged it onto the original RGB document. Is maybe one more step (well its about the same, you don't need to convert back to RGB). Its interesting to see the difference in color kick in when you convert from Lab back to RGB. If you try both techniques, the net results, especially based on what he's trying to do (paint in highlights) look about the same but with the duplicate technique, the original image doesn't have to be converted to Lab. All the stuff you paint into this image from the moved layer of course did undergo the Lab damage.

Then I found another potential issue. The original document I opened was in ColorMatch RGB, my working space is set for ProPhoto RGB. If you do the RGB to Lab and back, you end up (in this case) in ProPhoto RGB, not the original color space (ColorMatch RGB). That's not an issue when you just drag the Lab created layer back to the original RGB document.
« Last Edit: December 07, 2007, 03:30:15 PM by digitaldog »
Andrew Rodney
Author “Color Management for Photographers”

Another here who is ignoring all posts from: "AlterEgo" "deeejjaaa"
Pages: 1 ... 4 5 [6]   Go Up