Color Spaces CIE and Adobe RGB

Looking at monitor specs, usually, the color space of the monitor is given in terms of a target color space, like 96% Adobe RGB. Some give several, but along comes Dell, u2412, and they supply one: 82% CIE.
I know what CIE is, but making a guesstimate from the Dell spec requires more than what I presently know about such matters.
So, what are the expectations? Is that a meaningful spec for comparison sake? IOW, how much does Adobe RGB enclose CIE 1976?
TIA
Lawrence

I went back to here:
http://forums.adobe.com/thread/916368?start=0&tstart=0
and ran some of those checks with the various presentations. Also, embarrassingly, I did know about the site but failed to go back when I looked for any test results for the 2412.
sic transit Gloria!
I also generated a step tablet in PS, as well as doing several calibration reruns. I did a calibration in "Standard"ode and one in "Custom" where I had access to RGB controls.
TFT Central did the same and claimed that the Custom was more troublesome and didn't yield any significant improvement. I beg to differ!
Also, they made available the results of the Standard and Custom as an ICC profile for users and I defy anyone to tell me there is no significant difference. Between my two calibrations and TFT's, I have 4 flavors from which to choose. Wow! I'm impressed (NOT!)
At any rate I settled on using my custom version as it shows the most neutral gray. It also showed the smaller dE both average and max deviation, 0.34 and 1.2 respectively, the only one exceeding 1.0. It also was close to the factory default than the others.
What a way to run a railroad!
The other fussbudget item is X-Rite. I doesn't like calibrating LCD. It manages to skip over steps along the way, and if I hadn't the experience and expectations step to step with my crt, I would probably be returning the Dell at this time. The differences from the data pov between my Custom and Average should be barely visible, but in fact, it is visually significant. Normal conclusions would hold the monitor at fault.
Off to contact X-Rite.
Lawrence

Similar Messages

Color profile (sRGB Vs. Adobe RGB)

Hello,
As I am struggling with choosing the 'right' color profile for my photo's (either sRGB or Adobe RGB) I was wondering what your opinion of this subject is. I have searched the internet for the information about this subject, but the forums/answers/information couldn't give me enough satisfaction.
For editing photo's I am using Adobe Photoshop, for my library I use iPhoto. Some photo's are uploaded to sites as www.facebook.com. Sometimes I order a photo book via iPhoto.
Because there are pros and cons for both sRGB and Adobe RGB I am not sure which profile I have to choose. I would like to choose one format, since this will standardize my library.
Looking forward to your opinion.
Best Regards,
Jelle

Larry & Terence,
Did you do any on-screen testing or proofing? All modern browsers support ICC profiles and should show improvement with Adobe RGB in certain color ranges (NOT just Facebook).
Apple products aren't "designed" for sRGB. sRGB is a standard developed by Hewlett Packard and Microsoft (and I think we all can agree those aren't Apples best friends). sRGB is the default for most Cameras and SmartPhones, that doesn't mean it's the best.
Most monitors sold in the last 5 years have wider gamut support than the sRGB.
Article "Can the entire sRGB color gamut be displayed on today's LCD monitors?"
http://ninedegreesbelow.com/photography/srgb-bad-working-space-profile.html
"sRGB was created to match the display characteristics of consumer-grade CRT monitors manufactured in the1990s." "LCDs use a completely different technology to make colors..." "All wide gamut monitors by definition can show more greens, yellows, and cyans than sRGB."
Apple even suggests "Adobe RGB offers a wider gamut than sRGB, and is usually a better choice, if available." in this article:
http://support.apple.com/kb/ht2026
iPhoto 6 and newer have support for ColorSync profiles, older versions may not work with Adobe RGB and could cause the color to look worse. If a profile isn't present, or isn't supported iPhoto assigns Camera RGB. Complaints about "dark" color from iPhoto are more than 5 years old.

Color space, gamma, and code value range data

Greetings!
I'm getting close to submitting my film for professional DCP creation. It's a ProRes 422 4096 by 1716, 2.39 - 1 file, created as a "master file" in a Premiere Pro CC export (the sequence being an "online" of sorts, built from SpeedGrade color-corrected DPX files).
The Guidelines for "Digital Cinema Source Delivery" require me to provide information about Color Space, Gamma, and Code Value Range Information (head vs full). Specifically, an order form asks for TRT, Color-Space, and Full or Head.
This is simply all Greek to me. I know my film looks gorgeous, and the rest of what I've told you, but that's the limit of my experience.
Can someone help me out? Specifics are preferred to broad strokes. Many thanks in advance.

This is probably too late now for you anyway but here is some extra information:
The "Digital Source Master" is the video footage before any D-Cinema formatting or encoding has been done.
It can be literally anything. The DCI specification did not specify this.
They did however specify exactly what the transcoded verison has to look like. The "D-Cinema Distribution Master" (16bit TIFF, XYZ)
So in other words, you need to tell your service provider:
The resolution, fileformat, frame rate and especially the colourspace that you used.
For example r709 for HD or any other RGB colourspace with applied gamma value (2.3 for example).

PS CS with color space set to Prophoto RGB - will ACR change embedded profiles?

Probably a foolish question but my problem is that I have a mixture of files:
My own files (all initially RAW (NEF) which I import into ACR as 16 bit Prophoto RGB ).
Files from family members and from slide scanning performed elsewhere - they are in 2 groups:
The first of these from elsewhere acquired files were all JPEGs that I converted to Tiffs in Bridge before setting out to edit them-- all unfortunately 8bit and sRGB.
The scanned files were scanned as tiffs but also 8bit and sRGB.
My normal procedure is that I in ACR I have set the files to 16 bit and Prophoto RGB. In PS the same but also to preserve embedded profiles. I have the impression that working with the "foreign" files in 16 bit does give me more room for editing but that I should continue with the embedded profiles.
Is there a way to ensure that the color profiles are not changed in ACR even if the line in the middle below says 16 bit Prophoto RGB (I have PS CS5). I would hate to have to change this line each time I view a file in ACR. I would hate more to loose the editing facilities in ACR as these acquired files do need som special care before they are mixed with my own in our family albums. I prefer the 16 bit Prophoto RGB option for my own files as I like to play with them - i.e. apart from including them in Photo Albums.
I do see that a logical way is to process all the acquired files before going to my own files but it is so much more practical for me to work with a mixture of the files sorted chronologically - a year or month at the time.
I would even consider getting an upgrade to CS6 if this version could help me.
Can someone enligthen me?
Thanks, Git

Hi, Tom.
The real issue here is getting accurate color. You can't get accurate color by setting your monitor profile to sRGB. sRGB is a virtual color space that doesn't describe the exact color gamut of any physical device. But, in order to display sRGB or any color space accurately, you need to get a characterization of your monitor.
Here is an AWESOME way to get access to a colorimeter: http://www.lensrentals.com/rent/pantone-huey-colorimeter Looks like for $32 you can rent this for a week. Go in on this with a friend and profile both of your monitors and hardly pay a thing. If you have a reasonably good quality LCD monitor, this custom profile you make will be fairly accurate for many months. At the very least, this is way more accurate than having no regular calibration at all.
Hope this helps!
Bret

IPhoto 5 and Adobe RGB - RGB 1998

Dear fellow members,
1. I've been using iPhoto 5 for a couple of years and haven't questionned about this version <<compatible>> with Adobe RGB (RGB 1998). I understand that the sRGB is already an embedded profile of iPhoto 5, but is Adobe RGB embedded either?
The reason I ask this question is because I wish to work in Adobe RGB, from my new digital still camera, to my other post-processing softwares [from Adobe and Phase One manufacturers].
I understand that Adobe RGB offers some more tonalities and color spectrum, this is the reason why I wish to move from sRGB to Adobe RGB.
2. If I wish to publish photos on the web, I should be careful about exporting in sRGB for a broader audience, though.
But does iPhoto knows it automatically, I'm not sure, however, I can try to convert to sRGB in Preview.app and compare...
3. Looking at pictures on a browser, Safari, or Firefox also differs: Safari manages Adobe RGB, but not Firefox
(see e.g. http://www.gballard.net/psd/golive_pageprofile/embeddedJPEGprofiles.html) .
4. From what I've learnt, I also had to recalibrate my Ti667 screen from the Apple preset 1.8 to Gamma 2.2.
5. Finally what does Generic RGB mean in the OS X system?
Thank you for your comments and responses.
Best Regards.

Mr. Scuttles:
1 - It depends on what camera you're using as to the profile used. Canon cameras use a profile titled Camera RGB. It's an RGB profile that is very similar to the other RGBs except for the Adobe. The Adobe has a wider gamut (range) of colors. If your camera embeds Adobe when you shoot then you don't have to do anything.
2 - If you edit in iPhoto the modified version will retain its Adobe RGB profile. So if you plan on using the photos on the web and want to use sRGB you will have to embed that profile with a 3rd party application. I've modified a ColorSync Applescript to do that. You can download it from Toad's Cellar. It's much faster than using Preview as it can do batches of photos at one time. Just drop the files or a folder of file on it and let it do it's stuff. It's a lossless process. It's a tad slow however, but does a very good job.
5 - See this Technical document for the Generic RGB and Apple RGB differences: http://developer.apple.com/qa/qa2005/qa1430.html
If you open the ColorSync Utility application (in the Applications/Utilities folder) you can view and compare the various profiles.
Do you Twango?

Is there a way to assign Color Spaces in AME (Adobe Media Encoder) CC?

I am trying to output h.264 video for a web project and cannot seem to get sRGB color match when rendering out from AE.
I see it in AE's native renderer, but not in AME.
Thanks.

AME (and Premiere Pro) does not support color management in the way that After Effects does. Via Dynamic Link, which is how AME reads After Effects comps, the color-space-adjusted pixels are not corrected for screen display.
To get the results you want, add an adjustment layer to the top of the layer stack in the comp and apply the Color Profile Converter effect. Set the Output Profile to Rec.709 (sRGB is practically identical and will also work, but Dynamic Link uses Rec.709 internally so is a better match). This forces After Effects to transform the adjusted pixels into a non-linearized color space that looks correct.
Note that while the CPC effect is active and View > Display Color Management is enabled (it is enabled by default), this extra layer of color transforms will make the comp appear incorrect in After Effects, at the same time the comp will now look correct in AME or Premiere Pro. Disable Display Color Management to make the appearance of the comp in After Effects match what you see in AME or Premiere Pro. While working on the comp, however, you probably want to work with Display Color Management enabled and the adjustment layer disabled.
Under the hood, when color management is enabled in After Effects, the pixels it writes into the cache include the appropriate color transforms for the settings you have chosen. When the comp is displayed in the Composition panel in After Effects, an additional transform is added to the screen buffer pixels (not the pixels in the cache) to make it look correct on your computer screen, or not if you have disabled Display Color Management. When the pixels are read through Dynamic Link, no display color management happens, nor does AME or Premiere Pro apply any, so you get the same appearance as having Display Color Management disabled in After Effects.
Make sense?

Color space conversion problem when importing JPEG's

Hi,
I'm currently playing with the trial version of LR. While importing JPEG's with different color spaces (sRGB and Adobe RGB) to LR I've noticed a strange effect: There is a small but noticable difference in color, depending if the JPEG was previously saved in AdobeRGB, or sRGB. All the images I've tested so far should not contain critical colors that exceed normal sRGB. When opened in CS2 both versions of a JPEG, AdobeRGB and sRGB, typically look perceptually identical, no matter if I leave the sRGB image to sRGB, or convert it to the working space (AdobeRGB). Also my color-managed image viewer behaves as it should. So I don't think it's a matter of the different color spaces.
Looking at the imported images in LR I would say that the AdobeRGB image is correctly converted while the sRGB image suffers from a slight reddish cast, most noticable in skin tones. The effect is not as strong as if I would load the sRGB image into CS2 and skip color conversion to my working space (AdobeRGB).
The sRGB versions of the JPEG's were obtained from the AdobeRGB JPEG's using CS2 for conversion.
Anyone else here experienced a similar problem? Is this a bug in the xRGB-to-ProPhotoRGB conversion of LR, or a feature?
/Steffen

Hi Uli,
thanks for pointing me to your thread. I followed the discussion with great interest. Actually, I think the effect I am describing here is of different nature and a LOT stronger, at least for the type of images I've tested.
I did some more experiments yesterday with interesting results:
1) When I export a processed RAW from LR to JPEG or PSD, no matter what Color Space (I tested AdobeRGB, sRGB and ProphotoRGB), and re-import those JPEG/PSD's to LR, they look absolutely identical to the RAW I started with. Also, at first glance, they look similar when opened in CS2, but only because I tested with color images. I can indeed see small differences when testing with B/W, as you described in your "Color management bug" thread.
2) When I change the color space of an PSD or JPEG inside CS2 (I used the default setting 'relative colorimetric') and save it to JPEG and then import this JPEG to LR, colors are far off. The strength of this mostly reddish color cast depends on the color space of the imported JPEG, strongest for Prophoto, less strong for Adobe and sRGB. Interestingly, when I convert the color space inside CS2 and save the result to PSD, it will display correctly when imported in LR. Another interesting side effect: the thumbnails of LR-exported JPEG's in the "Open" dialogs of CS2 and LR (I guess those are not color-managed) show the typical color-flatness for the Adobe and even more the ProPhoto version. For the CS2-converted JPEG's, all thumbnails look just a colorful as the thumbnail of the sRGB version.
3) Such an image which doesn't display correctly in LR will keep its color cast when exported again to a JPEG (not sure about PSD). So something goes wrong with the color conversion during the import of such CS2-converted images.
My explanation so far is that CS2 uses a slightly different way of coding the colorspace information in the metadata of JPEG's which somehow prevents LR to recognise the color space correctly.
Can you confirm this behaviour?
Steffen

ProColor RGB or Adobe RGB ?

I have always run Adobe RGB on PS (now CS3)... have it "automatically convert".
*When I go to PS it is normally because the Output will be to a Printer in the End (and also a web version) ... (also have my camera set to Adobe RGB, "although" I always shoot RAW ... never know when you might run out of space lol)
OK, so because LR is PROphoto RGB ... is it NOW better to Export ALL my images from LR using PROphoto RGB and not have PS CS3 "auto convert" all my images to Adobe RGB anymore? (my default in PS CS3 is to work in Adobe RGB)
* YES, whenever I Print in office ... or send a Profiled JPG to a Printer SITE ... I am using a Printer ICC or converting to the ICC.
lol, have a feeling I might know the answer ... but want to confirm if it is in FACT better to be working in PROphoto RGB all the way?
And that most is doing it this way ....
HG

On 3/19/07 6:45 PM, "M Behrens" wrote:
Or is the "working color space" of LR inconsequential since you cannot get an image out of LR without seleting an embedded color space that the image is converted to? I read somewhere that ProPhotoRGB isn't really the working color space of LR, it mentioned Mellisa or Love Child. If LR has its own color space and simply converts on output. Monitor display is simply another output to sRGB, if calibrated having an ICC file to assist in conversion.
There are two color spaces to consider. One you can control, one you cant. The internal color space for all processing in LR is ProPhoto RGB using a linear encoding. We cant mess with that and theres no reason to.
We can export to three color spaces, two smaller than the internal color space (sRGB and Adobe RGB (1998)).
I dont have any issues doing everything in ProPhoto RGB 16-bit. With a totally raw workflow, thats easy. Where things get a tad dicey is using existing rendered images in LR. They have a color space before you import them. So in theory, you could be moving from sRGB to ProPhoto RGB (internal color space processing) then out to either sRGB again (which seems like a good idea) or Adobe RGB (1998) or finally, ProPhoto RGB. It would be cool if LR could somehow honor the original and output color space. So if you start with sRGB, you get sRGB (but again, theres a conversion to ProPhoto RGB/linear gamma if you do any corrections).
If you stick with 16-bits going out of LR, I doubt youll have an issue doing this theoretical sRGB to ProPhoto RGB dance but I suspect if the original color space was sRGB, that was for a reason and I suspect many want to honor that. Of course, if you start with a color space thats not one of the three spaces that are supported for export, its kind of moot. IOW, you can end up witb any color space you wish, as long as its sRGB, Adobe RGB or ProPhoto RGB.
Melissa RGB (Love Child RGB) is a cute name for the space thats used to represent the histogram and percentage values. Youre never really dealing with this space.
Applications dont have a color space? Well they use a color space for processing so yes. In the case of LR, the internal color space used is ProPhoto RGB as defined by this specs white point and primaries (chromaticity values) but using a linear encoding (what some would call a gamma of 1.0). Melissa RGB is the same expect its using the sRGB tone response curve (what would incorrectly be called a 2.2 gamma encoding). Then you have three options for a color space in which to encode your images upon export out of LR.

MPB 17" and what Adobe RGB color space coverage I might expect from it

Hello,
I am photographer and currently PC user. However, I plan to dive to the Mac’s world.
Before I become a Mac user, I have few questions.
Now I think about MacBook Pro 17”, i7 2.66MHz, 8GB RAM, 500 GB 7200rpm HDD and antiglare screen.
I plan to use additional monitor for photo editing.
I did search on google about *NVIDIA GeForce GT 330M* and *Adobe RGB color space* it covers, however, it gave me no results related to Mac. The only information about this card and Adobe colors I found is that Sony Vaio use this graphic card and in some forums, one say it covers 98% and in other 100% of Adobe color space which made me wonder what type of screen Vaio have.
- is MacBook Pro 17” good for photo editing?
- what % of AdobeRGB color space I might expect from it on my external screen or what % of sRGB colors space it delivers?
- Is it possible to calibrate Mac’s native screen and external one, use both at the time and have different profiles on each?
- Tell me anything that would stop me thinking about MBP for photo editing?
Thank you for your time reading this and hope to find the answers here.

You should consider posting your questions in the Pro Application section for Aperture. You will bump into more photographers there than you will here. But I will make an attempt at answers:
whats about Adobe color space?
No, the MBP screen will not encompass the Adobe Color Space. In fact, few desktop monitors are capable of this.
does the native MBP screen display full color range the video card is able to produce...
There really is no limit to the color extremes, which define a color space, as established by a graphics card. So your question is not a well formed question. An old ATI Rage card with 8-bit output would reveal the same color gamut as would the NVIDIA GeForce GT 330M connected to the same display. The gamut is determined by the attached display, not the graphics card.
...or connecting external monitor to it’s mini display port would bring much wider color range to my eyes?
Yes, certainly the potential for that exists. Notebook screens are usually a compromise and can't be expected to compete with a high-end desktop display in many categories, including color gamut. But whether it would bring a "much wider color range to" your eyes is hard to say. It depends on what type of external display is in use.

For P.O.D. Printing: How to Set Adobe RGB Color Space

Hello and thanks in advance,
(I'm using InDesign CS 5.5 on a Mac.)
I need to set the proper PDF export settings
For printing a book on demand, with color drawings inside on the text pages.
The onnly instructions that I have been able to find, say this:
"Submit your graphics in the Adobe RGB color space, withprofile embedded."
The Big Question: How do I do that ?
I know enough to start with
File --> Adobe PDF Presets --> Press Quality
Then I click on the "Output Menu"
and here's where I start to get lost.
for
Color Conversion ...
I think I should select "Convert to Destination"
for
Destination
I think it should be "Adobe RGB (1998)"
Now in order to embed this profile,
What should I select under:
Profile Inclusion Policy ?
And is there anything else I should be doing to get these inside color images printing nicely ?
Thanks again,
IthacaAuthor (aka ZorbaTheGeek, but the forum would not let me log in with my old screen name)

Virtually all digital printing is done via either PostScript or PDF. In the former case, the PDF is converted to PostScript viat use of Acrobat and in the latter case, the PDF is sent directly to the digital printer.
In either case, CMYK is in fact the actual destination color space. There are no real RGB printers!!! What is true is that non-PostScript / non-PDF printers (typically low end laser and inkjet printers as well as specialized inkjet and dye sublimation photo printers) do take in RGB via drivers and convert that to CMYK, but I don't believe that is what you are dealing with.
Our recommendation at Adobe for best printing results, whether for offset or digital printing, is to export PDF as PDF/X-4 with no color conversion using the default CMYK color space (SWOP CMYK) or if instructed otherwise by your print service provider, one of the other CMYK color spaces provided by Adobe or by the print service provider themselves. FWIW, most on-demand digital print devices do have settings to fully emulate SWOP CMYK printing conditions. Using PDF/X-4 in this manner allows the existing color content in your InDesign document to be properly tagged in the output PDF file and converted to CMYK at the digital printing device's RIP.
(It might also assist us if you can provide a pointer to the explicit instructions provided by your print service provider.)
- Dov

Why does Lightroom (and Photoshop) use AdobeRGB and/or ProPhoto RGB as default color spaces, when most monitors are standard gamut (sRGB) and cannot display the benefits of those wider gamuts?

I've asked this in a couple other places online as I try to wrap my head around color management, but the answer continues to elude me. That, or I've had it explained and I just didn't comprehend. So I continue. My confusion is this: everywhere it seems, experts and gurus and teachers and generally good, kind people of knowledge claim the benefits (in most instances, though not all) of working in AdobeRGB and ProPhoto RGB. And yet nobody seems to mention that the majority of people - including presumably many of those championing the wider gamut color spaces - are working on standard gamut displays. And to my mind, this is a huge oversight. What it means is, at best, those working this way are seeing nothing different than photos edited/output in sRGB, because [fortunately] the photos they took didn't include colors that exceeded sRGB's real estate. But at worst, they're editing blind, and probably messing up their work. That landscape they shot with all those lush greens that sRGB can't handle? Well, if they're working in AdobeRGB on a standard gamut display, they can't see those greens either. So, as I understand it, the color managed software is going to algorithmically reign in that wild green and bring it down to sRGB's turf (and this I believe is where relative and perceptual rendering intents come into play), and give them the best approximation, within the display's gamut capabilities. But now this person is editing thinking they're in AdobeRGB, thinking that green is AdobeRGB's green, but it's not. So any changes they make to this image, they're making to an image that's displaying to their eyes as sRGB, even if the color space is, technically, AdobeRGB. So they save, output this image as an AdobeRGB file, unaware that [they] altered it seeing inaccurate color. The person who opens this file on a wide gamut monitor, in the appropriate (wide gamut) color space, is now going to see this image "accurately" for the first time. Only it was edited by someone who hadn't seen it accurately. So who know what it looks like. And if the person who edited it is there, they'd be like, "wait, that's not what I sent you!"
Am I wrong? I feel like I'm in the Twilight Zone. I shoot everything RAW, and I someday would love to see these photos opened up in a nice, big color space. And since they're RAW, I will, and probably not too far in the future. But right now I export everything to sRGB, because - internet standards aside - I don't know anybody who I'd share my photos with, who has a wide gamut monitor. I mean, as far as I know, most standard gamut monitors can't even display 100% sRGB! I just bought a really nice QHD display marketed toward design and photography professionals, and I don't think it's 100. I thought of getting the wide gamut version, but was advised to stay away because so much of my day-to-day usage would be with things that didn't utilize those gamuts, and generally speaking, my colors would be off. So I went with the standard gamut, like 99% of everybody else.
So what should I do? As it is, I have my Photoshop color space set to sRGB. I just read that Lightroom as its default uses ProPhoto in the Develop module, and AdobeRGB in the Library (for previews and such).
Thanks for any help!
Michael

Okay. Going bigger is better, do so when you can (in 16-bit). Darn, those TIFs are big though. So, ideally, one really doesn't want to take the picture to Photoshop until one has to, right? Because as long as it's in LR, it's going to be a comparatively small file (a dozen or two MBs vs say 150 as a TIF). And doesn't LR's develop module use the same 'engine' or something, as ACR plug-in? So if your adjustments are basic, able to be done in either LR Develop, or PS ACR, all things being equal, choose to stay in LR?
ssprengel Apr 28, 2015 9:40 PM
PS RGB Workspace: ProPhotoRGB and I convert any 8-bit documents to 16-bit before doing any adjustments.
Why does one convert 8-bit pics to 16-bit? Not sure if this is an apt comparison, but it seems to me that that's kind of like upscaling, in video. Which I've always taken to mean adding redundant information to a file so that it 'fits' the larger canvas, but to no material improvement. In the case of video, I think I'd rather watch a 1080p movie on an HD (1080) screen (here I go again with my pixel-to-pixel prejudice), than watch a 1080p movie on a 4K TV, upscaled. But I'm ready to be wrong here, too. Maybe there would be no discernible difference? Maybe even though the source material were 1080p, I could still sit closer to the 4K TV, because of the smaller and more densely packed array of pixels. Or maybe I only get that benefit when it's a 4K picture on a 4K screen? Anyway, this is probably a different can of worms. I'm assuming that in the case of photo editing, converting from 8 to 16-bit allows one more room to work before bad things start to happen?
I'm recent to Lightroom and still in the process of organizing from Aperture. Being forced to "this is your life" through all the years (I don't recommend!), I realize probably all of my pictures older than 7 years ago are jpeg, and probably low-fi at that. I'm wondering how I should handle them, if and when I do. I'm noting your settings, ssprengel.
ssprengel Apr 28, 2015 9:40 PM
I save my PS intermediate or final master copy of my work as a 16-bit TIF still in the ProPhotoRGB, and only when I'm ready to share the image do I convert to sRGB then 8-bits, in that order, then do File / Save As: Format=JPG.
Part of the same question, I guess - why convert back to 8-bits? Is it for the recipient? Do some machines not read 16-bit? Something else?
For those of you working in these larger color spaces and not working with a wide gamut display, I'd love to know if there are any reasons you choose not to. Because I guess my biggest concern in all of this has been tied to what we're potentially losing by not seeing the breadth of the color space we work in represented while making value adjustments to our images. Based on what several have said here, it seems that the instances when our displays are unable to represent something as intended are infrequent, and when they do arise, they're usually not extreme.
Simon G E Garrett Apr 29, 2015 4:57 AM
With 8 bits, there are 256 possible values. If you use those 8 bits to cover a wider range of colours, then the difference between two adjacent values - between 100 and 101, say - is a larger difference in colour. With ProPhoto RGB in 8-bits there is a chance that this is visible, so a smooth colour wedge might look like a staircase. Hence ProPhoto RGB files might need to be kept as 16-bit TIFs, which of course are much, much bigger than 8-bit jpegs.
Over the course of my 'studies' I came across a side-by-side comparison of either two color spaces and how they handled value gradations, or 8-bit vs 16-bit in the same color space. One was a very smooth gradient, and the other was more like a series of columns, or as you say, a staircase. Maybe it was comparing sRGB with AdobeRGB, both as 8-bit. And how they handled the same "section" of value change. They're both working with 256 choices, right? So there might be some instances where, in 8-bit, the (numerically) same segment of values is smoother in sRGB than in AdobeRGB, no? Because of the example Simon illustrated above?
Oh, also -- in my Lumix LX100 the options for color space are sRGB or AdobeRGB. Am I correct to say that when I'm shooting RAW, these are irrelevant or ignored? I know there are instances (certain camera effects) where the camera forces the shot as a jpeg, and usually in that instance I believe it will be forced sRGB.
Thanks again. I think it's time to change some settings..

RAW output to an adobe rgb and srgb look identical in bridge but different in PS on wide gamut monitor.

Photoshop CS6. Wide gamut HP LP2475w monitor. Spider 3 Elite calibrated. Working space adobe rgb. When outputting a raw to Adobe RGB jpg it looks a bit whacked with color blotches/jumps in PS. The sRGB of it does not. BUT......in bridge they look identical. The adobe rgb jpg almost acts like viewing an image in a non-color aware browser on a wide gamut monitor. Like bridge shows it right but photoshop is showing it whacked out. I can't tell what is lying to me and if there is even a problem with the image. Here is a half second 2 frame gif alternating between the two from a screen cap. http://www.extremeinstability.com/hmm.gif Abrupt blotchy color changes with the adobe rgb when viewed in photoshop. And again, when you look at the two images in bridge they don't show that, they look identical.
Thanks,
Mike

I guess I now learned that Bridge only generates srgb previews. So I see them the same in there I guess. Looks like it comes down to the adobe space and jpg. Oddly enough an 8 bit adobe tiff covers it fine without breaking up. Can see the 3 on this gif. http://www.extremeinstability.com/3.gif

Everything is Green in RGB color space in Photoshop CS5 Mac

The image explains it all.
CMYK works fine, but RGB doesn't. The preview (in the channels pane) looks fine though.
Pixelmator had the same problem, but I fixed it by turning off color management in Pixelmator.
My question is, how can I fix this problem in a legal copy of Photoshop CS5 Extended?
My Monitor is a dell e193fp, and am running Mac OS X 10.7.2.
My video card is an ATI Radeon HD 4600, and I have a Mid-08 Mac Pro.

It could be your display profile, or a problem with the video card drivers.
I'd bet on the profile.
Also: RGB is not a colorspace. RGB is a color model, or color mode. A model or mode describes the number of channels, not the meaning of the channels.
sRGB and Adobe RGB are colorspaces. A colorspace describes the meaning of the color channels (a specific red, a specific green, a specific blue, a specific white point, a specific tone curve) for a given mode or model.
For a color mode or model, there can be many spaces.

Color space RGB or YUV?

Hello. What color space in premiere? RGB or YUV? How I can change color space? In Avid composer, when importing, i can select RGB or YUV. In premiere cc is there?
screenshot from avid

How does P Pro handle YUV (YCbCr) and RGB color spaces?

RGB / CMYK Color Space View

This might be a really basic question, but can anyone tell me how I can toggle between the "RGB Color Space View" and "CMYK Color Space View" in the color picker menu box? Thanks.

To the best of my knowledge, there is no CMYK Color Space View in the color picker. You determine whether the swatch you create is RGB, CMYK or LAB by clicking in one of the fields of each color model.
Peter

Color Spaces CIE and Adobe RGB

Similar Messages

Maybe you are looking for