but later my computer/VGA card and display, all have their own profiles to shoot the image on my screen and they all affect each other. there is one embedded in the original photo, then the image editor might use another. In fact I dont even understand how these color profiles are stacked. Everything else gives me one color in Photoshop, then a different color in another app, then a different color on my display. Aside from changing perceptually how the images are displayed on my monitor, I cant ever understand how they affect the final results or have anything to do with color accuracy. Maybe I could get some advise to clear my mind of my stupidity.ġ) Regarding Color Profiles themselves (tech talk) I have NEVER for the life of me understood the whole thing. I have 2 fundamental issues that have been eating my brain for years. from using raw.įleckintosh, this is KILLER!!!.Thank you indeed VERY much for this share They don’t match the JPEGs *perfectly* but imo I think they’re an improvement (reds don’t go a weird pink colour any more), and of course you get all the extra control over the tone curve, sharpening etc. I use them (primarily Acros (even though it's for XPro2) and Astia) with my XE1 and they’re just lovely. Possibly related to how you set the camera for JPEGs – the colours in JPEGs are different depending on whether you’ve got the camera set to sRGB or Adobe RGB.Īs for the profiles, oh man they’re exactly what I’ve been looking for. I thought an icc-profile assigned in the Base Characteristics tab processes the RAW data independent from a colourSpace. via soft proofing before displaying on your screen and when setting your colourSpace in the process recipe. Could you explain why the icc profile has a colourSpace at all please? If you’re working on RAW files, I thought the resulting output colourSpace is assigned later in the rendering pipeline i.e.
0 Comments
Leave a Reply. |