01.05.2021, 14:55
I'm using Hybrid 2021.04.12.1
When I'm encoding the videos with NVEnc, some times happen that Hybrid add cropping information even if "Picture Crop" checkbox is unchecked.
To speed-up the encoding I check the box NVEnc->Hardware->Only use encoder, so that all the video stuff, including eventually the crop, are performed by NVEnc.
At the following link it is available a sample where is applied the wrong cropping.
https://file.re/2021/05/01/sample1080px264/
Also I attached the full debug output.
It seems that the problem happen if previously has been used the "Picture Crop" to crop some file, then if the file has a size of 1080x804 (like in the sample provided).
Hybrid add to the encoding program the following command "--crop 0,0,0,276 --vpp-resize default --output-res 1920x804", which is wrong.
It seems that Hybrid try to fill the gap with the 1080p resolution, but in this case has not been asked and it is wrong.
Unfortunately I was unable to find an exact sequence to reproduce this problem, it seems that is activated by some internal "state" of the program and after some encoding.
Please, read the 'Infos needed to fix&reproduce bugs,..'-sticky before you post about a problem.
When I'm encoding the videos with NVEnc, some times happen that Hybrid add cropping information even if "Picture Crop" checkbox is unchecked.
To speed-up the encoding I check the box NVEnc->Hardware->Only use encoder, so that all the video stuff, including eventually the crop, are performed by NVEnc.
At the following link it is available a sample where is applied the wrong cropping.
https://file.re/2021/05/01/sample1080px264/
Also I attached the full debug output.
It seems that the problem happen if previously has been used the "Picture Crop" to crop some file, then if the file has a size of 1080x804 (like in the sample provided).
Hybrid add to the encoding program the following command "--crop 0,0,0,276 --vpp-resize default --output-res 1920x804", which is wrong.
It seems that Hybrid try to fill the gap with the 1080p resolution, but in this case has not been asked and it is wrong.
Unfortunately I was unable to find an exact sequence to reproduce this problem, it seems that is activated by some internal "state" of the program and after some encoding.
Please, read the 'Infos needed to fix&reproduce bugs,..'-sticky before you post about a problem.