Nicolas Dufresne [Wed, 10 Jun 2015 18:17:01 +0000 (14:17 -0400)]
collectpads: Don't initially send an invalid DTS
Sending a possibly invalid DTS may confuse the muxers, which will
then think the DTS is going backward.
https://bugzilla.gnome.org/show_bug.cgi?id=740575
Nicolas Dufresne [Fri, 3 Apr 2015 21:54:50 +0000 (17:54 -0400)]
collectpads: Add negative DTS support
Make gst_collect_pads_clip_running_time() function also store the
signed DTS in the CollectData. This signed DTS value can be used by
muxers to properly handle streams where DTS can be negative initially.
https://bugzilla.gnome.org/show_bug.cgi?id=740575
Nicolas Dufresne [Fri, 12 Jun 2015 16:06:05 +0000 (12:06 -0400)]
clock: Add signed time utilities
Add utility to print signed value of time. This is useful to
trace running time values in gint64 or GstClockTimeDiff values.
Additionally, define GST_CLOCK_STIME_NONE to indicate an invalid
signed time value and validation macro. New macros are:
GST_CLOCK_STIME_NONE
GST_CLOCK_STIME_IS_VALID
GST_STIME_FORMAT
GST_STIME_ARGS
https://bugzilla.gnome.org/show_bug.cgi?id=740575
Thiago Santos [Wed, 10 Jun 2015 23:44:26 +0000 (20:44 -0300)]
message: add allow-none to gst_message_new_ function
No restriction for creating messages without a source
Tim-Philipp Müller [Fri, 12 Jun 2015 12:45:33 +0000 (13:45 +0100)]
win32: update .def file for new API
Lazar Claudiu [Wed, 27 May 2015 09:29:41 +0000 (12:29 +0300)]
controller: Added absolute direct control binding, example and test
Fixes: 740502
API: gst_direct_control_binding_new_absolute
Matthew Waters [Wed, 3 Jun 2015 14:03:16 +0000 (00:03 +1000)]
memory: provide a mem_map_full that takes the GstMapInfo
Follow up of
7130230ddb349d0ca7942abdba26b7558df055d1
Provide the memory implementation the GstMapInfo that will be used to
map/unmap the memory. This allows the memory implementation to use
some scratch space in GstMapInfo to e.g. track different map/unmap
behaviour or store extra implementation defined data about the map
in use.
https://bugzilla.gnome.org/show_bug.cgi?id=750319
Alison Chaiken [Wed, 8 Apr 2015 21:21:43 +0000 (14:21 -0700)]
docs: manual: fix name reversal in basics-pads
https://bugzilla.gnome.org/show_bug.cgi?id=747532
Tim-Philipp Müller [Thu, 11 Jun 2015 22:06:26 +0000 (23:06 +0100)]
gst_writev: define UIO_MAXIOV on iOS/OSX
Apparently it's only seton iOS/OSX if defined(KERNEL).
Jan Schmidt [Thu, 11 Jun 2015 15:15:19 +0000 (01:15 +1000)]
gst_writev: Respect UIO_MAXIOV limit for the iov array
If we receive more than UIO_MAXIOV (1024 typically) buffers
in a single writev call, fall back to consolidating them
into one output buffer or multiple write calls.
This could be made more optimal, but let's wait until it's
ever a bottleneck for someone
Sebastian Dröge [Thu, 11 Jun 2015 10:34:04 +0000 (12:34 +0200)]
pipeline: Add gst_pipeline_set_latency(), getter and GObject property
This overrides the default latency handling and configures the specified
latency instead of the minimum latency that was returned from the LATENCY
query.
https://bugzilla.gnome.org/show_bug.cgi?id=750782
Carlos Rafael Giani [Thu, 11 Jun 2015 09:37:30 +0000 (11:37 +0200)]
concat: Add active-pad property
https://bugzilla.gnome.org/show_bug.cgi?id=746949
Sebastian Dröge [Thu, 11 Jun 2015 09:05:53 +0000 (11:05 +0200)]
concat: Also reset the current start offset when receiving a FLUSH_STOP on the srcpad
Sebastian Dröge [Thu, 11 Jun 2015 09:05:38 +0000 (11:05 +0200)]
concat: Add some newlines to event handling code to make the code look a bit less dense
Carlos Rafael Giani [Thu, 11 Jun 2015 08:53:30 +0000 (10:53 +0200)]
concat: Reset segment base offset after FLUSH_STOP with reset_time = TRUE
If the reset_time value of a FLUSH_STOP event is set to TRUE, the pipeline
will have the base_time of its elements reset. This means that the concat
element's current_start_offset has to be reset to 0, since it was
calculated with the old base-time in mind.
Only FLUSH_STOP events coming from the active pad are looked at.
Signed-off-by: Carlos Rafael Giani <dv@pseudoterminal.org>
Carlos Rafael Giani [Sat, 28 Mar 2015 15:46:32 +0000 (16:46 +0100)]
concat: Forward FLUSH_START and FLUSH_STOP events
Without this, seeking deadlocks if performed while the pipeline is paused.
Only flush events coming from the active pad are forwarded.
https://bugzilla.gnome.org/show_bug.cgi?id=745366
Stefan Sauer [Tue, 9 Jun 2015 12:28:30 +0000 (14:28 +0200)]
cruft: add the obsolete tmpl dir to cruft-dirs
Edward Hervey [Tue, 9 Jun 2015 09:30:10 +0000 (11:30 +0200)]
Automatic update of common submodule
From d9a3353 to 6015d26
Edward Hervey [Tue, 9 Jun 2015 09:01:53 +0000 (11:01 +0200)]
filesink: Fix fsync/_commit usage
_MSC_VER will only be defined when building *on* windows and not just
*for* windows. Instead, use the G_OS_WIN32 define
Sebastian Dröge [Tue, 9 Jun 2015 08:59:42 +0000 (10:59 +0200)]
ptp: Check for the actual API we use instead of just looking for __APPLE__
Should fix the build on FreeBSD, DragonFly and other BSDs.
https://bugzilla.gnome.org/show_bug.cgi?id=750530
Sebastian Dröge [Mon, 8 Jun 2015 15:10:56 +0000 (17:10 +0200)]
netclientclock: Use the new GST_CLOCK_FLAG_NEEDS_STARTUP_SYNC flag
https://bugzilla.gnome.org/show_bug.cgi?id=750574
Sebastian Dröge [Mon, 8 Jun 2015 15:04:55 +0000 (17:04 +0200)]
netclientclock: Make the clock a wrapper clock around an internal clock
The internal clock is only used for slaving against the remote clock, while
the user-facing GstClock can be additionally slaved to another clock if
desired. By default, if no master clock is set, this has exactly the same
behaviour as before. If a master clock is set (which was not allowed before),
the user-facing clock is reporting the remote clock as internal time and
slaves this to the master clock.
This also removes the weirdness that the internal time of the netclientclock
was always the system clock time, and not the remote clock time.
https://bugzilla.gnome.org/show_bug.cgi?id=750574
Stefan Sauer [Mon, 8 Jun 2015 21:07:40 +0000 (23:07 +0200)]
Automatic update of common submodule
From d37af32 to d9a3353
Tim-Philipp Müller [Mon, 8 Jun 2015 19:00:47 +0000 (20:00 +0100)]
tests: fakesink: fix string leak in unit test
Jan Schmidt [Mon, 8 Jun 2015 14:52:34 +0000 (00:52 +1000)]
filesink: Fix Windows build by using _commit instead of fsync.
Sebastian Dröge [Mon, 8 Jun 2015 10:22:56 +0000 (12:22 +0200)]
ptp: Make sure to always initialize the variables we put into the statistics structure later
CID 1304676, 1304677, 1304678, 1304679.
Sebastian Dröge [Mon, 8 Jun 2015 10:02:39 +0000 (12:02 +0200)]
ptp: Ensure that not too much is read from or written to struct ifreq.ifr_name
Jan Schmidt [Mon, 8 Jun 2015 09:33:03 +0000 (19:33 +1000)]
basetransform: Add Since markers for new vfuncs
Add Since: 1.6 markers for the new submit_input_buffer() and
generate_output() vfuncs
Jan Schmidt [Fri, 22 May 2015 15:08:29 +0000 (01:08 +1000)]
basetransform: Split input buffer processing from output generation
Allow for sub-classes which want to collate incoming buffers or
split them into multiple output buffers by separating the input
buffer submission from output buffer generation and allowing
for looping of one of the phases depending on pull or push mode
operation.
https://bugzilla.gnome.org/show_bug.cgi?id=750033
Jan Schmidt [Thu, 16 Apr 2015 00:32:02 +0000 (10:32 +1000)]
Add GST_BUFFER_FLAG_SYNC_AFTER flag, and implement in filesink.
Makes it possible to get filesink to fsync() after rendering
a buffer.
Руслан Ижбулатов [Mon, 8 Jun 2015 08:46:24 +0000 (10:46 +0200)]
ptp: Fix build on Windows, and in general the GI build when PTP support was not available
It's not going to work on Windows still, the helper process needs to be
ported.
Stefan Sauer [Sun, 7 Jun 2015 21:05:53 +0000 (23:05 +0200)]
Automatic update of common submodule
From 21ba2e5 to d37af32
Stefan Sauer [Sun, 7 Jun 2015 15:31:50 +0000 (17:31 +0200)]
Automatic update of common submodule
From c408583 to 21ba2e5
Stefan Sauer [Sun, 7 Jun 2015 14:58:40 +0000 (16:58 +0200)]
docs: remove variables that we define in the snippet from common
This is syncing our Makefile.am with upstream gtkdoc.
Stefan Sauer [Sun, 7 Jun 2015 15:16:06 +0000 (17:16 +0200)]
Automatic update of common submodule
From d676993 to c408583
Sebastian Dröge [Sun, 7 Jun 2015 14:44:26 +0000 (16:44 +0200)]
Back to development
Sebastian Dröge [Sun, 7 Jun 2015 08:52:33 +0000 (10:52 +0200)]
netclientclock: The NTP poll interval is a signed int8, not unsigned
Sebastian Dröge [Sun, 7 Jun 2015 07:41:28 +0000 (09:41 +0200)]
Release 1.5.1
Sebastian Dröge [Sun, 7 Jun 2015 07:33:52 +0000 (09:33 +0200)]
po: Update translations
Sebastian Dröge [Sun, 7 Jun 2015 07:32:39 +0000 (09:32 +0200)]
netclientclock: Add Since marker to the docs for gst_ntp_clock_new()
Sebastian Dröge [Sun, 7 Jun 2015 07:32:12 +0000 (09:32 +0200)]
Update .po files
Sebastian Dröge [Sun, 7 Jun 2015 07:08:35 +0000 (09:08 +0200)]
memory: Fix compiler warnings in unit test
gst/gstmemory.c:570:38: error: implicit conversion from enumeration type 'GstMapFlags' to different enumeration
type 'GstLockFlags' [-Werror,-Wenum-conversion]
fail_unless (gst_memory_lock (mem, GST_MAP_WRITE));
~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~
Sebastian Dröge [Sun, 7 Jun 2015 06:59:23 +0000 (08:59 +0200)]
ptpclock: Use the current path delay for calculation the local/remote clock times
The mean might currently be changing, and the current path delay is the
closest we can get to the actual delay around the current SYNC message.
Sebastian Dröge [Sat, 6 Jun 2015 21:05:32 +0000 (23:05 +0200)]
netclientclock: Add some copyright stuff
Sebastian Dröge [Sat, 6 Jun 2015 19:43:05 +0000 (21:43 +0200)]
netclientclock: Add NTPv4 support
This uses all of the netclientclock code, except for the generation and
parsing of packets. Unfortunately some code duplication was necessary
because GstNetTimePacket is public API and couldn't be extended easily
to support NTPv4 packets without breaking API/ABI.
Sebastian Dröge [Sat, 6 Jun 2015 18:39:47 +0000 (20:39 +0200)]
netclientclock: Preparation for NTPv4 support
We extend our calculations to work with local send time, remote receive time,
remote send time and local receive time. For the netclientclock protocol,
remote receive and send time are assumed to be the same value.
For the results, this modified calculation makes absolutely no difference
unless the two remote times are different.
Sebastian Dröge [Sat, 6 Jun 2015 17:01:06 +0000 (19:01 +0200)]
netclientclock. Fix last commit
Apparently I failed at git add -i.
Sebastian Dröge [Sat, 6 Jun 2015 16:42:18 +0000 (18:42 +0200)]
netclientclock: Make gst_net_client_clock_new() a thing wrapper around g_object_new()
Bindings will like this, and also it fixes a FIXME comment.
Sebastian Dröge [Sat, 6 Jun 2015 12:34:39 +0000 (14:34 +0200)]
ptpclock: Use #define everywhere instead of G_N_ELEMENTS()
Sebastian Dröge [Sat, 6 Jun 2015 12:31:16 +0000 (14:31 +0200)]
netclientclock: Filter RTTs based on the median of the last RTTs before considering them at all
This improves accuracy on wifi or similar networks, where the RTT can go very
high up for a single observation every now and then. Without filtering them
away completely, they would still still modify the average RTT, and thus all
clock estimations.
Sebastian Dröge [Sat, 6 Jun 2015 12:19:21 +0000 (14:19 +0200)]
ptpclock: Use a system clock for the time observations instead of gst_util_get_timestamp()
They don't necessarily use the same underlying clocks (e.g. on Windows), or
might be configured to a different clock type (monotonic vs. real time clock).
We need the values a clean system clock returns, as those are the values used
by the internal clocks.
Sebastian Dröge [Sat, 6 Jun 2015 10:35:58 +0000 (12:35 +0200)]
ptpclock: Fix documentation a bit
Tim-Philipp Müller [Fri, 5 Jun 2015 18:35:29 +0000 (19:35 +0100)]
tests: fakesink: test notify::last-message and deep-notify::last-message
deep-notify::last-message seems to cause some problems, so disable for now.
https://bugzilla.gnome.org/show_bug.cgi?id=681642
Sebastian Dröge [Fri, 5 Jun 2015 08:02:04 +0000 (10:02 +0200)]
typefind: Post an error if we can't typefind the data until EOS
https://bugzilla.gnome.org/show_bug.cgi?id=750439
Sebastian Dröge [Thu, 4 Jun 2015 17:05:44 +0000 (19:05 +0200)]
ptp-helper: Make sure to use g_poll() for the main context
The modified main context from https://bugzilla.gnome.org/show_bug.cgi?id=741054
somehow calls setugid(), which abort()s setuid root applications on OSX.
Sebastian Dröge [Thu, 4 Jun 2015 16:32:14 +0000 (18:32 +0200)]
ptp-helper: Make sure that we are running setuid root if configured that way
Sebastian Dröge [Thu, 4 Jun 2015 16:00:50 +0000 (18:00 +0200)]
ptp-helper: Fix interface listing and MAC retrieval on OSX
Vivia Nikolaidou [Wed, 3 Jun 2015 16:04:15 +0000 (19:04 +0300)]
gst-indent: Add support for gindent as executable name
gst-indent used to support gnuindent and indent as executable names.
However, on OSX one can "brew install gnu-indent" and then the
executable name will be gindent. Added support for that.
https://bugzilla.gnome.org/show_bug.cgi?id=750351
Luis de Bethencourt [Wed, 3 Jun 2015 15:42:57 +0000 (16:42 +0100)]
gitignore: add libs/gst/helpers/gst-ptp-helper
Luis de Bethencourt [Wed, 3 Jun 2015 15:34:58 +0000 (16:34 +0100)]
ptp: ignore permission errors in Makefile
To satisfy the buildslaves ignore permission errors in chown, chmod and setcap
Sebastian Dröge [Wed, 3 Jun 2015 15:06:09 +0000 (17:06 +0200)]
ptp: Don't use SIOCGIFHWADDR on Apple
Just #ifdef the code for now, this should be implemented around
IOKit later instead of using ioctls.
Philippe Normand [Wed, 3 Jun 2015 14:28:44 +0000 (16:28 +0200)]
build: make install-exec-hooks depend on install-helpersPROGRAMS
To avoid race conditions where make would try to change ownership and
permissions of the not-yet-installed ptp helper.
Sebastian Dröge [Wed, 3 Jun 2015 14:08:43 +0000 (16:08 +0200)]
ptp: Fix debug output to print the difference instead of absolute values
Wim Taymans [Wed, 3 Jun 2015 13:22:31 +0000 (15:22 +0200)]
ptpclock: fix compilation
Don't put code between declarations.
Fix use of uninitialized variables
Sebastian Dröge [Wed, 3 Jun 2015 09:04:48 +0000 (11:04 +0200)]
ptp: Add median based pre-filtering of delays
If the delay measurement is too far away from the median of the window of last
delay measurements, we discard it. This increases accuracy on wifi a lot.
https://bugzilla.gnome.org/show_bug.cgi?id=749391
Sebastian Dröge [Tue, 2 Jun 2015 13:24:06 +0000 (15:24 +0200)]
ptp: Add #define to only use SYNC messages for which we can send DELAY_REQ
https://bugzilla.gnome.org/show_bug.cgi?id=749391
Sebastian Dröge [Fri, 15 May 2015 13:58:51 +0000 (16:58 +0300)]
ptp: Add #defines to enable/disable improvements for unreliable networks
We should do some more measurements with all these and check how much sense
they make for PTP. Also enabling them means not following IEEE1588-2008 by the
letter anymore.
https://bugzilla.gnome.org/show_bug.cgi?id=749391
Sebastian Dröge [Thu, 14 May 2015 10:18:25 +0000 (12:18 +0200)]
ptp: Initial implementation of a PTP clock
GstPtpClock implements a PTP (IEEE1588:2008) ordinary clock in
slave-only mode, that allows a GStreamer pipeline to synchronize
to a PTP network clock in some specific domain.
The PTP subsystem can be initialized with gst_ptp_init(), which then
starts a helper process to do the actual communication via the PTP
ports. This is required as PTP listens on ports < 1024 and thus
requires special privileges. Once this helper process is started, the
main process will synchronize to all PTP domains that are detected on
the selected interfaces.
gst_ptp_clock_new() then allows to create a GstClock that provides the
PTP time from a master clock inside a specific PTP domain. This clock
will only return valid timestamps once the timestamps in the PTP domain
are known. To check this, the GstPtpClock::internal-clock property and
the related notify::clock signal can be used. Once the internal clock
is not NULL, the PTP domain's time is known. Alternatively you can wait
for this with gst_ptp_clock_wait_ready().
To gather statistics about the PTP clock synchronization,
gst_ptp_statistics_callback_add() can be used. This gives the
application the possibility to collect all kinds of statistics
from the clock synchronization.
https://bugzilla.gnome.org/show_bug.cgi?id=749391
Sebastian Dröge [Wed, 3 Jun 2015 11:16:15 +0000 (13:16 +0200)]
clock: Add GST_CLOCK_FLAG_NEEDS_STARTUP_SYNC and related API
gst_clock_wait_for_sync(), gst_clock_is_synced() and gst_clock_set_synced()
plus a signal to asynchronously wait for the clock to be synced.
This can be used by clocks to signal that they need initial synchronization
before they can report any time, and that this synchronization can also get
completely lost at some point. Network clocks, like the GStreamer
netclientclock, NTP or PTP clocks are examples for clocks where this is useful
to have as they can't report any time at all before they're synced.
https://bugzilla.gnome.org/show_bug.cgi?id=749391
Matthew Waters [Wed, 3 Jun 2015 08:03:36 +0000 (18:03 +1000)]
memory: provide a mem_unmap function that takes the flags to unmap
There are gstmemory's available that operate in two memory domains
and need to ensure consistent access between these domains.
Imagine a scenario where e.g. the GLMemory is mapped twice in both
the GPU and the CPU domain. On unmap or a subsequent map, it would
like to ensure that the most recent data is available in the memory
domain requested. Either by flushing the writes and/or initiating a
DMA transfer. Without knowing which domain is being unmapped, the
memory does not know where the most recent data is to transfer to
the other memory domain.
Note: this still does not allow downgrading a memory map.
https://bugzilla.gnome.org/show_bug.cgi?id=750319
Matthew Waters [Tue, 2 Jun 2015 06:14:50 +0000 (16:14 +1000)]
memory: gst_memory_share may fail to exclusively lock the parent memory
Now that locking exclusively dows not always succeed, we need to signal
the failure case from gst_memory_init.
Rather than introducing an API or funcionality change to gst_memory_init,
workaround by checking exclusivity in the calling code.
https://bugzilla.gnome.org/show_bug.cgi?id=750172
Matthew Waters [Mon, 1 Jun 2015 14:23:37 +0000 (00:23 +1000)]
buffer: locking memory exclusively may fail
Attempt to return a copy of the memory instead.
https://bugzilla.gnome.org/show_bug.cgi?id=750172
Matthew Waters [Sun, 31 May 2015 11:25:23 +0000 (21:25 +1000)]
miniobject: disallow a double write/exclusive lock
gst_memory_lock (mem, WRITE | EXCLUSIVE);
gst_memory_lock (mem, WRITE | EXCLUSIVE);
Succeeds when the part-miniobject.txt design doc suggests that this should fail:
"A gst_mini_object_lock() can fail when a WRITE lock is requested and
the exclusive counter is > 1. Indeed a GstMiniObject object with an
exclusive counter 1 is locked EXCLUSIVELY by at least 2 objects and is
therefore not writable."
https://bugzilla.gnome.org/show_bug.cgi?id=750172
Tim-Philipp Müller [Tue, 2 Jun 2015 19:32:35 +0000 (20:32 +0100)]
uri: match return type of get_uri_type() implementation to declaration
https://bugzilla.gnome.org/show_bug.cgi?id=750292
Jan Schmidt [Tue, 2 Jun 2015 14:12:36 +0000 (00:12 +1000)]
gstbuffer: Add a note about metas needing to be copied last
Jan Schmidt [Wed, 27 May 2015 12:23:00 +0000 (22:23 +1000)]
gstvalue: Implement gst_value_is_subset() for flagsets
Edward Hervey [Tue, 2 Jun 2015 14:33:48 +0000 (16:33 +0200)]
check: Use GST_CHECK_MAIN macro
eunhae choi [Wed, 20 May 2015 12:18:08 +0000 (21:18 +0900)]
downloadbuffer: release lock before posting msg
to avoid the deadlock in playbin2,
send msg after release the download buffer lock.
https://bugzilla.gnome.org/show_bug.cgi?id=749535
Reynaldo H. Verdejo Pinochet [Sun, 31 May 2015 23:21:42 +0000 (20:21 -0300)]
structure: add note about missing field creation on _set()
Tim-Philipp Müller [Sat, 30 May 2015 12:01:09 +0000 (13:01 +0100)]
tests: fix some leaks in new flagset checks
Tim-Philipp Müller [Sat, 30 May 2015 11:39:19 +0000 (12:39 +0100)]
queuearray: remove duplicate assignment
We've already done this earlier in the function,
and nothing has changed since we first read it.
Nirbheek Chauhan [Wed, 27 May 2015 11:52:28 +0000 (17:22 +0530)]
gst/gst.c: Add a warning about DllMain to prevent misuse
DllMain should not be relied on for anything except storing the DLL handle.
It should also not be defined for static builds, but doing so is not
straightforward and is mostly harmless, so let's just add a comment about that
for now.
Sebastian Dröge [Wed, 27 May 2015 11:54:25 +0000 (13:54 +0200)]
funnel: Improve debug output a bit
Luis de Bethencourt [Tue, 26 May 2015 13:46:16 +0000 (14:46 +0100)]
docs: fix typo in draft-klass.txt
Luis de Bethencourt [Tue, 26 May 2015 13:03:25 +0000 (14:03 +0100)]
code-reviews: remove obsolete code reviews
This obsolete folder hasn't been touched since 2001 and has no purpose. It
confuses new developers.
Matthew Waters [Mon, 25 May 2015 11:02:28 +0000 (21:02 +1000)]
basesink: use the slightly more correct take_sample for last-sample
gst_value_take_buffer() and gst_value_take_sample() both resolve to
g_value_take_boxed(). Use the method with the correct name if we
ever change that.
Jan Schmidt [Mon, 25 May 2015 06:23:33 +0000 (16:23 +1000)]
gstvalue: Add GstFlagSet type
GstFlagSet is a new type designed for negotiating sets
of boolean capabilities flags, consisting of a 32-bit
flags bitfield and 32-bit mask field. The mask field
indicates which of the flags bits an element needs to have
as specific values, and which it doesn't care about.
This allows efficient negotiation of arrays of boolean
capabilities.
The standard serialisation format is FLAGS:MASK, with
flags and mask fields expressed in hexadecimal, however
GstFlagSet has a gst_register_flagset() function, which
associates a new GstFlagSet derived type with an existing
GFlags gtype. When serializing a GstFlagSet with an
associated set of GFlags, it also serializes a human-readable
form of the flags for easier debugging.
It is possible to parse a GFlags style serialisation of a
flagset, without the hex portion on the front. ie,
+flag1/flag2/flag3+flag4, to indicate that
flag1 & flag4 must be set, and flag2/flag3 must be unset,
and any other flags are don't-care.
https://bugzilla.gnome.org/show_bug.cgi?id=746373
Thibault Saunier [Wed, 20 May 2015 18:19:29 +0000 (20:19 +0200)]
gstvalue: Add a comparision function for GstStructures
Tim-Philipp Müller [Tue, 19 May 2015 13:34:04 +0000 (14:34 +0100)]
net: keep GCancellable fd around instead of re-creating it constantly
Just create the cancellable fd once and keep it around instead
of creating/closing it for every single packet. Since we spend
most time waiting for packets, an fd is alloced and in use pretty
much all the time anyway.
Tim-Philipp Müller [Mon, 18 May 2015 11:52:00 +0000 (12:52 +0100)]
Revert "doc: Workaround gtkdoc issue"
This reverts commit
460a7bf68292d057c77e84d1ea86b8e73fc081f3.
This should be fixed by the gtk-doc 1.23 release.
<para> cannot contain <refsect2>:
http://www.docbook.org/tdg/en/html/para.html
http://www.docbook.org/tdg/en/html/refsect2.html
Wim Taymans [Mon, 11 May 2015 08:52:23 +0000 (10:52 +0200)]
sparsefile: small cleanup
The error path unrefs file->file so make sure we only go there when
there is a non-NULL file->file.
Nicolas Dufresne [Sun, 17 May 2015 03:29:03 +0000 (23:29 -0400)]
doc: Workaround gtkdoc issue
With gtkdoc 1.22, the XML generator fails when a itemizedlist is
followed by a refsect2. Workaround the issue by wrapping the refsect2
into para.
Reynaldo H. Verdejo Pinochet [Wed, 13 May 2015 16:28:05 +0000 (13:28 -0300)]
docs/design/part-negotiation.txt: minor corrections
Thibault Saunier [Sat, 16 May 2015 10:57:12 +0000 (12:57 +0200)]
timedvaluecontrolsource: Check that the only iter is the end iter in the GSequence
Previous patch was assuming that if the returned iter was the last iter
the GSequence was empty, which is obviously wrong.
Thibault Saunier [Sat, 16 May 2015 09:17:40 +0000 (11:17 +0200)]
timedvaluecontrolsource: Fix removing all keyframes, and adding one back
We were segfaulting because g_sequence_search was returning the iter_end,
and that iterator does not contain anything and thus should not be used
directly
Tim-Philipp Müller [Fri, 15 May 2015 19:44:08 +0000 (20:44 +0100)]
fakesrc: fix property description
We're enterprise now folks.
Vincent Penquerc'h [Fri, 15 May 2015 13:57:14 +0000 (14:57 +0100)]
pad: bump chain function call logs from LOG to DEBUG
They're really useful compared to other LOG stuff in there, so
there is value is including them and not the rest.
Stefan Sauer [Fri, 15 May 2015 11:43:12 +0000 (13:43 +0200)]
gstobject: add gst_object_has_as_ancestor and deprecate previous function
The old gst_object_has_ancestor will call the new code. This establishes the
symetry with the new gst_object_has_as_parent.
API: gst_object_has_as_ancestor()
Stefan Sauer [Fri, 15 May 2015 06:05:50 +0000 (08:05 +0200)]
gstobject: rename gst_object_has_parent to gst_object_has_as_parent
This avoid confusion with a potential punction that check if a gstobject has-a
parent.
API: gst_object_has_as_parent()
Jian [Thu, 14 May 2015 07:49:43 +0000 (15:49 +0800)]
basesink: Fix QoS/lateness checking if subclass implements prepare/prepare_list vfuncs
In basesink functions gst_base_sink_chain_unlocked(), below code is used to
checking if buffer is late before doing prepare call to save some effort:
if (syncable && do_sync)
late =
gst_base_sink_is_too_late (basesink, obj, rstart, rstop,
GST_CLOCK_EARLY, 0, FALSE);
if (G_UNLIKELY (late))
goto dropped;
But this code has problem, it should calculate jitter based on current media
clock, rather than just passing 0. I found it will drop all the frames when
rewind in slow speed, such as -2X.
https://bugzilla.gnome.org/show_bug.cgi?id=749258