X-Git-Url: http://research.m1stereo.tv/gitweb?a=blobdiff_plain;f=docs%2Fwestley.txt;h=2d5e29196ee016d3571c52af6cde6e498ca6d040;hb=3b9de6081136b2a28bf7a6f85354ec04d92065bb;hp=3984083f0a8bd865585d984e37d10d1770eb6640;hpb=4ee4b9829c53db721194a1983ab5c5054ba766c9;p=melted
diff --git a/docs/westley.txt b/docs/westley.txt
index 3984083..2d5e291 100644
--- a/docs/westley.txt
+++ b/docs/westley.txt
@@ -125,7 +125,6 @@ Playlists:
Interlude - Introducing Multitracks:
-
So far we've defined basic producers and playlists/tracks - the tractor is
the element that allows us to arrange our tracks and specify filters and
transitions. Similarly to a playlist, a tractor is a container.
@@ -280,3 +279,182 @@ Tractors:
placed between all producers and the consumer).
TODO: transition example
+
+
+Flexibility:
+
+ The information presented above is considered the MLT Westley "normal"
+ form. This is the output generated by the westley consumer, for example,
+ when used with inigo. It is the output generated when you use the
+ "Westley to File" consumer in the demo script, which beginners will find
+ most useful for learning to use westley XML. This section describes
+ alternative forms the westley producer accepts.
+
+ First of all, the normal form is more of a linear format with producers
+ and playlists defined prior to their usage in a multitrack. Westley
+ also accepts a hierarchical format with producers as children of tracks
+ or playlist entries and with playlists as children of tracks:
+
+
+
+
+
+
+
+
+
+ Obviously, this example is meant to demonstrate hierarchy and not effective
+ use of playlist or multitrack!
+
+ Secondly, as part of error handling, westley is forgiving if you fail to
+ supply ,