[x265] [PATCH] param: update calculated maxCLL, maxFALL values to contentLightLevelInfo
Deepthi Nandakumar
deepthi at multicorewareinc.com
Wed Aug 26 16:16:13 CEST 2015
Right, is there a need to modify user's param structure?
On Aug 26, 2015 5:14 PM, "Steve Borho" <steve at borho.org> wrote:
> On 08/26, Deepthi Nandakumar wrote:
> > Agreed that's the general philosophy. But this works better if the user
> > wants to regenerate headers, because the encoder->param has now been
> > reset. Else, the user is responsible for
> >
> > a) copying stats->maxCLL to user Param
> > b) doing an encoder reconfig, and copying user param to encoder->param
> > c) generate headers
>
> this doesn't change the user's param structure
>
> --
> Steve Borho
> _______________________________________________
> x265-devel mailing list
> x265-devel at videolan.org
> https://mailman.videolan.org/listinfo/x265-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.videolan.org/pipermail/x265-devel/attachments/20150826/7eb0fc06/attachment.html>
More information about the x265-devel
mailing list