- Sep 19, 2013
-
-
Sebastian Dröge authored
-
Sebastian Dröge authored
-
Sebastian Dröge authored
-
- Sep 18, 2013
-
-
-
HEAD requests to discover if the server is seekable shouldn't be done in READY as it might lock the main thread that is doing the state change. https://bugzilla.gnome.org/show_bug.cgi?id=705371
-
Wim Taymans authored
When we trigger the timeout logic of a timer, reevaluate it because it is possible that it still has the lowest timeout.
-
Wim Taymans authored
Don't try to estimate the current time when we got unscheduled.
-
Wim Taymans authored
Already init the packet spacing variables on the first buffer so that we can calculate the spacing on the second buffer already.
-
Wim Taymans authored
-
Wim Taymans authored
Instead of pushing the lost event from the chain function, schedule a timeout that will push the lost event from the timer thread. This avoid blocking the upstream thread while we push and sync the event.
-
Wim Taymans authored
The test is modified slightly because the late lost packets are only generated now when a large gap is received.
-
Wim Taymans authored
Make sure the gap duration in the lost event is a multiple of the packet duration. Enable another test.
-
Wim Taymans authored
Keep track of the estimated duration of missing packets and use it in the lost event. Enable another unit test
-
Wim Taymans authored
When we have a large number of missing packets, generate one lost event for all the packets that have no chance of being pushed out in time. Fix and activate unit test for large gaps.
-
Wim Taymans authored
Also make sure we only increment the expected seqnum and last output timestamp.
-
- Sep 17, 2013
-
-
Wim Taymans authored
-
Wim Taymans authored
Keep track of the current time in the timeout loop. Loop over all timers and trigger all the expired ones, we can do this in the same loop that selects the new best timer.
-
Wim Taymans authored
Also update the timers when retransmission is disabled. We need to do this because when we added LOST timers when we detected missing packets and we need to remove those timers when the packet finally arrives.
-
Tim-Philipp Müller authored
Fixes undefined references to rint and pow on ubuntu build bot.
-
Wim Taymans authored
-
Wim Taymans authored
-
- Sep 16, 2013
-
-
-
Wim Taymans authored
-
Wim Taymans authored
Use a separate thread for scheduling the timeouts instead of using the downstream streaming thread that might block at any time.
-
This reverts commit f72c3cf71fde622067f41f31a53978ba4c94469d. https://bugzilla.gnome.org/show_bug.cgi?id=707340
-
-
- Sep 13, 2013
-
-
Olivier Crête authored
If there are RTCP buffers in the RTP stream, process them as RTCP. This way, we want receive streams following RFC 5761 https://bugzilla.gnome.org/show_bug.cgi?id=687657
-
Jan Schmidt authored
The extra caps entry in the template was making it sometimes get plugged for any dynamically allocated payload type.
-
Wim Taymans authored
Avoid mapping the packet multiple times when sending RTP.
-
Wim Taymans authored
Store all info in the PacketInfo so that we can avoid mapping the packet multiple times.
-
Wim Taymans authored
-
Wim Taymans authored
Rename a structure because we are also going to use this for the sender bits.
-
Wim Taymans authored
-
Thiago Santos authored
Check for GST_SEEK_TYPE_NONE for stop poistion and only update the stop time if it is requested. Otherwise just maintain whatever was stored at the segment https://bugzilla.gnome.org/show_bug.cgi?id=707530
-
In addition to a956a6ce
-
- Sep 12, 2013
-
-
Sebastian Dröge authored
Thanks to iputinei for reporting this on IRC.
-
Wim Taymans authored
We keep the DTS and PTS in running-time inside the jitterbuffer. Make sure to transform it back to a buffer timestamp before pushing out the buffer. Fixes https://bugzilla.gnome.org/show_bug.cgi?id=707931
-