Skip to content

F
ffmpeg.wasm-core
Switch branch/tag
  1. 18 Apr, 2018 1 commit
  3. 17 Apr, 2018 1 commit
  5. 04 Apr, 2018 1 commit
  7. 03 Apr, 2018 2 commits
    • wm4's avatar
      avutil/pixdesc: deprecate AV_PIX_FMT_FLAG_PSEUDOPAL · d6fc031c
      wm4 authored 
      PSEUDOPAL pixel formats are not paletted, but carried a palette with the
intention of allowing code to treat unpaletted formats as paletted. The
palette simply mapped the byte values to the resulting RGB values,
making it some sort of LUT for RGB conversion.

It was used for 1 byte formats only: RGB4_BYTE, BGR4_BYTE, RGB8, BGR8,
GRAY8. The first 4 are awfully obscure, used only by some ancient bitmap
formats. The last one, GRAY8, is more common, but its treatment is
grossly incorrect. It considers full range GRAY8 only, so GRAY8 coming
from typical Y video planes was not mapped to the correct RGB values.
This cannot be fixed, because AVFrame.color_range can be freely changed
at runtime, and there is nothing to ensure the pseudo palette is
updated.

Also, nothing actually used the PSEUDOPAL palette data, except xwdenc
(trivially changed in the previous commit). All other code had to treat
it as a special case, just to ignore or to propagate palette data.

In conclusion, this was just a very strange old mechnaism that has no
real justification to exist anymore (although it may have been nice and
useful in the past). Now it's an artifact that makes the API harder to
use: API users who allocate their own pixel data have to be aware that
they need to allocate the palette, or FFmpeg will crash on them in
_some_ situations. On top of this, there was no API to allocate the
pseuo palette outside of av_frame_get_buffer().

This patch not only deprecates AV_PIX_FMT_FLAG_PSEUDOPAL, but also makes
the pseudo palette optional. Nothing accesses it anymore, though if it's
set, it's propagated. It's still allocated and initialized for
compatibility with API users that rely on this feature. But new API
users do not need to allocate it. This was an explicit goal of this
patch.

Most changes replace AV_PIX_FMT_FLAG_PSEUDOPAL with FF_PSEUDOPAL. I
first tried #ifdefing all code, but it was a mess. The FF_PSEUDOPAL
macro reduces the mess, and still allows defining FF_API_PSEUDOPAL to 0.

Passes FATE with FF_API_PSEUDOPAL enabled and disabled. In addition,
FATE passes with FF_API_PSEUDOPAL set to 1, but with allocation
functions manually changed to not allocating a palette.
      d6fc031c
    • Tobias Rapp's avatar
      fftools/cmdutils: add support for level flag in loglevel option parser · 4b736bc9
      Tobias Rapp authored 
      Allows to manage the AV_LOG_PRINT_LEVEL flag as a prefix to the loglevel
option value, similar to the existing AV_LOG_SKIP_REPEATE flag. Adds
support for setting flags relative to the existing value by using a +/-
prefix.

Previous version reviewed-by: Michael Niedermayer <michael@niedermayer.cc>
Signed-off-by: 's avatarTobias Rapp <t.rapp@noa-archive.com>
      4b736bc9
  9. 02 Apr, 2018 2 commits
  11. 01 Apr, 2018 1 commit
    • Jan Ekström's avatar
      ffmpeg: prevent premature EOF in sub2video with nullptr AVSubtitles · e760c12a
      Jan Ekström authored 
      With certain types of input and the filter chain getting re-initialized
or re-configured, multiple nullptr AVSubtitles can get pushed into
sub2video_update() in a row from sub2video_heartbeat.

This causes end_pts, and on the next round pts, to become INT64_MAX,
latter of which signals EOF in framesync, leading to complete loss of
subtitles from that point on.

Thus, check that the sub2video.end_pts is smaller than INT64_MAX
in a similar fashion to sub2video_flush before sending out the
nullptr AVSubtitle. This keeps premature EOFs from happening in
framesync and the subtitle overlay is kept past the filter chain
re-initializations/configurations.
      e760c12a
  13. 31 Mar, 2018 1 commit
  15. 30 Mar, 2018 1 commit
  17. 28 Mar, 2018 2 commits
  19. 24 Mar, 2018 2 commits
  21. 22 Mar, 2018 1 commit
  23. 20 Mar, 2018 1 commit
  25. 17 Mar, 2018 1 commit
  27. 16 Mar, 2018 1 commit
  29. 12 Mar, 2018 1 commit
  31. 05 Mar, 2018 2 commits
  33. 27 Feb, 2018 1 commit
  35. 24 Feb, 2018 2 commits
  37. 23 Feb, 2018 1 commit
  39. 08 Feb, 2018 1 commit
  41. 06 Feb, 2018 2 commits
  43. 02 Feb, 2018 2 commits
  45. 28 Jan, 2018 1 commit
  47. 25 Jan, 2018 1 commit
    • Mark Thompson's avatar
      ffmpeg: Ignore SIGPIPE · 74cf4a75
      Mark Thompson authored 
      On systems which deliver SIGPIPE (Unices), a broken pipe will currently
result in the immediate termination of the ffmpeg process (the default
disposition as required by POSIX).  This is undesirable, because while
the broken pipe is likely fatal to useful cleanup of whatever component
is writing to it, there might be other components which can do useful
cleanup - for example, a muxer on another stream may still need to write
indexes to complete a file.  Therefore, set the signal disposition for
SIGPIPE to ignore the signal - the call which caused the signal will
fail with EPIPE and the error will be propagated upwards like any other
I/O failure on a single stream.
      74cf4a75
  49. 07 Jan, 2018 1 commit
  51. 06 Jan, 2018 1 commit
  53. 04 Jan, 2018 1 commit
  55. 26 Dec, 2017 1 commit
  57. 28 Nov, 2017 2 commits
  59. 26 Nov, 2017 1 commit
  61. 22 Nov, 2017 1 commit
    • Mark Thompson's avatar
      lavu,lavfi,ffmpeg: Remove experimental OpenCL API · 3650cb2d
      Mark Thompson authored 
      This was added in early 2013 and abandoned several months later; as far as
I can tell, there are no external users.  Future OpenCL use will be via
hwcontext, which requires neither special OpenCL-only API nor global state
in libavutil.

All internal users are also deleted - this is just the unsharp filter
(replaced by unsharp_opencl, which is more flexible) and the deshake filter
(no replacement).
      3650cb2d