docs/design/: Add doc about synchronisation

Original commit message from CVS:
* docs/design/Makefile.am:
* docs/design/part-synchronisation.txt:
Add doc about synchronisation
* docs/design/draft-latency.txt:
* docs/design/part-TODO.txt:
* docs/design/part-clocks.txt:
* docs/design/part-events.txt:
* docs/design/part-gstbus.txt:
* docs/design/part-gstpipeline.txt:
* docs/design/part-live-source.txt:
* docs/design/part-messages.txt:
* docs/design/part-overview.txt:
* docs/design/part-streams.txt:
* docs/design/part-trickmodes.txt:
Documentation updates.

1 files changed, 6 insertions, 3 deletions

diff --git a/docs/design/part-overview.txt b/docs/design/part-overview.txt
index 5e700a3583..0a3cf47db8 100644
--- a/docs/design/part-overview.txt
+++ b/docs/design/part-overview.txt
@@ -166,6 +166,7 @@ Pipeline
    - Manage running_time based on the selected clock. Running_time is the elapsed
      time the pipeline spent in the PLAYING state and is used for
      synchronisation.
+   - Manage latency in the pipeline.
    - Provide means for elements to comunicate with the application by the GstBus.
    - Manage the global state of the elements such as Errors and end-of-stream.
  
@@ -365,7 +366,8 @@ Pipeline states
 
  Before going to PLAYING, the pipeline select a clock and samples the current time of 
  the clock. This is the base_time. It then distributes this time to all elements. 
- Elements can then synchronize against the clock using the buffer timestamp+base time. 
+ Elements can then synchronize against the clock using the buffer running_time +
+ base_time (See also part-synchronisation.txt). 
 
  The following chain of state changes then takes place:
 
@@ -385,7 +387,7 @@ Pipeline status
 
  The bus is distributed to all elements added to the pipeline. The elements use the bus
  to post messages on. Various message types exist such as ERRORS, WARNINGS, EOS, 
- STATE_CHANGED,  etc..
+ STATE_CHANGED, etc..
 
  The pipeline handles EOS messages received from elements in a special way. It will
  only forward the message to the application when all sink elements have posted an
@@ -412,7 +414,8 @@ Pipeline EOS
  The EOS event will eventually arrive in the sink element. The sink will then post
  an EOS message on the bus to inform the pipeline that a particular stream has
  finished. When all sinks have reported EOS, the pipeline forwards the EOS message
- to the application. 
+ to the application. The EOS message is only forwarded to the application in the
+ PLAYING state.
 
  When in EOS, the pipeline remains in the PLAYING state, it is the applications
  responsability to PAUSE or READY the pipeline. The application can also issue