mirrors/gstreamer
mirrors/gstreamer
1
1
Fork 0
mirror of https://gitlab.freedesktop.org/gstreamer/gstreamer.git synced 2024-12-29 11:40:38 +00:00
Code Issues 1 Projects Releases Wiki Activity
15363 commits 44 branches 1510 tags 354 MiB
Commit graph

15363 commits

This branch
This branch
All branches
Author SHA1 Message Date
Sebastian Dröge
748690aba1 parse: Add comment about why we disable the "tracing" 
It did not print anything useful before anyway, everything
was commented out.

Also remove some unneeded struct members.
 2014-01-14 13:46:24 +01:00
Sebastian Dröge
c47f0f2ec5 parse-launch: Add some more failing pipelines 
Also convert some comments about valgrind warnings to
FIXME comments. These were leaking since some time already.
 2014-01-14 13:46:24 +01:00
Fabian Kirsch
2b33d33185 parse: Refactor grammar, make it more consistent and fix conflicts 
https://bugzilla.gnome.org/show_bug.cgi?id=710034
 2014-01-14 13:46:22 +01:00
Stefan Sauer
4f70bd5a5a docs: ensure GstBufferPools shows up as with GObject features 
GstBufferPool is a GstObject, add the _get_type function to the types file.
 2014-01-13 20:51:03 +01:00
Thiago Santos
4f9d382a0a tests: baseparse: add test for reverse playback on passthrough 
Baseparse stores buffers for reverse playback to push on the next
DISCONT, the issue was that it wouldn't ever check for a discont
on passthrough mode as it skips all real parsing. This test
was create to verify this issue and prevent it from happening again

https://bugzilla.gnome.org/show_bug.cgi?id=721941
 2014-01-13 08:43:28 -03:00
Thiago Santos
aad8123ff9 tests: baseparse: add basic test for baseparse 
Just a small test to check that basic playback works
 2014-01-13 08:43:28 -03:00
Thiago Santos
a3ff2976cc baseparse: do not accumulate buffers on passthrough mode 
If on passthrough during reverse playback, do not accumulate buffers as
baseparse will never check for DISCONT flag to push those buffers.
So just push buffers downstream as if it was forward playback.

https://bugzilla.gnome.org/show_bug.cgi?id=721941
 2014-01-13 08:43:28 -03:00
Stefan Sauer
6a05291ca2 basesrc: don't confuse GST_PAD_MODE_NONE and PULL 
Use a switch-case to explicitly handle all pad-modes. This way we don't log an error when the pad is not yet activated.
 2014-01-09 08:49:40 +01:00
Stefan Sauer
46b18f7a8b gstobject: add FIXME and docs for the disabled notify on parent 
We haven't found a way to re-enable emitting notify and deep-notify for parent
changes. Add a FIXME-2.0 and a doc blob on the property. See #693281.
 2014-01-09 08:49:40 +01:00
Thiago Santos
51fa54a281 baseparse: do not ignore TIME segments 
TIME segments are being ignored and a standard initialized
segment is used instead. This causes issues as not properly detecting
reverse playback or not cliping output based on the segment.

This seems to be a regression from one of the GstSegment/GstEvent
redesigns on the 0.10 -> 1.0 transition
 2014-01-08 16:40:23 -03:00
Wim Taymans
6c95262447 tests: improve check, also check stream-time 2014-01-08 15:47:10 +01:00
Wim Taymans
b5e4e24e75 tests: add unit test for segment _offset_running_time() 
Add a unit test to check that positive and negative offsets are applied
correctly in various cases.
 2014-01-08 15:31:28 +01:00
Wim Taymans
f664fbd198 segment: take offset into account in _to_position() 
Take the offset into account when converting between running-time and
segment positions.
 2014-01-08 15:23:00 +01:00
Wim Taymans
6d3fc584d5 pad: use new segment offset method to apply the offset 
Fixes https://bugzilla.gnome.org/show_bug.cgi?id=721422
 2014-01-08 15:04:00 +01:00
Wim Taymans
dc0176e4a0 segment: add method to offset the segment running-time 
Add a method that can apply an offset to the calculated running-time of
a segment.
 2014-01-08 15:04:00 +01:00
Wim Taymans
888ab23968 collectpads: take offset into account for expected segment position 
The firt valid segment position is start + offset.
Also add some more debug and a FIXME
 2014-01-08 15:04:00 +01:00
Wim Taymans
42d36b9495 info: debug segment offset field as well 2014-01-08 15:04:00 +01:00
Sebastian Dröge
c343ebd454 multiqueue: Allow growing a queue if all other queues are not linked 
See https://bugzilla.gnome.org/show_bug.cgi?id=719893
 2014-01-08 09:54:01 +01:00
Wim Taymans
c80ea6895d filesrc: don't try to seek to -1 offset 
The offset can be -1 when we are configured in TIME format. Instead of
failing the seek and erroring, do what and offset of -1 is supposed to
do and simply read from the current offset.
 2014-01-07 16:18:37 +01:00
Stefan Sauer
74adc33982 basesrc: demote error to warning 
This is not an error. A subclass returning FALSE for is_seekable() is one way of
saying that we can't operate in pull mode.
 2014-01-06 21:10:33 +01:00
YanpingZhang
1de533735b multiqueue: Fix hanging if shut down while handling a serialized query 
https://bugzilla.gnome.org/show_bug.cgi?id=721253
 2014-01-03 11:15:33 +01:00
Thiago Santos
e02c00a58a baseparse: remove pending_segment as it was being misused 
It wasn't required, instead baseparse was using it to check the media
caps to identify if it was handling audio or video.

The pending_segment was removed and a checked_media boolean
replaced it for a more accurate naming.

https://bugzilla.gnome.org/show_bug.cgi?id=721350
 2014-01-02 16:48:23 -03:00
Thiago Santos
accaadf52a baseparse: push pending events before GAP event 
A GAP event is handled as an empty buffer by sinks and they expect
to receive start up events before GAP events (like a segment).

This is important specially if there is a GAP at the beginning of
a stream (before any buffers) so that the segment event can be
pushed downstream before the GAP

https://bugzilla.gnome.org/show_bug.cgi?id=721350
 2014-01-02 16:38:40 -03:00
Thiago Santos
d917eb7160 baseparse: refactor pending events pushing 
Refactor code repeated 3 times to a common function

https://bugzilla.gnome.org/show_bug.cgi?id=721350
 2014-01-02 16:38:40 -03:00
Stefan Sauer
fb2140b627 design/part-toc.txt: update design docs 2014-01-02 20:18:36 +01:00
Sebastian Dröge
9e125e7bab pad: Add unit test for adding/removing blocking probes while a pad is blocked 
And make sure that these new probes are actually called if they should
instead of silently blocking the pad forever.

https://bugzilla.gnome.org/show_bug.cgi?id=721289
 2014-01-02 13:34:52 +01:00
Sebastian Dröge
93ce90f833 pad: Check if new probes need to be called when adding/removing some 
This allows blocking a pad, add a new blocking probe, removing
the first probe and then having the second probe called. Which
could then decide that data-flow should actually continue
instead of blocking now.

https://bugzilla.gnome.org/show_bug.cgi?id=721289
 2014-01-02 13:33:20 +01:00
Sebastian Dröge
34f8b4d6f3 tee: Remove dyn lock 
It was used for pad-alloc in 0.10 but currently is completely unused
and not necessary. All pad access is protected by the tee object lock
and keeping another reference to the current pad.
 2014-01-02 11:13:27 +01:00
Sebastian Dröge
e80fd39947 tee: Keep another ref to our one and only srcpad around while pushing 
A pad probe on that pad might otherwise just release the pad, drop
the last reference and cause great misery.

https://bugzilla.gnome.org/show_bug.cgi?id=721300
 2014-01-02 11:09:59 +01:00
Sebastian Dröge
d04c8b6d2e pad: Keep an extra ref of the pad when calling an IDLE probe immediately 
The callback might destroy the pad.
 2013-12-30 19:03:22 +01:00
Sebastian Dröge
0324358ebc pad: Only call IDLE probes if we are actually idle 
Also only check the data types for non-IDLE probes. When we
are idle, we have no data type obviously.

Previously we were calling IDLE probes during data flow whenever
a non-blocking probe would be called. The pad was usually not idle
at that time.
 2013-12-30 18:53:36 +01:00
Tim-Philipp Müller
2ddbe8df49 nettimeprovider: remove unnecessary NULL check 
Error is never NULL when we break out of the loop.

COVERITY CID 1037151
 2013-12-30 16:10:08 +00:00
Tim-Philipp Müller
0735c052e1 Revert "nettimeprovider: Remove dead code" 
This reverts commit 9649cd4ca1.

This is not right, and it's also not what coverity
is complaining about.
 2013-12-30 16:07:08 +00:00
Edward Hervey
af6fd4f5bb queue: Remove unneeded checks 
item is guaranteed to be non-null.

COVERITY CID 1037152
COVERITY CID 1037153
 2013-12-30 16:51:01 +01:00
Edward Hervey
9649cd4ca1 nettimeprovider: Remove dead code 
err is always NULL by the point we reach this line

COVERITY CID 1037151
 2013-12-30 16:51:01 +01:00
Stefan Sauer
b571f3ad7d taglist: fix since marker again (1.3 -> 1.4) 
Since markers should point to the appropriate stable version.
 2013-12-30 14:47:19 +01:00
Stefan Sauer
e8023bf470 taglist: fix since-marker in docs (we're in 1.3.X) 2013-12-30 14:40:40 +01:00
Stefan Sauer
cb218f2827 taglist: add a tag for midi base note numbers 
Audio files containing sampled instruments can have metadata describing the note
that was played on the instrument.
 2013-12-30 14:22:37 +01:00
Sebastian Dröge
901cd5560c pad: Don't ignore probe callback return value when immediately calling IDLE probe 
https://bugzilla.gnome.org/show_bug.cgi?id=721096
 2013-12-30 10:53:09 +01:00
Pedro Côrte-Real
e5067fd9aa scripts: git-update.sh: fix for non-master branches 
Pull from tracking branch instead of origin/master, so
that this works with e.g. 1.2 as well.
 2013-12-29 14:09:24 +00:00
Sebastian Dröge
c3181fa5df parse: Use GLib malloc/free/realloc functions 
https://bugzilla.gnome.org/show_bug.cgi?id=720100
 2013-12-27 12:55:40 +01:00
Tim-Philipp Müller
d2e5953643 scripts: create-uninstalled-setup: re-use existing master branch if it exists 
When creating separate checkout for non-master branches.
 2013-12-26 12:17:06 +00:00
Erik Andresen
2cbab400b2 docs: fix memory leak of appsink example in manual 
https://bugzilla.gnome.org/show_bug.cgi?id=721076
 2013-12-26 11:21:29 +00:00
Tim-Philipp Müller
b03361ac38 Automatic update of common submodule 
From dbedaa0 to d48bed3
 2013-12-22 22:33:12 +00:00
Tim-Philipp Müller
a4459ef372 po: update for string changes 2013-12-22 22:04:37 +00:00
Tim-Philipp Müller
cd26b32822 po: set gettext domain in Makevars so we don't have to patch the generated Makefile.in.in 
https://bugzilla.gnome.org/show_bug.cgi?id=705455
 2013-12-22 21:58:03 +00:00
Wim Taymans
62932b17d7 utils: Add round down 128 macro for completeness 2013-12-20 14:43:57 +01:00
Nicolas Dufresne
59bb1f58bb utils: Add round up 128 macro 2013-12-20 14:43:57 +01:00
Sebastian Dröge
0199cd5dbf funnel: Setting the PROXY_CAPS flag on the srcpad does not make much sense 
funnel outputs whatever one of the upstreams currently outputs, a caps
query to a random upstream does not give the right answer here.
 2013-12-20 14:30:22 +01:00
Sebastian Dröge
5937199726 funnel: Proxy CAPS and ALLOCATION queries 2013-12-20 11:38:18 +01:00