Cinema4D version 2022.1.1-R6 (Obsolete stable) 08.07.2023

[aoktar]

New build (R4) is out with some fixes! Enjoy it!

[gifmotion]

Strange. Not for me.

But this could be because your using cinema4D 2023. I'm on R25 (as that's the latest version supported by Deadline)

Thanks for your help though SSmolak. I'll stick to Octane 2021 until I find a fix.

Thanks,
Dean

[AaronWestwood]

Strange. Not for me.

But this could be because your using cinema4D 2023. I'm on R25 (as that's the latest version supported by Deadline)

Thanks for your help though SSmolak. I'll stick to Octane 2021 until I find a fix.

Thanks,
Dean

Just to add onto what SSmolak said, ACES has never/will never allow you to control gamma/highlight compression. If it did, you would have no consistency/it would be counter intuitive to its purpose. It’s like this everywhere.

So if you have gamma control (and its altering the image in your IPR), it means you arnt working in ACES and it hasn’t been setup correctly.

[SSmolak]

So if you have gamma control (and its altering the image in your IPR), it means you arnt working in ACES and it hasn’t been setup correctly.

I think that it depends how "force tonemap" is applied in Octane renderer. If it is applied after OCIO conversion it works the same as in After Effect or any post software where you load ACES exr and manipulate gamma or brightness curves. Of course this manipulation done in Octane cause that rendered output lose its 32 bit depth.

I will make test how looks the same ACES image using altered gamma in Octane and after alter gamma in post.

[AaronWestwood]

So if you have gamma control (and its altering the image in your IPR), it means you arnt working in ACES and it hasn’t been setup correctly.

I think that it depends how "force tonemap" is applied in Octane renderer. If it is applied after OCIO conversion it works the same as in After Effect or any post software where you load ACES exr and manipulate gamma or brightness curves. Of course this manipulation done in Octane cause that rendered output lose its 32 bit depth.

You definitely don’t want to be doing this though (force tonemapping), at least the way it’s setup currently as it changes the OCIO properties simply by turning it on, nullifying the OCIO. It’s not a 1:1 where you can then apply tonemapping as a post process like in an external app.

[J.C]

Saving .exr passes from Live viewer window not give you an option to choose file compression and premultiplied or unmultiplied alpha.

[SSmolak]

New build (R4) is out with some fixes! Enjoy it!

Thank you for Shape Fields ! It is very powerfull for creating dirts around chosen objects. But I found two issues :

1. It doesn't work correctly for sdf from objects ( space translation issue )

It works fine for regular sdf's

sdf_2.jpg (11.55 KiB) Viewed 1533 times

2. Using SDF's in scene cause crash while restart rendering.

3. Field Shape doesn't work while connecting Projection node to it.

Scene attached.

[gifmotion]

So if you have gamma control (and its altering the image in your IPR), it means you arnt working in ACES and it hasn’t been setup correctly.

I think that it depends how "force tonemap" is applied in Octane renderer. If it is applied after OCIO conversion it works the same as in After Effect or any post software where you load ACES exr and manipulate gamma or brightness curves. Of course this manipulation done in Octane cause that rendered output lose its 32 bit depth.

You definitely don’t want to be doing this though (force tonemapping), at least the way it’s setup currently as it changes the OCIO properties simply by turning it on, nullifying the OCIO. It’s not a 1:1 where you can then apply tonemapping as a post process like in an external app.

I understand technically why you say Aces doesn't do this and shouldn't.

But as artists wanting speed and primarily caring about what the visual image looks like, this is important. I don't want to look at my image in liveviewer and then be like "I think this will look good if I take it into photoshop or aftereffects or an alternative app to do more color correction". Aces I find is giving me a nice look, however I think its very important as an artist to then have the ability to break the rules and have further ability to force tonemapping and change highlight compression and gamma. It may not be 'technically' the right thing to be doing but visually it looks good. So I believe we want to have this feature or otherwise another color correction set of tools that can be done during the liveviewer process to do this. So we aren't jumping around between programs.

Lastly, I posted a video a few comments back using aces and had this ability in the 2021 plugin. Potentially it may have been setup wrong but from what I can tell from using it for the past year, It was setup correctly and was allowing me to do this feature.

Thankyou for your responses though SSmolak and Arronwestwood

[thanulee]

Mate, you are not using ACES 1 year as you think, is all everyone says here

Nothing to do with artistic control, which we are all after that and we all need CC controls and luts etc.

If you wanna use aces you need to disable force tonemapping and only then you will understand why you do not need tonemapping in ACES.

[SSmolak]

I understand technically why you say Aces doesn't do this and shouldn't.

AaronWestwood has right. You shouldn't use "force tonemap". See attached video and you understand why. Technically it totally flatten wide range of lighting and colors.

If you want similar to ACES look and be "artistic" try built-in LUT's or try some other. I don't remember which exactly now - but I did tests some months ago and there is LUT that have near the same look in the terms of colors and contrast that ACES and you actually have full of other controls ready to use including mixing.

There is also AOV color correction node and you can make simple corrections of Beauty pass inside Octane AOV which is displayed in LiveViewer when AOV is enabled in render settings.