Opened 5 years ago
Last modified 5 years ago
#8603 new enhancement
QSV VPPFrameRateConversion enhancements
| Reported by: | OpenSourceAnarchist | Owned by: | |
|---|---|---|---|
| Priority: | wish | Component: | avfilter |
| Version: | git-master | Keywords: | qsv |
| Cc: | Blocked By: | ||
| Blocking: | Reproduced by developer: | no | |
| Analyzed by developer: | no |
Description
Summary of the bug:
In vf_vpp_qsv.c, there is support for mfxExtVPPFrameRateConversion. However, the only algorithm used is MFX_FRCALGM_DISTRIBUTED_TIMESTAMP. In Intel Media SDK, two other algorithms are supported: MFX_FRCALGM_PRESERVE_TIMESTAMP and MFX_FRCALGM_FRAME_INTERPOLATION.
It would be useful to allow the user to select their preferred algorithm instead of only supporting MFX_FRCALGM_DISTRIBUTED_TIMESTAMP. Moreover, enabling support for MFX_FRCALGM_FRAME_INTERPOLATION would allow users to have another frame interpolation filter than minterpolate which could provide significant speed enhancements on supported hardware.
Note:
See TracTickets
for help on using tickets.
The usefulness may not be as great as I initially anticipated. See clarification of frame interpolation support in MediaSDK here: https://github.com/Intel-Media-SDK/MediaSDK/issues/2065. Essentially, MFX_FRCALGM_FRAME_INTERPOLATION was likely not implemented fully in MediaSDK so it simply duplicates/drops frames instead of interpolating them.
In case this gets corrected, though, ffmpeg should still expose all the FrameRateConversion algorithms to the user.