cml/kc
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

notes.txt : Added note on cross fade parameter order and timing.

Browse Source
This commit is contained in:
kevin 2013-12-12 12:12:17 -05:00
parent 84f5efccef
commit 3751bda630
1 changed files with 13 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
doc/notes.txt
View File

@ -60,6 +60,19 @@ LA Secs - Fragment recd/play unit look-ahead time in seconds.
Fade DbpSec - Framgent recd/play unit fade out time Fade DbpSec - Framgent recd/play unit fade out time
(time to fade to 0 following a fade msg) (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 **** Live Test Score