- 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
-
- Aug 13, 2015
-
-
Thiago Santos authored
According to the design docs: The ACCEPT_CAPS query is not required to work recursively, it can simply return TRUE if a subsequent CAPS event with those caps would return success. So make it a shallow check instead of recursivelly check downstream. https://bugzilla.gnome.org/show_bug.cgi?id=748635
-
Thiago Santos authored
Doesn't seem like it is going to get back to life anytime soon Also removes a {} block that was likely used to keep the dead code around.
-
Thiago Santos authored
GstPad has a flag for suggesting if the accept-caps query should use intersect instead of the default subset caps operation to verify if the caps would be acceptable. basetransform currently always uses the subset check and this patch makes it honor the flag for using intersect if it is set. https://bugzilla.gnome.org/show_bug.cgi?id=748635
-
- Aug 12, 2015
- Aug 11, 2015
-
-
Tim-Philipp Müller authored
-
If no date and only a time is given in gst_date_time_new_from_iso8601_string(), assume that it is "today" and try to parse the time-only string. "Today" is assumed to be in the timezone provided by the user (if any), otherwise Z - just like the behavior of the existing code. https://bugzilla.gnome.org/show_bug.cgi?id=753455
-
- Aug 09, 2015
-
-
To be able to disable the slightly "magic" forwarding of the necessary events between the harnesses. Also introduce a new test-suite for GstHarness, that documents the feature, and should hopefully expand into documenting most of the features the harness possesses. https://bugzilla.gnome.org/show_bug.cgi?id=752746
-
- Aug 08, 2015
-
-
Wim Taymans authored
-
We want to get the caps query *result*
-
Wim Taymans authored
Add methods to add/remove the providers that should be hidden by this provider. Also make a method to get a list of hidden providers. This makes it possible to have multiple systems monitor the same devices and remove duplicates. Add a property to see all devices, even duplicate ones from hidden providers.
-
The previous implementation was doing a direct call to the peer pad, which resulted in query probes never being called on the original pad. Instead of that, get the peer pad caps by using gst_pad_peer_query() which will call probes in the expected fashion.
-
- Aug 07, 2015
-
-
While calling gst_value_deserialize_sample, if there is a failure after caps is ref'ed, then caps is getting leaked. Hence checking for caps in fail: goto condition and unref'ing it https://bugzilla.gnome.org/show_bug.cgi?id=753338
-
- Aug 05, 2015
-
-
When running gst_registry_scan_plugin_file we were losing the information about the registry being loaded and ended up adding the plugin to the default registry which was not correct. https://bugzilla.gnome.org/show_bug.cgi?id=752662
-
Nicolas Dufresne authored
As of now, even for stream completly inside segment, there is no guarantied that the DTS will be inside the segment. Specifically for H.264 with B-Frames, the first few frames often have DTS that are before the segment. Instead of using the sync timestamp to clip out of segment buffer, take the duration from the start/stop provided by the sub-class, and check if the pts and pts_end is out of segment. https://bugzilla.gnome.org/show_bug.cgi?id=752791
-
Luis de Bethencourt authored
Even though asserts can't be disabled in GstHarness, Coverity still complains about running code inside them. Moving the code to outside the g_asserts(). CID #1311326, #1311327, #1311328
-
- Aug 04, 2015
-
-
Wim Taymans authored
Get a list of the currently monitored providers.
-
In case there is an IDLE probe fired from gst_pad_push_data and it doesn't return GST_FLOW_OK, the code jumps to the probe_stopped label which tries to unref the data object. However, at this point the data object belongs downstream and must not be touched. By setting data = NULL, the code skips this unref. https://bugzilla.gnome.org//show_bug.cgi?id=753151
-
Jan Schmidt authored
Don't use 'glbufferrefmeta' as the debug category for the parent buffer meta.
-
Eunhye Choi authored
upstream_size can be negative but queue->upstream_size is unsigned type. to get a chance to update queue->upstream_size in gst_queue2_get_range() it should keep the default value. https://bugzilla.gnome.org/show_bug.cgi?id=753011
-
Jan Schmidt authored
Don't export the debug variable for the parent_buffer_meta. This was accidentally exported and shouldn't be public
-
- Aug 03, 2015
-
-
Stefan Sauer authored
Helps to distiguish multiple filesinks.
-
- Jul 30, 2015
-
-
Tim-Philipp Müller authored
We don't "iterate" bins or pipelines any more.
-