If you want to ensure new documents are set up with the correct profile, use Edit > Color Settings.) (Note that this only changes the currently open document.
#Photoshop match color between images update
Now, every RGB image that does have a color profile embedded should look the same, but all the RGB images that have no profile will update and probably look far better. Here you can assign the sRGB profile and then click OK.
So if it says Adobe RGB or something like that, and if you want to change it to sRGB, then click Cancel here, and then choose Edit > Assign Profile: You can find it by choosing Edit > Convert to Profile:īut don’t change the profile here! Convert to Profile is good for learning about the document, but it can cause bad things to happen if you change anything here. Check to see what your InDesign document’s default RGB profile is.Photoshop saves profiles by default in the Save As dialog box, but it’s off in Save for Web. If you can, try to ensure every RGB image has a color profile saved with it.OK, so what can you do about this problem? Here are a couple ideas: I’m just saying it’s okay if the RGB profiles are different.) What to Do About It (By the way, you do want your default CMYK profiles to match among all the Adobe programs. Because when you use sRGB, then all those web images and images from other less-reliable-than-Photoshop sources will probably look right when you place them.
You almost certainly want your InDesign documents to have a default RGB profile of sRGB. And so a lot of people synchronize all these settings, and the result is that InDesign’s default RGB profile gets changed to Adobe RGB or some RGB other than sRGB.Īs I wrote over a decade ago, it’s a good thing to have your programs unsynchronized, and have different RGB defaults! InDesign’s normal “default RGB” profile is sRGB, but Adobe makes a big stink about how you should make sure your RGB and CMYK color profiles are all the same in Photoshop and InDesign and Illustrator. And in those situations, it applies its default RGB color profile. If there’s no embedded profile, then InDesign has no idea what the colors in that image are supposed to mean. This is why the colors may look really different when you import an image you found on the web, or exported from some simple pixel-editing program.
The reason is that InDesign knows what the colors are supposed to look like in the tagged image (the one with the color profile in it), but it has no clue what the colors look like in the one with no profile. So why do they appear so different? (If you don’t care and you just want to fix it, skim through the next section and head right for “What to do about it.”) Tagged vs. Holy mackerel! Remember, those two images look exactly the same in Photoshop the RGB values are identical. OK, now look what happens when I turn on View > Overprint Preview: But when I choose View > Preview on CPU (which turns off the new-and slightly buggy-GPU rendering), you can see the differences more: Now, you probably can’t tell the difference right now, right? On my screen there is a very tiny difference. Here’s one common example: I’ve placed two images into InDesign… the images appear to be identical, but there’s one important difference: one of them was saved with a color profile embedded in it, and the other was not (also called “untagged”). While there are a number of possible solutions, the most likely problem is: There’s a color profile mismatch somewhere! And often that mismatch is due to the fact that one or more images does not have a color profile embedded in it. You place two images that have identical colors in them… but they look different! This can drive you crazy.
0 kommentar(er)
