- Sep 18, 2015
-
-
Sebastian Dröge authored
-
Sebastian Dröge authored
-
Sebastian Dröge authored
-
- Sep 15, 2015
- Sep 14, 2015
- Sep 11, 2015
-
-
On e.g. QNX it is in an external library, not libc. https://bugzilla.gnome.org/show_bug.cgi?id=754875
-
- Sep 09, 2015
-
-
Arun Raghavan authored
This reverts commit 0dffeb03. The commit is erroneous and documents the function twice.
-
Arun Raghavan authored
Thanks to Nirbheek Chauhan <nirbheek@centricular.com> for pointing this out.
-
- Sep 07, 2015
-
-
In order for gst_harness_new_full to be MT-safe the increase and decrease of HARNESS_REF must be MT-safe. This allows for creating multiple harnesses from different threads wrapping the same element. https://bugzilla.gnome.org/show_bug.cgi?id=754661
-
It should be allowed to not have a function to initialize the user data since it's often not necessary; it may already be initialized. https://bugzilla.gnome.org/show_bug.cgi?id=754661
-
- Sep 06, 2015
-
-
Tim-Philipp Müller authored
-
- Sep 05, 2015
-
-
Tim-Philipp Müller authored
-
Tim-Philipp Müller authored
This has not worked (as in: crashed) since 2005, so perhaps it should just be removed instead.
-
- Aug 31, 2015
-
-
Tim-Philipp Müller authored
This caused problems with oggdemux when queue2 was operating in queue mode and the souphttpsrc upstream is not seekable because the server doesn't support range requests. It would then still claim seekability and then things go wrong from there. This reverts commit 7b0b93da. https://bugzilla.gnome.org/show_bug.cgi?id=753887
-
1. Get a list of pad templates from the element class, not the factory. This allows us to interact with test-elements that does not have a factory. 2. Use the pad_template_caps in caps-queries when caps is not set explicitly on the pad. Not doing so is simply wrong, and prohibits interactions with special templates used for testing. https://bugzilla.gnome.org/show_bug.cgi?id=754193
-
- Aug 26, 2015
-
-
Thiago Santos authored
gst/gstevent.c:250:5: error: ‘for’ loop initial declarations are only allowed in C99 or C11 mode
-
- Aug 25, 2015
-
-
Doing so would deadlock from trying to acquire the object lock twice https://bugzilla.gnome.org/show_bug.cgi?id=754036
-
- Aug 21, 2015
-
-
Nicolas Dufresne authored
There exist cases where a reconfigure event was propagated from downstream, but caps didn't change. In this case, we would reconfigure only when the next buffer arrives. The problem is that due to the allocation query being cached, the return query parameters endup outdated. In this patch we refactor the reconfigurating code into a function, and along with reconfiguring when a new buffer comes in, we also reconfigure when a query allocation arrives. https://bugzilla.gnome.org/show_bug.cgi?id=753850
-
- Aug 20, 2015
-
-
Nicolas Dufresne authored
As this test is using a short sleep (GST_USECOND, which is 10ms in microsecond), sometimes that EOS event is received before the loop in basesrc have run _do_seek() and pushed the update segment. To solve this issue, we wait for the initial segment (and flush it) then we wait for the second segment before sending EOS. https://bugzilla.gnome.org/show_bug.cgi?id=753365
-
Thibault Saunier authored
-
- Aug 19, 2015
-
-
Sebastian Dröge authored
-
Sebastian Dröge authored
-
Sebastian Dröge authored
-
- Aug 18, 2015
-
-
Tim-Philipp Müller authored
Explicitly keep track again whether upstream tags or parser tags already contain bitrate information, and only force a tag update for a bitrate if we are actually going to add the bitrate to the taglist later. This fixes constant re-sending of the same taglist, because upstream provided a bitrate already and we didn't add it, so we didn't save the 'posted' bitrate, which would then in turn again trigger the 'bitrate has changed too much, update tags' code path. Fixes tag spam with m4a files for example. https://bugzilla.gnome.org/show_bug.cgi?id=679768
-
- Aug 17, 2015
-
-
Stefan Sauer authored
Use round corners for bins and elements. Put sink pads on the left and src pads on the right of elements.
-
- Aug 16, 2015
-
-
Tim-Philipp Müller authored
In 0.10 there were no sticky events, and all tag events sent would just be merged with the previously-received tags. In 1.x we have sticky events, and the tags in the tag event(s) should at all times carry the complete tags, so we can't just push some tags and then just push tags with just bitrates to update the bitrates, etc. Instead we need to keep track of the upstream stream tags received, of the tags set by the video decoder subclass, and send an updated tag event with the combined tags including our own bitrate tags (if applicable) whenever the upstream tags, the subclass tags or any of our bitrates change. https://bugzilla.gnome.org/show_bug.cgi?id=679768
-
Tim-Philipp Müller authored
This is needed so that we can do proper tag handling all around, and combine the upstream tags with the tags set by the subclass and any extra tags the base class may want to add. API: gst_base_parse_merge_tags() https://bugzilla.gnome.org/show_bug.cgi?id=679768
-
Tim-Philipp Müller authored
We'll need those later. https://bugzilla.gnome.org/show_bug.cgi?id=679768
-
- Aug 15, 2015
-
-
Tim-Philipp Müller authored
Use gst_pad_peer_query_duration() and remove a few unnecessary levels of indentation. Rest of code might looks a bit questionable, but leave it as is for now.
-
Sebastian Dröge authored
Microoptimization we can do because the array is sorted by type.
-
In some cases, probes might want to handle the buffer/event/query themselves and stop the data from travelling further downstream. While this was somewhat possible with buffer/events and using GST_PROBE_DROP, it was not applicable to queries, and would result in the query failing. With this new GST_PROBE_HANDLED value, the buffer/event/query will be considered as successfully handled, will not be pushed further and the appropriate return value (TRUE or GST_FLOW_OK) will be returned This also allows probes to return a non-default GstFlowReturn when dealing with buffer push. This can be done by setting the GST_PAD_PROBE_INFO_FLOW_RETURN() field accordingly https://bugzilla.gnome.org/show_bug.cgi?id=748643
-
Mathieu Duponchelle authored
-
Mathieu Duponchelle authored
-
Thiago Santos authored
-
- Aug 14, 2015
-
-
-
Thiago Santos authored
Check if all the default 4 accept-caps possibilities are working: subset or intersect check and query-caps or template caps comparisons. https://bugzilla.gnome.org/show_bug.cgi?id=753623
-
Thiago Santos authored
It will make the default accept-caps handler use the pad template caps instead of the query-caps result to check if the caps is acceptable. This is aligned with what the design docs says the accept-caps should do (be non-recursive) and should be faster. It is *not* enabled by default, though. API: GST_PAD_FLAG_ACCEPT_TEMPLATE API: GST_PAD_IS_ACCEPT_TEMPLATE API: GST_PAD_SET_ACCEPT_TEMPLATE API: GST_PAD_UNSET_ACCEPT_TEMPLATE https://bugzilla.gnome.org/show_bug.cgi?id=753623
-
Edward Hervey authored
Makes it easier to differentiate from other modules states unit test
-