I have been working on some T-shirt images where a Blank character is the base layer, after which outfits are added to create unique characters. Please see here for example. As you can see the images are very bright, & have that sheen to them.
Once finished. I want to keep the Outfit (all layers except the Blank character on the base layer) & store in a seperate file. This way I have 2 files, a blank, & a collection of outfits. Instead of a new file for each one. I know it's not the end of the world, but it has highlighted a problem for me.
The problem I am getting is, When I paste into the 2nd file. All the colors become dull & flat. I tried importing the swatch 1st so the colors were there already, but the color change still occurs. Can anyone shed any light as to what I may be doing wrong.
Thanks in advance of your suggestions. I'm sure someone here will see the obvious, where I missed it ![]()
Erm.. (skulks away because it was such a simple solution) Yes that was it thanks ![]()
One point I will mention though. If I change the original to CMYK, I get the dull colors as in the picture in the OP, but if I then change back to RGB, the colors change but not back to the original?
Aside from the color issue:
Once finished. I want to keep the Outfit (all layers except the Blank character on the base layer) & store in a seperate file. This way I have 2 files, a blank, & a collection of outfits. Instead of a new file for each one.
As described, I'm not understanding why you would want two files for this. If all the outfits are already in one file, why not just store the blank character as a Symbol in that same file?
If the outfits consist of elements (helmets, gloves, shirts, boots) that you are mixing & matching in various combinations, you might consider storing each element as a Symbol and using Replace Symbol to swap them out, in place.
If you want to store each unique combination as a set that can be recalled on-demand, you might consider storing each element in its own file, and use the Variables palette to capture the combinations as DataSets.
If you don't want to have individual files, you might consider having each element on its own top-level Layer, turn on/off the Layers' visibility as desired and store each combinaton as a View.
JET
If I change the original to CMYK, I get the dull colors as in the picture in the OP, but if I then change back to RGB, the colors change but not back to the original?
Think of it this way:
When you change from RGB to CMYK, for each color, you are changing three numbers to four numbers. There is a plethora of ways to do that. For example, the product of 2*3*4 (24) can be expressed as 1*2*3*4, as 2*2*3*2, as 2*6*1*2, as 4*5*2*1.6666, or...
So you change a three component value (RGB) to a four component value (CMYK) according to any of a plethora of algorithms for doing that. Now you have a new CMYK value; there is no record of where that CMYK value came from. Then you change the four component value (CMYK) "back" to a three component value (RGB) according to any of a plethora of algorithms for doing that. But there is no "back" to it, because there is no single 1:1 correspondence between an RGB value and a CMYK value.
JET
@JET - Thx for the ideas of how to set up the file. Never thought of using Symbols for the Blank or the seperate pieces. Now I know why I was messing up the colors, I will look again at the easiest way to keep the finished items. Very much appreciated.
Feel free to make one if you have time
, the download is on my deviantART on the OP link.
Sinner-PWA wrote:
...
One point I will mention though. If I change the original to CMYK, I get the dull colors as in the picture in the OP, but if I then change back to RGB, the colors change but not back to the original?
It is color matching and not color restoration which is impossible. When you convert colors from a wider color space like sRGB to a narrower color space like U.S. Web Coated (SWOP)v2, the color management tries to match the colors as much as possible but when the narrower color space doesn't contain the original colors they are clipped and this results in a color change. Then when the image is converted to a wider color space, if it encompasses all the colors of the image, you should see almost no color change except for some rounding of the values. Try changing the RGB color space in your Color Settings to AdobeRGB or ProPhoto and you should see no change in color appearance when converting from CMYK to RGB. The default sRGB color space has relatively narrower gamut and some parts of the blues and greens of the CMYK color space stick out of the sRGB color space because they are not fully encompassed from the sRGB color space.
You can have a very good idea about the different color spaces and compare them in a 3D plot if you check this site: http://www.iccview.de/content/view/3/7/lang,en/ you may need to install the 3D viewer plug in for your browser in order to view the 3D comparisons. And don't forget to drag you mouse to see the color spaces in the 3D plot from all sides. Holding Shift will rotate the view faster. Examining color spaces in 3D tells the whole story while 2D charts don't tell much.
For example here's a screen shot from an angle that reveals the parts of the CMYK space that stick out of the sRGB color space. When the image has colors in that parts for example pure cyan, the color appearance will shift when converted to sRGB. but will remain the same if you convet to AdobeRGB or ProPhoto.
North America
Europe, Middle East and Africa
Asia Pacific