1. 23 Feb, 2018 1 commit
  2. 08 Feb, 2018 1 commit
  3. 06 Feb, 2018 2 commits
  4. 02 Feb, 2018 2 commits
  5. 28 Jan, 2018 1 commit
  6. 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
  7. 07 Jan, 2018 1 commit
  8. 06 Jan, 2018 1 commit
  9. 04 Jan, 2018 1 commit
  10. 26 Dec, 2017 1 commit
  11. 28 Nov, 2017 2 commits
  12. 26 Nov, 2017 1 commit
  13. 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
  14. 21 Nov, 2017 1 commit
  15. 20 Nov, 2017 1 commit
  16. 19 Nov, 2017 2 commits
  17. 15 Nov, 2017 3 commits
  18. 11 Nov, 2017 1 commit
    • Timo Rothenpieler's avatar
      ffmpeg: use explicitly requested hwaccel only · 6a4d1c90
      Timo Rothenpieler authored
      With there being two hwaccels that use the CUDA pix_fmt now, just
      relying on the pix_fmt to identify the selected hwaccel is not enough
      anymore.
      
      So this checks if the user explicitly selected a hwaccel, and only
      accepts that one.
      6a4d1c90
  19. 10 Nov, 2017 1 commit
  20. 05 Nov, 2017 3 commits
  21. 04 Nov, 2017 2 commits
  22. 01 Nov, 2017 1 commit
  23. 30 Oct, 2017 1 commit
  24. 29 Oct, 2017 3 commits
  25. 26 Oct, 2017 1 commit
  26. 24 Oct, 2017 1 commit
  27. 23 Oct, 2017 2 commits
  28. 21 Oct, 2017 1 commit