Ahh, finally a source i can trust. I keep seeing videos on how to use ACES, but they suggest setting everything to linear. Linear isn't ACES, linear is linear! Thanks for the OCIO tip!
I feel like it does not work with the latest update anymore. I'm running a Octane 2022.1, Cinema 4D R25. All of the version for the .ocio file is not working, will have error.
Any chance to get an updated version of this video for c4d 2023? I get different render results when using the "baked in" settings. Plus the new color management system is a little confusing...
Working in Octane 2020.1.5-R4 in C4D R23, I have no Color Management tab under Settings (my tabs skip from C4D Shaders to Other). I'm assuming I need to enable Color Management in Octane, but I'm not sure how. Anyone know how to do this? I posted this question, then realized that I may be looking at the instructions on how to do so in the Color Management tab shown right in this video. After deleting my question, I realized I wasn't having any luck finding "an OCIO view in a 'camera imager/OCIO' section" and I re-posted. Is there a clear/concise/current tutorial covering Open Color IO settings in Octane anyone can point me to?
You're also supposed to convert any maps that contribute to colour to ACES before plugging them in your lights and shaders. Albedo/Diffuse/Base Colour, HDRIs for lighting and SSS maps. Those kinda things
@@treycubine1534 Annoyingly the only 3D app that can do that is Houdini as it as a convert node. If not you're gonna have to use Nuke, Fusion or there's a $2 plugin on gumroad that will do all the textures you need in one go
Dont need to do it with octane due to its spectral nature
3 роки тому+1
@@voodoorampager Please elaborate? I am reading some conflicting information online on whether converting your color texture maps to ACEScg is necessary or not with Octane. What about Octane's spectral nature bypasses the need to convert the texture map color spaces?
anyone know why after doing this my result comes out fully black? I can have "view" set to 'None (sRGB)' and it looks normal, and then set it to 'ACES: sRGB' and the viewport is just black. still rendering but black... not sure why this is happening.
so cool! Thanks you very much! What about after? Importing the render inside after effects for having the EXACT same result ? Need to change something in aces too?
Good question. The closest I managed to get to what I had in octane live viewer to after effects was by using the second export option shown in the video (bake ACES)
You will either need to bake the ACES view transform into the image (as shown in the video) or set up After Effects to apply the same transform when displaying the image. I'm not sure whether this is possible in After Effects - perhaps it supports OCIO natively, perhaps there is a plugin for that, or perhaps you're out of luck and will have to resort to baking.
You can load ocio of ACES in after effects but to have the same result you need to export from octane to a linear EXR without the aces color mapping applied because you will apply the color mapping in After Effects which will give you the same result and you will still preserve the high dinamic range data which you can tweak in AF. One thing that is incorrect in this video is that his textures are loaded in an sRGB profile which is incorrect. Your textures in the scene has to be loaded without any profiles or you will get incorrect saturation like in the video(still works artistically but not 100% accurate). At least that is how it is in other rendering engines which makes sense.
@@ДимитърЦонев-г9у Not sure what you mean by "without any profiles" - color data is always in some color space. Anyway, in Octane, all textures currently have to be sRGB (although you can adjust the gamma). When using ACES output Octane takes care of any conversions.
@@karlhendrikse1843 Sorry my bad. What I ment is your diffuse textures needs to be sRGB if they are saved with an sRGB profile but the rest like reflection, refraction and bump should be loaded as RAW images and usually the 3d software(depends which one) is transforming them automatically to gamma 2.2 which should be the case for those maps. For normal maps tho they need to be loaded as RAW without any gamma correction to them to work correctly with ASEC or you will get incorrect normal mapping results. In other words you need to transform your textures to work correctly with ASEC color space before rendering.
After selecting Camera Imager --> OCIO --> View to ACES sRGB, my render view goes black. I tried ACES 1.0.2, 1.0.3 and 1.2 as well. Any idea what am I doing wrong ?
@@neerajjast5002 Yeah I tinkered with it some more and got it to work, which is weird because in the end, some of my settings weren't any different. Just needed them switched around and reselected I guess. Seems pretty buggy.
Why render engines has to make some settings so difficult to access. Thanks a lot for this short tutorial, super helpful! I have been searching for this for months.
@@cgpov This, I actually found a bit confusing, since it had some " you can either, or... but then keep in mind to, or..." parts. I would highly appreciate a " Do This. Period"- kind of tutorial... :) Since this whole topic is confusing already!
Using Octane in c4d.....is it possible to send the render out to picture viewer using the baked in method in a way that still respects the custom LUT's you use in your Octane Camera Tag? It seems like the baked-in method disregards those.
Has anyone else the same issue where setting up ACES exactly described like here, causes Octane to crash when you render to the Picture Viewer? Even a new blank scene with nothing in it but the ACES settings crash every time :/
Wow, I think I just found the cause for the crashes. So if you're baking in the ACES color profile into your final 8bit png/jpg/whatever IN COMBINATION with the "Use denoised beauty pass" leads to constant crashes for me. Has anyone else the same issues?
@@loganpatrick1469 so far my workaround was to disable the „use denoised beauty“ and let octane save the denoised beauty for me in the render passes section. Works basically the same, just a few more clicks
Hi Chad! Thanks for the amazing tutorial. I have read elsewhere that the diffuse (and specular) textures need to be converted into ACEScg space before rendering. Is that still right? (ACES workflow in Octane seemed to have changed a lot during the last year and there are conflicting information on the web)
After you have set ACES up, can you use the Octane LUT's in camera imager, or will it look strange? I'll do a few tests now.. Thanks for the great quick and easy video!
Hi Chad, Thank you so much for all your tutorials as they have been so helpful. I just have an issue that I’m hoping you could maybe help me with. I’m trying to render a cloth simulation in Arnold 6 in cinema 4D, so I used both the c4D and Arnold materials on my cloth but for some weird reason, I’m the material doesn’t show on my IPR but when I change my material projection from UVWW to Cubic, it shows but it doesn’t stay on the surface of my cloth. Do you have any idea of what the problem might be? I will really appreciate your help. Thank you!
Hello, Thanks for the video Greyscalegorilla, was really clear and easy to follow. But I'm having an issue, I did the exact same steps and copied the Aces config file from Github but this error appears when I try to render: Failed to build OCIO LUT: OCIO error: The specified file reference 'Log2_48_nits_Shaper_to_linear.spi1d' could not be located. Does anyone have a magic solution to help me fix this ? Thanks a lot in advance and I wish you a great day :)
Great video! Thanks for doing these, Chad! One question..Why set the intermediate space to Aces2065 and not AcesCG? My understanding is that AcesCG was built specifically for rendering, as the wider gamut primaries of 2065 caused rendering inaccuracies.
Octane does all its rendering spectrally, so it's already inherently more accurate than any RGB color space, and ACES doesn't change this. The intermediate color space setting is for a completely different purpose: it's so that Octane knows how to convert between its spectral representation and the color spaces from the OCIO config you're using. In an upcoming version the intermediate color space is set automatically by default so you don't have to worry about it.
@@karlhendrikse1843 Thanks for the reply! It's such a strange thing for me to get my head around. Because Octane is a spectral renderer, the usual benefit of rendering with wider color primaries in an RGB renderer is moot, right? It's not an issue with Octane. So I guess Octane is just using the OCIO config to automatically convert any textures for you, which I guess is being converted into this Aces2065 intermediate space because why not, it's spectral and can handle it without the rendering errors an RGB renderer would have. Do I have this correct? Also, is Octane just assuming all textures to be sRGB? I tried bringing in an AcesCG exr as a texture, setting the gamma to 1, but it looked terrible. So unless I'm missing something, Octane Aces requires sRGB color and sRGB gamma for textures. Is that correct? Thanks again for the reply!
@@igobyzak That's all correct, except that Octane currently only uses OCIO for output, not input, so it doesn't convert any textures for you. As you observed, Octane requires all textures to be sRGB (although you can adjust the gamma) - this is true whether using OCIO or not. For output using OCIO, ACES2065-1 is used as a "bridge" - Octane produces an image in ACES2065-1, and then uses OCIO to convert it from ACES2065-1 to the desired final OCIO color space.
@@karlhendrikse1843 Thanks so much for the explanation! This is great info. Octane has an interesting set up here, on the one hand you don't have to convert any assets into Aces, however, if you're using any assets that have already been converted to Aces or are in another color space, those would have to be converted to sRGB before being used. It's probably much less common, but still could come into play if you're working with a team and sharing assets. Thanks again for all the nerdy details! Love it!
First dummy tip not included on the tutorial: CREATE a GITHUB account, otherwise you can't download the file. Then struggle to find how to download this specific file. lol.
I did exactly as you said, "select LDR （8-bit），Output（Output - sRGB）" to export as PSD,JPG and PNG, This will show up in OC's render window that everything is fine,，but after opening it in PS, it could not display properly，It still appears as if ACES is not enabled
@@shahrilsuhaimi5109 Turn out I did not have the latest version. I had to download it from the website because even when I check for "latest version" inside of de Cinema Octane plug-in it didn't recognize that there was a new version so just download it directly from otoy.com
Any specific reason why you have used such an old ACES config file (1.0.3 - 3 years old), versus the latest version (1.2 - 13 months)?
Watched the video and installed an ACES preset in under 10 min! Thank you for delivering quality as always!!!
Awesome, thanks Chad. I'd love to see a follow up vid on .exr workflow with aces!
Ahh, finally a source i can trust. I keep seeing videos on how to use ACES, but they suggest setting everything to linear. Linear isn't ACES, linear is linear! Thanks for the OCIO tip!
Please do a Redshift version of this tutorial!
I feel like it does not work with the latest update anymore. I'm running a Octane 2022.1, Cinema 4D R25. All of the version for the .ocio file is not working, will have error.
The difference is super subtle but it's the baby steps that we need to take to achieve better photorealism.
Any chance to get an updated version of this video for c4d 2023? I get different render results when using the "baked in" settings. Plus the new color management system is a little confusing...
I've been trying to make the render the same as what I'm seeing in the Picture Viewer for 1 week... this is exhausting
The Color Management tab not showing in my setting window, any idea why? I'm using the latest octane and cinema (legal) versions.
im having this problem
update the latest octane...should have that features
Has anyone figured this one out? I’m on S24 and still no CM tab anywhere.
@@JoniKukkohovi I figured it out it was my octane version. just update on the OTOY and it will be there.
THIS IS AMAZING! Finally the questions have been answered. All hail the greyscales.
from Version 2023.0.0, do you need to add the Aces 1.2 config in the C4D project scene colour management settings.
Working in Octane 2020.1.5-R4 in C4D R23, I have no Color Management tab under Settings (my tabs skip from C4D Shaders to Other). I'm assuming I need to enable Color Management in Octane, but I'm not sure how. Anyone know how to do this?
I posted this question, then realized that I may be looking at the instructions on how to do so in the Color Management tab shown right in this video.
After deleting my question, I realized I wasn't having any luck finding "an OCIO view in a 'camera imager/OCIO' section" and I re-posted. Is there a clear/concise/current tutorial covering Open Color IO settings in Octane anyone can point me to?
You're also supposed to convert any maps that contribute to colour to ACES before plugging them in your lights and shaders. Albedo/Diffuse/Base Colour, HDRIs for lighting and SSS maps. Those kinda things
100% I hope octane will have an option later to convert any texture without having to use third party software.
@@treycubine1534 Annoyingly the only 3D app that can do that is Houdini as it as a convert node. If not you're gonna have to use Nuke, Fusion or there's a $2 plugin on gumroad that will do all the textures you need in one go
Dont need to do it with octane due to its spectral nature
@@voodoorampager Please elaborate? I am reading some conflicting information online on whether converting your color texture maps to ACEScg is necessary or not with Octane. What about Octane's spectral nature bypasses the need to convert the texture map color spaces?
Awesome - tried it in Octane for Blender and it works exactly the same. it also seems that the profile is baked when saving the render in .png
can you send a link to Octane that works? The links I found don't open anything for me.
anyone know why after doing this my result comes out fully black? I can have "view" set to 'None (sRGB)' and it looks normal, and then set it to 'ACES: sRGB' and the viewport is just black. still rendering but black... not sure why this is happening.
ocio in viewport results in black! any advice? follow step by step
I am using Octane X on my MacBook and trying to use ACES but can't see tab for Colour Management. Appreciate your help.
i swear i watch this video every month, idk why something so simple on paper is so easy to messed up lol
so cool! Thanks you very much!
What about after? Importing the render inside after effects for having the EXACT same result ? Need to change something in aces too?
Good question. The closest I managed to get to what I had in octane live viewer to after effects was by using the second export option shown in the video (bake ACES)
You will either need to bake the ACES view transform into the image (as shown in the video) or set up After Effects to apply the same transform when displaying the image. I'm not sure whether this is possible in After Effects - perhaps it supports OCIO natively, perhaps there is a plugin for that, or perhaps you're out of luck and will have to resort to baking.
You can load ocio of ACES in after effects but to have the same result you need to export from octane to a linear EXR without the aces color mapping applied because you will apply the color mapping in After Effects which will give you the same result and you will still preserve the high dinamic range data which you can tweak in AF. One thing that is incorrect in this video is that his textures are loaded in an sRGB profile which is incorrect. Your textures in the scene has to be loaded without any profiles or you will get incorrect saturation like in the video(still works artistically but not 100% accurate). At least that is how it is in other rendering engines which makes sense.
@@ДимитърЦонев-г9у Not sure what you mean by "without any profiles" - color data is always in some color space. Anyway, in Octane, all textures currently have to be sRGB (although you can adjust the gamma). When using ACES output Octane takes care of any conversions.
@@karlhendrikse1843 Sorry my bad. What I ment is your diffuse textures needs to be sRGB if they are saved with an sRGB profile but the rest like reflection, refraction and bump should be loaded as RAW images and usually the 3d software(depends which one) is transforming them automatically to gamma 2.2 which should be the case for those maps. For normal maps tho they need to be loaded as RAW without any gamma correction to them to work correctly with ASEC or you will get incorrect normal mapping results. In other words you need to transform your textures to work correctly with ASEC color space before rendering.
Super helpful, thanks Chad!
After selecting Camera Imager --> OCIO --> View to ACES sRGB, my render view goes black. I tried ACES 1.0.2, 1.0.3 and 1.2 as well. Any idea what am I doing wrong ?
same, just black window
same did you ever get a fix ?
Still having this issue, if anyone knows how to solve this please let us know.
@@MattObviously working for me now.
@@neerajjast5002 Yeah I tinkered with it some more and got it to work, which is weird because in the end, some of my settings weren't any different. Just needed them switched around and reselected I guess. Seems pretty buggy.
Great tutorial! Thanks! This ACES looks really amazing.
Why render engines has to make some settings so difficult to access. Thanks a lot for this short tutorial, super helpful! I have been searching for this for months.
Please do the same tutorial for Redshift!!!
This should help ua-cam.com/video/vEoIXTbyz6o/v-deo.html
@@cgpov This, I actually found a bit confusing, since it had some " you can either, or... but then keep in mind to, or..." parts. I would highly appreciate a " Do This. Period"- kind of tutorial... :) Since this whole topic is confusing already!
Using Octane in c4d.....is it possible to send the render out to picture viewer using the baked in method in a way that still respects the custom LUT's you use in your Octane Camera Tag? It seems like the baked-in method disregards those.
Has anyone else the same issue where setting up ACES exactly described like here, causes Octane to crash when you render to the Picture Viewer? Even a new blank scene with nothing in it but the ACES settings crash every time :/
Wow, I think I just found the cause for the crashes. So if you're baking in the ACES color profile into your final 8bit png/jpg/whatever IN COMBINATION with the "Use denoised beauty pass" leads to constant crashes for me. Has anyone else the same issues?
@@halbvoll I had the same issue.
whats the workaround? how we can get some denoised renders and use aces
@@loganpatrick1469 so far my workaround was to disable the „use denoised beauty“ and let octane save the denoised beauty for me in the render passes section. Works basically the same, just a few more clicks
Hi Chad! Thanks for the amazing tutorial. I have read elsewhere that the diffuse (and specular) textures need to be converted into ACEScg space before rendering. Is that still right? (ACES workflow in Octane seemed to have changed a lot during the last year and there are conflicting information on the web)
bump, this would be good to know...
new version 1.2 not working in octane...and i cant download 1.0.3 anywhere...
This is fantastic! Thanks Chad!
omg omg ... I liked, before I finished watching! hehe
Hi
The LDR shows bad in both Picture View and and After Effects - is not baking any looks
Hi Chad! For some reason output looks differenlty from the live viewer - it's brighter. How to fix it?
does the "enable camera imager" tab affect this, what do we choose there natural response ?
thanks chad! what about "old" shaders, will they be converted automatically once i copy an older asset into a new ACES scene?
Brilliant. Thanks Chad.
After you have set ACES up, can you use the Octane LUT's in camera imager, or will it look strange? I'll do a few tests now.. Thanks for the great quick and easy video!
@@Mimr3D As far as I know from using the profile so far, LUT's are ineffective while using Aces, they don't work at all.
@@JCShannon i agree tried to do this multiple ways does not work with any LUTs in camera
Wooohoooo🎉🎉🎉just what I'm looking for
Heyy chad but Chris brejon also recommending to use ACEScg and not 2065-1 for rendering and compositing I think it's the same case here.
how'd you get the plant in the jar?
Awesome Video! Anyone knows what's the difference between ACES and LUTS? I think both do Colour grading things.
Please do one with redshift
This should help ua-cam.com/video/vEoIXTbyz6o/v-deo.html
@@cgpov Thanks!
Hi Chad,
Thank you so much for all your tutorials as they have been so helpful. I just have an issue that I’m hoping you could maybe help me with.
I’m trying to render a cloth simulation in Arnold 6 in cinema 4D, so I used both the c4D and Arnold materials on my cloth but for some weird reason, I’m the material doesn’t show on my IPR but when I change my material projection from UVWW to Cubic, it shows but it doesn’t stay on the surface of my cloth. Do you have any idea of what the problem might be? I will really appreciate your help. Thank you!
I'm not understanding this. How is this different than color grading in PS after or is it just that, you can skip PS?
When I render to the picture viewer it looks all blown out and wrong, why is it looking so different?
How to a setup ACES in the c4d Octane x PR13 on the macos12.0.1?
Hello,
Thanks for the video Greyscalegorilla, was really clear and easy to follow.
But I'm having an issue, I did the exact same steps and copied the Aces config file from Github but this error appears when I try to render: Failed to build OCIO LUT: OCIO error: The specified file reference 'Log2_48_nits_Shaper_to_linear.spi1d' could not be located.
Does anyone have a magic solution to help me fix this ?
Thanks a lot in advance and I wish you a great day :)
Great video! Thanks for doing these, Chad! One question..Why set the intermediate space to Aces2065 and not AcesCG? My understanding is that AcesCG was built specifically for rendering, as the wider gamut primaries of 2065 caused rendering inaccuracies.
Was wondering the same thing...
Octane does all its rendering spectrally, so it's already inherently more accurate than any RGB color space, and ACES doesn't change this. The intermediate color space setting is for a completely different purpose: it's so that Octane knows how to convert between its spectral representation and the color spaces from the OCIO config you're using. In an upcoming version the intermediate color space is set automatically by default so you don't have to worry about it.
@@karlhendrikse1843 Thanks for the reply! It's such a strange thing for me to get my head around. Because Octane is a spectral renderer, the usual benefit of rendering with wider color primaries in an RGB renderer is moot, right? It's not an issue with Octane. So I guess Octane is just using the OCIO config to automatically convert any textures for you, which I guess is being converted into this Aces2065 intermediate space because why not, it's spectral and can handle it without the rendering errors an RGB renderer would have. Do I have this correct? Also, is Octane just assuming all textures to be sRGB? I tried bringing in an AcesCG exr as a texture, setting the gamma to 1, but it looked terrible. So unless I'm missing something, Octane Aces requires sRGB color and sRGB gamma for textures. Is that correct? Thanks again for the reply!
@@igobyzak That's all correct, except that Octane currently only uses OCIO for output, not input, so it doesn't convert any textures for you. As you observed, Octane requires all textures to be sRGB (although you can adjust the gamma) - this is true whether using OCIO or not. For output using OCIO, ACES2065-1 is used as a "bridge" - Octane produces an image in ACES2065-1, and then uses OCIO to convert it from ACES2065-1 to the desired final OCIO color space.
@@karlhendrikse1843 Thanks so much for the explanation! This is great info. Octane has an interesting set up here, on the one hand you don't have to convert any assets into Aces, however, if you're using any assets that have already been converted to Aces or are in another color space, those would have to be converted to sRGB before being used. It's probably much less common, but still could come into play if you're working with a team and sharing assets. Thanks again for all the nerdy details! Love it!
Anyone else not have a "Color Management" tab in Octane settings?
for ref I'm using Studio 2020.1.4
SAME. I don't have it either. I'm on C4D R20. I wonder if that's why.
Got it. Hadn't properly installed 2020.2
@@CodyGarrow When I check for updates mine doesn't offer that version for download
Can you do the same for arnold?
how did you guys make blue frame in live viewever pls help?
do textures need to be converted to Aces format before being used?
Nope
You should though, especially when it comes to diffuse maps that contain colour information these won’t be technically correct using this method.
First dummy tip not included on the tutorial: CREATE a GITHUB account, otherwise you can't download the file. Then struggle to find how to download this specific file. lol.
It doesn't work for me. The LDR output doesn't match the picture viewer
I did exactly as you said, "select LDR （8-bit），Output（Output - sRGB）" to export as PSD,JPG and PNG, This will show up in OC's render window that everything is fine,，but after opening it in PS, it could not display properly，It still appears as if ACES is not enabled
same
@@edrevvvv same here
Yup same! if you export as PSD it doesnt work and if you export as EXR it does but you lose the layers with all the passes,:(
What about the multipass output set up?
chad u the king
😊
My version of octane doesn't even have that menu?
yeah even i don't have color management tab under settings, Please if anybody knows how to install?
I'm using Octane 2020.2 if that helps
Love this.
How I can export exr Log Acces with octane?
Is there a version of this for Redshift?
I might be extremely biased, but I think this one is really good:
ua-cam.com/video/7uY4-bPvRKs/v-deo.html
@@igobyzak thanks this is solid 👌
Thanks! at last!
dont see color managment under octane X version
so helpful
ACES配置文件如何安装，请问，非常感谢能够告知
Does anyone here know a good workflow post rendering or working in After Effects for comping and adding motion graphics
Here you go, SilverWingVFX put out a recent video explaining the Octane to After Effects full aces workflow: ua-cam.com/video/ZIXceP3CKWI/v-deo.html
cant find same setings in houdini
Redshift please
This should help ua-cam.com/video/vEoIXTbyz6o/v-deo.html
Pls the same but with Redshift!!!!!!😭
Check my previous replies 🤘
Any one knows if this works with RNDR?
ACES in Arnold please
I have Octane up to date and do not see the Color Management tab. Which version are you using?
NVM I GOT IT
@@mexihkano where? i did not have color management tab too~
@@shahrilsuhaimi5109 Turn out I did not have the latest version. I had to download it from the website because even when I check for "latest version" inside of de Cinema Octane plug-in it didn't recognize that there was a new version so just download it directly from otoy.com
@@shahrilsuhaimi5109 it should be version 2020.2 and up I think
Haha ;) One way of doing it is Use curves in Photoshop!!!! ..... in Under 1 Minutes
not the same man
Such look can be achieved without aces, you just have to learn better your tools ;)
Please do the same tutorial for Redshift!!!
Check previous replies I link to a good one