{"push_id":1339002319,"size":2,"distinct_size":2,"ref":"refs/heads/master","head":"fb36608ccd95004b3c2b38d6451c009fbad899b6","before":"701e54cecfce85c2e2bdb3ae96b142c76400ed44","commits":[{"sha":"4aadf50012cb057422f29644b41fcaa30c1a2dd2","author":{"name":"Edward Hervey","email":"56b3d7b303b2b24c81f6adbbf53c982dd054dce9@centricular.com"},"message":"adaptivedemux: Calculate values before queue2\n\nIn order to calculate the *actual* bitrate for downloading a fragment\nwe need to take into account the time since we requested the fragment.\n\nWithout this, the bitrate calculations (previously reported by queue2)\nwould be biased since they wouldn't take into account the request latency\n(that is the time between the moment we request a specific URI and the\nmoment we receive the first byte of that request).\n\nSuch examples were it would be biased would be high-bandwith but high-latency\nnetworks. If you download 5MB in 500ms, but it takes 200ms to get the first\nbyte, queue2 would report 80Mbit/s (5Mb in 500ms) , but taking the request\ninto account it is only 57Mbit/s (5Mb in 700ms).\n\nWhile this would not cause too much issues if the above fragment represented\na much longer duration (5s of content), it would cause issues with short\nones (say 1s, or when doing keyframe-only requests which are even shorter)\nwhere the code would expect to be able to download up to 80Mbit/s ... whereas\nif we take the request time into account it's much lower (and we would\ntherefore end up doing late requests).\n\nAlso calculate the request latency for debugging purposes and further\nusage (it could allow us to figure out the maximum request rate for\nexample).\n\nhttps://bugzilla.gnome.org/show_bug.cgi?id=733959\n\nhttps://bugzilla.gnome.org/show_bug.cgi?id=772330","distinct":true,"url":"https://api.github.com/repos/GrokImageCompression/gst-plugins-bad/commits/4aadf50012cb057422f29644b41fcaa30c1a2dd2"},{"sha":"fb36608ccd95004b3c2b38d6451c009fbad899b6","author":{"name":"Edward Hervey","email":"56b3d7b303b2b24c81f6adbbf53c982dd054dce9@centricular.com"},"message":"mpegts: Also clear packetizer on TIME DISCONT\n\nWhen dealing with TIME-based input, the incoming stream could have\npotentially changed completely.\n\nIn order to check whether it did or not, we need to re-check all sections\n(PAT, PMT...). If it didn't, we will keep using the existing streams/pad,\nand if it did we will act as if there was a program switch.\n\nFixes HLS streaming with decodebin3/playbin3","distinct":true,"url":"https://api.github.com/repos/GrokImageCompression/gst-plugins-bad/commits/fb36608ccd95004b3c2b38d6451c009fbad899b6"}]}
{"actor":{"display_login":"boxerab"}}