This should fix Issue #470. Patch is attached.
# HG changeset patch # User Nomis101 <[email protected]> # Date 1555164185 -7200 # Sat Apr 13 16:03:05 2019 +0200 # Node ID b89d065b20751f3f20d542faa2a75dba74bb9982 # Parent 768ab38fd5fd104a8d58f42b646d6117d63b2c0a Fix for Issue #470 diff -r 768ab38fd5fd -r b89d065b2075 source/x265.h --- a/source/x265.h Thu Apr 04 13:35:58 2019 +0530 +++ b/source/x265.h Sat Apr 13 16:03:05 2019 +0200 @@ -1845,17 +1845,17 @@ static const char * const x265_preset_na * with ultrafast mapping to "0" and placebo mapping to "9". This mapping may * of course change if new presets are added in between, but will always be * ordered from fastest to slowest. * * Warning: the speed of these presets scales dramatically. Ultrafast is a full * 100 times faster than placebo! * * Currently available tunings are: */ -static const char * const x265_tune_names[] = { "psnr", "ssim", "grain", "zerolatency", "fastdecode", 0 }; +static const char * const x265_tune_names[] = { "psnr", "ssim", "grain", "zerolatency", "fastdecode", "animation", 0 }; /* returns 0 on success, negative on failure (e.g. invalid preset/tune name). */ int x265_param_default_preset(x265_param *, const char *preset, const char *tune); /* x265_picture_alloc: * Allocates an x265_picture instance. The returned picture structure is not * special in any way, but using this method together with x265_picture_free() * and x265_picture_init() allows some version safety. New picture fields will
Issue470.bin
Description: application/macbinary
_______________________________________________ x265-devel mailing list [email protected] https://mailman.videolan.org/listinfo/x265-devel
