Pages: 1 [2]   Go Down

Author Topic: RGB Working space  (Read 11316 times)


  • Sr. Member
  • ****
  • Offline Offline
  • Posts: 1122
    • theimagingfactory
RGB Working space
« Reply #20 on: September 06, 2006, 05:02:43 PM »

Please kindly explain.

[a href=\"index.php?act=findpost&pid=75489\"][{POST_SNAPBACK}][/a]

Car photography is commonly done with as little reflection clutter as possible, so you'll have the usual mandatory sunset staging. If a car is some metalic gray color, then the car consists of numerous gradations from neutral to near-neutral tones in all color variaties. If additionally the car is a toned near-neutral metallic, then even more subtle tonal shifts are possible. Obviously, the more steps available to generate these gradations, the better. (Encoding efficiency argument).
Oscar Rysdyk


  • Sr. Member
  • ****
  • Offline Offline
  • Posts: 1772
RGB Working space
« Reply #21 on: September 11, 2006, 12:47:46 AM »

I'm a bit confused first a general question then a specific one.
1. In general; If I shoot pure red and the sensor records fully saturated red and nothing else, then I process the raw in a large and a small color space aren't I still recording fully saturated red. (R=256 G=0 B=0) Then if I view it using it's appropriate color space won’t it look the same? (assuming the monitor can display both) or is a larger color spaces fully saturated red actually more saturated? How would the sensor know what red it is? all it would know is that all my red photo sites are maxed out?
2. Specifically; for a 5D and an iPF5000 what would be the optimum color space to use, assuming a raw file and 16 bit all the way through the workflow (Canon 16 bit plugin for printing)? It seems to me a space that is slightly bigger than the sensors and the printers capabilities would be ideal.
3. Would the content of the image make a difference or the sensor capability? i.e. should the color space be tailored to encompass the sensors gamut or the images gamut?
Thanks Marc
Marc McCalmont
Pages: 1 [2]   Go Up