jitter2 — Generates a segmented line with user-controllable random segments.
ktotamp -- Resulting amplitude of jitter2
kamp1 -- Amplitude of the first jitter component
kcps1 -- Speed of random variation of the first jitter component (expressed in cps)
kamp2 -- Amplitude of the second jitter component
kcps2 -- Speed of random variation of the second jitter component (expressed in cps)
kamp3 -- Amplitude of the third jitter component
kcps3 -- Speed of random variation of the third jitter component (expressed in cps)
jitter2 also generates a segmented line such as jitter, but in this case the result is similar to the sum of three randi opcodes, each one with a different amplitude and frequency value (see randi for more details), that can be varied at k-rate. Different effects can be obtained by varying the input arguments.
jitter2 can be used to make more natural and “analog-sounding” some static, dull sound. For best results, it is suggested to keep its amplitude moderate.
Here is an example of the jitter2 opcode. It uses the file jitter2.csd.
Example 414. Example of the jitter2 opcode.
See the sections Real-time Audio and Command Line Flags for more information on using command line flags.
<CsoundSynthesizer> <CsOptions> ; Select audio/midi flags here according to platform -odac ;;;realtime audio out ;-iadc ;;;uncomment -iadc if realtime audio input is needed too ; For Non-realtime ouput leave only the line below: ; -o jitter2.wav -W ;;; for file output any platform </CsOptions> <CsInstruments> sr = 44100 ksmps = 32 nchnls = 2 0dbfs = 1 instr 1 ktotamp init p4 kamp1 init .5 kcps1 init 10 kamp2 init .5 kcps2 init 2 kamp3 init .5 kcps3 init 3 kj2 jitter2 ktotamp, kamp1, kcps1, kamp2, kcps2, kamp3, kcps3 aout pluck 1, 200+kj2, 1000, 0, 1 aout dcblock aout outs aout, aout endin </CsInstruments> <CsScore> i 1 0 15 2 ;a bit jitter i 1 8 15 10 ;some more i 1 16 15 20 ;lots more e </CsScore> </CsoundSynthesizer>