Im love with DRS20 but this issue needs to be addressed.

Most of the new features DVRS 20 brings to the table are completly amazing, I'm very proud to said that I bought the license since 17, and comparing back then to now is a huge upgrade.

The only thing that I see that is lacking on Davinci Resolve lately are adjustment clips and it's compatibility with OFX plugins and even some stock nodes. I think its a core issue that needs to be adressed.

The issues I been having are that some OFX plugins I use like: Universe or RSMB on their latest version, don't work very well with adjustment clips and not only that, the compatibility with the new keyframes function on this public beta is absolutely none, very buggy to the point that it doesn't work with adjustment clips.

Some examples are:

Stacking adjustment clips one above another with effects do weird behaviors on the previews and final renders
Non functional parameters tab | Keyframes tab

I used Sony Vegas before and the way adjustment layers work is the way I expected adjustment clips to work in Davinci Resolve but as said before, since the first time I used Davinci Resolve the compatibility with OFX plugins and even native nodes is not quite there, right now is so buggy that on this beta I got weird pink artifacts on the editing tab preview only using native nodes but at the time of exporting the artifacts were not there (before saying it's cache issues I don't use cache at all) it's something that I never had before and the spark that made me create this post, most of the time is using large adjustment clips with effects that breaks.

So please, if anybody from Davinci Resolve is reading, give a little bit more love to adjustment clips they are very handy and powerful. Love the program and I also appreciate the hard work you put in, 100% won't replace it for any other editing software. I made this topic because it's been a long time with updates not improving the compatibility and the lack of fixing errors regarding adjustment layers.

Additionally I'd love an option to manually refresh the previews from the editing tab because sometimes removing cache from the option we already have doesn't refresh the current preview unless you change something from the clip.

Adjustment clips work on the composite image of what is bellow. I would not use them stacked together. Its an accident waiting to happen, That should be done with nodes, which is the point of color page and fusion. Adjustment clips have their place. What you are trying to do is not it. I would not even try that. You are not using Photoshop. Use proper workflow. Use nodes.

the way adjustment layers work is the way I expected adjustment clips to work in Davinci Resolve

That may not be a reasonable expectation. They are different programs. Not all things will be a direct analog.

I use Red Giant OFX plug-ins as well. Even in 19.1.4 they behave erratically. This happens in Fusion and the Edit page. It could be Red Giant's issues but between the two companies, I'd put my money on the one that handle C4D, ZBrush, Mocha and Redshift to have better support for OFX.

I agree that the use of stacked Adjustment layers is a shaky proposition but in theory, it should work just fine. I reality, the processing order in Resolve might be a hot mess but we have no way of knowing that. It should render V1, then V2, and so on. In which case, stacking adjustments would be fine. My suspicion is that BM's implementation of OFX is incomplete since Fusion throws errors all over different OFX plugins but I'm only an end user.

Definitely try to make an adjustment/fusion layer that does all the processing in one flow.

Adjustment clips work on the composite image of what is bellow. I would not use them stacked together. Its an accident waiting to happen, That should be done with nodes, which is the point of color page and fusion. Adjustment clips have their place. What you are trying to do is not it. I would not even try that. You are not using Photoshop. Use proper workflow. Use nodes.

100% agree. I wish more people would understand that Adjustment Clips are -- to me -- a "last ditch" place where you can do a minor project-wide adjustment. I don't think it's a good idea to rely on it for composites or effects or noise reduction or anything like that. I feel the exact same way about Timeline nodes -- I think it's a mistake to try to do a lot in there.

We already have Pre-Clip Nodes, Post-Clip Nodes, and Node Stack Layers, and all of those are incredibly useful in terms of organizing corrections and making the signal path very clear. They also allow fast and easy changes, even when the edit itself is in a state of flux. But an Adjustment Clips (especially stacked together) are absolutely an accident waiting to happen.

I use Red Giant OFX plug-ins as well. Even in 19.1.4 they behave erratically. This happens in Fusion and the Edit page. It could be Red Giant's issues but between the two companies, I'd put my money on the one that handle C4D, ZBrush, Mocha and Redshift to have better support for OFX.

Red Giant's plug-ins were so unstable on my systems with Resolve 16 and 17, I raised the issue with Maxon, and they ultimately agreed to refund my money. New Blue Effects were also unpredictable and erratic. BorisFX, Sapphire, Neat Video, Dehancer, Filmbox, Sapphire, Beauty Box, Scatter, Contour, and DigiDiff all work flawlessly -- zero problems with any of those in Resolve.

HitFilm Ignite is another developer where their plug-ins used to be compatible with Resolve, then fell off a cliff, I think when the company went through a few ownership changes.

Adjustment clips work on the composite image of what is bellow. I would not use them stacked together. Its an accident waiting to happen, That should be done with nodes, which is the point of color page and fusion. Adjustment clips have their place. What you are trying to do is not it. I would not even try that. You are not using Photoshop. Use proper workflow. Use nodes.

I know what Adjustment clips are and trust that I also tried using nodes in a single adjustment clip but as stated before, even using native nodes on adjustment clips right now it's a gamble, making weird artifacts that I never had prior 20 version, not only that, stacking adjustment clips ABSOLUTELY had 0 issues before this update too. It might not be the "proper workflow" but it's convenient (personally and I'm sure many editors too) interms of easy editing when you have big node trees with keyframes, custom transitions and when it's a project with multiple different clips and you can't just go 1 by 1 copying and pasting effects. There is no reason for adjustment clips doing less that they were capable of doing before version 20.

[quote=Red Giant's plug-ins were so unstable on my systems with Resolve 16 and 17, I raised the issue with Maxon, and they ultimately agreed to refund my money. New Blue Effects were also unpredictable and erratic. BorisFX, Sapphire, Neat Video, Dehancer, Filmbox, Sapphire, Beauty Box, Scatter, Contour, and DigiDiff all work flawlessly -- zero problems with any of those in Resolve.

Yeah, I didn't even bother to try them for a few revisions after how flakey they were in 16. I figured the stability increases came as a combination of Resolve solidifying their OFX support more and Redgiant starting to pay more attention to Resolve as it became more of their user base. I remember a few update notes about OFX over the years. It must be a small hell to have to be a developer trying to get things like this to work 100%. Even now I will pre-render the flow as close to the plug in as I can and keep if from processing if at all possible. They do make some sexy additions though.

P.S. I love hearing how you look at the post process. Your use of terms like "signal path" really show where your education and experience started. Even if it's all digital now, we absolutely still should keep that stuff in consideration.

+1

yesterday I had adjustment clips on photos for a slideshow and it eliminated my ability to have transparency so I had to do workarounds to have that blurry background and Blanking Fill didn't work properly.