p-fields:
/* TVSPECTACLE - FFT-based delay processor with time-varying properties p0 = output start time p1 = input start time p2 = input duration p3 = amplitude multiplier p4 = ring-down duration p5 = FFT length (power of 2, usually 1024) p6 = window length (power of 2, usually FFT length * 2) p7 = window type (0: Hamming; see below for others) p8 = overlap - how much FFT windows overlap (any power of 2) 1: no overlap, 2: hopsize=FFTlen/2, 4: hopsize=FFTlen/4, etc. 2 or 4 is usually fine; 1 is fluttery; the higher the more CPU time p9 = wet/dry mix (0: dry -> 1: wet) [optional, default is 1] p10 = input channel [optional, default is 0] p11 = percent to left channel [optional, default is .5] The following function tables control amplitude. Function table 1 is the input amplitude, spanning just the input duration. Function table 2 is the output amplitude, spanning the entire note, including ring-down duration. The following function tables control EQ, delay time, and delay feedback for all the frequency bands of the FFT. Think of them as curves on a graph with frequency on the x axis and amplitude, delay time or feedback on the y axis. Function table 3 is EQ table A (i.e., amplitude scaling of each band), in dB (0 dB means no change, + dB boost, - dB cut). Function table 4 is delay time table A. Function table 5 is delay feedback table A. Values > 1 are dangerous! Function table 6 is EQ table B. Function table 7 is delay time table B. Function table 8 is delay feedback table B. These tables control the movement between the A and B tables described above. The values should be in the range [0, 1]; if not, the instrument prints a warning and pins the values to that range. A value of 0 means to read only from table A; a value of 1, from table B; and values in between 0 and 1 request linear interpolation between the two tables. Function table 9 describes the curve between EQ tables A and B. Function table 10 describes the curve between delay time tables A and B. Function table 11 describes the curve between delay feedback tables A and B. NOTES: p7 - window type: 0: Hamming, 1: Hanning, 2: Rectangle, 3: Triangle, 4: Blackman, 5: Kaiser When in doubt, use Hamming. p8 - overlap: 1: no overlap, 2: hopsize=FFTlen/2, 4: hopsize=FFTlen/4, etc. 2 or 4 is usually fine; 1 is fluttery; higher overlaps use more CPU. Also possible to use negative powers of 2, e.g., .5, .25, .125, etc. This leaves a gap between successive FFTs, creating ugly robotic effects -- beware of clipping. p9 - wet/dry mix: This is pre-EQ. */No sample scorefiles that I could find... sorry!