[FFmpeg-devel] [PATCH V5 0/2] Add libsvt HEVC encoder wrapper

mypopy at gmail.com mypopy at gmail.com
Mon Dec 24 03:30:43 EET 2018

On Sun, Dec 23, 2018 at 12:57 AM Jean-Baptiste Kempf <jb at videolan.org> wrote:
> Hello,
> On Sat, 22 Dec 2018, at 13:02, Carl Eugen Hoyos wrote:
> > > HEVC-compliant encoder library core that achieves excellent density-quality
> >
> > I don't find it ideal that FFmpeg git claims that an Intel encoder
> > does something "excellent" - unrelated to our actual opinion.
> > Please rephrase.
> My understanding from the testing we've done, is that SVT is a good encoder for live cases, but clearly not excellent in all cases, notably the VOD scenarios that are often used with FFmpeg.
For this part, SVT-HEVC will public a white paper (Now the white paper
on the internal legal review status, after the review finish, will)
> > > tradeoffs, and is highly optimized for Intel Xeon Scalable Processor and
> >
> > (and while there, also remove / change "highly optimized")
> Yep, mention AVX-512, not the marketing terms.
Will update as the comments :)
> > > Xeon D processors. Intel open source SVT-HEVC encoder in:
> > > https://github.com/intel/SVT-HEVC.
> >
> > > This wrapper work with SVT-HEVC master branch, more information can get
> > > from https://github.com/intel/SVT-HEVC/blob/new_api/ffmpeg_plugin/.
> >
> > This is irrelevant:
> > If SVT is another example of a library that does not plan some kind
> > of api stability, we should not merge your patch.
> > If api stability is to be expected, the sentence is not necessary.
> API will be stable, from my understandings, but not soon.
I've talked with the SVT-HEVC guys, I think the API is a stable status
now. (Maybe have small change if adds/export some new features, but in
this type case, SVT-HEVC will update the version, so we can cover this
in the FFmpeg wrappers to check the SVT-HEVC version).

More information about the ffmpeg-devel mailing list