1. 11 Jun, 2022 13 commits
  2. 04 Jun, 2022 22 commits
  3. 03 Jun, 2022 2 commits
    • Steve Lhomme's avatar
      video_output: remove dropped_current_frame test · dd8c8e03
      Steve Lhomme authored
      When we go in the `(next != NULL)` section, we have a new picture to render.
      We need to wait until its "refresh" date to start the rendering.
      It doesn't matter if there was a picture shown before that one.
      The code is almost the same as before where dropped_current_frame was almost
      always true. The only time it was false was:
      * first picture and next is not NULL (first pic & next NULL is impossible here)
      * not first picture and next is NULL
      So the new code only changes the case where it is the "first picture and next
      is not NULL". But in that case, first was true and therefore the test was
      not passing, just like now.
      It is logically equivalent to the code before. But now it's clear that when we
      don't have a next picture we request a redisplay (of displayed.current).
    • Steve Lhomme's avatar
      video_output: clarify the display.current replacement · e6fe279c
      Steve Lhomme authored
      We don't release the picture because there's dropped_current_frame. We have to
      release it because we're replacing the value and we were holding the picture
      in there.
  4. 31 May, 2022 1 commit
    • Rémi Denis-Courmont's avatar
      vout: restart if context changes · 1430071b
      Rémi Denis-Courmont authored and Jean-Baptiste Kempf's avatar Jean-Baptiste Kempf committed
      If the video context changes, filter chains and display must be
      restarted with the new context.
      As the video output object holds a reference to the saved context and
      the caller holds a reference to the new context, contexts are
      contemporary. Consequently, a pointer comparison is safe.
  5. 29 May, 2022 2 commits