I can confirm this…
This is now reported for our developers as (Report ID=CC4D-1288)
As a workaround, I can only recommend going to Edit > Scene Settings > Color Management > Change Render Space… > Legacy sRGB.
To achieve the same image appearance as when using the ACEScg color management mode, make sure that you have the ACES OT tone mapping operator added and enabled in the Corona VFB. The image will then appear the same in the VFB, when saved from the VFB, and when automatically saved by C4D.
Oh thanks very much for this quick help.
Another update regarding this:
This only happens when using the Corona VFB (when starting rendering from the Corona VFB or when the default frame buffer is set to Corona VFB in Corona Preferences). So another workaround would be switching to the native C4D Picture Viewer.
hi I have the same issue. with the diffeence what I see in the VFB than what is saved in the final render.
Is there already a fix for it or is the quickfix with the legay srgb in colorsetting still the way to go for now?
Best regards
Colin
i am on corona version 14 update 1(hotfix 1), windows 11, cinema 2026.1.4.
It’s hard to say what exact issue you are having. Are your images saved through autosave? Are you rendering inside the Corona VFB?
What you could try is the newest preview build: https://forum.corona-renderer.com/ Chaos Corona 15 for Cinema 4D Previews (daily builds) - Changelog
If it doesn’t happen there, then it means it is already fixed.
If it still does - please contact us here and we will investigate: https://support.chaos.com/hc/en-us/requests/new
Hi Maru,
I am rendering on Autosave with the takes.
What do you mean by rendering in VFB? if i render both VFb and the pictureviewr pop up.
should i revert the quickfix in the scene settings and install the preview? or just install the preview?
Best regrads
Colin
Remember that preview builds are experimental and you need to save a backup of your scene before opening it in a preview build.
You can simply try reproducing the problem in a preview build.
Hi Maru
i have just found this on the changelog for preview 15
Fixes when starting render from Corona VFB
Fixed wrong output color space of image saved with automatic saving after render when OCIO is enabled
I think this will be the fix. I havent testet it but will as soon as i have finished the activ project.
anyway thanks and i appreciate the quick response for help
I have encountered another problem.
i have instaled the preview bulit 15. but the only way to get the saved image correct is still only possible when changeing the scene setting to Legacy mode. but here comes the tricky bit. i have a new project that I have rendered with tose setting described above. the saved file looks correct when opening in PSD but it is saved in the linerar colorspace. As soon as i try to copy some images from previous psd files i get the error “paste Profile Mismatch” in PSD. Then I have reendered an old project with the same settings above and this time the save image is shown correct and it is in the SRGB colorspace. So it must have something to do with some settings in the File itself. Do you know where i can specify this option , or where this setting might be in the file?
Hi Colin,
For the second issue you are describing - where one scene saves as Linear sRGB and another as sRGB in Photoshop even with the Legacy sRGB workaround applied to both - I do not want to guess at the cause without seeing the actual scene settings. It is likely something in how the color management is stored inside the specific project file.
Could you open a ticket with both scenes attached (the one that saves as sRGB and the one that saves as Linear sRGB) so we can compare them directly?
(this is being discussed in support ticket #480159)