- 15 Feb, 2010 3 commits
-
-
Tim-Philipp Müller authored
-
Tim-Philipp Müller authored
Fixes #609724.
-
Sebastian Dröge authored
-
- 14 Feb, 2010 3 commits
-
-
Sebastian Dröge authored
Now the alpha is multiplied with the already existing alpha value instead of simply ignoring it and the luma/chroma values are kept, even if the output is 100% transparent.
-
Sebastian Dröge authored
-
Sebastian Dröge authored
From 96dc793 to 44ecce7
-
- 13 Feb, 2010 6 commits
-
-
Tim-Philipp Müller authored
For GST_RIFF_TAG_JUNQ.
-
Tim-Philipp Müller authored
-
Edward Hervey authored
We silently ignore them instead of erroring out.
-
Edward Hervey authored
It was previously checking for DIFF(a, b > 6 * GST_SECOND) instead of the proper DIFF(a,b) > 6 * GST_SECOND
-
Edward Hervey authored
-
Edward Hervey authored
Used the _add_associationv variant of GstIndex since we know how many associations we're adding. Trims up to 50% from index generation time. Note : It would be great if the index could be generated on the fly or on request as opposed to being fully created at startup.
-
- 12 Feb, 2010 28 commits
-
-
Wim Taymans authored
If we detect backward timestamps on the server, don't try to resync when we don't have an input timestamp (such as when using RTSP over TCP) instead, do nothing but assume the timestamp was ok, it will correct itself when time goes forwards.
-
Wim Taymans authored
-
Wim Taymans authored
There is no need to set the latency in the jittebuffer in _init, we will set that later when going to PAUSED. Set the jitterbuffer active and not buffering when starting.
-
Wim Taymans authored
When deactivating jitterbuffers when the buffering starts, keep the current percent of the jitterbuffer and also set the jitterbuffer in the buffering state so that we know when it's filled again. Add property to get the buffering percentage of the jitterbuffer.
-
Wim Taymans authored
When we are in buffer mode, adjust the buffering low/high thresholds based on the total configured latency. If we don't and there is a huge queue or element with a big latency downstream we might drain the complete queue immediately and start buffering again.
-
Wim Taymans authored
Add the ts-offset to the buffer timestamp to get the final output timestamp of the buffer.
-
Wim Taymans authored
Return the next timestamp in the jitterbuffer. Use the min-timestamp of the jitterbuffers to calculate an offset so that the next timestamp is pushed with a timestamp equal to running_time. Start producing timestamps from 0 in the buffering case too.
-
Wim Taymans authored
Only start buffering when the percentage message is < 100 %.
-
Wim Taymans authored
Keep track of the time we spend pausing the jitterbuffers when they were buffering and distribute this elapsed time to the jitterbuffers. Also keep the latency in nanosecond precision.
-
Wim Taymans authored
Keep track of an outgoing offset that we add to each outgoing buffer to compensate for PAUSE when buffering. Adjust the offset when activating.
-
Wim Taymans authored
-
Wim Taymans authored
Pass the current running time to the jitterbuffer when pausing or resuming so that it calculate the right offsets. Small cleanups and comments. Set the default rtspsrc latency to 2 seconds.
-
Wim Taymans authored
-
Wim Taymans authored
Add signal to pause the jitterbuffer. This will be emitted from gstrtpbin when one of the jitterbuffers is buffering. Make rtpbin collect the buffering messages and post a new buffering message with the min value. Remove the stats callback from jitterbuffer but pass a percent integer to functions that affect the buffering state of the jitterbuffer. This allows us then to post buffering messages from outside of the jitterbuffer lock.
-
Wim Taymans authored
Propagate buffer-mode property to the jitterbuffers. Intercept BUFFERING messages in rtpbin
-
Wim Taymans authored
Add callback for buffering stats. Configure the latency in the jitterbuffer instead of passing it with _insert. Calculate buffering levels when pushing and popping Post buffering messages.
-
Wim Taymans authored
Add a buffering state to the jitterbuffer and wait until buffering ends before pushing out packets.
-
Wim Taymans authored
Expose a mode property on the jitterbuffer. Fix the case where timestamps are -1 in the check for outgoing timestamps.
-
Wim Taymans authored
Add getters and setters for different buffering modes that the jitterbuffer will support. Default to the current slave mode.
-
Tim-Philipp Müller authored
-
Robert Swain authored
Allows for better support of seeking in flv files when in push mode
-
Robert Swain authored
The audio packets in AVI are generally muxed ~0.5s before the corresponding video packet. This changes causes downstream to only receive packets with roughly corresponding timestamps.
-
Wim Taymans authored
Add some debug in the DISCONT handling code. When we receive a DISCONT in push mode, mark all streams as DISCONT.
-
Robert Swain authored
-
Wim Taymans authored
Make sure we reset the demuxer correctly wrt parsing the index. Don't leak pending seek events. Rename some methods to reflect what they do and to avoid confusion with similar method names. Try to make the seeking threadsafe by protecting the setup code with a lock. Make sure we post errors when a seek fails.
-
Wim Taymans authored
seek_event -> seg_event event_seek -> seek_event
-
Wim Taymans authored
When we have not parsed any indexes yet, we don't know the length of the streams and we must take the length given in the avih as a fallback. Avoid some typechecking.
-
Robert Swain authored
-