I appreciate your effort in crafting all of these episodes. I've gained a great deal of knowledge! I hope that moving forward, you'll be able to share even more insights, as this has been truly invaluable. Thank you
Nice job. Is there a way to plugin directly to the color space transform so that if a camera isn’t supported one could create a new input color space/gamma combination and have their own transform code invoked?
You can't add new cameras to the CST OFX, but afaik the ACES transform does allow for the creation of custom IDTs and ODTs using DCTLs and they will show up in the ACES Transform OFX if placed in the correct folders.
Hi! I have a question. I have it setup almost identically to the way you've done it in this video, with the forward and inverse functions. I've verified the forward/inverse functions are implemented correctly by using the built in CST in resolve. However, when I add the code that adjusts for exposure, it does not match the results from doing the same thing in the HDR Global EXP slider. I am not sure why this is. I am using version 18.5 of resolve. btw. Could you give me some guidance on this? Why might this not work like in the video? Is it possible that the input is not in davinci intermediate, so applying the transform doesn't correctly put it in linear space?
Have you chosen the correct working/timeline color space in your project settings? The HDR palette and all other color space aware tools use that option as the expected color space they work by.
A DCTL doesn't inherently have a color space or transfer function. Those which do, as in this case, tend to transform from a transfer function encoded signal to linear, apply the image manipulations and then encode the image with the transfer function again. This is done as linear is how light is in it's natural state. As such applying doing manipulations on 'linear' light ie. w/o any encodings, has it work like physical light does in the real world. Hope this answers your question.
Thank you so much Kaur!🙏 Learning a lot with this amazing tutorials ;)
Thanks, I'm glad to hear you're enjoying these!
I appreciate your effort in crafting all of these episodes. I've gained a great deal of knowledge! I hope that moving forward, you'll be able to share even more insights, as this has been truly invaluable. Thank you
Thank you! I do plan on doing more training, but most likely as either a paid course or live workshops.
What topics would you be most interested in?
thanks for the tutorial, really nice!!
Great. Thank you for this Guide. As a DCTL beginner I learn a lot there.
Glad to hear you're enjoying it!
This opens so many doors and possibilities. thank you so much for making this!
You're so very welcome!
An excellent and extremely useful lesson. Thank you
Thanks, Belinskiy
learned a lot
Might also be useful to point out the _exp2f() convenience function where you would only need to pass your p_Exp parameter.
Thanks for pointing it out! That's a more compact way of doing it. I decided to show a longer way to make it more clear.
Nice job. Is there a way to plugin directly to the color space transform so that if a camera isn’t supported one could create a new input color space/gamma combination and have their own transform code invoked?
You can't add new cameras to the CST OFX, but afaik the ACES transform does allow for the creation of custom IDTs and ODTs using DCTLs and they will show up in the ACES Transform OFX if placed in the correct folders.
@@KaurHThat's a bummer, but thank you.
Hi! I have a question. I have it setup almost identically to the way you've done it in this video, with the forward and inverse functions. I've verified the forward/inverse functions are implemented correctly by using the built in CST in resolve. However, when I add the code that adjusts for exposure, it does not match the results from doing the same thing in the HDR Global EXP slider. I am not sure why this is. I am using version 18.5 of resolve. btw.
Could you give me some guidance on this? Why might this not work like in the video? Is it possible that the input is not in davinci intermediate, so applying the transform doesn't correctly put it in linear space?
Have you chosen the correct working/timeline color space in your project settings? The HDR palette and all other color space aware tools use that option as the expected color space they work by.
Do you know how to use resolve to simulate black soft filter? Or what's the math behind the black soft filter?Can we use math to calculate it?
Imitating physical filters can be quite difficult, but in terms of plugins, I'd recommend Scatter by Video Village. They do a great job!
@@KaurH Thanks, it's a little expensive, maybe I should buy a real physical filters😂
@@user-gd6pj6oh8p The real deal is indeed the better choice most of the time
Hai kaur, if we not change any colorspace or gamma, is dctl read it we use rec 709 gamma 2.4?
A DCTL doesn't inherently have a color space or transfer function. Those which do, as in this case, tend to transform from a transfer function encoded signal to linear, apply the image manipulations and then encode the image with the transfer function again. This is done as linear is how light is in it's natural state. As such applying doing manipulations on 'linear' light ie. w/o any encodings, has it work like physical light does in the real world.
Hope this answers your question.
@@KaurH thanks that’s help a lot
E'pic kh