From 9dbf52bedba68d15738565109026240bbd7f2752 Mon Sep 17 00:00:00 2001 From: Bernhard Wagner Date: Thu, 16 Feb 2023 15:20:26 +0100 Subject: [PATCH] ADDS: Continuation to Pattern Alignment --- website/src/pages/technical-manual/patterns.mdx | 2 ++ 1 file changed, 2 insertions(+) diff --git a/website/src/pages/technical-manual/patterns.mdx b/website/src/pages/technical-manual/patterns.mdx index 8ea41a86..45664ad7 100644 --- a/website/src/pages/technical-manual/patterns.mdx +++ b/website/src/pages/technical-manual/patterns.mdx @@ -37,3 +37,5 @@ Each event has a value, a begin time and an end time, where time is represented Note that the query function is not just a way to access a pattern, but true to the principles of functional programming, is the pattern itself. This means that in theory there is no way to change a pattern, it is opaque as a pure function. In practice though, Strudel and Tidal are all about transforming patterns, so how is this done? The answer is, by replacing the pattern with a new one, that calls the old one. This new one is only able to manipulate the query before passing it to the old pattern, and manipulate the results from it before returning them to caller. But, this is enough to support all the temporal and structural manipulations provided by Strudel (and Tidal's) extensive library of functions. The above examples do not represent how Strudel is used in practice. In the live coding editor, the user only has to type in the pattern itself, the querying will be handled by the scheduler. The scheduler will repeatedly query the pattern for events, which are then scheduled as sound synthesis or other event triggers. + +Can we [align](/technical-manual/alignment) patterns?