karu wrote:evan.musin wrote:Hi Paul,
Since installing Octane Render 2021.xx, I have noticed when saving out PNG files, it saves the PNGs with an embedded sRGB profile. Pre-2021.xx, it would save the PNGs with no profile at all. Is there a way to set a legacy save with no profile? Our production pipeline has taken a slight hit in consistency due to this. Thank you!
Hi Evan,
This change was made to ensure exported images display the same in other applications as they do in Octane - we had issues where users would open exported PNGs in Photoshop, where the working space was set to something different, and complain that the image looked wrong. There is currently no way to prevent the inclusion of an sRGB profile - the idea was that since Octane specifically considers the image to be sRGB, it ought to always put that information in the file, and viewers can choose to ignore it if they want.
I am curious as to what problems the inclusion of the profile is causing - is it that you want to use a different profile, or just that the data is superfluous, or something else? If Octane had a setting to control the embedding of a profile, would just an on/off checkbox suffice? Would you want to control this per export or just in one overall Octane setting?
Hi there,
A checkbox would suffice in this case, or even having the option to select "None" in the color space drop down when saving from Octane. We have a lot of our actions/scripts set up for an unprofiled image so we can easily add our working profile. Thank you!