Skip to content

v0.0.12

Latest

Choose a tag to compare

@fluxin fluxin released this 22 Oct 20:01
· 38 commits to main since this release

encoders: VP9 forward probability updates and a noise-tolerant split, H.264 motion seeds for fast pans, a faster H.265 encoder with identical output, and an ultrafast speed preset. VP9: the compressed header sends forward updates (coefficients, skip, transform size, inter and intra modes, references, partitions, motion vectors) where a delta pays for its own bits on the frame's counts; tiles stage their symbols and code them in parallel on the pool once the header has settled the probabilities; an inter block splits only past twice the expected quantizer noise. At equal quality (BD-rate over q 60 to 180 on 720p, 1280x544 and 1080p camera clips and a 40 px/frame pan) files are 4.7 to 13.2% smaller than v0.0.11 at 1.00 to 1.06x the time; the 320x180 animation is 1.6 to 1.9x libvpx's size at matched PSNR, from 11x. H.264: the integer search also starts from the previous macroblock's and the previous search's vectors, and a poorly predicted 16x16 also descends from a grid out to three search radii, keeping the cheaper descent; a lone coefficient in an 8x8 is dropped when its bits cost more than the distortion it removes: 0.7 to 3.0% smaller on the camera clips and 77% on the pan (v0.0.11 lost the motion), 1.01 to 1.02x the time. H.265: the bitstream pass skips the prediction and reconstruction the search already did and takes the deblocked picture SAO was decided on, and the mode decision saves a candidate's state only when another follows: output byte-identical to v0.0.11 on every clip and QP, 0.94 to 0.97x the time. ultrafast (media.Config, video.Writer_Config, the H.264 and H.265 encoder configs) prefers encode speed over size: H.264 searches one reference and 16x16 motion and settles on inter sooner (0.55 to 0.58x the time, -1 to +32% BD-rate); H.265 decides the CU tree top-down, tries four intra modes and searches a diamond to half-pel (0.32 to 0.37x, +28 to +66%); VP9 and the hardware encoders do not use it yet. The VP9 encoder README now describes v0.0.11's
backward adaptation, which it still called absent. Gates: ci check --programs and test; vp9_encode_check (reconstruction identical to FFmpeg and libvpx at every size, q and block size, alpha, Chromium transparency); encoder_matrix and 14 more H.264 streams (FFmpeg equals our decoder, regular and ultrafast); chroma_check_h265 (84 cases) and 20 ultrafast cases (reconstruction equals our decoder, FFmpeg and HM, picture hashes checked)