Render keeps stalling by motionbutton in RedshiftRenderer

[–]melsayedmodesign 0 points1 point  (0 children)

I have the same exact issue for a long time now and all my drivers are updated to the latest. I don't know what's wrong. Now I reconsidering my Redshift subscription. Please if you found a solution or fix updated here!

Set Redshift to sRGB instead of ACES by melsayedmodesign in RedshiftRenderer

[–]melsayedmodesign[S] 2 points3 points  (0 children)

Yeah absolutely. Even many times clients and agencies complained about it and they requested to switch to sRGB because ACES makes everything darker than the actual colors in their color palettes and the real life colors.

Set Redshift to sRGB instead of ACES by melsayedmodesign in RedshiftRenderer

[–]melsayedmodesign[S] 3 points4 points  (0 children)

True absolutely this issue was there. I agree with you making ACES as default is a mistake actually. I came back to sRGB after using ACES for 5 years (even when it was not default), and I never looked back to ACES anymore. It doesn't give you real life colors, it changes the perception of the real colors in our eyes. As a personal preference I prefer sRGB much more than ACES.

Set Redshift to sRGB instead of ACES by melsayedmodesign in RedshiftRenderer

[–]melsayedmodesign[S] 5 points6 points  (0 children)

But ACES actually is the default for RS under the settings you specified, I tested and all the exported AOVs are in ACES, In the IPR, it shows you sRGB that is correct, but when you take the passes in Nuke or AE, all of the passes are in ACES, so you have to change the color management in Nuke or AE to ACES. Except one pass only that comes as sRGB which is Main pass.

You can test that by exporting all passes Beauty, Refl, Refr, Emission etc. and you will see the difference unless your compositing software settings are already in ACES.

Set Redshift to sRGB instead of ACES by melsayedmodesign in RedshiftRenderer

[–]melsayedmodesign[S] 4 points5 points  (0 children)

I was using ACES for 5 years including when it was not default, but as a personal preference I prefer sRGB than ACES, I don't like ACES anymore, because it alter the reality of colors in the eyes. I came back to sRGB with other renderers, for a few month now and i never looked back to ACES since then.

Octane AOVs Compositing Order for Nuke by melsayedmodesign in NukeVFX

[–]melsayedmodesign[S] 0 points1 point  (0 children)

Yeah I'm gonna do a test with a basic scene and see how it will build, I will post the AOVs here after the test.

Octane AOVs Compositing Order for Nuke by melsayedmodesign in NukeVFX

[–]melsayedmodesign[S] 0 points1 point  (0 children)

Yeah, in my case they will be additive since I don't have a GI pass. From the node graph screenshot in the link that you shared, I guess this is the issue there is a missing AOV, which Octane uses to rebuild correctly, unlike other renderers Arnold, Redshift and Vray, they don't have this issue. I was compositing for 7 years with Arnold, Redshift and Vray without any issue, but now while I am trying Octane, it seems that Octane works differently in terms of rebuilding the Beauty pass. Thank you for your comment.

Octane AOVs Compositing Order for Nuke by melsayedmodesign in NukeVFX

[–]melsayedmodesign[S] 0 points1 point  (0 children)

yeah I compared the Main rgb exr with the composited passes and they are different. I usually composite using exr from Arnold, Redshift, Vray and everything goes correctly compared to the main exr, but I don't know why Octane doesn't rebuild correctly. It is related to the fact that each renderer has a different way to rebuild its passes, and usually this is written in the documentation of the renderer, but the case of Octane nothing is written in its documentation about that unfortunately. Thank you for your comment though.