docs: small docs updates

diff --git a/docs/design/part-qos.txt b/docs/design/part-qos.txt
index 2ab58a0..9aa67b3 100644 (file)
--- a/docs/design/part-qos.txt
+++ b/docs/design/part-qos.txt
@@ -54,11 +54,14 @@ QoS message
 -----------
 
 Whenever QoS discards a piece of data or affects the quality of the stream, a
-message must be posted by the element that performed the QoS. 
+message must be posted by the element that performed the QoS.  We assume that
+the time gained by dropping the data outweighs the time spend in creating and
+posting the QoS message so that posting the message should not cause more
+performance problems.
 
 This message can be posted by a sink/src that performs synchronisation against the
 clock or it could be dropped by an upstream element that performs QoS because of
-QOS events received from downstream.
+QOS events received from a downstream element.
 
  - live: G_TYPE_BOOLEAN:
       If the QoS message was dropped by a live element such as a sink or a live
@@ -72,7 +75,7 @@ QOS events received from downstream.
       The lateness of the buffer. 
 
  - proportion, G_TYPE_DOUBLE:
-      Long term prediction of the ideal rate.
+      Long term prediction of the ideal rate. 
 
 Optional stats:
 

diff --git a/docs/design/part-seeking.txt b/docs/design/part-seeking.txt
index 6a0f2d4..31c48aa 100644 (file)
--- a/docs/design/part-seeking.txt
+++ b/docs/design/part-seeking.txt
@@ -2,9 +2,9 @@ Seeking
 -------
 
 Seeking in GStreamer means configuring the pipeline for playback of the
-media between a certain start and stop time, called a segment. By default a
-pipeline will play from position 0 to the total duration of the media at a rate
-of 1.0.
+media between a certain start and stop time, called the playback segment.
+By default a pipeline will play from position 0 to the total duration of the
+media at a rate of 1.0.
 
 A seek is performed by sending a seek event to the sink elements of a
 pipeline. Sending the seek event to a bin will by default forward
@@ -13,7 +13,9 @@ the event to all sinks in the bin.
 When performing a seek, the start and stop values of the segment can be
 specified as absoulte positions or relative to the currently configured
 playback segment. Note that it is not possible to seek relative to the current
-playback position.
+playback position. To seek relative to the current playback position, one must
+query the position first and then perform an absolute seek to the desired
+position.
 
 Feedback of the seek operation can be immediatly using the GST_SEEK_FLAG_FLUSH
 flag. With this flag, all pending data in the pipeline is discarded and playback
@@ -55,6 +57,14 @@ are allowed to skip decoding. This can be useful when resource consumption is
 more important than accurately producing all frames.
 
 
+Seeking in push based elements
+------------------------------
+
+
+
+
+
+
 Generating seeking events
 -------------------------