1. 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
  2. 10 Nov, 2017 1 commit
  3. 05 Nov, 2017 3 commits
  4. 04 Nov, 2017 2 commits
  5. 01 Nov, 2017 1 commit
  6. 30 Oct, 2017 1 commit
  7. 29 Oct, 2017 3 commits
  8. 26 Oct, 2017 1 commit
  9. 24 Oct, 2017 1 commit
  10. 23 Oct, 2017 2 commits
  11. 21 Oct, 2017 1 commit
  12. 18 Oct, 2017 1 commit
  13. 16 Oct, 2017 1 commit
  14. 11 Oct, 2017 1 commit
  15. 08 Oct, 2017 1 commit
    • Marton Balint's avatar
      ffmpeg: always use single threaded decoding for attached pictures · 41569bbc
      Marton Balint authored
      Since af1761f7 ffmpeg waits for a frame in each
      stream before writing the output header. If we are using threaded decoding for
      attached pictures, we have to read till EOF to be able to finally flush the
      decoder and output the decoded frame. This essentially makes ffmpeg buffer all
      non-attached picture packets, which will cause a "Too many packets buffered for
      output stream" eventually.
      
      By forcing single threaded decoding, we get a frame from a single packet as
      well and we can avoid the error.
      
      Fixes part of ticket #6375:
      ffmpeg -i 46564100.mp3 -acodec libmp3lame -ab 128k -ac 2 out.mp3
      Reviewed-by: 's avatarHendrik Leppkes <h.leppkes@gmail.com>
      Signed-off-by: 's avatarMarton Balint <cus@passwd.hu>
      41569bbc
  16. 03 Oct, 2017 1 commit