But its not is it? If you convert RGB to multichannel the colour balance changes. To me this indicates that one or more of the seps has changed density. If you change back to RGB again the colour imbalance is corrected. Doesn't this mean that photoshop 'remembers' the changes its made and corrects it. How and why does this occur - and why?
I'm confused as you can tell...
David--
I appreciate the fact that you're confused, and it seems like you're getting hung up on how PS is presenting the data to you vs. the actual data contained in the image.
First off, don't take my word for it, try this for yourself. Start with a nice, colorful image (easier to see the difference in the 3 channels).
Take 1 copy of it, keep it as RGB, invert it, and split the channels.
Take a second copy, convert to Multichannel, invert it, and split the channels.
Now compare the inverted R channel (from RGB) to the inverted cyan channel (from Multi.)
Compare G channel to magenta channel.
Compare B channel to yellow channel.
Each pair of images should be identical.
Now for understanding why the image appearance changes in Photoshop...I hope you can follow me on this.
If you've set up PS correctly, there is a working space (like AdobeRGB, ProPhoto, etc.) assigned for RGB. Because of this profile, PS understands how to translate the R,G,B color numbers stored in the file into colors on the screen.
Now, let's assume you convert this image into a CMYK color space. There's also a default profile for this color space. Now, the default profile (typically, "US Web Coated SWOP v2), has a smaller gamut in some areas than even sRGB, so when you convert from your RGB working space to the CMYK space, PS uses the profile information to map the colors in the RGB space that are outside the CMYK gamut, to colors that are in-gamut (via the different "Rendering Intent" choices). This actually changes the information in the image, and a deep, pure blue in the original may become muddy and slightly purple, for example. If you were to then convert that image back to RGB, those slightly duller, muted colors would remain, because the information in the image was actually changed (think of it as "clipping", like if you overexposed on a digital camera).
You're operating in a 3rd case. There is no default profile associated with multichannel mode. As a result, PS uses a purely mathematical transformation to get from RGB values to CMY values, but it has no profile information to tell it how those CMY values relate to actual colors, so it uses some default set of parameters, which turns out to be muddy and magenta-looking. Now, because there is no gamut boundary defined (no profile), there was no clipping involved. So no information was lost or changed. This is why converting back to RGB in this case yields the original image, because you're back to RGB values, and PS knows how to display those properly.
This last case I describe is similar, in a sense, to viewing a color-managed image in a non-color managed environment. In that environment, the image viewing program makes some assumption about the color space the image exists in. It displays the image according to that assumption, which may or may not be correct. This is why an image may appear duller or super-saturated compared to how it looks in PS. The display assumption is not correct, but the image appears different without a profile, even though no information in the image is being changed.
I sure wrote enough...I hope you find it useful.
--Greg