The Ppar pattern allows you to merge multiple event streams to play in parallel.
Ppar is a ListPattern and so like most ListPatterns it takes two arguments, a list of event patterns to play in parallel and a repeats count.
Ppar's child patterns must be event patterns. Using value patterns in a Ppar is an error because value patterns contain no duration data.
A Ppar is done when all of its subpatterns are done.
The Ppar pattern starts all of its subpatterns at the same time.
A Ptpar pattern includes a start time parameter before each subpattern which allow the subpatterns to be started at some time delay within the pattern. The start time is given in beats.
The time arguments are sent the
value message when the Ptpar pattern is started, so you may use functions to specify the times.
FilterPatterns take an existing pattern and apply some modification to its properties.
There is a simpler way to write the modal transposition example given in part 5. In fact the earlier examples are setting the values of
ctranspose which is not the best way to change those variables, because it wipes out any modifications to them by parent patterns. It is better to take the current value of those properties and add a value to them.
The Padd filter takes the current value of a property and adds a value to it.
In order to process duration correctly Pstretch should be used.
In fact there is an even shorter version of the modal transposition example. Paddp reads one pattern to get values for adding to a property and plays the second pattern once through modified with each new value.
Another example using Paddp:
Pbindf is like Pbind except that it merges all the bound symbols into events that it gets from a subpattern. It takes the same initial arguments in pairs as Pbind does, with an additional pattern to be modified as the last argument.
Patterns can be used as the arguments to Pbindf.
To go to the next file: Understanding Streams, Patterns and Events - Part 7