>>Bridge generating sRGB previews for AdobeRGB tagged images maybe you're onto something, i hope you can get it figured out ... View more

. not sure what you are disagreeing with, but "RGB" is a color model ProPhotoRGB, AdobeRGB, sRGB, MonitorRGB are color spaces (and are based on ICC profiles) so your posts continue to be unclear to me, but most computer displays are either sRGB or AdobeRGB compliant devices, yes? that means they are limited to displaying colors within those specific color gamuts, yes? my ProPhotoRGB>MonitorRGB example is like "Soft Proofing" contrasty, oversaturated sRGB colors in a CMYK color space (out-of-gamut colors dull and change because they are being compressed/clipped, they don't translate well to the smaller CMYK colorspace because they don't exist there), yes? in ProPhotoRGB, the phenomenon is probably occurring on the monitor because some of your theoretical source colors cannot not be reproduced in the much smaller Monitor space i have no idea why Bridge is displaying differently than Photoshop, as you say, your uploaded examples of the unaltered PDI images looked like a spot on match to me in Ps & Br ... View more

in other words, to not exploit the color problems you are setting up using ppRGB source space, you would need a ProPhotoRGB proofing device (monitor) ... View more

does Bridge generate only sRGB previews of images (even when they have a wider gamut), as has been suggested by others on this forum, or am I experiencing a bug? i will guess it is safe to say any color-managed digital display is only "softproofing" a source document in monitor RGB and since displays are limited to sRGB or aRGB, it will have anomalies such as what you are seeing when monitor proofing extreme 'native' ProPhoto RGB colors of the types you are talking about because they have to be substantially clipped or compressed into the much smaller gamut proofing space there are those who frequent here with more knowledge than me, pls stay tuned... ... View more

Look at the Chromaticity diagrams of ppRGB and sRGB In another ProPhoto RGB Source> MonitorRGB example: Think of ProPhoto RGB (Source) as a semi-trailer truck full of RGB numbers that has to be fit inside a pickup truck bed (Monitor RGB) — a lot of RGB information needs to be compressed, remapped and/or deleted in real time to perform this routine, on-the-fly, behind-the-scenes Photoshop color management magic trick (Source> Monitor). User options to influence or control HOW the remapping of color information is calculated during a Profile conversion include two basic Rendering Intents: Perceptual & Relative Colorimetric. Perceptual is said to "compress" the color information into the smaller Space; Relative Colorimetric is said to "clip" the out-of-gamut information (and discard it). Photoshop Soft Proofing images (documents) on the monitor in various device-specific ICC Profiles can effectively demonstrate the visual effects of this remapping of color gamuts, including the dreaded out-of-gamut-color phenomenon. ... View more

Does Bridge on your system show previews with colors outside the sRGB gamut for images in wider gamuts (specifically ProPhotoRGB Bridge most certainly displays its previews like Photoshop (tagged Source colors are faithfully converted to MonitorRGB, Source>MonitorRGB) how else could both apps display tagged ppRGB and wRGB the same from your screenshots, it appears your Br and Ps are displaying the tagged PDI consistantly as expected at that point you should be able to run your own color patch tests and draw your own conclusions a color scientist may be able to clear this up better than me... IT IS THE THEORY THAT DECIDES WHAT WE CAN OBSERVE. -Albert Einstein ... View more

converting the WhackedRGB sample to sRGB does not result in any color changes (to my eyes), which would seem to mean that every color used in the sample is already within the sRGB gamut. that's a real tough statement for me to understand -- all of the PDI targets on my site were Converted to the packaged spaces from the original Photodisc freeware target (AdobeRGB) obviously, visually, moving extreme colors from theoretical ultra-wide-gamut spaces like ProPhotoRGB to much smaller color gamuts like Monitor RGB and sRGB and Print spaces is a challenge for the math and technology to maintain visual appearance between devices one can always argue that a monitor (or any device) is not even capable of "proofing" the full theoretical color gamut of ProPhotoRGB, but it a useful tool no less... ... View more

i filled the box in Photoshop as noted (Br right, Ps left) using sRGB as my Source profile i saved the .tif and opened in Br and Ps, then took this screenshot i opened my screenshot and Converted MonitorRGB to sRGB, Saved and uploaded it with sRGB profile embedded while i had a hair of wobble in both Hex values -- my Bridge is a virtual "match" to Photoshop display you are getting into color science, maybe one of the geniuses can take to to the next step and teach us both something... ... View more

it doesn't look like the WhackedRGB or ProPhoto samples have anything outside the sRGB range. not sure i follow, try opening the tagged Whacked & ProPhoto targets, then Edit> Assign Profile: sRGB The issue is back - the colors are very different! not sure i follow, i sampled your color spots (in your last screenshot post #12) and yes they have changes i would NOT expect, yet the PDI image remains close if not equal let me do a simple test here... ... View more

i have to step out, but be sure your Source documents have the proper embedded profile and that you "Use" that profile in Photoshop any display discrepencies after that are likely tied to any number of factors including OS, video driver and app bugs/behavior including hardware design limitations... ... View more

try doing the whacked example on the second monitor (I don't see any problem in your Whacked Example post #9) -- the CR2 example is hard for me to evaluate without getting eyestrain you should be using the profile embedded during the capture (not having to Assign it) on a Mac, a screen capture can deposit the file on the desktop (with the embedded monitor profile that can be a clue) not pasting it in Ps ... View more

your second screenshot just added (with profile embedded post #5) you have profile issues going on that you need to resolve... your over-saturated screenshot has ProphotoRGB Profile Embedded, it looks like you used Assigned Profile —— wrong move —— most screenshots should have Monitor RGB embedded (that's what you should upload so we can see what you see) as a whole not seeing a difference on the monitor... it is hard to tell because i don't know the correct profile to use (you stripped it, and Assigned the wrong, it looks like)... ... View more

i don't see any difference in the two apps BUT YOU DIDN'T INCLUDE A PROFILE IN YOUR SCREENSHOT you are applying the Whacked profile in Ps and are not in proof colors mode it looks like Br and Ps are displaying consistent on that monitor? try setting your Ps Color Management Policies to: that may help trap at least one of the problems... ... View more

here is how to verify what monitor profile Photoshop is using: there is a problem with some setups running two monitors off one video card (even off two separate cards) that Ps only uses the default monitor profile for both displays (that is likely what's going on, unless you have a source profile or softproof issues)... ... View more

to make the point more obvious, here's a TIFF in Bridge and Photoshop: try downloading a copy of the tagged WhackedRGB PDI reference image and open it in Br & Ps (use the embedded profile, do not convert colors) set Br and Ps side-by-side and take one screenshot of the two windows (embed the profile) keep your zoom ratios the same 25% 50%... Be sure to show the entire Ps window including the top bar with the name and the Document Profile showing in the low/left corner do this on each monitor post your results... ... View more

The basic problem is that Bridge displays images markedly differently than either ACR or Photoshop. those are all three color-managed application that each transform/convert colors to the monitor profile -- so if they are displaying differently -- i would first verify which source profile each app is using, and second, which monitor profile each app is displaying through on each monitor external monitor as the primary display (and the laptop monitor as a secondary) that's probably the debacle as you suspect, success is dependent on any number of factors including OS, video driver and app bugs/behavior including hardware design limitations... ... View more

OSX has a DARK PRINTING bug using Epson if you check 16 Bit in the print settings (uncheck 16 bit to resolve it) see http://www.gballard.net/photoshop/epson/cs6/#dark for more detailed info... ... View more

ROB DAY solved it (Bug 2)!!! Set your Profile Inclusion Policy to Include All RGB... I am not sure what the difference in wording is between "Include All RGB and Tagged Source CMYK Profiles" and what I was stuck on "Include Tagged Source Profiles" BUT the tagged image, text and gray box appear to all have retained their profiles using his setting: Futher, i just checked my original 10-image (five color spaces) PDF and the correct profiles were embedded in my five tagged objects still a problem with "Include All RGB and Tagged Source CMYK Profiles": my five untagged objects were assumed and tagged with Indesign's default RGB profile but at least I can predict the behavior now and work around it to do exactly what I want ... View more

> pdf inflated the orginal file size by the factor 10 I should have warned you about that, Uncheck "Preserve Photoshop editing capabilities" this extra step should look pretty good and make the doc even smaller: Do not Downsample Compression: JPG Image Quality: High or Max ... View more

actually, that was InDesign> Export PDF but the secret word is: COMPRESSION CS6 Screenshot, Save As: Photoshop PDF ... View more

compression (center box) ... View more

okay, here is Indesign> Export PDF (Print) BUG 2 in simple PDF: http://www.gballard.net/sRGB_Strip_Profile_Test.pdf NOTE: I have an error in the PDF, give me 30 minutes to update it...(updated, good to download both links) If an object is based on InDesign's Working profile, this workflow strips its profile regardless of Export> Output settings If you don't trust my screenshots, here is the project folder http://www.gballard.net/IDexportBug.zip It would be great if this was fixed (or at least looked at), too ... View more

can you do anything with BUG 2? ID> Export PDF (Print) would be an extremely useful tool if it did what the Adobe dialog says it does in plain English:        Profile Inclusion Policy: "Include Tagged Source Profiles" EXAMPLE: i produce a simple sRGB poster .tif in Photoshop (save with embedded sRGB profile), i Place that .tif in InDesign (Indesign Working RGB: sRGB) i Export> Adobe PDF (Print) InDesign> Export Adobe PDF (print)> Output> Color: Color Conversion: "No Color Conversion" and Profile Inclusion Policy: "Include Tagged Source Profiles" i save and reopen the exported PDF in Acrobat Acrobat's Object Inspector says it is "DeviceRGB" (my embedded profile was stripped) -- this was 100% repeatable in my tests and it always stripped Indesign's Working profile in other words, if my Indesign Working RGB is the same as one of my embedded profiles, the profile is stripped on Export to PDF (Print) ... View more

RIGHT ON!!! Clear & Convincing!!! I Converted your PDF using these settings (and reproduced the bug): ... View more

ya, but five profiles are pretty dramatic:) on the Indesign (bug 2) if you are testing Whacked RGB set InDesign Working RGB: Whacked RGB (Preserve Profiles) and Adobe ACE, Place the your Tagged WhackedRGB image, Export it to PDF using my settings (below), NO CONVERSION, INCLUDE TAGGED SOURCE PROFILES check the (formerly Tagged) Whacked object with Object Inspector (it has become "DeviceRGB" its profile has been stripped) ... View more

I think I have it now. great, Andrew, i really appreciate your time... gary ... View more

man, this a black hole of time (let me know if you want me to take your name/link off my page, i have very thick skin) Build from scratch: open my iPhoto Tutorial images (the 10 .jpg images) in Photoshop and save each one as Photoshop PDF as marked (tagged/untagged) (don't alter my original images) then drag one PDF into Acrobat to open it and then drag the other nine .pdf into its Pages Panel, then Save the PDF or just DOWNLOAD my original Ps PDF Next open the downloaded or Saved PDF In Acrobat go to: View> Tools> Print Production> Convert Colors dialog, and select Convert Command: Convert to Profile; Conversion Profile: try ProPhoto (i don't think it matters much what profile you target to see my point) Save and reopen at that point the Tagged files should be obvious Acrobat's working space was assumed on all 10 RGB objects and Converted to Destination ... View more

i guess my point to people who read bug reports would be to download my test Photoshop pdf (assembled in Acrobat) and try Convert Colors -- as outlined -- the fact its five embedded RGB profiles are stripped and Working RGB is assumed, then Converted to Destination -- should take less than 5 minutes to complete and be proof enough to look at the problem in more detail likewise download my test .indd project folder zip, Export PDF (Print) -- as outlined -- and check for the missing embedded profile (Indesign's RGB working profile) -- should take less than 5 minutes to complete and be proof enough to look at the problem in more detail i believe both problems are 100% reproducable (with almost no time/effort) if we can get on the same page ... View more

my typo #48 the tagged Ps PDFs dispay properly when Placed in ID and they Export (Print) properly to PDF, and display properly in Acrobat should be: the tagged Ps PDFs display proper in my original PDF (that set was never placed in ID) remember post #34: i took my iPhoto Tutorial images (the 10 .jpg images) into Photoshop and saved each one as Photoshop PDF as marked (tagged/untagged) then i dragged one into Acrobat and then the rest into its Pages Panel, then Saved/uploaded it that's how i packaged my original Ps PDF AR: But this has nothing to do with a Photoshop PDF versus Photoshop TIFF initially used to create the document? this is confusing because i actually found and discussed two "bugs" (and never used .tif in my tests) ONE: Photoshop PDF> Acrobat> Convert Colors (stripped profiles) OUTLINED HERE TWO: Photoshop .jpg> Indesign> Export PDF (Print) (ID's Working profile stripped) OUTLINED HERE scroll down a bit further to: ANOTHER ACROBAT BUG? I found and confirmed one very irritating anomaly in this InDesign> Export PDF (Print) process: Acrobat's Object Inspector is reporting the Tagged sRGB image as Colorspace: "Device RGB" (Untagged) — its embedded profile was stripped during InDesign's export process despite its Profile Inclusion Policy was set to "Include Tagged Source Profiles": these two claims are both very easy for me to predict, observe and prove (and i've been over them many times) ... View more