+2006-10-28 Tim-Philipp Müller <tim at centricular dot net>
+
+ Patch by: Kjartan Maraas <kmaraas at gnome org>
+
+ * docs/design/part-MT-refcounting.txt:
+ * docs/random/wtay/capsnego2-docs:
+ * gst/gstclock.c:
+ * gst/gstxml.c:
+ Typo fixes (#366212).
+
2006-10-28 Wim Taymans <wim@fluendo.com>
Patch by: Sergey Scobich <sergey dot scobich at gmail dot com>
(gst_base_sink_get_position_last),
(gst_base_sink_get_position_paused), (gst_base_sink_change_state):
Convert and store timestamps in stream time and running time, the
- raw timestamps are not usefull, also document this better.
+ raw timestamps are not useful, also document this better.
Use different window sizes for good and bad QoS observations so
we react to badness a little quicker.
Keep track of the amount of rendered and dropped buffers.
* gst/gstobject.c: (gst_object_has_ancestor):
* gst/gstobject.h:
gst_object_has_ancestor() copied from gstbin.c as it is a
- usefull function.
+ useful function.
* tests/instantiate/create.c: (create_all_elements):
* tests/lat.c: (handoff_src), (handoff_sink):
taking a _ref() before adding it to the bin. The reason being that after the
_bin_add() call disposing the bin also destroys the element.
- Taking ownership of an object happens trough the process of "sinking" the
+ Taking ownership of an object happens through the process of "sinking" the
object. the _sink() method on an object will decrease the refcount of the
object if the FLOATING flag is set. The act of taking ownership of an object
is then performed as a _ref() followed by a _sink() call on the object.
When two pads are connected get_caps is called on both pads to get their caps.
Then the intersection between those caps is made, this will give us all the
-possible media types that can flow trough this pad connection. Optionally the
+possible media types that can flow through this pad connection. Optionally the
application can provide additional caps, the pad intersection is also made with
the application caps.
* slaved to another #GstClock with the gst_clock_set_master(). The clock will
* then automatically be synchronized to this master clock by repeadedly
* sampling the master clock and the slave clock and recalibrating the slave
- * clock with gst_clock_set_calibration(). This feature is mostly usefull for
+ * clock with gst_clock_set_calibration(). This feature is mostly useful for
* plugins that have an internal clock but must operate with another clock
* selected by the #GstPipeline. They can track the offset and rate difference
* of their internal clock relative to the master clock by using the
/**
* gst_xml_get_element:
* @xml: The GstXML to get the element from
- * @name: The name of element to retreive
+ * @name: The name of element to retrieve
*
* This function is used to get a pointer to the GstElement corresponding
* to name in the pipeline description. You would use this if you have