Opened 5 years ago
Last modified 5 years ago
#8060 new enhancement
hwupload_qsv
Reported by: | fortman | Owned by: | |
---|---|---|---|
Priority: | normal | Component: | avfilter |
Version: | git-master | Keywords: | hwupload_qsv |
Cc: | Blocked By: | ||
Blocking: | Reproduced by developer: | no | |
Analyzed by developer: | no |
Description
Summary of the bug:
When mixing multiple HW contexts at the same time, some filter graphs are impossible. That's because in some cases we lack the option for selecting the target HW device. For example, if we're using "-filter_hw_device cuda", then it's impossible to upload to a QSV device. But if you use "-filter_hw_device qsv" then you have the option to use the filter "hwupload_cuda".
So, I suggest to create the filter "hwupload_qsv" too (and even other versions like "hwupload_vappi" for example).
Please consider this enhancement.
Thank you!
Change History (4)
follow-up: 2 comment:1 by , 5 years ago
comment:2 by , 5 years ago
Hi heleppkes,
Replying to heleppkes:
If improvements are needed for using multiple hardware devices, then those should be made in a more generic manner, and not filters cloned for no other reason then using a different device.
Using your argument the developers require to remove "hwupload_cuda". So I don't agree with you. The filter "hwupload" isn't compatible with different hw context. And the most simple, elegant and powerful solution is to enhance all hw platforms supported with a simple "hwupload_*".
Regards.
follow-up: 4 comment:3 by , 5 years ago
In an ideal world hwupload_cuda should indeed be removed. But it existed before the generic infrastructure was brought to a point where it is today, so it was grandfathered in.
Thats no reason to make even more of those filters, because they are anything but elegant.
comment:4 by , 5 years ago
Replying to heleppkes:
In an ideal world hwupload_cuda should indeed be removed. But it existed before the generic infrastructure was brought to a point where it is today, so it was grandfathered in.
OK, I don't know it.
Thank you for the explanation.
Replying to heleppkes:
Thats no reason to make even more of those filters, because they are anything but elegant.
You may feel they're not elegant, but they're useful. Please, note that some filter graphs are IMPOSSIBLE without such type of filters.
So which do you prefer: elegance or functionality?
Please, with all due respect, take into account the needs of users, and not personal preferences or interests.
Regards.
If improvements are needed for using multiple hardware devices, then those should be made in a more generic manner, and not filters cloned for no other reason then using a different device.