Browse Source

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

master
kevin 11 years ago
parent
commit
3751bda630
1 changed files with 13 additions and 0 deletions
  1. 13
    0
      doc/notes.txt

+ 13
- 0
doc/notes.txt View File

@@ -60,6 +60,19 @@ LA Secs  - Fragment recd/play unit look-ahead time in seconds.
60 60
 Fade DbpSec - Framgent recd/play unit fade out time 
61 61
               (time to fade to 0 following a fade msg)	
62 62
 
63
+*** Cross-fade Notes
64
+Cross-fades are initiated by sending any msg to the 'AvailCh.trig' input.
65
+The 'AvailCh' object then  toggles the parameter router channels and xfader gates.
66
+Only after this should the new parameter values be transmitted either from
67
+the 'ActiveMeas' object (through the scale range chains) or directly from the
68
+'ScMod' object.
69
+
70
+Sending parameter values prior to triggering the 'AvailCh' will result in the
71
+parameters being sent to the currently active 'Kr'. This will result in two
72
+possibly unintended effects: 
73
+1) The effect of the parameter will be heard immediately - possibly resulting in distortion.
74
+2) If a subsequent trigger is sent to 'AvailCh' the parameters will be routed to
75
+   the fade-out (current) channel rather than the fade-in (next) channel.
63 76
  
64 77
 
65 78
 ****  Live Test Score

Loading…
Cancel
Save