Removing DenoisePass in favor of an API schema

Hi,
We originally included a prim DenoisePass in usdRender that could be used to store settings related to the denoising of a given RenderPass prim. A RenderPass prim had a relationship to a DenoisePrim, a la RenderProducts. The idea being that multiple RenderPass prims may want to share denoise settings.

However, now that we have integrated usdRender further into our pipeline, we’ve decided that it makes more sense to instead share settings on RenderPass prims via inheritance. In that case, the separate DenoisePass prim becomes redundant, as any shared denoise settings can live in an API schema on the parent RenderPass. So we’ve removed DenoisePass in favor of an API schema. And since there’s no broadly applicable denoise settings, we’ve kept our DenoisePassAPI schema internal only, as it only has settings specific to how we denoise.

I’m hoping that DenoisePass is not widely used, so hopefully this change is coming before any serious attempts of integrating a usd-backed denoise pipeline. If you have questions or concerns let me know.

Thanks,
Jeremy