Stefan Sauer [Thu, 25 Sep 2014 18:23:31 +0000 (20:23 +0200)]
basesrc: move the quick return up
Don't assign local vars if we skip anyway. Add logging for failure conditio
Tim-Philipp Müller [Thu, 25 Sep 2014 18:01:52 +0000 (19:01 +0100)]
tests: parallelise 'make valgrind'
Use $(MAKE) instead of 'make' inside the Makefile,
otherwise the make will run as if -j1 had been
specified and complain about the job server not
being available, and with $(MAKE) in inherits the
parent make's settings it seems.
Upgrade common submodule for parallel check-valgrind.
Let this settle a bit before upgrading the other modules.
Tim-Philipp Müller [Thu, 25 Sep 2014 17:57:32 +0000 (18:57 +0100)]
win32: update .def file
It's sorted. If it's unsorted, make check-exports fails.
Tim-Philipp Müller [Thu, 25 Sep 2014 17:55:03 +0000 (18:55 +0100)]
info: remove confusing warning about running under valgrind
We're not actually doing anything differently anywhere when
we detect that we're running under valgrind, so let's not
print that confusing message that makes people wonder how
they can switch it off so they can valgrind the normal
code paths. Seeing that we're not doing that nor have done
so in the last 10 years we might just as well remove the
entire check actually.
Tim-Philipp Müller [Thu, 25 Sep 2014 15:21:51 +0000 (16:21 +0100)]
tests: fix caps leak in baseparse unit test
Jonas Holmberg [Thu, 25 Sep 2014 12:54:23 +0000 (14:54 +0200)]
flowcombiner: add a gst_flow_combiner_clear() method
https://bugzilla.gnome.org/show_bug.cgi?id=737359
API: gst_flow_combiner_clear()
Thibault Saunier [Wed, 24 Sep 2014 08:11:54 +0000 (10:11 +0200)]
scripts: Handle gst-python in gst-uninstalled
https://bugzilla.gnome.org/show_bug.cgi?id=709082
Thibault Saunier [Tue, 3 Jun 2014 12:23:30 +0000 (14:23 +0200)]
capsfilter: Remove EOS event from pending_event list on FLUSH_STOP
https://bugzilla.gnome.org/show_bug.cgi?id=709868
William Manley [Mon, 22 Sep 2014 13:27:05 +0000 (14:27 +0100)]
docs: Fix GstBuffer typo "memory bock" -> "memory block"
https://bugzilla.gnome.org/show_bug.cgi?id=737117
William Manley [Mon, 22 Sep 2014 16:27:31 +0000 (17:27 +0100)]
docs: Improve gst_buffer_get_meta() to clear up confusion
I was confused by the existence of `gst_buffer_get_meta` as it suggested
to me that you should only attach one of any type of GstMeta to a buffer.
It's perfectly fine to attach multiple from a single API so I'm
documenting that here.
https://bugzilla.gnome.org/show_bug.cgi?id=737129
Marcin Kolny [Mon, 22 Sep 2014 17:05:32 +0000 (19:05 +0200)]
datetime: added missing include directives
https://bugzilla.gnome.org/show_bug.cgi?id=737133
Thibault Saunier [Tue, 23 Sep 2014 12:31:29 +0000 (14:31 +0200)]
queue: Do not forget to release the QUEUE_LOCK in the out_flow_error path
Avoiding deadlocks!
Stefan Sauer [Tue, 23 Sep 2014 10:53:18 +0000 (12:53 +0200)]
docs: fix a small contradition in the docs
The vmethod get_size() shall return the size in 'format' as configured by
_set_format().
Thibault Saunier [Mon, 22 Sep 2014 07:33:04 +0000 (09:33 +0200)]
queue: Do not hold GST_QUEUE_LOCK while posting ERROR messages
This might create deadlocks and we need to avoid holding element
specific lock while posting messages
For example a deadlock will happen if while posting the message,
someone connected on the bus (sync) tries to DOT the pipeline.
https://bugzilla.gnome.org/show_bug.cgi?id=737102
Thiago Santos [Fri, 19 Sep 2014 15:02:46 +0000 (12:02 -0300)]
queue2: do not post buffering messages holding the lock
It might cause deadlocks to post messages while holding the queue2
lock. To avoid this a new boolean flag is set whenever a new
buffering percent is found. The message is posted after the lock
is released.
To make sure the buffering messages are posted in the right order, messages
are posted holding another lock. This prevents 2 threads trying to post
messages at the same time.
https://bugzilla.gnome.org/show_bug.cgi?id=736969
Ravi Kiran K N [Fri, 19 Sep 2014 04:12:10 +0000 (09:42 +0530)]
gsturi: Remove unnecessary code
gst_uri_handler_set_uri() function has new_uri, location and colon
are not necessary, they can be removed.
https://bugzilla.gnome.org/show_bug.cgi?id=736877
Tim-Philipp Müller [Thu, 18 Sep 2014 23:33:58 +0000 (00:33 +0100)]
docs: pwg: fix some links to the API docs
https://bugzilla.gnome.org/show_bug.cgi?id=736762
Tim-Philipp Müller [Thu, 18 Sep 2014 17:55:47 +0000 (18:55 +0100)]
filesrc: remove FIXME
https://bugzilla.gnome.org/show_bug.cgi?id=735878
Olivier Crête [Thu, 18 Sep 2014 01:49:18 +0000 (21:49 -0400)]
gst: Fix spelling error
Thank to Adrian Owen for reporting this error.
https://bugzilla.gnome.org/show_bug.cgi?id=736839
Ognyan Tonchev [Wed, 17 Sep 2014 15:17:10 +0000 (17:17 +0200)]
typefindelement: do not leak sticky events in flush_stop
https://bugzilla.gnome.org/show_bug.cgi?id=736813
Stefan Sauer [Fri, 12 Sep 2014 12:42:23 +0000 (14:42 +0200)]
info: avoid global variable for log_file
Use user_data to pass the log_file handle to the logger-function.
If one wants to change the log target (e.g. GST_DEBUG_FILE), simply call
gst_debug_remove_log_function() and re-add the handler with the new log-target
using gst_debug_add_log_function ().
Ognyan Tonchev [Tue, 16 Sep 2014 11:48:18 +0000 (13:48 +0200)]
event: add annotations to gst_event_parse_toc_select()
https://bugzilla.gnome.org/show_bug.cgi?id=736739
Thiago Santos [Thu, 11 Sep 2014 21:01:58 +0000 (18:01 -0300)]
multiqueue: do not post messages holding the lock
It might cause deadlocks to post messages while holding the multiqueue
lock. To avoid this a new boolean flag is set whenever a new buffering percent
is found. The message is posted after the lock can be released.
To make sure the buffering messages are posted in the right order, messages
are posted holding another lock. This prevents 2 threads trying to post
messages at the same time.
https://bugzilla.gnome.org/show_bug.cgi?id=736295
Wim Taymans [Tue, 16 Sep 2014 14:07:40 +0000 (16:07 +0200)]
docs: fix typo
Ognyan Tonchev [Tue, 16 Sep 2014 10:17:48 +0000 (12:17 +0200)]
query: Add annotations to gst_query_add_allocation_pool()
https://bugzilla.gnome.org/show_bug.cgi?id=736736
Aurélien Zanelli [Mon, 15 Sep 2014 14:38:17 +0000 (16:38 +0200)]
basesrc: handle reference in set_allocation rather than in prepare_allocation
Otherwise we can forget to unref objects in error cases.
https://bugzilla.gnome.org/show_bug.cgi?id=736680
Sebastian Dröge [Mon, 15 Sep 2014 10:06:40 +0000 (13:06 +0300)]
check: Use the name parameter of gst_check_setup_src_pad_by_name() and the sink variant
This was hardcoded to "sink" / "src" by accident in previous refactoring.
Tim-Philipp Müller [Sat, 13 Sep 2014 19:12:52 +0000 (20:12 +0100)]
coreelements: mark properties with MUTABLE_PLAYING
Thibault Saunier [Thu, 11 Sep 2014 13:52:32 +0000 (15:52 +0200)]
check: Add a function to check destruction of objects
Add a method letting people to ensure that unreffing one object
leads to its destruction, and possibly the destruction of more object
(think destruction of a GstBin etc...).
https://bugzilla.gnome.org/show_bug.cgi?id=736477
Tim-Philipp Müller [Fri, 12 Sep 2014 13:10:40 +0000 (14:10 +0100)]
tools: gst-inspect: don't list pad functions
Don't print all the different pad functions, it's just
confusing and no one has ever needed to know this for
anything ever anyway, it's just useless information.
Besides, we also label the default implementations as
'custom' implementations (the code that tries to
prevent that doesn't actually work it seems).
https://bugzilla.gnome.org/show_bug.cgi?id=736377
Sebastian Dröge [Fri, 12 Sep 2014 12:22:19 +0000 (15:22 +0300)]
pad: Make sure the buffer to get/pull_range() has at least the requested size
https://bugzilla.gnome.org/show_bug.cgi?id=735861
Tiago [Fri, 5 Sep 2014 18:36:02 +0000 (18:36 +0000)]
check: Adding documentation to the gst_check_setup_sink_pad_by_name function
https://bugzilla.gnome.org/show_bug.cgi?id=734190
Ognyan Tonchev [Wed, 10 Sep 2014 12:53:00 +0000 (14:53 +0200)]
query: add annotations to gst_query_set_nth_allocation_pool()
https://bugzilla.gnome.org//show_bug.cgi?id=736424
Rémi Lefèvre [Thu, 11 Sep 2014 07:35:17 +0000 (09:35 +0200)]
valve: fix typo in description
https://bugzilla.gnome.org/show_bug.cgi?id=736455
Tim-Philipp Müller [Tue, 9 Sep 2014 19:43:02 +0000 (20:43 +0100)]
baseparse: minor docs fix
Tim-Philipp Müller [Wed, 3 Sep 2014 16:38:16 +0000 (17:38 +0100)]
devicemonitor: fix typo in sample code in docs
https://bugzilla.gnome.org/show_bug.cgi?id=735975
Wim Taymans [Mon, 25 Aug 2014 09:34:48 +0000 (11:34 +0200)]
tests: add flush-stop on inactive pad test
Check that pushing flush-stop on an inactive pad does not clear the
flushing flag.
Wim Taymans [Thu, 21 Aug 2014 13:49:17 +0000 (15:49 +0200)]
pad: don't accept flush-stop on inactive pads
Inactive pads should at all times have the flushing flag set. This means
that when we get a flush-stop on an inactive pad we must ignore it.
On sinkpads, make this more explicit. We used to not clear the flush
flag but remove the events and then return an error because the flushing
flag was set. Now just simply refuse the event without doing anything.
On srcpads, check that we are trying to push a flush-stop event and
refuse it. We would allow this and mark the srcpad as non-flushing
anymore.
Fixes https://bugzilla.gnome.org/show_bug.cgi?id=735357
Ravi Kiran K N [Wed, 27 Aug 2014 11:36:57 +0000 (17:06 +0530)]
output-selector: Send all events to active src pad and EOS to all src pads
Fixes tests/icles/output-selector-test
https://bugzilla.gnome.org/show_bug.cgi?id=729811
Guillaume Desmottes [Thu, 28 Aug 2014 15:24:56 +0000 (17:24 +0200)]
manual: fix typo in advanced-dataaccess.xml
https://bugzilla.gnome.org/show_bug.cgi?id=735609
Arnaud Vrac [Tue, 26 Aug 2014 18:14:40 +0000 (20:14 +0200)]
buffer: do not touch memory tag flag when copying buffer flags
The tag memory flag will be set later if the memory is also copied. This
patch avoids buffers being freed needlessly in bufferpools.
https://bugzilla.gnome.org/show_bug.cgi?id=735574
Linus Svensson [Tue, 15 Jul 2014 14:06:49 +0000 (16:06 +0200)]
bus: gst_bus_add_watch() can return 0 on error
Fixes: https://bugzilla.gnome.org/show_bug.cgi?id=735195
Thiago Santos [Mon, 25 Aug 2014 16:44:30 +0000 (13:44 -0300)]
baseparse: handle streamheaders by prepending them to the stream
Add a first_buffer boolean state flag to have baseparse do actions
before pushing data. This is used to check the caps for streamheader
buffers that are prepended to the stream, but only if the first buffer
isn't already marked with the _HEADER flag. In this case, it is assumed
that the _HEADER marked buffer is the same as the streamheader.
https://bugzilla.gnome.org/show_bug.cgi?id=735070
Sebastian Dröge [Wed, 27 Aug 2014 08:01:01 +0000 (11:01 +0300)]
concat: Allow seeking on the currently playing stream
This is consistent with the stream time reporting.
Tim-Philipp Müller [Sat, 23 Aug 2014 11:24:27 +0000 (12:24 +0100)]
pad: add g-i 'transfer full' annotations to chain and chain_list functions
https://bugzilla.gnome.org/show_bug.cgi?id=735210
Guillaume Desmottes [Fri, 22 Aug 2014 08:32:38 +0000 (10:32 +0200)]
pad: annotate GstPadEventFunction event with 'transfer full'
The callback is supposed to take ownership of the event so
best to be explicit about it.
https://bugzilla.gnome.org/show_bug.cgi?id=735210
Linus Svensson [Wed, 20 Aug 2014 10:55:51 +0000 (12:55 +0200)]
tests: add test that triggers deadlock in state change of queue
When receiving FLASH_STOP in a state transition to READY, a queue
element can end up with an active task that will never end.
https://bugzilla.gnome.org/show_bug.cgi?id=734688
Tim-Philipp Müller [Thu, 21 Aug 2014 13:02:16 +0000 (14:02 +0100)]
queue: fix race when flush-stop event comes in whilst shutting down
Don't re-start the queue push task on the source pad when a
flush-stop event comes in and we're in the process of shutting
down, otherwise that task will never be stopped again.
When the element is set to READY state, the pads get de-activated.
The source pad gets deactivated before the queue's own activate_mode
function on the source pads gets called (which will stop the thread),
so checking whether the pad is active before re-starting the task on
receiving flush-stop should be fine. The problem would happen when the
flush-stop handler was called just after the queue's activate mode
function had stopped the task.
Spotted and debugged by Linus Svensson <linux.svensson@axis.com>
https://bugzilla.gnome.org/show_bug.cgi?id=734688
Tim-Philipp Müller [Wed, 6 Aug 2014 13:01:09 +0000 (14:01 +0100)]
bytereader: add gst_byte_reader_peek_sub_reader() and _get_sub_reader()
Adds API to get or peek a sub-reader of a certain size from
a given byte reader. This is useful when parsing nested chunks,
one can easily get a byte reader for a sub-chunk and make
sure one never reads beyond the sub-chunk boundary.
API: gst_byte_reader_peek_sub_reader()
API: gst_byte_reader_get_sub_reader()
Aurélien Zanelli [Fri, 25 Jul 2014 14:39:40 +0000 (16:39 +0200)]
docs: make explicit that the caps passed to gst_base_src_set_caps() are 'tranfer none'
https://bugzilla.gnome.org/show_bug.cgi?id=733741
Thiago Santos [Thu, 14 Aug 2014 21:53:40 +0000 (18:53 -0300)]
inputselector: always proxy caps query
Otherwise it would only be proxied for the active pad which can lead
upstream to use an incompatible caps for the downstream element.
Even if a reconfigure event is sent upstream when the pad is activated, this
will save the caps reconfiguration if it is already using an acceptable caps.
Tim-Philipp Müller [Thu, 14 Aug 2014 13:37:56 +0000 (14:37 +0100)]
base: and fix build with new g-i again
Tim-Philipp Müller [Thu, 14 Aug 2014 13:25:06 +0000 (14:25 +0100)]
base: remove g-i annotation that makes older g-ir-scanner crash
Just remove one skip annotation that causes this:
** (g-ir-compiler:12458): ERROR **: Caught NULL node, parent=empty
with older g-i versions such as 1.32.1.
Philippe Normand [Wed, 13 Aug 2014 12:12:00 +0000 (14:12 +0200)]
bus: destroy signal watch from the context it was mapped to
Don't rely on g_source_remove() because it operates on the main
context. If a signal watch was added to a new thread-default context
g_source_remove() would have no effect. So simply use
g_source_destroy() to avoid this problem.
Additionally the source_id was removed from GstBusPrivate because it
was redundant with the signal watch GSource also stored in that
structure.
https://bugzilla.gnome.org/show_bug.cgi?id=734716
Thibault Saunier [Thu, 7 Aug 2014 10:18:04 +0000 (12:18 +0200)]
multiqueue: Not post BUFFERING message if one of the singlequeue doesn't need it
Imagine the following 'pipeline'
--------------
p1/| 'fullqueue' |--- 'laggy' downstream
--------- / | |
-| demuxer | | multiqueue |
--------- \ | |
p2\| 'emptyqueue' |--- 'fast' downstream
--------------
In the case downstream of one single queue (fullqueue) has (a lot of) latency
(for example for reverse playback with video), we can end up having the other
SingleQueue (emptyqueue) emptied, before that fullqueue gets
unblocked. In the meantime, the demuxer tries to push on fullqueue, and
is blocking there.
In that case the current code will post a BUFFERING message on the bus when
emptyqueue gets emptied, that leads to the application setting the pipeline state to
PAUSED. So now we end up in a situation where 'laggy downstream' is
prerolled and will not unblock anymore because the pipeline is set to
PAUSED, the fullequeue does not have a chance to be emptied and
the emptyqueue can not get filled anymore so no more BUFERRING message
will be posted and the pipeline is stucked in PAUSED for the eternity.
Making sure that we do not try to "buffer" if one of the single queue
does not need buffering, prevents this situtation from happening though it lets the
oportunity for buffering in all other cases.
That implements a new logic where we need all singlequeue to need
buffering for the multiqueue to actually state buffering is needed,
taking the maximum buffering of the single queue as the reference point.
https://bugzilla.gnome.org/show_bug.cgi?id=734412
Sebastian Dröge [Wed, 13 Aug 2014 10:01:23 +0000 (13:01 +0300)]
multiqueue: Only handle flow returns < EOS as errors, not e.g. flushing
Sebastian Dröge [Wed, 13 Aug 2014 09:40:37 +0000 (12:40 +0300)]
bin: Use allow-none instead of nullable until we depend on a new enough GI version
Sebastian Dröge [Wed, 13 Aug 2014 09:39:47 +0000 (12:39 +0300)]
bin: gst_bin_new() can accept NULL as name
Sebastian Dröge [Wed, 13 Aug 2014 09:37:08 +0000 (12:37 +0300)]
element: Clarify docs about gst_element_get_request_pad() and remove deprecation part
This function is not really pad or slow for the common case of requesting a
pad with the name of the template. It is only slower if you to name your pads
directly instead of letting the element handle it.
Also there's no reason to deprecate it in favor of a more complicated function
for the common case.
Sebastian Dröge [Wed, 13 Aug 2014 09:20:51 +0000 (12:20 +0300)]
queue2: Post errors if we receive EOS after downstream reported an error
There will be no further data flow that would allow us to propagate the
error upstream, causing nobody at all to post an error message.
Sebastian Dröge [Wed, 13 Aug 2014 09:15:03 +0000 (12:15 +0300)]
queue: Post errors when receiving EOS after downstream returned an error
There might be no further data flow that would allow us to propagate the
error upstream, causing nobody to post an error at all.
Sebastian Dröge [Wed, 13 Aug 2014 09:10:39 +0000 (12:10 +0300)]
multiqueue: Post errors ourselves if they are received after EOS
After EOS there will be no further buffer which could propagate the
error upstream, so nothing is going to post an error message and
the pipeline just idles around.
Arun Raghavan [Tue, 12 Aug 2014 14:33:06 +0000 (20:03 +0530)]
docs: Trivial pad documentation fix
Presumably a copy-pasto.
Sebastian Dröge [Fri, 8 Aug 2014 07:54:02 +0000 (09:54 +0200)]
concat: Add unit tests for concat element
Sebastian Dröge [Fri, 8 Aug 2014 07:13:50 +0000 (09:13 +0200)]
concat: Add documentation and integrate into documentation build
Sebastian Dröge [Thu, 7 Aug 2014 12:42:44 +0000 (14:42 +0200)]
concat: Add new element that concatenates multiple streams
https://bugzilla.gnome.org/show_bug.cgi?id=734470
Thiago Santos [Sat, 9 Aug 2014 13:57:56 +0000 (10:57 -0300)]
tests: caps: add check for caps with features intersection
Checks that a caps without features doesn't intersect with
one that has features
Tim-Philipp Müller [Thu, 7 Aug 2014 13:54:37 +0000 (14:54 +0100)]
examples: controller: fix typo in comments
Tim-Philipp Müller [Wed, 6 Aug 2014 12:58:22 +0000 (13:58 +0100)]
bytereader: use unchecked inline variant for get_remaining in more places
We've already done the g_return_*_if_fail (reader != NULL)
dance in those places, so no need to do it again.
Sebastian Dröge [Wed, 6 Aug 2014 12:43:08 +0000 (14:43 +0200)]
utils: Ghostpads can be request pads too but check if the pad has a template
Otherwise we dereference NULL in some cases and crash.
Sebastian Rasmussen [Wed, 6 Aug 2014 10:34:42 +0000 (12:34 +0200)]
tests: Add missing unrefs of objects after use
Unreffing the objects returned by gst_bin_get_by_name() and
gst_pipeline_get_use() were missing in several tests, so add these.
Fixes https://bugzilla.gnome.org/show_bug.cgi?id=734345
Sebastian Dröge [Wed, 6 Aug 2014 10:55:57 +0000 (12:55 +0200)]
utils: Fix unititialized variable compiler warning
Sebastian Rasmussen [Sun, 13 Jul 2014 13:31:08 +0000 (15:31 +0200)]
tests: Add test verifying gst_element_link_pads_full()
Fixes https://bugzilla.gnome.org/show_bug.cgi?id=733119
Sebastian Rasmussen [Sun, 13 Jul 2014 13:28:32 +0000 (15:28 +0200)]
utils: Unref/release pads in error cases when linking pads
Previously gst_element_link_pads_full() forgot to unreference or release
request pads in several error cases. Also comments were added mentioning
why releasing is not necessary in some places.
Fixes https://bugzilla.gnome.org/show_bug.cgi?id=733119
Tiago Cesar Katcipis [Fri, 1 Aug 2014 20:27:39 +0000 (17:27 -0300)]
gstcheck: add docs for gst_check_setup_src_pad_by_name()
https://bugzilla.gnome.org/show_bug.cgi?id=734142
Edward Hervey [Thu, 31 Jul 2014 16:32:03 +0000 (18:32 +0200)]
Makefile: Add usage of build-checks step
Allows building checks without running them
Mohammed Sameer [Wed, 30 Jul 2014 12:46:22 +0000 (15:46 +0300)]
bufferpool: Add missing error checking to default_alloc_buffer()
default_alloc_buffer() calls gst_buffer_new_allocate() but does not check for
failed allocation.
This patch makes default_alloc_buffer() return an error (GST_FLOW_ERROR) if
buffer allocation fails.
https://bugzilla.gnome.org/show_bug.cgi?id=733974
Thiago Santos [Tue, 29 Jul 2014 17:21:33 +0000 (14:21 -0300)]
multiqueue: avoid using infinite buffers limit if finite is requested
If the current max-buffers limit it infinite and a finite value is
requested, switch to the MAX (requested, current-value) to set some
limit but not below what we know that we've needed so far.
https://bugzilla.gnome.org/show_bug.cgi?id=733637
https://bugzilla.gnome.org/show_bug.cgi?id=733837
Sebastian Rasmussen [Thu, 24 Jul 2014 20:02:58 +0000 (22:02 +0200)]
parse: Unref reference to enclosing bins
Previously all reference to enclosing bins of an element were leaked
when doing delaying setting a property.
Fixes https://bugzilla.gnome.org/show_bug.cgi?id=733697
Руслан Ижбулатов [Sun, 27 Jul 2014 02:37:08 +0000 (02:37 +0000)]
gst-launch: Support SIGINT (Ctrl+C) on W32
W32 has no SIGINT, but it does have SetConsoleCtrlHandler(), which sets up
a handler for Ctrl+C.
https://bugzilla.gnome.org/show_bug.cgi?id=733814
Руслан Ижбулатов [Sun, 27 Jul 2014 03:06:16 +0000 (03:06 +0000)]
poll: Prevent false-negative from WAKE_EVENT() on W32
SetEvent() seems to not call SetLastError(0) internally, so checking last
error after calling SetEvent() may return the error from an earlier W32 API
call. Fix this by calling SetlastError(0) explicitly.
Currently WAKE_EVENT() code is cramped into a macro and doesn't look to be
entirely correct. Particularly, it does not check the return value of
SetEvent(), only the thread-local W32 error value. It is likely that SetEvent()
actually just returns non-zero value, but the code mistakenly thinks that the
call has failed, because GetLastError() seems to indicate so.
https://bugzilla.gnome.org/show_bug.cgi?id=733805
Tim-Philipp Müller [Sat, 26 Jul 2014 13:42:54 +0000 (14:42 +0100)]
gst: include atomicqueue.h again in gst.h
It's a public header of gstreamer core, so #include <gst/gst.h>
should make the API available.
Tim-Philipp Müller [Fri, 25 Jul 2014 10:45:56 +0000 (11:45 +0100)]
typefindelement: remove prototype for function that no longer exists
Thiago Santos [Thu, 24 Jul 2014 17:39:11 +0000 (14:39 -0300)]
bytereader: add gst_byte_reader_masked_scan_uint32_peek
Adds gst_byte_reader_masked_scan_uint32_peek just like
GstAdapter has a _peek and non _peek version
Upgraded tests to check that the returned value is correct in the
_peek version
API: gst_byte_reader_masked_scan_uint32_peek
https://bugzilla.gnome.org/show_bug.cgi?id=728356
Tim-Philipp Müller [Thu, 26 Jun 2014 13:09:25 +0000 (14:09 +0100)]
bufferlist: pre-allocate buffer array in one go with the buffer list
We can now create and free a buffer list with one slice alloc/free
call in most cases, instead of one slice alloc/free for the list,
one slice alloc/free for the GArray, and one malloc/free for the
GArray array. In practice we know the max size of our buffer list
from the start, so can avoid reallocs.
https://bugzilla.gnome.org/show_bug.cgi?id=732284
Stefan Sauer [Wed, 23 Jul 2014 19:27:48 +0000 (21:27 +0200)]
private: allow internal access to the debug base-time
Moving the extern to the head lets us access this from other parts as well. This
is neeed in the tracer branch.
Arun Raghavan [Tue, 22 Jul 2014 18:45:17 +0000 (00:15 +0530)]
scripts: Use git pull --rebase
No point introducing redundant merge commits.
Thiago Santos [Mon, 21 Jul 2014 15:41:08 +0000 (12:41 -0300)]
Revert "tests: taglist: add basic test for taglists serialization"
This reverts commit
85d23d19b7de40541d63b0bc76d8b646c321af26.
There was already a gsttag.c tests file, this test has been merged
in it in the previous commit
Thiago Santos [Mon, 21 Jul 2014 15:40:47 +0000 (12:40 -0300)]
tests: tag: add the empty taglist serialization test
Adds the test to the appropriate and already existing file.
Thiago Santos [Mon, 14 Jul 2014 21:46:54 +0000 (18:46 -0300)]
tests: taglist: add basic test for taglists serialization
Make sure it works with empty taglists
Thiago Santos [Mon, 14 Jul 2014 21:25:50 +0000 (18:25 -0300)]
tests: gststructure: serialization of tag event structure
Adds a test that checks that the serialization of a tag event structure
works without problems
https://bugzilla.gnome.org/show_bug.cgi?id=733131
Thiago Santos [Mon, 14 Jul 2014 21:23:43 +0000 (18:23 -0300)]
gstvalue: add GstTagList compare function
When serializing GstStructures from events in GDP it will add a taglist
as a GstStructure field, having the compare function allows comparison of
GstStructures to check if the serialized/deserialized version matches the
original one, among other cases.
https://bugzilla.gnome.org/show_bug.cgi?id=733131
Srimanta Panda [Wed, 9 Jul 2014 13:48:10 +0000 (15:48 +0200)]
funnel: Fix for racy EOS event handling
When eos events are forwarded simultaneouly from two sinkpads on
funnel, it doesnot forward the eos to sourcepad. The reason is
sticky events are stored after the event callbacks are returned.
Therefore while one is about to store the sticky events on the its
sinkpad, other sinkpad starts checking for the eos events on all other
sinkpads and assumes eos is not present yet.
https://bugzilla.gnome.org/show_bug.cgi?id=732851
Sebastian Dröge [Thu, 17 Jul 2014 14:05:00 +0000 (16:05 +0200)]
pipeline: Add unit test for resetting of the start time
Also check if this properly affects basesink elements to not
report the old start time but the real current position when
setting to PAUSED again.
Sebastian Dröge [Tue, 15 Jul 2014 16:19:24 +0000 (18:19 +0200)]
pipeline: Reset the start time when going from PAUSED to READY too
Sebastian Dröge [Tue, 15 Jul 2014 15:19:10 +0000 (17:19 +0200)]
pipeline: Reset start time in READY->PAUSED before chaining up
Otherwise bin will change the state of the child elements without
distributing the new start time.
Tim-Philipp Müller [Sat, 28 Jun 2014 16:58:26 +0000 (17:58 +0100)]
elements: improve buffer flags to string utility function
Avoid relocations and refactor so that we don't calculate
the fixed and known at compile time maximum string size
every time. Also skip the mini object flags which we are
not going to print anyway.
Sebastian Dröge [Sat, 19 Jul 2014 16:04:31 +0000 (18:04 +0200)]
Back to development
Sebastian Dröge [Sat, 19 Jul 2014 14:46:41 +0000 (16:46 +0200)]
Release 1.4.0
Sebastian Dröge [Sat, 19 Jul 2014 14:21:20 +0000 (16:21 +0200)]
Update .po files