Skip navigation
Currently Being Moderated

Color Management in Bridge CS6

Sep 2, 2012 11:04 AM

Tags: #color_management #bridge_cs6

Hello,

 

I'm having a strange color management issue in Bridge (64 bit). Essentially, Bridge is not displaying images in either the thumbnails or preview pane using the correct color profile.

 

Background: I'm on Windows using a dual monitor setup (both independantly calibrated) but I have the issue even when I use only one monitor. Photoshop has no issues with color settings. I've tried resetting all settings (hitting Ctrl as Bridge starts). I've tried purging my cache and having Bridge generate monitor-size previews.

 

The weirdest part is when I start Bridge, for a split second images appear to be in the correct profile, and then Bridge adjusts everything to the wrong color profile.

 

Any thoughts?

 

Thanks!

 
Replies 1 2 Previous Next
  • Currently Being Moderated
    Sep 2, 2012 11:07 AM   in reply to Nrbelex

    Nrbelex wrote:

     

    The weirdest part is when I start Bridge, for a split second images appear to be in the correct profile, and then Bridge adjusts everything to the wrong color profile.

    What you are probably seeing here is the embedded thumb that shows briefly before being replaced by your HQ preview.  If you are using raw images this likely means your default ACR settings/color profiles are not correct. 

     
    |
    Mark as:
  • Currently Being Moderated
    Sep 2, 2012 11:39 AM   in reply to Nrbelex

    When it comes to color issues I am definately a dunce.  Here is a link that may shed some light on issue.  http://forums.adobe.com/thread/891077

     
    |
    Mark as:
  • Currently Being Moderated
    Oct 16, 2012 12:26 PM   in reply to Nrbelex

    I am having ALMOST exactly the same problem as you are and I, also, can't find a solution. This is a list of the similarities and differences:

     

    1. I have dual monitors, but only the primary (and wide-gamut) monitor is calibrated. The second is only for holding palettes/panels and less important documents.

    2. When using my calibrated monitor, I do NOT see the right preview at any time. (I expect it to be wrong in the secondary one, and it is, but there are differences between them.)

    3. From the moment of launch all the previews are either darker than they really are; completely changed; or both. (Ex: dark pink becomes a muddy brown).

    4. When viewing the same documents using Bridge CS4, all previews are as they should be (that is, CS4 is capable of interpreting sRGB, AdobeRGB, and ProPhotoRGB correctly). CS6 misinterprets all three.

    5. When viewing them in CS6, however, they look like documents sent to print with the wrong profile attached.

    6. I checked my Bridge Preferences in CS4 and in CS6 and can't find what I'm doing differently or any settings that might govern color rendering.

    7. None of the images look like the Bridge thumbnail when opened in Photoshop. I even converted them to sRGB and e-mailed them to myself. The e-mail program renders them correctly (matching the Photoshop sRGB version) and so does Windows when I view thumbnails.

    8. This is the strangest uniquely CS6 Bridge behavior: A layered tif or psd image (in whichever color space) might display well. The flat version of the same image (layer>merge visable) gets distorted almost every time. (Both versions look fine in Photoshop CS6, CS4, Windows, and Bridge CS4).

     

    Bridge CS6 is completely unreliable!

     
    |
    Mark as:
  • Omke Oudeman
    4,001 posts
    Nov 27, 2004
    Currently Being Moderated
    Oct 16, 2012 12:50 PM   in reply to ckc48

    Can you specify your system details and computer details

     

    Don't have dual monitors my self but seem to recall there is a system setting (at least on a Mac) to specify the primary screen

     

    Also can you tell if you own a suite or just PS as stand alone. What are your color settings in PS itself.

    In Bridge you can reach Camera Raw preferences, can you check the default image settings and see if Apply Auto tone adjustment is Deselected.

     

    And have you also tried to purge cache for a selected file (use right mouse click menu for this when pointing to the selected file(s) and see if this changes things.

     
    |
    Mark as:
  • Currently Being Moderated
    Oct 16, 2012 3:13 PM   in reply to Omke Oudeman

    I have the stand-alone Photoshop CS6.

     

    I have Windows 7 Professional with Service Pack 1.

     

    My dell computer has an Intel Co i7 Processor, 12 GB of RAM, 64-bit.

     

    My color settings are set for ProPhoto as default. I process and archive in ProPhoto 16-bit @320 ppi but sometimes save a flat 72ppi copy in 8-bit sRGB.

     

    I haven't tried to purge the cache for the individual images, but I did uncheck "apply auto tone adjustment" and some of the images did improve. In particular, the pink that turned muddy brown did improve. I think that this setting, which slipped past me somehow, accounts for some (if not most) of the problems I've been having. It didn't occur to me to check ACR settings because some of the files were not photographs, but rather created on the computer with Photoshop.

     

    There is one other problem I've been having with some images--and I'm not 100% sure this happened under CS6, but I believe it did--and it's that some images that I KNOW previously had a profile associated with them, now appear as "untagged." On one folder over 70 images lost their profile and over 200 did not. This was an archival folder on my computer (not on an external drive) which I haven't needed again until just recently.

     

    Luckily, I had backup copies of the originals elsewhere and can re-save them from other media. But, still, it makes me nervous that this type of thing can just happen. (I don't want to convert to a profile  now because I'm afraid they will be altered in the process and these are files that were published once, need to be published again, and I want the 2nd edition to match the first).

     

    Thank you so much for your help. A big part of my frustration has been eliminated in one simple unchecking, but I never would have thought to do so on my own!

     
    |
    Mark as:
  • Omke Oudeman
    4,001 posts
    Nov 27, 2004
    Currently Being Moderated
    Oct 16, 2012 3:35 PM   in reply to ckc48

    There is one other problem I've been having with some imagesand I'm not 100% sure this happened under CS6, but I believe it didand it's that some images that I KNOW previously had a profile associated with them, now appear as "untagged." On one folder over 70 images lost their profile and over 200 did not. This was an archival folder on my computer (not on an external drive) which I haven't needed again until just recently.

     

     

    Glad unchecking the auto tone adjustment solved the biggest of your problems. You have quit an impressive way of saving files, will take up a lot of disk space

     

    However, Bridge is not capable of converting to a color space (it needs Photoshop for that or via tools / batch menu but that is using PS also) nor do I believe it will be possible to rip the color space of the file. However, having a regular workflow with always working in ProPhotoRGB 16 bit you will have to convert the files one time to 8 bit when sending to publish. And at the point of sending files without saved colorspace the problem might start, before that you can just assign the colorspace again because you did not alter the colors or space in any way in the meantime as it seems.

     

    And keep in mind that some file type (especially Raw and DNG) appear as untagged in the metadata panel because you need to choose the colorspace the moment you export or convert those files.

     
    |
    Mark as:
  • Currently Being Moderated
    Oct 16, 2012 6:39 PM   in reply to Omke Oudeman

    I guess it will always be a mystery. Luckily, I had backups ,and backups of the backups. The publisher had asked me for Adobe RGB files (at 350 dpi!) and they converted them to their particular CMYK profile (which is something I wasn't capable of doing anyway). It was something like 14 DVD's. I got my DVD's back and they were all correctly tagged.

     

    But I wasn't worried about the RAW files being untagged--that's the nature of the beast--but files that I had saved before and never touched again until just recently did concern me. I guess I'll never know what happened--maybe when I transferred the files from one computer (XP/32bit) to another (W7/64bit). Could be, I suppose. If Bridge can't do it, that's the most likely culprit.

     

    As for my workflow, YES!!!, very big files! But, since most of it is of artwork, which means color fidelity and gradiation are essential, so I have to throw everything at it. Worst of all, I never know which file will be needed for printing in a book, which might be printed as a huge giclee, and which will just sit there forever, so I also save as big (dimension-wise) as I can--a real mess. My cloud storage company has been backing up my computer for two years and still hasn't finished! (I guess they will never catch up since I keep adding new files).

     

    Again, thank you!!

     
    |
    Mark as:
  • Pierre Courtejoie
    7,038 posts
    Jan 11, 2006
    Currently Being Moderated
    Mar 26, 2013 4:00 AM   in reply to Nrbelex

    Hello!

    What is the file format of the files with incorrect color rendition?

    Did you check in the preferences if Camera Raw is preferred for TIFF and JPEG? If its default setting is to desaturate, all new previews will look desaturated for TIFF and JPEGs...

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 26, 2013 9:13 AM   in reply to Nrbelex

    Nrbelex wrote:

     

    Bridge is using a markedly smaller gamut, so all photos look flat compared to once opened in either ACR or Photoshop.

    Bridge previews all images in sRGB regardless of the workspace. This is because Bridge generates previews in 8-bit sRGB (relative colormetric intent) and stores them in a cache as JPEGs.

     

    Sorry if this has already been said. I didn't read the whole thread.

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 26, 2013 10:17 AM   in reply to Nrbelex

    To follow up on my post #1 read this tutorial for how to take control of camera raw.  http://www.luminous-landscape.com/tutorials/cr-auto.shtml

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 26, 2013 11:52 AM   in reply to Nrbelex

    As I stated before your symptom of "I just want to emphasize that when Bridge first opens, for just a moment the colors are more saturated and may be in the correct gamut, but then immediately the colors desaturate." sounds exactlly like you are viewing the embedded jpeg profie and it switches to your default settings.  I know you state they are correct, but would double check.  Do you have HQ thumbnails selected?  In Camera Raw preferences do you have the correct boxes  unchecked so Bridge does not  automatically change your settings?

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 26, 2013 12:00 PM   in reply to Curt Y

    Curt Y wrote:

     

    As I stated before your symptom of "I just want to emphasize that when Bridge first opens, for just a moment the colors are more saturated and may be in the correct gamut, but then immediately the colors desaturate." sounds exactlly like you are viewing the embedded jpeg profie and it switches to your default settings.

    I don't think so, Curt. I frequently see this behaviour in Bridge, during thumbnail generation. I think what happens is that Bridge initially displays thumbnails with an sRGB display profile, and when it's finished generating thumbnails, it switches them to the monitor profile. This would be more apparent with a wide-gamut display.

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 26, 2013 12:21 PM   in reply to Nrbelex

    The options to change thumbnails is in toolbar right side.  The camera raw preferences I was refering to are in edit/camera raw and not in ACR.  But yammer may be correct, he is much more in tune to quality issues than I am.

     
    |
    Mark as:
  • Omke Oudeman
    4,001 posts
    Nov 27, 2004
    Currently Being Moderated
    Mar 26, 2013 3:44 PM   in reply to Nrbelex
    If that's true, then (barring a bug) shouldn't the opposite happen? Shouldn't they initially appear desaturated, then it should switch to the wide-gamut monitor profile and appear properly?


     

    Don't know if it is a bug or not possible but could you specify if you have only PS or do you have a Suite with other apps. In the later check the color settings for Bridge to match those of you having selected (saved?) in Photoshop. Otherwise if you have only PS and Bridge then Bridge chooses the color settings of PS automatically.

     

    Unfortunately I do next to nothing about Windows set up but my first change in your case would be in the color settings for PS and set RGB space to Adobe RGB (1998) and save it as setting (in case of a Suite you can chose this settings in the color settings for Bridge)

     

    And your color management specs (from Spyder Data color mention sRGB?)

     

    here is screenshot from my set up (using a useful color comparing RGB / CMYK provided by Guy Gowan www.guygowan.com ) I copied the original jpeg sRGB file and converted it to a new ProPhoto 16 bit file. saved and compared in Bridge and PS.

     

     

    ColorsBridge.jpg

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 27, 2013 12:27 AM   in reply to Nrbelex

    Nrbelex wrote:

     

     

    YammerP,

     

    Bridge previews all images in sRGB regardless of the workspace. This is because Bridge generates previews in 8-bit sRGB (relative colormetric intent) and stores them in a cache as JPEGs.

     

    If this is true, it's pretty shocking. If Bridge only generates sRGB previews and thumbnails, then all people who use any gamut outside of sRGB will never see an accurate representation of the colors of their images in Bridge. Really!?

    Why never accurate? All it means is that any colours outside the sRGB gamut will be clipped; all colours within will be rendered exactly the same.

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 27, 2013 12:32 AM   in reply to Nrbelex

    Nrbelex wrote:

     

    Yammer P,

     

    Would you elaborate on this a bit?

     

    I think what happens is that Bridge initially displays thumbnails with an sRGB display profile, and when it's finished generating thumbnails, it switches them to the monitor profile. This would be more apparent with a wide-gamut display.

     

    If that's true, then (barring a bug) shouldn't the opposite happen? Shouldn't they initially appear desaturated, then it should switch to the wide-gamut monitor profile and appear properly?

    I know, it sounds weird, but that's the way it would happen. If you display an image using an sRGB display profile on a wide gamut monitor, you will see over-saturated colours. Think Internet Explorer for Windows: it only does half the job, and it always uses the sRGB display profile, meaning that photos look awful on my system—same with photo attachments in MS Office (not colour-managed).

     

    If you remember that a profile is just a matrix of RGB numbers from 0-255, and that a wide-gamut monitor translates these numbers to more vivid colours than sRGB, you will see that a preview with an sRGB display profile will be over-saturated, until this is corrected.

     
    |
    Mark as:
  • Omke Oudeman
    4,001 posts
    Nov 27, 2004
    Currently Being Moderated
    Mar 27, 2013 1:52 AM   in reply to Nrbelex

    Omke, thanks. Would you mind embedding your monitor profile in your screenshot? Can't actually do a comparison otherwise.

     

     

    As a Mac user I don't have that info for color management like Windows provides, I only could provide a lot of info using the colorsync utility but A it is only technical and B it is in Dutch

     

    However I use a relatively old 30" Apple Cinema Display and a ATI Radeon HD 5770 with 1 GB VRAM.

     

    My display get's profiled with X-Rite Colormunki and inhere the white point target is D65 and the luminance set to around 120 (which in reality is about setting Brightness of the monitor to half).

     

    But like Yammer states, also to my opinion the monitor profile is not causing this because it only shows the results of the application itself. My screen shows 2 almost matching (maybe a slight difference in saturation for Bridge but hard to spot) and yours show 2 very different results, yet both in 1 view on the same monitor.

     

    Can you report back about my other questions regarding using a Suite, matching color settings in Bridge and also try to use PS RGB settings at Adobe RGB to see if this shows other results.

     

    It looks like you have set the files in Bridge to show proof colors in some CMYK colorspace while PS shows the real colors.

     

    And if this would be a bug it will be a very special one caused by a rare combination of components because this is certainly not normal behavior.

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 28, 2013 4:32 AM   in reply to Nrbelex

    Sorry. Been a busy week...

    Nrbelex wrote:

     

    The following look the same to me in Bridge but different in Photoshop:

     

    ProPhotoRGB Gamut Extremes.jpg

     

    sRGB Gamut Extremes.jpg

     

    However Yammer's statement...

     

    Bridge previews all images in sRGB regardless of the workspace. This is because Bridge generates previews in 8-bit sRGB (relative colormetric intent) and stores them in a cache as JPEGs.

     

    ...makes a lot of sense. If that is the case, both images above will look the same when downloaded and previewed in Bridge.

     

    Would anyone with a wide gamut monitor mind testing that out?

    I have a wide-gamut monitor, and I can confirm that I see the same as you:

    Both images look the same in Bridge, and markedly different in Photoshop (and Firefox*), with the ProPhoto image much brighter (especially the four patches on the right).

     

    If you do a RC conversion to sRGB in Photoshop they look the same.

     

    BTW, no need to keep saying "if Yammer is correct", I am 100% confident that this is the way Bridge does still image previews. Just look at your cache folders for proof.

     

    (* although, for some reason, the two image thumbnails in your above post above look the same until they are clicked on. Must be something to do with the Jive forum software.)

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 29, 2013 12:07 AM   in reply to Nrbelex

    That's (one of the reasons) why Bridge has no editing capabilities whatsoever.  It would be nonsensical to catastrophic if it did. 

     

    One has to keep in mind that Bridge is just an ad-hoc image file browser.  It essentially was created as nothing more and nothing less than Photoshop's file browser and it was called exactly that in its first iteration.

     

    Using the Bridge Preview panel to attempt to judge colors is futile.

     

    I have on numerous past occasions posted on the fallacy of the totally artificial Adobe Creative "Suite" concept, for which Bridge was jerry-rigged to somehow mimic the function of a connection element among the applications that were presented as a "suite", e.g.:

     

     

    Inconsistency between or among applications in the artificial "suites" should come as no surprise.

     

    The "suite" concept is a fabrication of Adobe marketing and bean-counting types.  The engineering teams are totally independent of each other, they are not only in different buildings but in different cities and states of the American Union, even in different countries.

     

    The fact that they have little if any communication among them is highlighted by requests occasionally made in these forums by top Adobe engineers to let the other teams know when there are problems in one application that impact our workflow in another one.

     
    |
    Mark as:
  • Omke Oudeman
    4,001 posts
    Nov 27, 2004
    Currently Being Moderated
    Mar 29, 2013 2:58 PM   in reply to Nrbelex

    Nrbelex wrote:

     

    Anyway, it looks like Bridge is showing you colors outside sRGB, which means I'm probably experiencing a bug. [I believe there's a flaw in your workflow. If the file was originally sRGB, you can't convert it to a wider gamut without being sure the actual values of the new image are correct. Although your colors also look out of the sRGB gamut, so not sure what's going on there.] The following look the same to me in Bridge but different in Photoshop:

    Sorry, when editing a forum post it does not seem to get updated in the mail nor do all the screenshots appear.

     

    I only use ProphotoRGB and 16 bit for critical situations with blue skies or interiors (more detail preserved), it leaves me more room for editing contrast before banding and posterisation steps in. For normal work I only use 8 bit AdobeRGB (when the 16 bit is finished I also convert to 8 bit AdobeRGB) for the simple reason that for the majority of my work my clients need 8 bit AdobeRGB (magazines, press etc) and often convert some again to sRGB for the simple fact 'normal' (non business) people have everything set to sRGB so converting for the job needed makes sense to me.

     

    So to show you again I have little to none difference between Bridge and PS here is a screenshot of my whole 30" screen (a messed up workspace for PS because otherwise I could not get the screenshot showing only the image floating).

     

    ColorsBridge16bitProPhoto.jpg

    The files are only edited for a better Dynamic Range in Photomatix and need more processing so they are halfway and yet not finished. However it shows that it does not matter for me starting with an original DNG or converting from jpeg, the result is the same.

     

    And in agreement with Station-Two, I never use Bridge for color judgement. 

     
    |
    Mark as:
  • Omke Oudeman
    4,001 posts
    Nov 27, 2004
    Currently Being Moderated
    Mar 29, 2013 4:43 PM   in reply to Nrbelex

    I also don't use Bridge for any adjustments. But I do (did) use it for appraising shots before I brought them into Photoshop. Color is obviously a part of that appraisment, so Bridge is not helpful in that sense.

     

     

    about A:

    I don't get that, I have a custom made monitor profile based on D65 and with or without this profile the only difference one would spot would be in the total picture, this screenshot shows what I see and that is not as much difference between the Bridge thumb and preview (and in the metadata placard you can see they are 16 bit ProPhoto with on top of it the floating PS panel with the same image. It is one picture of one screen, without my monitor profile (and without knowing what happens during the adding process to the Adobe site) or with, the difference between both applications would not change, only the total picture. (or I really don't understand anything anymore about color management )

     

    about B:

    There you have a point but this was a current project at hand and at this moment there is a bit over saturation in the wood. In real life I also almost never have to deal with the bright colors of your example. I don't want to go again messing my workspaces to create a screenshot for the files you provided but I can assure you I have less to none difference between both files in both Bridge and PS, like I never have seen your problem on my current computer (Mac Pro, 2 x 2,4 6 core intel Xeon mid 2012 and a lot of RAM and SSD etc including ATI Radeon HD 5770 1024 MB VRAM running OSX 10.8.3) as well as my former MacPro with same graphic card - and two others - that I used since 2008 during OSX 10.5 to 10.7 with all used versions of CS.

     

    And as for the quote, I also never make my choices based on colors for DNG in Bridge, in fact, I always shoot with manual WB set to 5500 K, whether in daylight or artificial light, I just don't bother because I want my colors to be adjusted in ACR and refined the way I want them in PS. The plus side of manual WB is that all colors are off in the same way and can be adjusted in the correct direction in one go for a series

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 30, 2013 3:05 AM   in reply to Nrbelex

    I think Omke has a MacPro, or something like that. I think these use IPS displays, which are all wide-gamut, as far as I know. Certainly, my HP LP2475w is IPS and has a close-to-AdobeRGB gamut. I bought mine after being impressed by a friend's MacPro.

     

    As Nrbelex correctly points out, a screenshot is ill-defined colourwise unless accompanied by a colour profile, or, more usually, correctly converted to sRGB (which would be inappropriate in this case).

     

    I made a Photoshop action for making screengrabs. After using the Windows Alt-PrtScn hotkey for grabbing the current window, Photoshop creates a New File (which is automatically sized for the grab in the buffer) and pastes the RGB into the document. The action then Assigns the monitor profile to the document. Finally, the document is Converted to sRGB. Clearly, this last step isn't much use here, and is really only for standard web use, where gamut isn't important.

     

    How this might work on a Mac I have no idea. I don't know anything about the Mac screen grab process.

     
    |
    Mark as:
  • Omke Oudeman
    4,001 posts
    Nov 27, 2004
    Currently Being Moderated
    Mar 30, 2013 5:09 AM   in reply to Yammer

    How this might work on a Mac I have no idea. I don't know anything about the Mac screen grab process.

     

    I have an Apple Cinema Display 30" and no idea if this is a wide Gamut, I believe so but will have to do more digging to find out and at this moment time is limited. Just tried a bit of rereading on the sites of G. Ballard but it has been a while I looked at this and there is plenty to study. Using Safari all is color managed for the example also shown somewhere on this or the related thread and this always has been so.

     

    Also I'm not sure about the profile for screenshots but nevertheless I keep stating that the screenshot shows what I see, no significant difference between Bridge and PS. Regardless what profile you have are use to see my screenshot, under- or over saturated, the difference between both applications on the same screen is not there as you clearly have in the OP problem.

     

    I do use bright colors every now and then but don't have them at hand at this moment, (on our calendar spring already started last week but this morning there was a bit snow so bright and nice colored flowers are also no option at this moment I'm afraid…) and the shocking difference of the earlier provided examples will be noticeable for many occasions and also unmissable. I never have seen this.

     

    So the used Color settings and monitor for your windows set up seems to do something with Bridge that I can't replicate on my Mac.

     

    When having more time I will try to get back, for the moment I step a little back.

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 30, 2013 5:58 AM   in reply to Omke Oudeman

    Omke Oudeman wrote:

     

    I have an Apple Cinema Display 30" and no idea if this is a wide Gamut, I believe so but will have to do more digging to find out and at this moment time is limited. Just tried a bit of rereading on the sites of G. Ballard but it has been a while I looked at this and there is plenty to study. Using Safari all is color managed for the example also shown somewhere on this or the related thread and this always has been so.

     

    Also I'm not sure about the profile for screenshots but nevertheless I keep stating that the screenshot shows what I see, no significant difference between Bridge and PS. Regardless what profile you have are use to see my screenshot, under- or over saturated, the difference between both applications on the same screen is not there as you clearly have in the OP problem.

    I just did a bit of research, and the available information is scant, but it seems that although the Apple 30" Cinema display is quoted to be "wide gamut", it is said to be about 70-75% of AdobeRGB, which isn't actually very wide. It may be "wide gamut" in the same sense that cassette tapes were often described as "low noise" (i.e. marketing speak). One source actually said they were sRGB, and not wide at all.

     

    If that is correct, it will be difficult to see the difference between images containing colours outside the sRGB gamut, even in colour-managed applications, as the wide gamut images will be restricted to the display profile, which will be quite close to sRGB.

     

    The thing about screen shots is that you check them on your own computer, not someone else's. Certainly in Windows, all a screenshot does is record the display's pixel RGB values--not the colour space. If you then display this screen grab with the same colour space, it will look the same. If you display it with a different colour space, it will look differently. This is why Nrbelex suggested embedding the display profile.

     

    Here is an illustration of a screen grab with and without an embedded display profile...

     

    Wide gamut screen grab with display profile assigned

    card-tagged.jpg

     

    Wide gamut screen grab with no profile assigned (therefore assumed to be sRGB)

    card-untagged.jpg

     
    |
    Mark as:
  • Omke Oudeman
    4,001 posts
    Nov 27, 2004
    Currently Being Moderated
    Mar 31, 2013 6:06 AM   in reply to Nrbelex

    And that would explain it. If the monitor is not wide gamut, there won't be any perceptible difference - plain and simple.

     

     

    Since I recently bought a new 1Dx, a new 24-70mm and a new Mac Pro I first have to earn a little more money beforeI can invest in a new monitor to confirm this definitively….

     

    Until now my thoughts about a new monitor are down to two brands, Eizo and Quato, but I want a large screen and they don't come cheap

     
    |
    Mark as:
1 2 Previous Next

More Like This

  • Retrieving data ...

Bookmarked By (0)

Answers + Points = Status

  • 10 points awarded for Correct Answers
  • 5 points awarded for Helpful Answers
  • 10,000+ points
  • 1,001-10,000 points
  • 501-1,000 points
  • 5-500 points