Skip to content
  1. Oct 28, 2016
  2. Oct 25, 2016
  3. Oct 21, 2016
  4. Oct 18, 2016
  5. Oct 14, 2016
  6. Oct 13, 2016
  7. Oct 12, 2016
  8. Oct 11, 2016
  9. Oct 09, 2016
  10. Oct 08, 2016
    • Edward Hervey's avatar
      mpegts: Also clear packetizer on TIME DISCONT · fb36608c
      Edward Hervey authored and Edward Hervey's avatar Edward Hervey committed
      When dealing with TIME-based input, the incoming stream could have
      potentially changed completely.
      
      In order to check whether it did or not, we need to re-check all sections
      (PAT, PMT...). If it didn't, we will keep using the existing streams/pad,
      and if it did we will act as if there was a program switch.
      
      Fixes HLS streaming with decodebin3/playbin3
      fb36608c
    • Edward Hervey's avatar
      adaptivedemux: Calculate values before queue2 · 4aadf500
      Edward Hervey authored and Edward Hervey's avatar Edward Hervey committed
      In order to calculate the *actual* bitrate for downloading a fragment
      we need to take into account the time since we requested the fragment.
      
      Without this, the bitrate calculations (previously reported by queue2)
      would be biased since they wouldn't take into account the request latency
      (that is the time between the moment we request a specific URI and the
      moment we receive the first byte of that request).
      
      Such examples were it would be biased would be high-bandwith but high-latency
      networks. If you download 5MB in 500ms, but it takes 200ms to get the first
      byte, queue2 would report 80Mbit/s (5Mb in 500ms) , but taking the request
      into account it is only 57Mbit/s (5Mb in 700ms).
      
      While this would not cause too much issues if the above fragment represented
      a much longer duration (5s of content), it would cause issues with short
      ones (say 1s, or when doing keyframe-only requests which are even shorter)
      where the code would expect to be able to download up to 80Mbit/s ... whereas
      if we take the request time into account it's much lower (and we would
      therefore end up doing late requests).
      
      Also calculate the request latency for debugging purposes and further
      usage (it could allow us to figure out the maximum request rate for
      example).
      
      https://bugzilla.gnome.org/show_bug.cgi?id=733959
      
      https://bugzilla.gnome.org/show_bug.cgi?id=772330
      4aadf500
  11. Oct 06, 2016
  12. Oct 05, 2016
  13. Oct 03, 2016
Loading