This is an automated email from the git hooks/post-receive script.

Git pushed a change to branch master
in repository ffmpeg.

    from b355200263 avcodec/mjpegdec: require progress in AVRn interlaced field 
loop
     new 517c3d5fc1 swscale/graph: re-check pixel format support in 
add_legacy_sws_pass()
     new 8366d5f8d6 swscale/tests/swscale: refactor format testing logic
     new c7046f0ab3 swscale/ops_backend: add missing float clear pattern
     new 3977bca9f4 swscale/utils: improve check for float formats that will be 
converted to uint16_t
     new 5a6bf8d4f4 swscale/tests/swscale: allow all backends for auxiliary 
conversions
     new 6b7fd40e25 swscale/swscale_unscaled: disable unscaled copy from 
yaf32be to grayf32be
     new 59166b4131 swscale/input: fix rgbf32 input (add half input functions)
     new 016cee7a02 tests/fate/sws-unscaled: constrain to -backends unstable
     new 7fc7aaf265 swscale/graph: prefer ops backend for floating point formats
     new 20b0a4faaa tests/fate: add fate-sws-unstable test

The 10 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "add" were already present in the repository and have only
been added to this reference.


Summary of changes:
 libswscale/graph.c                                 | 18 ++++++++--
 libswscale/input.c                                 | 37 +++++++++++++++++++++
 libswscale/ops_tmpl_float.c                        |  1 +
 libswscale/swscale_unscaled.c                      |  2 +-
 libswscale/tests/swscale.c                         | 38 ++++++++++++++++------
 libswscale/utils.c                                 |  2 +-
 tests/fate/libswscale.mak                          |  7 +++-
 .../fate/{ffmpeg-error-rate-fail => sws-unstable}  |  0
 8 files changed, 89 insertions(+), 16 deletions(-)
 copy tests/ref/fate/{ffmpeg-error-rate-fail => sws-unstable} (100%)

_______________________________________________
ffmpeg-cvslog mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to