summaryrefslogtreecommitdiff
AgeCommit message (Collapse)AuthorFilesLines
2015-03-07flowcombiner: add a gst_flow_combiner_update_pad_flow() methodMark Nauwelaerts2-0/+31
https://bugzilla.gnome.org/show_bug.cgi?id=744572 API: gst_flow_combiner_update_pad_flow()
2015-03-07flowcombiner: add a gst_flow_combiner_reset() methodMark Nauwelaerts2-0/+26
https://bugzilla.gnome.org/show_bug.cgi?id=744572 API: gst_flow_combiner_reset()
2015-03-06basesrc: Fix typo in debug messageSebastian Dröge1-1/+1
2015-03-05info: avoid malloc/free if log object is NULLTim-Philipp Müller1-2/+3
2015-03-05info: move __FILE__ path shortening into default log handlerTim-Philipp Müller1-5/+10
Instead of always shortening the __FILE__ path, even if the log message is not actually printed, which might happen if the log level is activated but the category is not, only shorten the path if we're actually going to output it and if it looks like it needs shortening. Log handlers had no guarantee that they would get a name instead of a path anyway on any architecture, so it shouldn't be a problem. https://bugzilla.gnome.org/show_bug.cgi?id=745213
2015-03-05info: shorten __FILE__ on all platformsPeter Urbanec1-4/+0
This is useful not only for MSVC, but also with gcc/Linux when doing cross-compilation builds and out-of-tree builds. https://bugzilla.gnome.org/show_bug.cgi?id=745213
2015-03-04docs: clarify min-latency wording in part-latency.txtVincent Penquerc'h1-3/+3
https://bugzilla.gnome.org/show_bug.cgi?id=744338
2015-03-04win32/common/gstconfig.h: removed libxml include directiveMarcin Kolny1-8/+0
This is a leftover from 0.10 and not needed anymore. Fixes https://bugzilla.gnome.org/show_bug.cgi?id=745210
2015-03-03queue2: Signal the sinkpad thread if a flow error happenedSebastian Dröge1-0/+7
It might still be waiting for a query to be handled, or the queue to become empty again for the next item. Also if downstream returns FLUSHING, flush the queue like we do in queue and multiqueue.
2015-03-03queue: Wake up the query function on errors from the loop functionSebastian Dröge1-2/+5
Otherwise we might wait forever for serialized queries to be handled as the loop function is stopped and as such we will never ever dequeue the query and handle it. https://bugzilla.gnome.org/show_bug.cgi?id=745319
2015-03-02utils: improve warning when linking elements without common ancestorTim-Philipp Müller1-2/+18
This comes up quite a lot and it's a common mistake, so let's try to improve the warning message a little.
2015-02-27input-selector: Drop custom latency query handlingArun Raghavan1-82/+0
The default latency query handler now implements this logic
2015-02-26gst-unsinstalled: Add ges-launch manuals path to MANPATH.Mathieu Duponchelle1-1/+1
2015-02-26pad: Don't fail latency query on unlinked padsArun Raghavan1-4/+13
A single unlinked pad can make the latency query fail across the pipeline, which is probably not desirable. Instead, we return a default anything goes value. Perhaps we should also be emitting a gst_message_new_latency() when a PLAYING element has one of its pads linked. https://bugzilla.gnome.org/show_bug.cgi?id=745197
2015-02-26baseparse: Don't emit errors on EOS if we saw GAP eventsEdward Hervey1-2/+6
If we saw GAP events (meaning the streams is advancing) before we get EOS, we should not post an ERROR, since it is not fatal. https://bugzilla.gnome.org/show_bug.cgi?id=745143
2015-02-26gstvalue: Make sure GST_FOURCC_ARGS produces printable charactersEdward Hervey2-5/+25
Some systems will crash if we use non-printable characters in print/debug statements. Make sure that GST_FOURCC_ARGS never does that https://bugzilla.gnome.org/show_bug.cgi?id=745144
2015-02-25gstutils: remove incorrect Fixme commentLuis de Bethencourt1-1/+0
If the checks were changed to using g_return_if_fail() the GST_DEBUG lines about the specific failure would be lost.
2015-02-25gstutils: remove obsolete Fixme commentLuis de Bethencourt1-5/+0
gst_pad_link_filtered() is very long gone and current gst_element_link_pads_filtered() doesn't apply to this Fixme comment.
2015-02-25gst-uninstalled: add adaptivedemux paths from -badMatthieu Bouron1-1/+1
https://bugzilla.gnome.org/show_bug.cgi?id=745122
2015-02-24docs: remove dead linkLuis de Bethencourt1-3/+1
Remove dead link to wiki page for SubmittingPatches https://bugzilla.gnome.org/show_bug.cgi?id=730311
2015-02-24helpers: Fix install of completion-helper.Mathieu Duponchelle1-1/+2
By applying the supplied transformation to the program name, for example --program-prefix.
2015-02-23completion-helper: Add missing DESTDIRNicolas Dufresne1-2/+2
Otherwise doing "make install DESTDIR" will try to write to /usr/share/...
2015-02-23completion-helper: Add filtering by klass and sink caps.Mathieu Duponchelle1-7/+50
2015-02-23multiqueue: avoid returning downstream GST_FLOW_EOS from previous segment to ↵Mark Nauwelaerts1-12/+67
current upstream segment
2015-02-23flowcombiner: fix documentation comment typoMark Nauwelaerts1-1/+1
2015-02-23baseparse: drain segment upon SEGMENT_DONE to ensure proper event orderMark Nauwelaerts1-0/+11
2015-02-23baseparse: clean up some bogus commented codeMark Nauwelaerts1-2/+0
2015-02-23completion-helper: Append $(EXEEXT) to the name of the moved file.Mathieu Duponchelle1-2/+2
Fixes the build on Windows (https://ci.gstreamer.net/job/cerbero-cross-mingw32/1742/console)
2015-02-23Fix distcheckTim-Philipp Müller1-1/+1
Disable bash completion during distchecking otherwise it may try to install into a system path and fail.
2015-02-23Dist new data directoryTim-Philipp Müller1-1/+2
Fixes 'make dist'
2015-02-23bash-completion: Implement in a different way.Mathieu Duponchelle11-1/+560
+ Gets installed + Uses a helper tool, gst-completion-helper, installed in bash-completions/helpers. + Adds a common script that other tools can source. https://bugzilla.gnome.org/show_bug.cgi?id=744877
2015-02-23GstDeviceMonitor: keep alphabetical orderLuis de Bethencourt2-2/+2
2015-02-20Revert "element: set pads need-parent flag to false when removing"Olivier Crête2-36/+0
This reverts commit 1911554cff2c4a11772b541a8215a80c728b1097. This breaks the functionality of GST_PAD_FLAG_NEED_PARENT, the reason for this flag is that if a pad is removed from a running element, you don't want functions (such as chain or event) to be called on the pad without a parent set. This can happen if you remove a request or sometimes pad from a running element. I don't see the code that caused this in tsdemux, but if it needs to unset the flag on remove, it should do it itself and then make sure that the parent exists in any pad function.
2015-02-19check: cast element in ASSERT_SET_STATE.Mathieu Duponchelle1-1/+1
https://bugzilla.gnome.org/show_bug.cgi?id=744777
2015-02-19inputselector: Use a separate query for upstream pads and let it fail if one ↵Sebastian Dröge1-5/+10
upstream query fails
2015-02-19pad: If the latency query fails for one of the pads, it fails overallSebastian Dröge1-2/+4
2015-02-18queue: Remove unused boolean parameter from internal functionsSebastian Dröge1-24/+17
2015-02-18queue: Add unit test for buffer list and time level handlingSebastian Dröge1-0/+152
2015-02-18queue: Add support for buffer listsSebastian Dröge1-32/+212
2015-02-18queue2: Count the number of buffers in a buffer list for updating the ↵Sebastian Dröge1-2/+2
current levels instead of just assuming one buffer.
2015-02-17message: revive async delivery message before bus thread can run unrefTim-Philipp Müller1-1/+3
Revive message in dispose handler before we signal the bus thread, otherwise the bus thread might be woken up and unref the message before we had a chance to revive it yet.
2015-02-17tests: bus: add unit test for async message deliveryTim-Philipp Müller1-0/+81
2015-02-17message, bus: fix async message deliveryTim-Philipp Müller3-7/+37
Async message delivery (where the posting thread gets blocked until the message has been processed and/or freed) was pretty much completely broken. For one, don't use GMutex implementation details to check whether a mutex has been initialized or not, esp. not implementation details that don't hold true any more with newer GLib versions where atomic ops and futexes are used (spotted by Josep Torras). This led to async message delivery no longer blocking with newer GLib versions on Linux. Secondly, after async delivery don't free mutex/GCond embedded inside the just-freed message structure. Use a new (private) mini object flag to signal GstMessage that the message being freed is part of an async delivery on the bus so that the dispose handler can keep the message alive and the bus can free it once it's done cleaning up stuff.
2015-02-16info: nicer buffer offset printing when offsets are not setTim-Philipp Müller1-4/+19
Print unset offsets as 'none' instead of humongous numbers, for better readability.
2015-02-16pad: Only initialize GValue to a type once, not on every retrySebastian Dröge1-1/+2
Otherwise we'll get warnings like this: cannot initialize GValue with type 'gboolean', the value has already been initialized as 'gboolean'
2015-02-15gstutils: check uri before using it in gst_pad_create_stream_id_internalMatthieu Bouron1-3/+5
If an element implements wrongly the URI query and set the uri to NULL and if the element calls gst_pad_create_stream_id at some point, it will lead to crash as the uri is not supposed to be NULL in the gst_pad_create_stream_id_internal function. https://bugzilla.gnome.org/show_bug.cgi?id=744520
2015-02-13timedvaluecontrolsource: Do not wrongly send value-removedThibault Saunier1-0/+3
And avoid freeing something we do not own
2015-02-13gst-uninstalled: Set GST_VALIDATE_PLUGIN_PATHThibault Saunier1-0/+1
2015-02-12basesrc: fix documentation and debug message after latency updatesThiago Santos1-4/+4
Changes docs and message according to latency handling fix
2015-02-12fdsrc: use g_ascii_strtoull() to convert size string in uriFrédéric Wang1-2/+4
sscanf() doesn't handle G_GUINT64_FORMAT well on mingw64 it appears, leading to compiler warnings. https://bugzilla.gnome.org/show_bug.cgi?id=744034
generated by cgit v1.2.3 (git 2.39.1) at 2024-11-23 08:19:12 +0000