Changes between Version 5 and Version 6 of swscale


Ignore:
Timestamp:
Jan 24, 2017, 3:35:32 PM (10 years ago)
Author:
Ronald S. Bultje
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • swscale

    v5 v6  
    55- very static in its core conversion approach: "fast" (direct) AtoB converters vs. "scaled path" (the generic case)
    66  * the fast AtoB converters are cute but cannot be chained. so anything not directly covered by a fast path goes through generic path even if it's slower than a chain of two fast paths
     7    - the pre-swscale imgconvert.c implementation (https://ffmpeg.org/doxygen/0.5/imgconvert_8c-source.html) at least attempted to do chaining, so strictly speaking this is a regression
    78  * the scaled path is static and limited
    89    - only YUV allowed as internal common format
    … …  
    3435    - dynamic ordering (chaining) of filters
    3536    - merging of operations (e.g. reading yuv input and yuv2rgb conversion to prevent memory stores) where possible and where it gains significant speed
     37  * it may well be possible for the "fast" and "scaled" codepaths to be mixed, although this obviously needs more thought
    3638- simd / platform optimizations
    3739  * these should ideally not be exposed in the common code (i.e. a grep for x86 in libswscale/*.c should be mostly empty)