1. 18 Dec, 2018 1 commit
  2. 27 Nov, 2018 2 commits
  3. 16 Nov, 2018 1 commit
  4. 11 Nov, 2018 3 commits
  5. 14 Oct, 2018 1 commit
  6. 09 Oct, 2018 1 commit
  7. 28 Aug, 2018 1 commit
  8. 07 Aug, 2018 1 commit
  9. 02 Jul, 2018 2 commits
  10. 28 Jun, 2018 1 commit
  11. 22 Jun, 2018 1 commit
  12. 17 Jun, 2018 1 commit
  13. 14 Jun, 2018 2 commits
  14. 09 Jun, 2018 1 commit
  15. 04 Jun, 2018 1 commit
  16. 02 May, 2018 1 commit
  17. 30 Apr, 2018 1 commit
  18. 28 Apr, 2018 2 commits
  19. 04 Apr, 2018 1 commit
  20. 02 Apr, 2018 1 commit
  21. 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
  22. 30 Mar, 2018 1 commit
  23. 28 Mar, 2018 2 commits
  24. 24 Mar, 2018 2 commits
  25. 20 Mar, 2018 1 commit
  26. 05 Mar, 2018 2 commits
  27. 27 Feb, 2018 1 commit
  28. 24 Feb, 2018 1 commit
  29. 23 Feb, 2018 1 commit
  30. 28 Jan, 2018 1 commit
  31. 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