I checked the crop filter and scale_vaapi implementation. The crop
filter omits the requested crop width and height from the link, and
expects the filter to know the final size ahead of time. So it seems
the user is expected to provide the hardware scale filter with a final
width and the height. sc
I think the passthrough flag should be validated at filter processing
time as well. Currently passthrough is checked at filter creation
time, when only input/output sizes are available. During
cudascale_filter_frame, the frame crop values should also be verified
to determine if it is truly a no-op
On 10.09.2024 20:10, Koushik Dutta wrote:
The crop filter has no effect on scale_cuda:
-vf crop=100:100,scale_cuda=300x300
Hardware frames (AV_PIX_FMT_FLAG_HWACCEL) are expected to use the crop_*
properties,
as seen in the implementation vf_crop.c.
The current workaround is to hwdownload the
On 10.09.2024 20:10, Koushik Dutta wrote:
The crop filter has no effect on scale_cuda:
-vf crop=100:100,scale_cuda=300x300
Hardware frames (AV_PIX_FMT_FLAG_HWACCEL) are expected to use the crop_*
properties,
as seen in the implementation vf_crop.c.
The current workaround is to hwdownload the
The crop filter has no effect on scale_cuda:
-vf crop=100:100,scale_cuda=300x300
Hardware frames (AV_PIX_FMT_FLAG_HWACCEL) are expected to use the crop_*
properties,
as seen in the implementation vf_crop.c.
The current workaround is to hwdownload the full frame
and perform the crop on CPU.
---
