- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report
Hi everyone,
I’ve noticed an issue with saving renders from Corona VFB when using a custom ACES OT value.
In Corona VFB, if I set ACES OT = 0.2, the image looks perfect — highlights are nicely compressed, no overexposure.
But when I save the image (PNG/JPG) directly from the VFB, the saved file looks overexposed, as if ACES OT was not applied at all.
When ACES OT = 1.0, the saved image matches the VFB perfectly.
When ACES OT = 0.2, the saved image no longer matches — it looks blown out, not like in the VFB.
Question:
👉Is this expected behavior?
👉Is there a workaround to make the saved image match the VFB when using a custom ACES OT value?
👉Should I use Corona Image Editor or another workflow?
Thanks in advance for any help or clarification!
Solved! Go to Solution.
