03.02.2021, 16:06
Windows x64
I had this issue a long time ago but did not give it too much importance. So I did not report on it.
In the August 2020 release, you could apply this filter on Luma and Chroma at the same time. (YUV) or (RGB) mode, depending on the source, one of the two modes always worked and the other did not.
In the December 2020 version, and I think the previous one too, but I'm not sure, only Luma (Y) or Chroma (UV) works, the auto mode is equal to Luma. This was already the case in the August version.
If YUV or RGB is selected, it does not work in either case, any source, does nothing at all. Encode doesn't start if it is selected one of these modes.
In the August version, it not only worked but you could tell the difference. In the old version (August) without using manual scripts only one denoise filter could be applied at a time, unlike the new versions. I don't know if this has something to do with it. But it could be the case too.
The filter should really be applicable in both planes at the same time. I have never gotten this filter to work with CPUs, although it makes sense as it is intended for use with GPUs. But I also mention it in case it has any importance.
Thank you very much.
I had this issue a long time ago but did not give it too much importance. So I did not report on it.
In the August 2020 release, you could apply this filter on Luma and Chroma at the same time. (YUV) or (RGB) mode, depending on the source, one of the two modes always worked and the other did not.
In the December 2020 version, and I think the previous one too, but I'm not sure, only Luma (Y) or Chroma (UV) works, the auto mode is equal to Luma. This was already the case in the August version.
If YUV or RGB is selected, it does not work in either case, any source, does nothing at all. Encode doesn't start if it is selected one of these modes.
In the August version, it not only worked but you could tell the difference. In the old version (August) without using manual scripts only one denoise filter could be applied at a time, unlike the new versions. I don't know if this has something to do with it. But it could be the case too.
The filter should really be applicable in both planes at the same time. I have never gotten this filter to work with CPUs, although it makes sense as it is intended for use with GPUs. But I also mention it in case it has any importance.
Thank you very much.