- Jun 07, 2015
-
-
Sebastian Dröge authored
-
Sebastian Dröge authored
-
Sebastian Dröge authored
-
Sebastian Dröge authored
-
Sebastian Dröge authored
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 authored
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.
-
- Jun 06, 2015
-
-
Sebastian Dröge authored
-
Sebastian Dröge authored
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 authored
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 authored
Apparently I failed at git add -i.
-
Sebastian Dröge authored
Bindings will like this, and also it fixes a FIXME comment.
-
Sebastian Dröge authored
-
Sebastian Dröge authored
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 authored
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 authored
-
- Jun 05, 2015
-
-
Tim-Philipp Müller authored
deep-notify::last-message seems to cause some problems, so disable for now. https://bugzilla.gnome.org/show_bug.cgi?id=681642
-
-
- Jun 04, 2015
-
-
Sebastian Dröge authored
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 authored
-
Sebastian Dröge authored
-
- Jun 03, 2015
-
-
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 authored
-
Luis de Bethencourt authored
To satisfy the buildslaves ignore permission errors in chown, chmod and setcap
-
Sebastian Dröge authored
Just #ifdef the code for now, this should be implemented around IOKit later instead of using ioctls.
-
Philippe Normand authored
To avoid race conditions where make would try to change ownership and permissions of the not-yet-installed ptp helper.
-
Sebastian Dröge authored
-
Wim Taymans authored
Don't put code between declarations. Fix use of uninitialized variables
-
Sebastian Dröge authored
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 authored
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 authored
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 authored
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 authored
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 authored
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 authored
Attempt to return a copy of the memory instead. https://bugzilla.gnome.org/show_bug.cgi?id=750172
-
Matthew Waters authored
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
-
- Jun 02, 2015
-
-
-
Jan Schmidt authored
-
Jan Schmidt authored
-
Edward Hervey authored
-