1. 01 Oct, 2019 1 commit
  2. 27 Sep, 2019 2 commits
  3. 17 Sep, 2019 1 commit
  4. 13 Sep, 2019 1 commit
  5. 05 Sep, 2019 1 commit
  6. 04 Sep, 2019 1 commit
  7. 14 Aug, 2019 2 commits
    • Andreas Rheinhardt's avatar
      fftools: Use right function signature and pointers · f2d522f2
      Andreas Rheinhardt authored
      The option tables of the various fftools (in particular ffprobe) are
      arrays of OptionDef; said type contains a union of a pointer to void and
      a function pointer of type int (*)(void *, const char *, const char *)
      as well as a size_t. Some entries (namely the common entry for writing a
      report as well as several more of ffprobe's entries) used the pointer to
      void to store a pointer to functions of type int (*)(const char *) or
      type int (*)(const char *, const char *); nevertheless, when the functions
      are actually called in write_option (in cmdutils.c), it is done via a
      pointer of the first type.
      
      There are two things wrong here:
      1. Pointer to void can be converted to any pointer to incomplete or
      object type and back; but they are nevertheless not completely generic
      pointers: There is no provision in the C standard that guarantees their
      convertibility with function pointers. C90 lacks a generic function
      pointer, C99 made every function pointer a generic function pointer and
      still disallows the convertibility with void *.
      2. The signature of the called function differs from the signature
      of the pointed-to type. This is undefined behaviour in C99 (given that
      C90 lacks a way to convert function pointers at all, it doesn't say
      anything about such a situation). It only works because none of the
      functions this patch is about make any use of their parameters at all.
      
      Therefore this commit changes the type of the relevant functions
      to match the type used for the call and uses the union's function
      pointer to store it. This is legal even in C90.
      Signed-off-by: 's avatarAndreas Rheinhardt <andreas.rheinhardt@gmail.com>
      Reviewed-by: 's avatarPaul B Mahol <onemda@gmail.com>
      Signed-off-by: 's avatarMichael Niedermayer <michael@niedermayer.cc>
      f2d522f2
    • Marton Balint's avatar
      ffplay: properly detect all window size changes · a1c70148
      Marton Balint authored
      SDL_WINDOWEVENT_SIZE_CHANGED should be used instead of SDL_WINDOWEVENT_RESIZED
      because SDL_WINDOWEVENT_RESIZED is only emitted if the resize happened due to
      an external event.
      
      Fixes ticket #8072.
      
      Additional references:
      https://bugzilla.libsdl.org/show_bug.cgi?id=4760
      https://wiki.libsdl.org/SDL_WindowEventIDSigned-off-by: 's avatarMarton Balint <cus@passwd.hu>
      a1c70148
  8. 03 Jul, 2019 1 commit
  9. 21 Jun, 2019 1 commit
  10. 02 Jun, 2019 2 commits
  11. 26 May, 2019 1 commit
  12. 20 May, 2019 1 commit
  13. 19 Apr, 2019 1 commit
  14. 16 Apr, 2019 1 commit
  15. 28 Mar, 2019 1 commit
    • Thierry Foucu's avatar
      fftools/ffmpeg: Check if we do have also a filter_complex filter. · 0ac3befd
      Thierry Foucu authored
      Right now, the code check for no filter description, but if we use a
      filter_complex, the code will use the AVFrame.duration which could be
      wrong in case of using fps filter.
      
      How to reproduce the problem:
      ffmpeg -f lavfi -i testsrc=duration=1 -vf fps=fps=50 -vsync 1 -f null -
      output 50 frames
      
      ffmpeg -f lavfi -i testsrc=duration=1 -filter_complex fps=fps=50 -vsync 1 -f null -
      output 51 frames
      
      With this commit, the same command will always output 50 frames.
      Signed-off-by: 's avatarMichael Niedermayer <michael@niedermayer.cc>
      0ac3befd
  16. 21 Feb, 2019 1 commit
    • Jan Ekström's avatar
      ffmpeg_filter: initialize sub2video.end_pts together with last_pts · 8cf757ee
      Jan Ekström authored
      This way re-initializations properly update end_pts, enabling
      sub2video_heartbeat to call sub2video_update as expected to re-init
      the sub2video AVFrame's contents and to feed a frame into the filter
      chain.
      
      This then fixes memory usage ballooning due to framesync waiting
      for secondary input in case of no actual subtitle samples being present
      for a while in source after a re-init occurs.
      8cf757ee
  17. 07 Feb, 2019 3 commits
  18. 14 Jan, 2019 1 commit
  19. 03 Jan, 2019 1 commit
  20. 02 Jan, 2019 1 commit
  21. 18 Dec, 2018 1 commit
  22. 01 Dec, 2018 2 commits
  23. 27 Nov, 2018 3 commits
  24. 16 Nov, 2018 1 commit
  25. 11 Nov, 2018 3 commits
  26. 14 Oct, 2018 1 commit
  27. 09 Oct, 2018 1 commit
  28. 07 Oct, 2018 1 commit
  29. 30 Sep, 2018 1 commit
  30. 17 Sep, 2018 1 commit