From 3751bda630c6c8c7605ebf77e86744689a0a6bfe Mon Sep 17 00:00:00 2001 From: kevin Date: Thu, 12 Dec 2013 12:12:17 -0500 Subject: [PATCH] notes.txt : Added note on cross fade parameter order and timing. --- doc/notes.txt | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/doc/notes.txt b/doc/notes.txt index 23976a7..f57c802 100644 --- a/doc/notes.txt +++ b/doc/notes.txt @@ -60,6 +60,19 @@ LA Secs - Fragment recd/play unit look-ahead time in seconds. Fade DbpSec - Framgent recd/play unit fade out time (time to fade to 0 following a fade msg) +*** Cross-fade Notes +Cross-fades are initiated by sending any msg to the 'AvailCh.trig' input. +The 'AvailCh' object then toggles the parameter router channels and xfader gates. +Only after this should the new parameter values be transmitted either from +the 'ActiveMeas' object (through the scale range chains) or directly from the +'ScMod' object. + +Sending parameter values prior to triggering the 'AvailCh' will result in the +parameters being sent to the currently active 'Kr'. This will result in two +possibly unintended effects: +1) The effect of the parameter will be heard immediately - possibly resulting in distortion. +2) If a subsequent trigger is sent to 'AvailCh' the parameters will be routed to + the fade-out (current) channel rather than the fade-in (next) channel. **** Live Test Score