Great tut! one thing - you should install the OpenColorIO folder in %programdata% (c:/USERNAME/ProgramData/) because that's the default location used by the OCIO plugins for After Effects etc - otherwise you'll have to browse to the "config.ocio file" every damn time you use it
Damn...this reminds me of watching tutorials back in 2012 on how to set up Vray and 3ds Max to render out in linear space. While I admire your tenacity for figuring out how to use it today, I think I'll wait until the software folks implement it natively!
Haha oh wow, glad to hear it. Most of it holds up other than the texture conversion, which is now done automatically. If you use the Beauty Output trick it helps a lot to enable CLAMP AOV, otherwise you can get crazy firefly noise
Thanks! I was discouraged at first when the default color selector was throwing super saturated colors - it felt like trying to balance a broom on its end. Can’t wait to get back and try piping it into a corrector node. I saw Saul made an OSL transform code which I hope works in cinema. It would be great to have that code in a text expander key bind.
Covered in the video, just throw down a color constant node and use the xgroup. If you keep the Xpool docked it's super fast to drag and drop the conversion node in
Hi Patrick, it is such a amazing work there, I just came from the video you have at the schools of motions. Do you think scanning real people into virtual world is possible as a professional 3d designer within the industry? I am so new into photogrammetry and 3d printing and curious about all these ideal of turning 3d object from real world to virtual or the other way around.
Regarding the import of the EXRs, I use AE 2020 on a pc and imported them using the import menu rather than the drag and drop method. It was nearly instantaneous on my slow-ass pc.
This is great dude, thank god for the xpresso nodes. FYI Xeetron responded with, Edit: I was mistaken about HDRs-it should work for those too. So i'm assuming that works for beachmobjellies's CLEANUP version too.
Hi Patrick. You might need to make your 0:00 time stamp say "Welcome". Seems to work on mine! Not much of a quid pro quo for your great explanation of ACES - but it's a start!
Note to anyone still using this, the file on the Redshift forum is not the same as the one on the Dropbox link or what's shown on the video and so if you download from the Redshift forum you will not have input and output like in the video, so I'm guessing it won't work. I just redownloaded it from Dropbox and it works the same way as the video and you don't need to do anything. I'm guessing if you're good at building nodes you might be able to make the other one work but it might be quite a bit different, I don't know. Luckily as unreliable as they can be, currently the Dropbox link works. I would advise the channel owner to add a Google drive link or a few alternatives in case this goes down.
Great tutorial. I'm wondering how a multi-layer EXR setup would look like in C4D. Would each pass need to be a direct output or could I just uncheck Redshift Post-Effects to ensure my layered EXR doesn't have Color Processing applied, thereby allowing me to do my ACES workflow in post in AE?
So I read through the forum thread about this xgroup node by xeeton. And someone (Stanislav Yakymenko) mentioned that this node seems to works the same way as "Utility-Linear-sRGB to ACEScg"? So it would work only for HDRI then? Not exactly good for albedo? When Stanislav ask xeeton on the forum about it, he just replied with "I don’t have the knowledge to push this forward"? Will this method of working produce accurate enough results as far as ACES goes? I'm so confused, lol.
I was concerned about that too, but I validated this workflow by comparing the results from that node group to conversion via Pyco conversion using Utility - Texture - sRGB mode. The nodegroup gave the same results. I think the forum user might have it backwards
I have practiced this workflow in two projects, so I was curious since HDRI lighting needs to be converted to be correct, what color space would it be in C4D Redshift's default lighting!?
Hey Patrick, I've just followed this step by step from Redshift in C4D to After Effects and I've just read that your AE set up is wrong in the description. I tried to follow the other tutorial but because he has footage, and not a C4D render I'm getting slightly confused about the configurations in AE. Is there any chance you could share a correct AE file with your set up so I can just slot my render in? I think this would be super helpful for me, and for other people too. Let me know what you think. Thank you!
Sorry I have a quick question....how about the gamma override stuff for textures linking to roughness or displacement map... Do we have to do the usual gamma override and apply ACES conversion on top of it or just ACES conversion will do? Thanks
No problem! One only needs to apply this conversion to diffuse textures, and specular color (if the spec map contributes color). Displacement, roughness, normals etc don't require the conversion
As far as I know, you don't need to, but you'd have to ask a more active AE user. From what I've seen online, this workflow gives you correct results. Let me know if you figure something out with Linearize on, 'cause it always gave me funky outputs
@@patrickletourneau8177 Nah you're right. Turning ON Linearize would just make the whole image bright and flat. Turning it off gives the same result as in the RS render view.
This workflow is incorrect. You have to check linearize workingspace and set working space to ACEScg. You also have to disable the viewers colormanagement which is the reason why it looks incorrect. You do that by the / key on the numpad or click the rgb icon on the viewer. You have to do that for each comp that already existed. Little bit annoying but hey, what isn't annoying about AE :)
@@shebbe5510 Haha oh noooo. The nightmare scenario of being called out in the comments :D. Thanks for the heads up - I just checked out Andrey Lebrov's video and see the errors of my ways, damn. Seems like the correct workflow is even more of a pain in the ass
@@patrickletourneau8177 no worries haha yea Andrey explains it correctly I think. I got it from this vid th-cam.com/video/1ixzKR21jdw/w-d-xo.html which is more vfx+film oriented but same principles apply. Maybe you did get the same result as your renderer but AE was still managing stuff itself and calculations/data weren't linear and in wider gamut unless you change those things. AE is ridiculously slow with exrs and working in linear 32-bit though so I wouldn't recommend anyone working this way. Fusion is much faster :) and free in Resolve free version.
Great tut!
one thing - you should install the OpenColorIO folder in %programdata% (c:/USERNAME/ProgramData/) because that's the default location used by the OCIO plugins for After Effects etc - otherwise you'll have to browse to the "config.ocio file" every damn time you use it
I've been wanting to try aces for ages, but watching this, I would have never figured it out myself. Thank you!!
Best ACES workflow explanation online, thanks man 🔥
This is the best tutorial I have seen, better than GSG's, thank you!
I can feel the hatred of after effects in oozing through the video! hahah thanks for making this Patrick!
A perfect tut. Thank you. Been missing some info in the others I've seen and this is much needed. SUBSCRIBED.
my god it is actually fairly simple. thanks a lot for the demystification 😌
Brilliant video, really helpful
Damn...this reminds me of watching tutorials back in 2012 on how to set up Vray and 3ds Max to render out in linear space. While I admire your tenacity for figuring out how to use it today, I think I'll wait until the software folks implement it natively!
Great! More practical example with aces please, especially material setup
Thank you , very informative and will be adopting to rendering ACES
hello old friend
i keep coming back to this, as I often end up quoting you for various work related reasons
because, reasons
Haha oh wow, glad to hear it. Most of it holds up other than the texture conversion, which is now done automatically. If you use the Beauty Output trick it helps a lot to enable CLAMP AOV, otherwise you can get crazy firefly noise
Thanks! I was discouraged at first when the default color selector was throwing super saturated colors - it felt like trying to balance a broom on its end. Can’t wait to get back and try piping it into a corrector node.
I saw Saul made an OSL transform code which I hope works in cinema. It would be great to have that code in a text expander key bind.
Covered in the video, just throw down a color constant node and use the xgroup. If you keep the Xpool docked it's super fast to drag and drop the conversion node in
Thanks so much dude, Subscribed!
The biggest thanks for this, Patrick!
I thought RS already implemented that aces conv node, I see they haven't
thanks for the workflow and demostration! can be a difficult subject to learn without examples :)
Hi Patrick, it is such a amazing work there, I just came from the video you have at the schools of motions. Do you think scanning real people into virtual world is possible as a professional 3d designer within the industry? I am so new into photogrammetry and 3d printing and curious about all these ideal of turning 3d object from real world to virtual or the other way around.
That's great, thanks so much.
Thanks for making this!
This is very useful. Thanks!!
Regarding the import of the EXRs, I use AE 2020 on a pc and imported them using the import menu rather than the drag and drop method. It was nearly instantaneous on my slow-ass pc.
Ah yes a friend mentioned this to me as he beta tested the tutorial, but frankly I find it crazy that they can’t get drag and drop working quickly : )
Awesome video thanks man!
This is great dude, thank god for the xpresso nodes. FYI Xeetron responded with, Edit: I was mistaken about HDRs-it should work for those too. So i'm assuming that works for beachmobjellies's CLEANUP version too.
Ah, but then you can't wire that into the dome light even with shadergraph. Lame!
Edit: Yay, chapters kicked in
Annoyingly, TH-cam isn't recognizing my timestamps as chapters. Check the description to skip around and save time :)
Hi Patrick. You might need to make your 0:00 time stamp say "Welcome". Seems to work on mine! Not much of a quid pro quo for your great explanation of ACES - but it's a start!
Note to anyone still using this, the file on the Redshift forum is not the same as the one on the Dropbox link or what's shown on the video and so if you download from the Redshift forum you will not have input and output like in the video, so I'm guessing it won't work. I just redownloaded it from Dropbox and it works the same way as the video and you don't need to do anything. I'm guessing if you're good at building nodes you might be able to make the other one work but it might be quite a bit different, I don't know. Luckily as unreliable as they can be, currently the Dropbox link works. I would advise the channel owner to add a Google drive link or a few alternatives in case this goes down.
Strange friends will call you back finally ahahhahaa
Estranged*
I love how you say OCIO.
🇨🇦🇨🇦🇨🇦
Great.
Killer stuff! ty
Great tutorial. I'm wondering how a multi-layer EXR setup would look like in C4D. Would each pass need to be a direct output or could I just uncheck Redshift Post-Effects to ensure my layered EXR doesn't have Color Processing applied, thereby allowing me to do my ACES workflow in post in AE?
This is a killer tutorial! But, what if I'm exporting a single image for composting in Photoshop?
7:02 To clarify, if we use the aces node in redshift we don't need to do the hdr conversion at the end?
You should convert your HDRIs regardless. TBH the difference with HDRIs isn't huge, but I would say test it in every scene to make sure
subscribed! thx.
So I read through the forum thread about this xgroup node by xeeton. And someone (Stanislav Yakymenko) mentioned that this node seems to works the same way as "Utility-Linear-sRGB to ACEScg"? So it would work only for HDRI then? Not exactly good for albedo? When Stanislav ask xeeton on the forum about it, he just replied with "I don’t have the knowledge to push this forward"? Will this method of working produce accurate enough results as far as ACES goes? I'm so confused, lol.
I was concerned about that too, but I validated this workflow by comparing the results from that node group to conversion via Pyco conversion using Utility - Texture - sRGB mode. The nodegroup gave the same results. I think the forum user might have it backwards
@@patrickletourneau8177 Glad to hear it then, thanks Patrick!!!
love the little jokes throughout the tutorial
I have practiced this workflow in two projects, so I was curious since HDRI lighting needs to be converted to be correct, what color space would it be in C4D Redshift's default lighting!?
What is the difference for CG in working with floatingpoint?
Hey Patrick, I've just followed this step by step from Redshift in C4D to After Effects and I've just read that your AE set up is wrong in the description. I tried to follow the other tutorial but because he has footage, and not a C4D render I'm getting slightly confused about the configurations in AE. Is there any chance you could share a correct AE file with your set up so I can just slot my render in? I think this would be super helpful for me, and for other people too. Let me know what you think. Thank you!
Oh shoot well, you should be all good if you follow the workflow in my video. I've heard from a few people that my technique is perfectly fine (yay)
Sorry I have a quick question....how about the gamma override stuff for textures linking to roughness or displacement map...
Do we have to do the usual gamma override and apply ACES conversion on top of it or just ACES conversion will do? Thanks
No problem! One only needs to apply this conversion to diffuse textures, and specular color (if the spec map contributes color). Displacement, roughness, normals etc don't require the conversion
@@patrickletourneau8177 Thanks for the clarification
"water is gonna taste better" hahahahah
Wait, so in AE we don't need to activate linearized working space?
As far as I know, you don't need to, but you'd have to ask a more active AE user. From what I've seen online, this workflow gives you correct results. Let me know if you figure something out with Linearize on, 'cause it always gave me funky outputs
@@patrickletourneau8177 Nah you're right. Turning ON Linearize would just make the whole image bright and flat. Turning it off gives the same result as in the RS render view.
This workflow is incorrect. You have to check linearize workingspace and set working space to ACEScg. You also have to disable the viewers colormanagement which is the reason why it looks incorrect. You do that by the / key on the numpad or click the rgb icon on the viewer. You have to do that for each comp that already existed. Little bit annoying but hey, what isn't annoying about AE :)
@@shebbe5510 Haha oh noooo. The nightmare scenario of being called out in the comments :D. Thanks for the heads up - I just checked out
Andrey Lebrov's video and see the errors of my ways, damn. Seems like the correct workflow is even more of a pain in the ass
@@patrickletourneau8177 no worries haha yea Andrey explains it correctly I think. I got it from this vid th-cam.com/video/1ixzKR21jdw/w-d-xo.html which is more vfx+film oriented but same principles apply. Maybe you did get the same result as your renderer but AE was still managing stuff itself and calculations/data weren't linear and in wider gamut unless you change those things. AE is ridiculously slow with exrs and working in linear 32-bit though so I wouldn't recommend anyone working this way. Fusion is much faster :) and free in Resolve free version.
my brain hurts