[FFmpeg-trac] #7204(avcodec:closed): Integration of Turing Codec (HEVC encoder)
FFmpeg
trac at avcodec.org
Tue May 15 00:42:40 EEST 2018
#7204: Integration of Turing Codec (HEVC encoder)
-------------------------------------+-----------------------------------
Reporter: fantesy | Owner:
Type: enhancement | Status: closed
Priority: wish | Component: avcodec
Version: git-master | Resolution: wontfix
Keywords: HEVC | Blocked By:
Blocking: | Reproduced by developer: 0
Analyzed by developer: 0 |
-------------------------------------+-----------------------------------
Comment (by jkqxz):
H.265 encoders currently available in ffmpeg:
* x265 (software via libx265)
* Kvazaar (software via libkvazaar)
* Intel (software and hardware encoders via libmfx, or hardware-only via
VAAPI)
* AMD (hardware via AMF or VAAPI)
* Nvidia (hardware via NVENC)
I think Turing would probably be accepted if there were any particular
argument to do so, but currently it just looks like a closed research
project:
* It's pretty much stated that the API isn't stable, hence the suggested
patch avoiding any common options and using the string argument stuff to
push any incompatibility onto users.
* The open-source project looks like an unsupported wall-throw - e.g.
<https://github.com/bbc/turingcodec/commit/09a838c9feeb43ac410391e300b8b53ff660c721>.
* There was little attempt to show that it's actually good for anything -
no visible users, no useful benchmarks.
--
Ticket URL: <https://trac.ffmpeg.org/ticket/7204#comment:6>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker
More information about the FFmpeg-trac
mailing list