On 12/5/2017 2:05 PM, Gyan Doshi wrote: > > On 12/5/2017 7:21 PM, Derek Buitenhuis wrote: > >> This is inconsistent with the way libx264.c does it. It calls the profile >> function before the param parsing. > > From http://x265.readthedocs.io/en/default/cli.html#profile-level-tier > > "API users must call x265_param_apply_profile() after configuring their > param structure. Any changes made to the param structure after this call > might make the encode non-compliant." > > and > > "Also note that x265 determines the decoder requirement profile and > level in three steps. First, the user configures an x265_param structure > with their suggested encoder options and then optionally calls > x265_param_apply_profile() to enforce a specific profile (main, main10, > etc). "
Sounds like a very good reason to me, then. Patch OK with log line dropped. - Derek _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel