1. 29 Oct, 2015 1 commit
  2. 21 Oct, 2015 3 commits
  3. 27 Sep, 2015 1 commit
  4. 06 Sep, 2015 1 commit
  5. 29 Aug, 2015 1 commit
  6. 23 Jun, 2015 1 commit
  7. 25 Apr, 2015 2 commits
  8. 24 Apr, 2015 1 commit
    • Rémi Denis-Courmont's avatar
      decoder: remove vout_FixLeaks() · e56293ea
      Rémi Denis-Courmont authored
      This function was intended to work around a certain class of bugs
      inside video decoders whereby the a reference picture was never
      dereferenced, i.e. missing decoder_UnlinkPicture() call.
      
      There are however some situations where this hack would release a
      still referenced picture:
      
      - If the video output or decoder has a high latency or if a video
        filter holds pictures (deinterlace), there may be zero free pictures
        even though the total number of pictures is sufficient overall.
        In that case, waiting for a picture buffer to be released normally
        is the right and safe approach.
      
      - If the byte stream is invalid or corrupt such that the number of
        required pictures (DPB size) is underestimated, dropping frames is
        acceptable. Frames would be corrupt anyway due to missing references.
        (This case could be better worked around by allocating extra
         pictures on-the-fly, though this would require memory copying in the
         video output.)
      
      - Even if the decoder indeed leaks pictures, the oldest referenced
        picture is not necessarily among those leaked.
      
      If the picture was not truly leaked, vout_FixLeaks() would cause an
      extraneous picture release. This should lead to an assertion failure in
      picture_Release(). Without assertions, it would lead to undefined
      behaviour, especially invalid pointer use in case of hardware surfaces.
      
      In any case, picture leaks are still recovered when resetting the video
      output with vout_Reset(), after the decoder is destroyed. That might
      turn out to be a problem too though.
      e56293ea
  9. 23 Apr, 2015 1 commit
  10. 30 Mar, 2015 1 commit
    • Thomas Guillem's avatar
      video_output: fix controls and events not processed · 93e1d6ad
      Thomas Guillem authored
      This issue is easily reproducible with VDPAU activated, with a 60fps ts file,
      see #14199.
      
      With this sample, The video_output Thread is looping in ThreadDisplayPicture
      way more often than with other videos. Consequently, vout_ManageWrapper and
      ThreadControl are not called enough. As a result, subtitles are processed too
      late, the mouse isn't able to hide/unhide, we can be stuck in fullscreen mode,
      or second click on video to pop up the menu doesn't work.
      
      To fix this issue: don't loop in ThreadDisplayPicture and don't wait in
      vout_control_Pop if a picture was previously displayed.
      
      Fixes #14199
      Signed-off-by: Jean-Baptiste Kempf's avatarJean-Baptiste Kempf <jb@videolan.org>
      93e1d6ad
  11. 07 Feb, 2015 1 commit
  12. 01 Nov, 2014 9 commits
  13. 30 Oct, 2014 1 commit
  14. 29 Oct, 2014 1 commit
  15. 26 Oct, 2014 1 commit
  16. 23 Oct, 2014 1 commit
  17. 16 Oct, 2014 13 commits