1. 03 Apr, 2020 5 commits
  2. 02 Apr, 2020 3 commits
  3. 01 Apr, 2020 1 commit
  4. 31 Mar, 2020 4 commits
  5. 30 Mar, 2020 1 commit
    • Håvard Graff's avatar
      rtpjitterbuffer: fix waiting timer/queue code · 818b38eb
      Håvard Graff authored
      Changing the types from boolean to guint due to the ++ operand used on
      them, and only call JBUF_SIGNAL_QUEUE after settling down,
      or else you end up signaling the waiting code in chain() for every buffer
      pushed out.
  6. 27 Mar, 2020 2 commits
  7. 26 Mar, 2020 2 commits
    • Jan Schmidt's avatar
      splitmuxsrc: Fix some deadlock conditions and a crash · 00a08c69
      Jan Schmidt authored
      When switching the splitmuxsrc state back to NULL quickly, it
      can encounter deadlocks shutting down the part readers that
      are still starting up, or encounter a crash if the splitmuxsrc
      cleaned up the parts before the async callback could run.
      Taking the state lock to post async-start / async-done messages can
      deadlock if the state change function is trying to shut down the
      element, so use some finer grained locks for that.
    • Jan Schmidt's avatar
      splitmux: Make the unit test faster · 8ef172d8
      Jan Schmidt authored
      The playback test is considerably faster if it runs with the
      appsink set to sync=false
  8. 25 Mar, 2020 7 commits
  9. 24 Mar, 2020 4 commits
  10. 23 Mar, 2020 2 commits
  11. 20 Mar, 2020 8 commits
    • Matthew Waters's avatar
      qt: reorganize include defines · 818dde2e
      Matthew Waters authored
    • Håvard Graff's avatar
      rtptimerqueue: remove ->num from the timer · a710bda1
      Håvard Graff authored
      This concept was only used by the "multi"-lost timer, and since that
      one is not around any longer, the "num" concept is superfluous.
    • Håvard Graff's avatar
      rtpjitterbuffer: remove the concept of "already-lost" · f1ff80ce
      Håvard Graff authored
      This is a concept that only applies when a buffer arrives in the chain
      function, and it has already been scheduled as part of a "multi"-lost
      However, "multi"-lost timers are now a thing of the past, making this
      whole concept superflous, and this buffer is now simply counted as "late",
      having already been pushed out (albeit as a lost-event).
    • Håvard Graff's avatar
      rtpjitterbuffer: immediately insert a lost-event on multiple lost packets · 5dacf366
      Håvard Graff authored
      There is a problem with the code today, where a single timer will
      be scheduled for a series of lost packets, and then if the first packet
      in that series arrives, it will cause a rescheduling of that timer, going
      from a "multi"-timer to a single-timer, causing a lot of the packets
      in that timer to be unaccounted for, and creating a situation in where
      the jitterbuffer will never again push out another packet.
      This patch solves the problem by instead of scheduling those lost packets
      as another timer, it instead asks to have that lost-event pushed straight
      This very much goes with the intent of the code here: These packets are
      so desperately late that no cure exists, and we might as well get the
      lost-event out of the way and get on with it.
      This change has some interesting knock-on effect being presented in
      later commits. It completely removes the concept of "already-lost", so
      that is why that test has been disabled in this commit, to be
      removed later.
    • Håvard Graff's avatar
      rtpjitterbuffer: rework large-gap tests · d045b40d
      Håvard Graff authored
      Make sure to set the time the buffer is supposed to arrive at, so
      as not to trigger an artificial situation.
    • Håvard Graff's avatar
      rtpjitterbuffer: refactor lost_timeout code · 2fa7e6a6
      Håvard Graff authored
      Split it up in code related to the timer, (do_lost_timeout) and code
      to insert a lost-item/event and update private jitterbuffer-variables.
    • Håvard Graff's avatar
    • Dmitriy Purgin's avatar
      gstqmlgl: Link to opengl32.lib on MinGW · 40a82104
      Dmitriy Purgin authored
  12. 19 Mar, 2020 1 commit
    • Seungha Yang's avatar
      qtmux: Fix build warning · 4f443c81
      Seungha Yang authored
      gstqtmux.c(644): warning C4133: '=':
        incompatible types - from 'gboolean (__cdecl *)(GstAggregator *,GstAggregatorPad *,GstEvent *)'
        to 'GstFlowReturn (__cdecl *)(GstAggregator *,GstAggregatorPad *,GstEvent *)'