1. 14 Dec, 2012 21 commits
  2. 13 Dec, 2012 3 commits
    • Wim Taymans's avatar
      check: add (but disable) more rtp jitterbuffer tests · 50391c77
      Wim Taymans authored
      Tests need to be ported to 1.0 before they can be enabled but added here so they
      don't get forgotten.
      See https://bugzilla.gnome.org/show_bug.cgi?id=667838
    • Havard Graff's avatar
      jitterbuffer: bundle together late lost-events · 9c94f118
      Havard Graff authored
      The scenario where you have a gap in a steady flow of packets of
      say 10 seconds (500 packets of with duration of 20ms), the jitterbuffer
      will idle up until it receives the first buffer after the gap, but will
      then go on to produce 499 lost-events, to "cover up" the gap.
      Now this is obviously wrong, since the last possible time for the earliest
      lost-events to be played out has obviously expired, but the fact that
      the jitterbuffer has a "length", represented with its own latency combined
      with the total latency downstream, allows for covering up at least some
      of this gap.
      So in the case of the "length" being 200ms, while having received packet
      500, the jitterbuffer should still create a timeout for packet 491, which
      will have its time expire at 10,02 seconds, specially since it might
      actually arrive in time! But obviously, waiting for packet 100, that had
      its time expire at 2 seconds, (remembering that the current time is 10)
      is useless...
      The patch will create one "big" lost-event for the first 490 packets,
      and then go on to create single ones if they can reach their
      playout deadline.
      See https://bugzilla.gnome.org/show_bug.cgi?id=667838
    • Wim Taymans's avatar
      rtspsrc: fix TCP reconnect · a858bf46
      Wim Taymans authored
      Ignore other commands when reconnecting, otherwise the loop function would pause
      and the reconnection would not happen. Continue looping after doing a reconnect
      so that we have a chance to actually read the new data.
  3. 12 Dec, 2012 5 commits
  4. 11 Dec, 2012 1 commit
  5. 10 Dec, 2012 2 commits
  6. 30 Nov, 2012 3 commits
  7. 27 Nov, 2012 1 commit
  8. 26 Nov, 2012 1 commit
  9. 25 Nov, 2012 2 commits
  10. 24 Nov, 2012 1 commit