+- Selur's Little Message Board (https://forum.selur.net)
+-- Forum: Hybrid - Support (https://forum.selur.net/forum-1.html)
+--- Forum: Problems & Questions (https://forum.selur.net/forum-3.html)
+--- Thread: Resize issue with "DGDecNV/IM Crop/Resize" (/thread-1692.html)
Pages:
1
2
RE: Resize issue with "DGDecNV/IM Crop/Resize" - Dan64 - 22.01.2021
I was able to test DGDecNV using VSEdit. Actually it is an hardware encoder using Nvidia GPU. For the resizing it is using the GPU and its quality is comparable to the one produced with NVenc, with the significant difference that NVenc is also and hardware encoder and it is much faster than DGDecNV.
Since in Hybrid is available a very good interface to NVenc, which is able to provide good hardware encoding both in h264 and h265, it does not makes sense using DGDecNV when the task to be performed can be execute also by using NVenc.
RE: Resize issue with "DGDecNV/IM Crop/Resize" - Selur - 22.01.2021
Quote:I was able to test DGDecNV using VSEdit. Actually it is an hardware encoder using Nvidia GPU.DGDecNV is a decoder using the NVIDIA VPU.
Quote:For the resizing it is using the GPU and its quality is comparable to the one produced with NVenc,No surprise both use the same chip.
Quote: with the significant difference that NVenc is also and hardware encoder and it is much faster than DGDecNV.Yes, hardware only decoding + filtering + encoding is faster.
Quote: Since in Hybrid is available a very good interface to NVenc, which is able to provide good hardware encoding both in h264 and h265, it does not makes sense using DGDecNV when the task to be performed can be execute also by using NVenc.Which is why when 'NVEncC->Hardware->Only use encoder' is enabled both Avisynth and Vapoursynth are disabled.
Cu Selur
RE: Resize issue with "DGDecNV/IM Crop/Resize" - Dan64 - 22.01.2021
Hello Selur
The last development version is working.
Thanks!