[FFmpeg-trac] #8765(avcodec:new): advice for merging upstream: tvheadend vaapi fix
FFmpeg
trac at avcodec.org
Tue Jun 30 03:11:33 EEST 2020
#8765: advice for merging upstream: tvheadend vaapi fix
---------------------------------+---------------------------------------
Reporter: th0ma7 | Type: enhancement
Status: new | Priority: normal
Component: avcodec | Version: git-master
Keywords: | Blocked By:
Blocking: | Reproduced by developer: 0
Analyzed by developer: 0 |
---------------------------------+---------------------------------------
Hi,
Over the past year I've taken over the role of maintaining the ffmpeg
package for SynoCommunity. From the repository history there where 2x
existing patches, relatively similar, for which the name relates to fixes
for tvheadend under x265 & vaapi:
*
https://github.com/SynoCommunity/spksrc/blob/master/cross/ffmpeg/patches/003
-tvheadend-ffmpeg.libx265.patch
*
https://github.com/SynoCommunity/spksrc/blob/master/cross/ffmpeg/patches/004
-tvheadend-ffmpeg.vaapi_encode.patch
With the upgrade from 4.2.3 to 4.3.0 I noticed that the libx265 patch got
merged upstream in a somewhat similar form to the patch I was keeping
around from the previous package maintainer, which is a really awesome
news.
This makes me wonder whether the changes to libavcodec/libx265.c wouldn't
be appropriate to be merged upstream as well for libavcodec/vaapi_encode.c
based on the second patch link above on some shaper form?
Bare with me, I'm not a C coder, although, as the patch doesn't apply
anymore against version 4.3, I thought it might be a good time to seek for
advice, hopefully leading to getting "this" fix merged upstream.
Thnx really much in advance.
--
Ticket URL: <https://trac.ffmpeg.org/ticket/8765>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker
More information about the FFmpeg-trac
mailing list