~siretart/x264/trunk : changes

~siretart/x264/trunk » Changes to common/frame.h from revision 2969

From Revision 2969 to 2116

Rev	Summary	Authors	Date
2961	Bump dates to 2019 Bump dates to 2019	Henrik Gramner	5 years ago
2922	x86: AVX-512 plane_copy and plane_copy_swap x86: AVX-512 plane_copy and plane_copy_swap Avoid the scalar C wrapper by utilizing opmasks to prevent overreading the input buffer.	Henrik Gramner	6 years ago
2897	Bump dates to 2018 Bump dates to 2018	Henrik Gramner	6 years ago
2868	Unify 8-bit and 10-bit CLI and libraries Unify 8-bit and 10-bit CLI and libraries Add 'i_bitdepth' to x264_param_t with the corresponding '--output-depth' CLI option to set the bit depth at runtime. Drop the 'x264_bit_depth' global variable. Rather than hardcoding it to an incorrect value, it's preferable to induce a linking failure. If applications relies on this symbol this will make it more obvious where the problem is. Add Makefile rules that compiles modules with different bit depths. Assembly on x86 is prefixed with the 'private_prefix' define, while all other archs modify their function prefix internally. Templatize the main C library, x86/x86_64 assembly, ARM assembly, AARCH64 assembly, PowerPC assembly, and MIPS assembly. The depth and cache CLI filters heavily depend on bit depth size, so they need to be duplicated for each value. This means having to rename these filters, and adjust the callers to use the right version. Unfortunately the threaded input CLI module inherits a common.h dependency (input/frame -> common/threadpool -> common/frame -> common/common) which is extremely complicated to address in a sensible way. Instead duplicate the module and select the appropriate one at run time. Each bitdepth needs different checkasm compilation rules, so split the main checkasm target into two executables.	Vittorio Giovara	6 years ago
2749	Bump dates to 2017 Bump dates to 2017	Henrik Gramner	7 years ago
2743	Cosmetics Cosmetics Also make x264_weighted_reference_duplicate() static.	Anton Mitrofanov	7 years ago
2660	Bump dates to 2016 Bump dates to 2016	Henrik Gramner	8 years ago
2566	Use forced frame types in slicetype analysis Use forced frame types in slicetype analysis This should improve MBTree and VBV when a lot of forced frame types are used.	Anton Mitrofanov	9 years ago
2526	Bump dates to 2015 Bump dates to 2015	Anton Mitrofanov	9 years ago
2384	Bump dates to 2014 Bump dates to 2014 Also update AUTHORS file and my e-mail address in the headers of various files.	Henrik Gramner	10 years ago
2354	Transparent hugepage support Transparent hugepage support Combine frame and mb data mallocs into a single large malloc. Additionally, on Linux systems with hugepage support, ask for hugepages on large mallocs. This gives a small performance improvement (~0.2-0.9%) on systems without hugepage support, as well as a small memory footprint reduction. On recent Linux kernels with hugepage support enabled (set to madvise or always), it improves performance up to 4% at the cost of about 7-12% more memory usage on typical settings.. It may help even more on Haswell and other recent CPUs with improved 2MB page support in hardware.	Henrik Gramner	11 years ago
2286	OpenCL lookahead OpenCL lookahead OpenCL support is compiled in by default, but must be enabled at runtime by an --opencl command line flag. Compiling OpenCL support requires perl. To avoid the perl requirement use: configure --disable-opencl. When enabled, the lookahead thread is mostly off-loaded to an OpenCL capable GPU device. Lowres intra cost prediction, lowres motion search (including subpel) and bidir cost predictions are all done on the GPU. MB-tree and final slice decisions are still done by the CPU. Presets which do not use a threaded lookahead will not use OpenCL at all (superfast, ultrafast). Because of data dependencies, the GPU must use an iterative motion search which performs more total work than the CPU would do, so this is not work efficient or power efficient. But if there are spare GPU cycles to spare, it can often speed up the encode. Output quality when OpenCL lookahead is enabled is often very slightly worse in quality than the CPU quality (because of the same data dependencies). x264 must compile its OpenCL kernels for your device before running them, and in order to avoid doing this every run it caches the compiled kernel binary in a file named x264_lookahead.clbin (--opencl-clbin FNAME to override). The cache file will be ignored if the device, driver, or OpenCL source are changed. x264 will use the first GPU device which supports the required cl_image features required by its kernels. Most modern discrete GPUs and all AMD integrated GPUs will work. Intel integrated GPUs (up to IvyBridge) do not support those necessary features. Use --opencl-device N to specify a number of capable GPUs to skip during device detection. Switchable graphics environments (e.g. AMD Enduro) are currently not supported, as some have bugs in their OpenCL drivers that cause output to be silently incorrect. Developed by MulticoreWare with support from AMD and Telestream.	Steve Borho	11 years ago
2284	Add slices-max feature Add slices-max feature The H.264 spec technically has limits on the number of slices per frame. x264 normally ignores this, since most use-cases that require large numbers of slices prefer it to. However, certain decoders may break with extremely large numbers of slices, as can occur with some slice-max-size/mbs settings. When set, x264 will refuse to create any slices beyond the maximum number, even if slice-max-size/mbs requires otherwise.	Fiona Glaser	11 years ago
2245	Bump dates to 2013 Bump dates to 2013	Loren Merritt	11 years ago
2212	Export the average effective CRF of each frame Export the average effective CRF of each frame Useful to judge the resulting quality of a frame when VBV is enabled.	Fiona Glaser	12 years ago
2197	Add mb_info API for signalling constant macroblocks Add mb_info API for signalling constant macroblocks Some use-cases of x264 involve encoding video with large constant areas of the frame. Sometimes, the caller knows which areas these are, and can tell x264. This API lets the caller do this and adds internal tracking of modifications to macroblocks to avoid problems. This is really only suitable without B-frames. An example use-case would be using x264 for VNC.	Fiona Glaser	12 years ago
2183	Sliced-threads: do hpel and deblock after returning Sliced-threads: do hpel and deblock after returning Lowers encoding latency around 14% in sliced threads mode with preset superfast. Additionally, even if there is no waiting time between frames, this improves parallelism, because hpel+deblock are done during the (singlethreaded) lookahead. For ease of debugging, dump-yuv forces all of the threads to wait and finish instead of setting b_full_recon.	Fiona Glaser	12 years ago
2172	Fix incorrect zero-extension assumptions in x86_64 asm Fix incorrect zero-extension assumptions in x86_64 asm Some x264 asm assumed that the high 32 bits of registers containing "int" values would be zero. This is almost always the case, and it seems to work with gcc, but it is not guaranteed by the ABI. As a result, it breaks with some other compilers, like Clang, that take advantage of this in optimizations. Accordingly, fix all x86 code by using intptr_t instead of int or using movsxd where neccessary. Also add checkasm hack to detect when assembly functions incorrectly assumes that 32-bit integers are zero-extended to 64-bit.	Henrik Gramner	12 years ago
2154	Bump dates to 2012 Bump dates to 2012	Hii	12 years ago
2116	Pass through user data Pass through user data	Kieran Kunhya	12 years ago

Older »