Examples
Here is an example of the A4 opcode. It uses the file A4.csd.
Example 34. Example of the A4 opcode.
See the sections Real-time Audio and Command Line Flags for more information on using command line flags.
See Also
+ +See also
- sr, - kr, - ksmps, - nchnls, - nchnls_i, - 0dbfs, - cpspch, - cpsoct, - cpsmidinn, - cps2pch, - cpsxpch. -
+ + Orchestra Header Statements + +Credits
diff --git a/ATSadd.html b/ATSadd.html index 92453abe61d..2dd88e325b7 100644 --- a/ATSadd.html +++ b/ATSadd.html @@ -38,20 +38,20 @@
Description
ATSadd reads from an ATS analysis file and uses the data to perform additive synthesis using an internal array of interpolating oscillators.
Syntax
ar ATSadd ktimepnt, kfmod, iatsfile, ifn, ipartials[, ipartialoffset, \
ipartialincr, igatefn]
Initialization
iatsfile – the ATS number (n in ats.n) or the name in quotes of the analysis file made using ATSA. @@ -69,7 +69,7 @@
Initialization
Performance
ktimepnt – The time pointer in seconds used to index the ATS file. Used for ATSadd exactly the same as for pvoc.
ATSadd and ATSaddnz are based on pvadd by Richard Karpen and use files created by Juan Pampin's ATS (Analysis - Transformation - Synthesis). @@ -80,7 +80,7 @@
Performance
Examples
ktime line 0, p3, 2.5 asig ATSadd ktime, 1, "clarinet.ats", 1, 20, 2 @@ -91,13 +91,13 @@Examples
Here is a complete example of the ATSadd opcode. It uses the file ATSadd.csd.- +Example 70. Example of the ATSadd opcode.
- +<CsoundSynthesizer> <CsOptions> @@ -147,13 +147,13 @@Examples
Here is another example of the ATSadd opcode. It uses the file ATSadd-2.csd.- +Example 71. Example 2 of the ATSadd opcode.
- +See also
-ATSread, - ATSreadnz, - ATSinfo, - ATSbufread, - ATScross, - ATSinterpread, - ATSpartialtap, - ATSaddnz, - ATSsinnoi
+- +Credits
diff --git a/ATSaddnz.html b/ATSaddnz.html index 97d616867e3..e781cd1f6f6 100644 --- a/ATSaddnz.html +++ b/ATSaddnz.html @@ -38,19 +38,19 @@
- +Description
ATSaddnz reads from an ATS analysis file and uses the data to perform additive synthesis using a modified randi function.
- +Initialization
iatsfile – the ATS number (n in ats.n) or the name in quotes of the analysis file made using ATSA. @@ -63,7 +63,7 @@
Initialization
- +Performance
ktimepnt – The time pointer in seconds used to index the ATS file. Used for ATSaddnz exactly the same as for pvoc and ATSadd.
ATSaddnz and ATSadd are based on pvadd by Richard Karpen and use files created by Juan Pampin's ATS (Analysis - Transformation - Synthesis). @@ -72,7 +72,7 @@
Performance
- +Examples
ktime line 0, p3, 2.5 asig ATSaddnz ktime, "clarinet.ats", 25 @@ -83,13 +83,13 @@Examples
Here is a complete example of the ATSaddnz opcode. It uses the file ATSaddnz.csd.- +Example 72. Example of the ATSaddnz opcode.
- +<CsoundSynthesizer> <CsOptions> @@ -109,18 +109,18 @@Examples
0dbfs = 1 ;ATSA wants a mono file! -ires system_i 1,{{ atsa beats.wav beats.ats }} ; default size +ires system_i 1,{{ atsa Mathews.wav Mathews.ats }} ; default options instr 1 ktime line 0, p3, p3 -asig ATSaddnz ktime, "beats.ats", 1, 4 ; only 1 noise band, the 4th noise band - outs asig*6, asig*6 ;amplify +asig ATSaddnz ktime, "Mathews.ats", 1, 4 ; only 1 noise band, the 4th noise band + outs asig*2, asig*2 ;amplify endin </CsInstruments> <CsScore> -i1 0 2 +i1 1 15.6 e </CsScore> </CsoundSynthesizer> @@ -134,13 +134,13 @@Examples
Here is another example of the ATSaddnz opcode. It uses the file ATSaddnz-2.csd.- +Example 73. Example 2 of the ATSaddnz opcode.
- +See also
-ATSread, - ATSreadnz, - ATSinfo, - ATSbufread, - ATScross, - ATSinterpread, - ATSpartialtap, - ATSaddnz, - ATSsinnoi
+- +Credits
diff --git a/ATSbufread.html b/ATSbufread.html index 09d5c3c7d2f..a6e3a11276b 100644 --- a/ATSbufread.html +++ b/ATSbufread.html @@ -38,20 +38,20 @@
- +Description
ATSbufread reads data from and ATS data file and stores it in an internal data table of frequency, amplitude pairs.
- +Initialization
iatsfile – the ATS number (n in ats.n) or the name in quotes of the analysis file made using ATSA. @@ -64,7 +64,7 @@
Initialization
- +Performance
ktimepnt – The time pointer in seconds used to index the ATS file. Used for ATSbufread exactly the same as for pvoc.
@@ -89,20 +89,20 @@
Performance
- +Examples
Here is an example of the ATSbufread opcode. It uses the file ATSbufread.csd.
- +Example 74. Example of the ATSbufread opcode.
- +<CsoundSynthesizer> <CsOptions> @@ -119,32 +119,34 @@Examples
nchnls = 2 0dbfs = 1 -; by Menno Knevel - 2021 +; by Menno Knevel - 2023 ;ATSA wants a mono file! ;it takes a while to analyze these files... ires1 system_i 1,{{ atsa finneganswake1.flac finneganswake.ats }} prints "\n***1st analyzed file is ready***\n\n" -ires2 system_i 1,{{ atsa beats.wav beats.ats }} +ires2 system_i 1,{{ atsa drumsMlp.wav drumsMlp.ats }} prints "\n***2nd analyzed file is ready***\n\n" instr 1 -ipr ATSinfo "finneganswake.ats", 3 ; get number of partials -prints "\n***number of partials = %d***\n\n", ipr +ires1 ATSinfo "finneganswake.ats", 3 ; get number of partials +ires2 ATSinfo "drumsMlp.ats", 3 ; get number of partials +prints "\n***number of partials of finneganswake.ats = %d***\n\n", ires1 +prints "\n***number of partials of drumsMlp.ats = %d***\n\n", ires2 ktime1 line 0, p3, 12.67 ktime2 line 0, p3, 2 kline line 0, p3, 1 ; cross from voice to the beats - ATSbufread ktime1, 1, "finneganswake.ats", ipr -aout ATScross ktime2, 1, "beats.ats", 1, kline, 1, ipr - outs aout*1.7, aout*1.7 + ATSbufread ktime1, 1, "finneganswake.ats", ires1 +aout ATScross ktime2, 1, "drumsMlp.ats", 1, kline, 1, ires2 + outs aout*2.5, aout*2.5 endin </CsInstruments> <CsScore> -; sine wave. -f 1 0 16384 10 1 +; sinoid wave. +f 1 0 16384 10 1 .3 .1 .5 i 1 0 12.7 e @@ -159,20 +161,16 @@Examples
See also the examples for ATScross, ATSinterpread and ATSpartialtap
- +See also
-ATSread, - ATSreadnz, - ATSinfo, - ATSsinnoi, - ATScross, - ATSinterpread, - ATSpartialtap, - ATSadd, - ATSaddnz
+- +Credits
diff --git a/ATScross.html b/ATScross.html index 8aa4ddccdb4..9bc56e8af0c 100644 --- a/ATScross.html +++ b/ATScross.html @@ -38,20 +38,20 @@
- +Description
ATScross uses data from an ATS analysis file and data from an ATSbufread to perform cross synthesis.
- +Syntax
ar ATScross ktimepnt, kfmod, iatsfile, ifn, kmylev, kbuflev, ipartials \ [, ipartialoffset, ipartialincr]- +Initialization
iatsfile – integer or character-string denoting a control-file derived from ATS analysis of an audio signal. An integer denotes the suffix of a file ATS.m; a character-string (in double quotes) gives a filename, optionally a full pathname. If not full-path, the file is sought first in the current directory, then in the one given by the environment variable SADIR (if defined). @@ -65,7 +65,7 @@
Initialization
- +Performance
ktimepnt – The time pointer in seconds used to index the ATS file. Used for ATScross exactly the same as for pvoc.
@@ -79,19 +79,19 @@
Performance
- +Examples
Here is an example of the ATScross opcode. It uses the file ATScross.csd.
- +Example 75. Example of the ATScross opcode.
- +<CsoundSynthesizer> <CsOptions> @@ -108,25 +108,28 @@Examples
nchnls = 2 0dbfs = 1 -; by Menno Knevel - 2021 +; by Menno Knevel - 2023 ;ATSA wants a mono file! ;it takes a while to analyze these files... ires1 system_i 1,{{ atsa finneganswake1.flac finneganswake.ats }} prints "\n***1st analyzed file is ready***\n\n" -ires2 system_i 1,{{ atsa beats.wav beats.ats }} + +ires2 system_i 1,{{ atsa drumsMlp.wav drumsMlp.ats }} prints "\n***2nd analyzed file is ready***\n\n" -instr 1 -ipr ATSinfo "finneganswake.ats", 3 ; get number of partials -prints "\n***number of partials = %d***\n\n", ipr +instr 1 +ires1 ATSinfo "finneganswake.ats", 3 ; get number of partials +ires2 ATSinfo "drumsMlp.ats", 3 ; get number of partials +prints "\n***number of partials of finneganswake.ats = %d***\n\n", ires1 +prints "\n***number of partials of drumsMlp.ats = %d***\n\n", ires2 ktime1 line 0, p3, 12.67 ktime2 line 0, p3, 2 kline line p4, p3, p5 - ATSbufread ktime1, 1, "finneganswake.ats", ipr -aout ATScross ktime2, 1, "beats.ats", 1, kline, 1, ipr ; cross from p4 to p5 - outs aout*1.7, aout*1.7 + ATSbufread ktime1, 1, "finneganswake.ats", ires1 +aout ATScross ktime2, 1, "drumsMlp.ats", 1, kline, 1, 68 ; cross from p4 to p5 + outs aout*2.5, aout*2.5 endin @@ -135,8 +138,8 @@Examples
; sine wave. f 1 0 16384 10 1 ; start end -i 1 0 12.7 0 1 ; voice --> beats -i 1 15 12.7 1 0 ; beats --> voice +i 1 0 12.7 0 1 ; voice --> drums +i 1 15 12.7 1 0 ; drums --> voice e </CsScore> </CsoundSynthesizer> @@ -148,20 +151,16 @@Examples
- +See also
-ATSread, - ATSreadnz, - ATSinfo, - ATSsinnoi, - ATSbufread, - ATSinterpread, - ATSpartialtap, - ATSadd, - ATSaddnz
+- +Credits
diff --git a/ATSinfo.html b/ATSinfo.html index ac3ec1d8038..2de238a0a0a 100644 --- a/ATSinfo.html +++ b/ATSinfo.html @@ -38,19 +38,19 @@
- +Initialization
iatsfile – the ATS number (n in ats.n) or the name in quotes of the analysis file made using ATSA. @@ -69,7 +69,7 @@
Initialization
8 - ATS file Type
- +Performance
Macros can really improve the legibility of your csound code, I have provided my Macro Definitions below:
@@ -86,19 +86,19 @@Performance
ATSinfo can be useful for writing generic instruments that will work with many ATS files, even if they have different lengths and different numbers of partials etc. Example 2 is a simple application of this.
- +Examples
Here is an example of the ATSinfo opcode. It uses the file ATSinfo.csd.
- +Example 76. Example of the ATSinfo opcode.
- +See also
-ATSread, - ATSreadnz, - ATSbufread, - ATScross, - ATSinterpread, - ATSpartialtap, - ATSadd, - ATSaddnz, - ATSsinnoi
+- +Credits
diff --git a/ATSinterpread.html b/ATSinterpread.html index 5790c9831e7..07a87a11dba 100644 --- a/ATSinterpread.html +++ b/ATSinterpread.html @@ -38,38 +38,38 @@
- +Performance
kfreq - a frequency value (given in Hertz) used by ATSinterpread as in index into the table produced by an ATSbufread.
ATSinterpread takes a frequency value (kfreq in Hz). This frequency is used to index the data of an ATSbufread. The return value is an amplitude gained from the ATSbufread after interpolation. ATSinterpread allows a user to determine the frequency envelope of any ATSbufread. This data could be useful for an number of reasons, one might be performing cross synthesis of data from an ATS file and non ATS data.
- +Examples
Here is an example of the ATSinterpread opcode. It uses the file ATSinterpread.csd.
- +Example 77. Example of the ATSinterpread opcode.
- +See also
-ATSread, - ATSreadnz, - ATSinfo, - ATSsinnoi, - ATSbufread, - ATScross, - ATSpartialtap, - ATSadd, - ATSaddnz
+- +Credits
diff --git a/ATSpartialtap.html b/ATSpartialtap.html index 11b6394233a..4111a922f43 100644 --- a/ATSpartialtap.html +++ b/ATSpartialtap.html @@ -38,46 +38,46 @@
- +Description
ATSpartialtap takes a partial number and returns a frequency, amplitude pair. The frequency and amplitude data comes from an ATSbufread opcode.
- +Initialization
ipartialnum - indicates the partial that the ATSpartialtap opcode should read from an ATSbufread.
- +Performance
kfrq - returns the frequency value for the requested partial.
kamp - returns the amplitude value for the requested partial.
ATSpartialtap takes a partial number and returns a frequency, amplitude pair. The frequency and amplitude data comes from an ATSbufread opcode. This is more restricted version of ATSread, since each ATSread opcode has its own independent time pointer, and ATSpartialtap is restricted to the data given by an ATSbufread. Its simplicity is its attractive feature.
- +Examples
Here is an example of the ATSpartialtap opcode. It uses the file ATSpartialtap.csd.
- +Example 81. Example of the ATSpartialtap opcode.
- +<CsoundSynthesizer> <CsOptions> @@ -94,15 +94,15 @@Examples
nchnls = 2 0dbfs = 1 -; by Menno Knevel - 2021 +; by Menno Knevel - 2023 -ires1 system_i 1,{{ atsa beats.wav beats1.ats }} ; default settings -ires2 system_i 1,{{ atsa -h.8 -c8 beats.wav beats2.ats }} ; longer hopsize & more cycles +ires1 system_i 1,{{ atsa drumsMlp.wav drumsMlp1.ats }} ; default settings +ires2 system_i 1,{{ atsa -h.8 -c8 drumsMlp.wav drumsMlp2.ats }} ; longer hopsize & more cycles instr 1 ktime line 0, p3, 2 - ATSbufread ktime, 1, p4 , 90 + ATSbufread ktime, 1, p4 , 54 kfreq1, kam1 ATSpartialtap 5 kfreq2, kam2 ATSpartialtap 20 kfreq3, kam3 ATSpartialtap 30 @@ -117,9 +117,9 @@Examples
</CsInstruments> <CsScore> f 1 0 16384 10 1 0 .5 0 .33 ; square-ish wave -; stretch the beats 2x -i 1 0 2 "beats1.ats" 1 ; defaults settings for ATSA -i 1 3 2 "beats2.ats" .25 ; different settings +; stretch the drums... +i 1 0 2 "drumsMlp1.ats" 2.5 ; defaults settings for ATSA +i 1 3 10 "drumsMlp2.ats" 1 ; different settings e </CsScore> </CsoundSynthesizer> @@ -133,20 +133,16 @@Examples
- +See also
-ATSread, - ATSreadnz, - ATSinfo, - ATSsinnoi, - ATSbufread, - ATScross, - ATSinterpread, - ATSadd, - ATSaddnz
+- +Credits
diff --git a/ATSread.html b/ATSread.html index bd0349481ca..09c674afeb0 100644 --- a/ATSread.html +++ b/ATSread.html @@ -38,19 +38,19 @@
- +Description
ATSread returns the amplitude (kamp) and frequency (kfreq) information of a user specified partial contained in the ATS analysis file at the time indicated by the time pointer ktimepnt.
- +Initialization
iatsfile – the ATS number (n in ats.n) or the name in quotes of the analysis file made using ATSA. @@ -60,7 +60,7 @@
Initialization
- +Performance
kfreq, kamp - outputs of the ATSread unit. These values represent the frequency and amplitude of a specific partial selected by the user using ipartial. The partials' informations are derived from an ATS analysis. ATSread linearly interpolates the frequency and amplitude between frames in the ATS analysis file at k-rate. The output is dependent on the data in the analysis file and the pointer ktimepnt. @@ -68,19 +68,19 @@
Performance
ktimepnt – The time pointer in seconds used to index the ATS file. Used for ATSread exactly the same as for pvoc and ATSadd.
- +Examples
Here is an example of the ATSread opcode. It uses the file ATSread.csd.
- +Example 78. Example of the ATSread opcode.
- +<CsoundSynthesizer> <CsOptions> @@ -135,13 +135,13 @@Examples
Here is a musical example of the ATSread opcode. It uses the file ATSread-musical.csd.- +Example 79. Example 2 of the ATSread opcode.
- +See also
-ATSreadnz, - ATSinfo, - ATSbufread, - ATScross, - ATSinterpread, - ATSpartialtap, - ATSadd, - ATSaddnz, - ATSsinnoi
+- +Credits
diff --git a/ATSreadnz.html b/ATSreadnz.html index 777d8984f7d..0c346b4a868 100644 --- a/ATSreadnz.html +++ b/ATSreadnz.html @@ -38,19 +38,19 @@
- +Description
ATSreadnz returns the energy (kenergy) of a user specified noise band (1-25 bands) at the time indicated by the time pointer ktimepnt.
- +Initialization
iatsfile – the ATS number (n in ats.n) or the name in quotes of the analysis file made using ATSA. @@ -60,7 +60,7 @@
Initialization
- +Performance
kenergy outputs the linearly interpolated energy of the noise band indicated in iband. The output is dependent on the data in the analysis file and the ktimepnt. @@ -72,7 +72,7 @@
Performance
- +Examples
ktime line 2.5, p3, 0 @@ -97,13 +97,13 @@Examples
Here is a complete example of the ATSreadnz opcode. It uses the file ATSreadnz.csd.- +Example 80. Another example of the ATSreadnz opcode.
- +<CsoundSynthesizer> <CsOptions> @@ -118,26 +118,26 @@Examples
sr = 44100 ksmps = 32 nchnls = 2 -0dbfs = 1 +0dbfs = 1 -; by Menno Knevel - 2021 +; by Menno Knevel - 2023 -ires system_i 1,{{ atsa beats.wav beats.ats }} ; default settings +ires system_i 1,{{ atsa Mathews.wav Mathews.ats }} ; default settings instr 1 ktime line 0, p3, 2 -kenergy ATSreadnz ktime, "beats.ats", p4 ; return energy from band p4 -anoise randi kenergy, 1500 - outs anoise *.7, anoise *.7 +kenergy ATSreadnz ktime, "Mathews.ats", p4 ; return energy from band p4 +anoise randi kenergy, 5000 + outs anoise *p5, anoise *p5 ; compensate amplitude differences! endin </CsInstruments> <CsScore> -; band -i 1 0 2 6 ; 3 different energy bands -i 1 3 2 12 -i 1 6 2 17 +; 3 different energy bands, compensated by different amplitude values +i 1 0 10 6 .015 ; loud!! +i 1 11 10 12 .4 ; less energy in this band +i 1 22 10 17 1 ; and even less... e </CsScore> @@ -150,20 +150,16 @@Examples
- +See also
-ATSread, - ATSinfo, - ATSbufread, - ATScross, - ATSinterpread, - ATSpartialtap, - ATSadd, - ATSaddnz, - ATSsinnoi
+- +Credits
diff --git a/ATSsinnoi.html b/ATSsinnoi.html index c52aceccc1a..c937ffc73b0 100644 --- a/ATSsinnoi.html +++ b/ATSsinnoi.html @@ -38,20 +38,20 @@
- +Description
ATSsinnoi reads data from an ATS data file and uses the information to synthesize sines and noise together.
- +Syntax
ar ATSsinnoi ktimepnt, ksinlev, knzlev, kfmod, iatsfile, ipartials \ [, ipartialoffset, ipartialincr]- +Initialization
iatsfile – the ATS number (n in ats.n) or the name in quotes of the analysis file made using ATSA. @@ -64,7 +64,7 @@
Initialization
- +Performance
ktimepnt – The time pointer in seconds used to index the ATS file. Used for ATSsinnoi exactly the same as for pvoc.
@@ -79,7 +79,7 @@
Performance
- +Examples
ktime line 0, p3, 2.5 @@ -90,13 +90,13 @@Examples
Here is a complete example of the ATSsinnoi opcode. It uses the file ATSsinnoi.csd.- +Example 82. Example of the ATSsinnoi opcode.
- +<CsoundSynthesizer> <CsOptions> @@ -115,8 +115,8 @@Examples
nchnls = 2 0dbfs = 1 -ires1 system_i 1,{{ atsa -h.5 -c1 beats.wav beats1.ats }} -ires2 system_i 1,{{ atsa beats.wav beats2.ats }} ; default settings -h.25 -c4 +ires1 system_i 1,{{ atsa -h.5 -c1 drumsMlp.wav drumsMlp1.ats }} +ires2 system_i 1,{{ atsa drumsMlp.wav drumsMlp2.ats }} ; default settings -h.25 -c4 instr 1 @@ -131,14 +131,14 @@Examples
<CsScore> s ; atsfile partial -i 1 0 2 "beats1.ats" 3 -i 1 3 2 "beats2.ats" 3 +i 1 0 2 "drumsMlp1.ats" 3 +i 1 3 2 "drumsMlp2.ats" 3 s -i 1 0 2 "beats1.ats" 13 -i 1 3 2 "beats2.ats" 13 +i 1 0 2 "drumsMlp1.ats" 13 +i 1 3 2 "drumsMlp2.ats" 13 s -i 1 0 2 "beats1.ats" 30 -i 1 3 2 "beats2.ats" 30 +i 1 0 2 "drumsMlp1.ats" 30 +i 1 3 2 "drumsMlp2.ats" 30 e </CsScore> @@ -152,13 +152,13 @@Examples
Here is another complete example of the ATSsinnoi opcode. It uses the file ATSsinnoi-2.csd.- +Example 83. Example 2 of the ATSsinnoi opcode.
- +See also
-ATSread, - ATSreadnz, - ATSinfo, - ATSbufread, - ATScross, - ATSinterpread, - ATSpartialtap, - ATSadd, - ATSaddnz
+- +Credits
diff --git a/AbletonLink.html b/AbletonLink.html new file mode 100644 index 00000000000..5026e66b2e7 --- /dev/null +++ b/AbletonLink.html @@ -0,0 +1,127 @@ + + + + + +
Ableton Link Opcodes + + + + + + + + + + ++ ++ + + diff --git a/C.html b/C.html index dcc1f54fec2..6411293845f 100644 --- a/C.html +++ b/C.html @@ -39,19 +39,19 @@+The purpose of Ableton Link is to synchronize musical time, beat, and phase +between musical applications performing in real time from separate +programs, processes, and network addresses. This is useful, e.g., for laptop +orchestras. +
++ Ableton Live is not required to use the Ableton Link protocol, as it is a peer-to-peer protocol. + There is one Link session on the local area network that maintains a global time, tempo, and + beat. Any peer may set the tempo, +and thereafter all peers in the session share that tempo. A process may +have any number of peers (i.e., any number of Link objects). Each peer +may also define its own "quantum" i.e. some multiple of the beat, e.g. a +quantum of 4 might imply 1 beat every measure of 4/4 time. The phase of the time is defined w.r.t +the quantum, e.g. phase 0.5 of a quantum of 4 would be the second beat of +the measure. Peers may read and write timelines with local time, beat, and +phase, counting from when the peer is enabled, but the tempo and beat on +all timelines for all peers in the session will coincide. +
++The first peer in a session determines the initial tempo. After +that, the tempo is changed only, and whenever, any peer explicity calls +the set tempo functon (link_tempo_set, in Csound). +
++The Link tempo is independent of the Csound score tempo. Performances that +need to synchronize the score tempo with the Link tempo may use the tempo +opcode to set the score tempo from the Link tempo; or conversely, set the +Link tempo from the score tempo using the tempoval opcode. +
++Please note, the phase and beat obtained or set by these opcodes is only as +precise as allowed by the duration of Csound's kperiod, the audio driver +used by Csound, network latency and stability, and the system's most precise clock. +
++++
+- +
+link_create - Creates an Ableton Link peer object.
+- +
+link_enable - Enable/disable synchronization with the network Ableton Link session tempo and beat.
+- +
+link_is_enabled - Returns whether or not this Ableton Link peer has joined the network session.
+- +
+link_tempo_set - Sets the tempo for the network's Ableton Link session.
+- +
+link_tempo_set - Returns the tempo of the network's Ableton Link session.
+- +
+link_beat_get - Returns the beat, phase, and current time of Ableton Link for this session for a given quantum.
+- +
+link_metro - Returns a trigger that is 1 on the beat and 0 otherwise along with the beat, phase, and current time of Ableton Link for this session for a given quantum.
+- +
+link_beat_request - Requests a beat with a specific number at a specific time at a given quantum.
+- +
+link_beat_force - Forces the network Ableton Link session to adopt a beat with a specific number at a specific time at a given quantum.
+- +
+link_peers - Returns the number of peers currently joined in the network Ableton Link session.
+
- +Examples
Here is an example of the C statement. It uses the file C.csd.
- +- Example 1261. Example of the C statement. + Example 1276. Example of the C statement.
+++Credits
diff --git a/CommandDesc.html b/CommandDesc.html index 36fafa24a08..b01ac33cd1c 100644 --- a/CommandDesc.html +++ b/CommandDesc.html @@ -71,7 +71,7 @@
Description of the
Csound reports on the various stages of score and orchestra processing as it executes, performing various syntax and error checks along the way. Once the actual performance has begun, any error messages will derive from either the instrument loader or the unit generators themselves. A CSound command may include any rational combination of flag arguments.
-Running the examples in this manual from the command line
+Running the examples in this manual from the command line
Most of the manual's examples come ready to run without the need of adding any command line flags since they specify options within the csd file's <CsOptions> tag, so you only need to type something like:
diff --git a/CommandEnvironment.html b/CommandEnvironment.html index 422b31a831f..cf18e7b49dd 100644 --- a/CommandEnvironment.html +++ b/CommandEnvironment.html @@ -87,11 +87,11 @@Csound Envi -
On the command line
+On the command line
You can set environment variables on the command line or the configuration file .csound6rc by using the command line flag --env:NAME=VALUE or --env:NAME+=VALUE, where NAME is the environment variable name, and VALUE is its value. See Command-line Flags
-Windows
+Windows
To set a csound environment on Windows XP and 2000 go to Control Panel->System->Advanced and click on the button 'Environment Variables'. On other versions of Windows earlier than Windows XP and Windows 2000 you set environment variables in the autoexec.bat file. Go to 'My Computer', select C: drive, right click on autoexec.bat, and select 'Edit'. The statement format is: SET NAME=VALUE .
-Linux
+Linux
You can set environment variables on Linux in many ways. You can set them using the export shell command, by setting them on .bashrc or similar files or by adding them to the /etc/profile file.
-Mac
+Mac
~$ export OPCODE6DIR64=/Users/you/your/Csound6/buildin addition if the bash shell is the default, then it is usually easier to edit your .bashrc or /etc/profile.
Note that if users choose one of the above methods, ie editing the .bashrc file then the environment variables are executed when a new shell is created. This can be problematic if your application implements a Quartz or Aqua interface and does not use the commandline.
diff --git a/CommandFlags.html b/CommandFlags.html index 3bcfd4b142a..53c99efe74f 100644 --- a/CommandFlags.html +++ b/CommandFlags.html @@ -37,20 +37,20 @@
csound
- +diff --git a/ControlFltkAppearance.html b/ControlFltkAppearance.html deleted file mode 100644 index 4aed423a2da..00000000000 --- a/ControlFltkAppearance.html +++ /dev/null @@ -1,189 +0,0 @@ - - - - - -Csound command line flags
Listed below are the command line flags available in Csound6 in alphabetical order. Various platform @@ -1396,7 +1396,9 @@
Csound command line flags
Start and stop instances of instruments at the nearest sample to the requested time. This is in contrast to traditional Csound which rounds the times to the nearest - k-cycle. Note that this does not work with tied notes. + k-cycle. Note that this does not work with tied notes, + nor does it change the Midi timing (as this is only + affected by ksmps size (control rate).diff --git a/CommandFlagsCategory.html b/CommandFlagsCategory.html index c92a92bb4a7..56af2a72cdb 100644 --- a/CommandFlagsCategory.html +++ b/CommandFlagsCategory.html @@ -1245,7 +1245,9 @@ Command-l Start and stop instances of instruments at the nearest sample to the requested time. This is in contrast to traditional Csound which rounds the times to the nearest - k-cycle. Note that this does not work with tied notes. + k-cycle. Note that this does not work with tied notes, + nor does it change the Midi timing (as this is only + affected by ksmps size (control rate).
diff --git a/CommandUnifile.html b/CommandUnifile.html index 577f53b161a..c9b3fdccb79 100644 --- a/CommandUnifile.html +++ b/CommandUnifile.html @@ -62,20 +62,20 @@ Description
The file is a structured data file which uses markup language, similar to any SGML such as HTML. Start tags (<tag>) and end tags (</tag>) are used to delimit the various elements. The file is saved as a text file.
-Structured Data File Format
-Mandatory Elements
+Structured Data File Format
+Mandatory Elements
The first tag in the file must be the start tag <CsoundSynthesizer>. The last tag in the file must be the end tag </CsoundSynthesizer>. This element is used to alert the csound compiler to the .csd format. All text before the start tag and after the end tag is ignored by Csound. The tag may also be spelled <CsoundSynthesiser>.
-Options (<CsOptions>)
+Options (<CsOptions>)
Csound command line flags are put in the Options Element. This section is delimited by the start tag <CsOptions> and the end tag </CsOptions> Lines beginning with # or ; are treated as comments.
-Orchestra (<CsInstruments>)
+Orchestra (<CsInstruments>)
The instrument definitions (orchestra) are put into the Instruments Element. The statements and syntax in this section are identical to the Csound orchestra file, and have the same requirements, including the header statements (sr, kr, etc.) This Instruments Element is delimited with the start tag <CsInstruments> and the end tag </CsInstruments>.
-Score (<CsScore>)
+Score (<CsScore>)
Csound score statements are put in the Score Element. The statements and syntax in this section are identical to the Csound score file, and have the same requirements. The Score Element is delimited by the start tag <CsScore> and the end tag </CsScore>.
@@ -87,8 +87,8 @@Score (<CsScore>)
the destination score file. The external program should create a standard Csound score. -Optional Elements
-Included Base64 Files (<CsFileB>)
+Optional Elements
+Included Base64 Files (<CsFileB>)
Base64-encoded files may be included with the tag <CsFileB filename=filename>, where filename is the name of the file to be included. The Base64-encoded data should be terminated with a </CsFileB> tag. For encoding files, the csb64enc and makecsd utilities (included with Csound 5.00 and newer) can be used. The file will be extracted to the current directory, and deleted at end of performance. If there is an already existing file with the same name, it is not overwritten, but an error will occur instead.
@@ -98,7 +98,7 @@Included Base64 Files (<CsFileB>)
Base64-encoded sample files may be included with the tag <CsSampleB filename=filename>, where filename is the name of the file containing the sample. There is no matching end tag. This was added in Csound version 4.07. Note: using this tag is not recommended; use <CsFileB> instead.
-Included Unencoded Files (<CsFile>)
+Included Unencoded Files (<CsFile>)
Unencoded files may be included with the tag <CsFile @@ -111,7 +111,7 @@
-Included Unencoded Files (<CsFile>)
the same name, it is not overwritten, but an error will occur instead.Version Blocking (<CsVersion>)
+Version Blocking (<CsVersion>)
Versions of Csound may blocked by placing one of the following statements between the start tag <CsVersion> and the end tag </CsVersion>: @@ -139,7 +139,7 @@
Version Blocking (<CsVersion>)
This was added in Csound version 4.09. -Licence Information (<CsLicence> or <CsLicense>)
+Licence Information (<CsLicence> or <CsLicense>)
Licencing details can be included in between the start tag <CsLicence> and the end tag @@ -147,7 +147,7 @@
Licence Information (<CsLicence> or <CsLicense& for this information, any text is acceptable. This text will be printed by Csound to the console when the CSD is run. -
Licence Information (<CsShortLicence> or <CsShortLicense>)
+Licence Information (<CsShortLicence> or <CsShortLicense>)
From version 6.05 licencing details can be also included in between the start tag @@ -185,7 +185,7 @@
Licence Information (<CsShortLicence> or <CsSho
-
Embedded HTML (<html>)
+Embedded HTML (<html>)
Any valid HTML code can be embedded in the CSD file. This code should be structured exactly like an ordinary Web page. This code can contain any valid HTML, JavaScript, Cascading Style Sheet, WebGL, etc., etc. code. diff --git a/Configuring.html b/Configuring.html index cfa754a3d56..d5885fff23d 100644 --- a/Configuring.html +++ b/Configuring.html @@ -9,7 +9,7 @@ - +
@@ -19,7 +19,7 @@Configuring - @@ -45,33 +45,18 @@Prev +Prev Part I. Overview Next Configuring
(Note that for csound5 these environment variables wereOPCODEDIRandOPCODEDIR64.) -The Python opcodes currently require at least Python 2.4, which can be downloaded from www.python.org if it is not already on your system. You can check if it is available by typing 'python' on a command prompt or DOS window. +
The Python opcodes currently require Python 3.x, which can be downloaded from www.python.org if it is not already on your system. You can check if it is available by typing 'python' on a command prompt or DOS window.
-Windows
+Windows
On Windows, make sure the directory or directories (normally the
C:\Program Files\Csounddirectory) containing the Csound executables directory are in yourPATHvariable, or else copy all the executable files to your Windowssystem32directory. Depending on your installation method, you might also need to set theOPCODE6DIRandOPCODE6DIR64environment variables. Assuming that Csound is installed to the default location ofC:\Program Files\Csoundyou can use (otherwise set the paths accordingly):set OPCODE6DIR=C:\Program Files\Csound\plugins set OPCODE6DIR64=C:\Program Files\Csound\plugins64 set PATH=%PATH%;C:\Program Files\Csound\bin----
-- -- --
Missing python24.dll or python25.dll -- -- -If you get a pop-up about the missing Python library (python24.dll or python25.dll) and don't need the python opcodes, just delete
-C:\Program Files\Csound\plugins\py.dllandC:\Program Files\Csound\plugins64\py.dll, and the pop-up about the missing Python library should be gone.Unix and Linux
+Unix and Linux
On Unix and Linux, either install the Csound program in one of the system
-bindirectories, typically/usr/local/bin, and the Csound and plugin shared libraries in places like/usr/local/lib/csound/pluginsor/usr/local/lib/csound/plugins64and make sure thatOPCODE6DIRandOPCODE6DIR64environment variable are set correctly.CsoundAC
+CsoundAC
CsoundAC requires some additional configuration. On all platforms, CsoundAC requires that you have Python installed on your computer. The directory containing the
_csoundACshared @@ -83,14 +68,14 @@CsoundAC
- Prev +Prev Up Next - Optimizing Audio I/O Latency +Realtime I/O with JACK Connection Kit Home diff --git a/ControlConditional.html b/ControlConditional.html index 1169dcd452e..975e4e5a9ab 100644 --- a/ControlConditional.html +++ b/ControlConditional.html @@ -30,7 +30,7 @@ diff --git a/ControlDurctl.html b/ControlDurctl.html index cfd2ef41355..54cd2af6742 100644 --- a/ControlDurctl.html +++ b/ControlDurctl.html @@ -10,7 +10,7 @@ - +
@@ -30,7 +30,7 @@ @@ -60,6 +60,13 @@Duration Control +
+ + + turnoff3 + +
+@@ -83,14 +90,14 @@
Duration Control
Up -Next +Next Conditional Values Home -FLTK Widgets and GUI controllers +Instrument Invocation Modifying FLTK Widget Appearance - - - - - - - - - - -- -- - - diff --git a/ControlFltkGeneral.html b/ControlFltkGeneral.html deleted file mode 100644 index 0f65017cce0..00000000000 --- a/ControlFltkGeneral.html +++ /dev/null @@ -1,116 +0,0 @@ - - - - - -The following opcodes modify FLTK widget appearance:
----
-- -
-- - FLcolor - -
-- -
-- - FLcolor2 - -
-- -
-- - FLhide - -
-- -
-- - FLlabel - -
-- -
-- - FLsetAlign - -
-- -
-- - FLsetBox - -
-- -
-- - FLsetColor - -
-- -
-- - FLsetColor2 - -
-- -
-- - FLsetFont - -
-- - -
-- -
-- - FLsetSize - -
-- -
-- - FLsetText - -
-- - -
-- - -
-- - -
-- -
-- - FLsetVal_i - -
-- -
-- - FLsetVal - -
-- -
-- - FLshow - -
-General FLTK Widget-related Opcodes - - - - - - - - - - -- -- - - diff --git a/ControlFltkIntro.html b/ControlFltkIntro.html deleted file mode 100644 index cfeb9f4135e..00000000000 --- a/ControlFltkIntro.html +++ /dev/null @@ -1,360 +0,0 @@ - - - - - -- The general FLTK widget-related opcodes are: -
----
-- -
-- - FLgetsnap - -
-- -
-- - FLloadsnap - -
-- -
-- - FLrun - -
-- -
-- - FLsavesnap - -
-- -
-- - FLsetsnap - -
-- -
-- - FLupdate - -
-- - -
--
-FLTK Widgets and GUI controllers - - - - - - - - - - -- -- - - diff --git a/ControlFltkOther.html b/ControlFltkOther.html deleted file mode 100644 index 4cf555d13bb..00000000000 --- a/ControlFltkOther.html +++ /dev/null @@ -1,214 +0,0 @@ - - - - - -- Widgets allow the design of a custom Graphical User Interface (GUI) to control an orchestra in real-time. - They are derived from the open-source library FLTK (Fast Light Tool Kit). This library is one of the - fastest graphic libraries available, supports OpenGL and should be source compatible with different - platforms (Windows, Linux, Unix and Mac OS). The subset of FLTK implemented in Csound provides the - following types of objects: -
----
-- - Containers -
-- -
-- FLTK Containers are widgets - that contain other widgets such as panels, windows, etc. Csound provides the following container - objects: -
----
-- Panels
-- Scroll areas
-- Pack
-- Tabs
-- Groups
--
-- - Valuators -
-- -
-- The most useful objects are named - FLTK Valuators. These objects - allow the user to vary synthesis parameter values in real-time. Csound provides the following - valuator objects: -
----
-- Sliders
-- Knobs
-- Rollers
-- Text fields
-- Joysticks
-- Counters
--
-- - Other widgets -
-- -
-- There are other FTLK widgets - that are not valuators nor containers: -
----
-- Buttons
-- Button banks
-- Labels
-- Keyboard and Mouse sensing
--
--
-- Also there are some other opcodes useful to modify the - widget appearance: -
----
-- Updating widget value.
-- Setting primary and selection colors of a widget.
-- Setting font type, size and color of widgets.
-- Resizing a widget.
-- Hiding and showing a widget.
--
-- There are also these general opcodes that allow the following actions: -
----
-- Running the widget thread: - FLrun
-- Loading snapshots containing the status of all valuators of an orchestra: - FLgetsnap and - FLloadsnap.
-- Saving snapshots containing the status of all valuators of an orchestra: - FLsavesnap and - FLsetsnap
-- Setting the snapshot group of a declared valuator: - FLsetSnapGroup
--
-- Below is a simple example of Csound code to create a window. Notice that all opcodes are init-rate and - must be called only once per session. The best way to use them is to place them in the header section of - an orchestra, before any instrument. Even though placing them inside an instrument is not prohibited, - unpredictable results can occur if that instrument is called more than once. -
-- Each container is made up of a couple of opcodes: the first indicating the start of the container block and the last indicating the end of that container block. Some container blocks can be nested but they must not be crossed. After defining all containers, a widget thread must be run by using the special FLrun opcode that takes no arguments. -
--
----<CsoundSynthesizer> -<CsOptions> -; Select audio/midi flags here according to platform -; Audio out Audio in No messages --odac -iadc -d ;;;RT audio I/O -; For Non-realtime ouput leave only the line below: -; -o linseg.wav -W ;;; for file output any platform -</CsOptions> -<CsInstruments> -;******************************* -sr=48000 -kr=480 -ksmps=100 -nchnls=1 - -;*** It is recommended to put almost all GUI code in the -;*** header section of an orchestra - - FLpanel "Panel1",450,550 ;***** start of container -; some widgets should contained here - FLpanelEnd ;***** end of container - - FLrun ;***** runs the widget thread, it is always required! -instr 1 -;put some synthesis code here -endin -;******************************* -</CsInstruments> -<CsScore> -f 0 3600 ;dummy table for realtime input -e - -</CsScore> -</CsoundSynthesizer>-- - The previous code simply creates a panel (an empty window because no widgets are defined inside the container). - -
-- The following example creates two panels and inserts a slider inside each of them: - -
----<CsoundSynthesizer> -<CsOptions> -; Select audio/midi flags here according to platform -; Audio out Audio in No messages --odac -iadc ; -d ;;;RT audio I/O -; For Non-realtime ouput leave only the line below: -; -o linseg.wav -W ;;; for file output any platform -</CsOptions> -<CsInstruments> -;******************************* -sr=48000 -kr=480 -ksmps=100 -nchnls=1 - - FLpanel "Panel1",450,550,100,100 ;***** start of container -gk1,iha FLslider "FLslider 1", 500, 1000, 0 ,1, -1, 300,15, 20,50 - FLpanelEnd ;***** end of container - - FLpanel "Panel2",450,550,100,100 ;***** start of container -gk2,ihb FLslider "FLslider 2", 100, 200, 0 ,1, -1, 300,15, 20,50 - FLpanelEnd ;***** end of container - - FLrun ;***** runs the widget thread, it is always required! - -instr 1 -; gk1 and gk2 variables that contain the output of valuator -; widgets previously defined, can be used inside any instrument -printk2 gk1 -printk2 gk2 ;print the values of the valuators whenever they change -endin -;******************************* -</CsInstruments> -<CsScore> -f 0 3600 ;dummy table for realtime input -e - -</CsScore> -</CsoundSynthesizer>--
-- All widget opcodes are init-rate opcodes, even if valuators output k-rate variables. This happens because an independent thread is run based on a callback mechanism. It consumes very few processing resources since there is no need of polling. (This differs from other MIDI based controller opcodes.) So you can use any number of windows and valuators without degrading the real-time performance. -
-- --- The opcodes for FLTK containers are: -
----
-- -
-- - FLgroup - -
-- -
-- - FLgroupEnd - -
-- -
-- - FLpack - -
-- -
-- - FLpackEnd - -
-- -
-- - FLpanel - -
-- -
-- - FLpanelEnd - -
-- -
-- - FLscroll - -
-- -
-- - FLscrollEnd - -
-- -
-- - FLtabs - -
-- -
-- - FLtabsEnd - -
--
-Other FLTK Widgets - - - - - - - - - - -- -- - - diff --git a/ControlFltkValuators.html b/ControlFltkValuators.html deleted file mode 100644 index 5537d7ac236..00000000000 --- a/ControlFltkValuators.html +++ /dev/null @@ -1,109 +0,0 @@ - - - - - -- Other FLTK widget opcodes are: -
----
-- -
-- - FLbox - -
-- -
-- - FLbutBank - -
-- -
-- - FLbutton - -
-- -
-- - FLexecButton - -
-- -
-- - FLkeyIn - -
-- -
-- - FLhvsBox - -
-- - -
-- -
-- - FLmouse - -
-- -
-- - FLprintk - -
-- -
-- - FLprintk2 - -
-- -
-- - FLslidBnk - -
-- -
-- - FLslidBnk2 - -
-- - -
-- -
-- - FLslidBnkSet - -
-- - -
-- - -
-- -
-- - FLvalue - -
-- -
-- - FLvkeybd - -
-- -
-- - FLvslidBnk - -
-- -
-- - FLvslidBnk2 - -
-- -
-- - FLxyin - -
--
-FLTK Valuators - - - - - - - - - - -- -- - - diff --git a/ControlInvocat.html b/ControlInvocat.html index 0081abb5284..3651e9c1117 100644 --- a/ControlInvocat.html +++ b/ControlInvocat.html @@ -9,7 +9,7 @@ - + @@ -19,7 +19,7 @@- The opcodes for FLTK valuators are: -
----
-- -
-- - FLcount - -
-- -
-- - FLjoy - -
-- -
-- - FLknob - -
-- -
-- - FLroller - -
-- -
-- - FLslider - -
-- -
-- - FLtext - -
--
-Instrument Invocation - @@ -30,7 +30,7 @@ @@ -53,6 +53,20 @@Prev +Prev Instrument Control Next Instrument Invo +
+ ++ + nstance + +
++ + + readscore + +
++ + + + schedulek + +
+@@ -104,20 +125,50 @@
Instrument Invo
Instruments definitions can be removed using the remove opcode. +
++ These opcodes will compile one or more instruments at init time: +
++++
+- +
++ + compilecsd + +
+- +
++ + compileorc + +
+- +
++ + compilestr + +
+
+ These opcodes are part of a counter system: +
+++
+- +
++ + count + +
+- +
++ + count_i + +
+- +
++ + cntCycles + +
+- +
++ + cntRead + +
+- +
++ + cntReset + +
+- +
++ + cntState + +
+- +
++ + cntCreate + +
+- +
++ + cntDelete + +
+- +
++ + cntDelete_i + +
+
diff --git a/ControlRealtime.html b/ControlRealtime.html index ecd04a19181..4d9f389b2e9 100644 --- a/ControlRealtime.html +++ b/ControlRealtime.html @@ -30,7 +30,7 @@ @@ -55,22 +55,29 @@Real-time Perf
+ ++ diff --git a/ControlReinitn.html b/ControlReinitn.html index b235295b0d9..6a7d7741789 100644 --- a/ControlReinitn.html +++ b/ControlReinitn.html @@ -30,7 +30,7 @@ diff --git a/ControlSensing.html b/ControlSensing.html index d3b7b03313e..54dfdb03fe0 100644 --- a/ControlSensing.html +++ b/ControlSensing.html @@ -30,7 +30,7 @@ @@ -38,7 +38,7 @@Sensing and Con @@ -67,6 +67,13 @@
TCL/TK widgets
++ + + flashtxt + +
++ @@ -83,7 +90,7 @@
TCL/TK widgets
@@ -91,6 +98,13 @@Keyboard and mouse sensing
+
- +
+ + joystick + +
+- @@ -110,7 +124,7 @@
Keyboard and mouse sensing
@@ -132,6 +146,13 @@Envelope followers
+- +
+ + lufs + +
+- +
- +
+ + vactrol + +
+@@ -155,7 +183,7 @@
Envelope followers
@@ -163,8 +191,8 @@Tempo and Pitch estimation
+ ++ + plltrack + +
++ ++ + ptrack + +
++ + + pvspitch + +
++ @@ -196,7 +245,7 @@
Tempo and Pitch estimation
@@ -204,22 +253,43 @@Tempo and Sequencing
- +
+- +
++ + metro2 + +
+- +
++ + metrobpm + +
+- +
@@ -237,6 +307,34 @@Tempo and Sequencing
+ ++ + sequ + +
++ ++ + splitrig + +
++ ++ + tempo + +
++ + + tempoval + +
+@@ -272,7 +370,7 @@ Tempo and Sequencing
@@ -292,12 +390,26 @@System
+
- +
++ + pcount + +
+- +
+ + pindex + +
+diff --git a/ControlStacks.html b/ControlStacks.html index 0c6c2974870..b7182a2a22e 100644 --- a/ControlStacks.html +++ b/ControlStacks.html @@ -30,10 +30,11 @@ +
These opcodes are deprecated.
Csound implements a global stack that can be accessed with the following opcodes:
diff --git a/ControlSubinstrument.html b/ControlSubinstrument.html index 1dde9f5d125..6649a9d168c 100644 --- a/ControlSubinstrument.html +++ b/ControlSubinstrument.html @@ -30,7 +30,7 @@ diff --git a/ControlTimeread.html b/ControlTimeread.html index 4e135bf5530..1bab6fb018f 100644 --- a/ControlTimeread.html +++ b/ControlTimeread.html @@ -30,7 +30,7 @@ @@ -39,6 +39,34 @@Time Reading
+
- + +
+- +
++ + elapsedtime + +
+- +
++ + eventcycles + +
+- +
+ + eventtime + +
+diff --git a/ControlTop.html b/ControlTop.html index a397c667ade..c408f2bb494 100644 --- a/ControlTop.html +++ b/ControlTop.html @@ -38,7 +38,7 @@
Instrument Control
diff --git a/CsBeats.html b/CsBeats.html index d8bd629fbc2..0d4d7a7d929 100644 --- a/CsBeats.html +++ b/CsBeats.html @@ -9,7 +9,7 @@ - + @@ -19,7 +19,7 @@Csbeats - @@ -48,7 +48,7 @@Prev +Prev Part III. Reference Next Csbeats
standard output.- +The opening of Bach's Goldberg variation number 3 can be coded as: @@ -271,21 +271,21 @@
Csbeats
- +A Complete Example
Here is a simple example of the csbeats score generator. It uses the file csbeats.csd.
- +- Example 1360. A simple example of csbeats. + Example 1378. A simple example of csbeats.
See the sections Real-time Audio and Command Line Flags for more information on using command line flags.
- +diff --git a/FLbox.html b/FLbox.html index 608eaa9d4bb..c0715c85317 100644 --- a/FLbox.html +++ b/FLbox.html @@ -39,7 +39,7 @@<CsoundSynthesizer> <CsOptions> @@ -410,14 +410,14 @@A Complete Example
- Prev +Prev Up Next - More Advanced Examples +scale Home diff --git a/CscoreAdvancd.html b/CscoreAdvancd.html deleted file mode 100644 index dda98a534c5..00000000000 --- a/CscoreAdvancd.html +++ /dev/null @@ -1,151 +0,0 @@ - - - - - -More Advanced Examples - - - - - - - - - - -- -- - - diff --git a/CscoreCompile.html b/CscoreCompile.html deleted file mode 100644 index 9d1dca57684..00000000000 --- a/CscoreCompile.html +++ /dev/null @@ -1,164 +0,0 @@ - - - - - -- The following program demonstrates reading from two different input files. The idea is to switch between two 2-section scores, and write out the interleaved sections to a single output file. -
--
----#include "cscore.h" /* CSCORE_SWITCH.C */ -cscore(CSOUND* cs) /* callable from either Csound or standalone cscore */ -{ - EVLIST *a, *b; - FILE *fp1, *fp2; /* declare two scorefile stream pointers */ - fp1 = cscoreFileGetCurrent(cs); /* this is the command-line score */ - fp2 = cscoreFileOpen(cs, "score2.srt"); /* this is an additional score file */ - a = cscoreListGetSection(cs); /* read section from score 1 */ - cscoreListPut(cs, a); /* write it out as is */ - cscorePutString(cs, "s"); - cscoreFileSetCurrent(cs, fp2); - b = cscoreListGetSection(cs); /* read section from score 2 */ - cscoreListPut(cs, b); /* write it out as is */ - cscorePutString(cs, "s"); - cscoreListFreeEvents(cs, a); /* optional to reclaim space */ - cscoreListFreeEvents(cs, b); - cscoreFileSetCurrent(cs, fp1); - a = cscoreListGetSection(cs); /* read next section from score 1 */ - cscoreListPut(cs, a); /* write it out */ - cscorePutString(cs, "s"); - cscoreFileSetCurrent(cs, fp2); - b = cscoreListGetSection(cs); /* read next sect from score 2 */ - cscoreListPut(cs, b); /* write it out */ - cscorePutString(cs, "e"); -}--
-- Finally, we show how to take a literal, uninterpreted score file and imbue it with some expressive timing changes. The theory of composer-related metric pulses has been investigated at length by Manfred Clynes, and the following is in the spirit of his work. The strategy here is to first create an array of new onset times for every possible sixteenth-note onset, then to index into it so as to adjust the start and duration of each note of the input score to the interpreted time-points. This also shows how a Csound orchestra can be invoked repeatedly from a run-time score generator. -
--
----#include "cscore.h" /* CSCORE_PULSE.C */ - -/* program to apply interpretive durational pulse to */ -/* an existing score in 3/4 time, first beats on 0, 3, 6 ... */ - - -static float four[4] = { 1.05, 0.97, 1.03, 0.95 }; /* pulse width for 4's */ -static float three[3] = { 1.03, 1.05, .92 }; /* pulse width for 3's */ - - -cscore(CSOUND* cs) /* This example should be called from Csound */ -{ - EVLIST *a, *b; - EVENT *e, **ep; - float pulse16[4*4*4*4*3*4]; /* 16th-note array, 3/4 time, 256 measures */ - float acc16, acc1,inc1, acc3,inc3, acc12,inc12, acc48,inc48, acc192,inc192; - float *p = pulse16; - int n16, n1, n3, n12, n48, n192; - - /* fill the array with interpreted ontimes */ - for (acc192=0.,n192=0; n192<4; acc192+=192.*inc192,n192++) - for (acc48=acc192,inc192=four[n192],n48=0; n48<4; acc48+=48.*inc48,n48++) - for (acc12=acc48,inc48=inc192*four[n48],n12=0;n12<4; acc12+=12.*inc12,n12++) - for (acc3=acc12,inc12=inc48*four[n12],n3=0; n3<4; acc3+=3.*inc3,n3++) - for (acc1=acc3,inc3=inc12*four[n3],n1=0; n1<3; acc1+=inc1,n1++) - for (acc16=acc1,inc1=inc3*three[n1],n16=0; n16<4; acc16+=.25*inc1*four[n16],n16++) - *p++ = acc16; - - - /* for (p = pulse16, n1 = 48; n1--; p += 4) /* show vals & diffs */ - /* printf("%g %g %g %g %g %g %g %g\n", *p, *(p+1), *(p+2), *(p+3), - /* *(p+1)-*p, *(p+2)-*(p+1), *(p+3)-*(p+2), *(p+4)-*(p+3)); */ - - a = cscoreListGetSection(cs); /* read sect from tempo-warped score */ - b = cscoreListSeparateTWF(cs, a); /* separate warp & fn statements */ - cscoreListPlay(cs, b); /* and send these to performance */ - a = cscoreListAppendStringEvent(cs, a, "s"); /* append a sect statement to note list */ - cscoreListPlay(cs, a); /* play the note-list without interpretation */ - for (ep = &a->e[1], n1 = a->nevents; n1--; ) { /* now pulse-modifiy it */ - e = *ep++; - if (e->op == 'i') { - e->p[2] = pulse16[(int)(4. * e->p2orig)]; - e->p[3] = pulse16[(int)(4. * (e->p2orig + e->p3orig))] - e->p[2]; - } - } - - cscoreListPlay(cs, a); /* now play modified list */ -}--
-Compiling a Cscore Program - - - - - - - - - - -- -- - - diff --git a/CscoreMain.html b/CscoreMain.html deleted file mode 100644 index 0e1f6d63ea6..00000000000 --- a/CscoreMain.html +++ /dev/null @@ -1,390 +0,0 @@ - - - - - -- A Cscore program can be invoked either as a standalone program or as part of Csound in between sorting the score and performing the score with the orchestra: -
--
----
cscore[scorefilein] [> scorefileout]-
-- or -
--
----
csound[-C] [otherflags] [orchname] [scorename]-
-- Before trying to compile your own Cscore program, you will most likely want to obtain a copy of the Csound source code. Either download the latest source distribution for your platform or check out a copy of the csound5 module from Sourceforge CVS. There are several files in the sources that will help you. Within the
-examples/cscore/directory are a number of examples of Cscore control programs, including all of the examples contained in this manual. And in thefrontends/cscore/directory are the two files cscoremain.c and cscore.c. cscoremain.c contains a simple main function that performs all of the initialization that a standalone Cscore program needs to do before it calls your control function. This main “stub” initializes Csound, reads the commandline arguments, opens the input and output score files, and then calls a function cscore(). As described above, it is expected that you will write the cscore() function and provide it in another file. The file frontends/cscore/cscore.c shows the simplest example of a cscore() function that reads in a score of any length and writes it to the output unchanged. --So, to create a standalone program, write a control program as shown in the previous section. Let's assume that you saved this program in a file named “mycscore.c”. Next, you need to compile and link this program with the Csound library and cscoremain.c in order to create an exectuable by following the set of directions below that apply to your operating system. It will be helpful to already have some familiarity with the C compiler on your computer since the information below cannot be complete for all possible systems. -
-Linux and Unix
--The following commands assume that you have copied your file mycscore.c into the same directory as cscoremain.c, that you have opened a terminal to that same directory, and that you have previously installed a binary distribution of Csound that placed a library libcsound.a or libcsound.so into /usr/local/lib and the header files for the Csound API into /usr/local/include/csound. -
--To compile and link: -
----gcc mycscore.c cscoremain.c -o cscore -lcsound -L/usr/local/lib -I/usr/local/include/csound--To run (sending the results to standard output): -
---./cscore test.sco--It is possible that on some Unix systems, the C compiler will be named cc or something else other than gcc. -
-Windows
--Csound is usually compiled on Windows using the MinGW environment that makes GCC -- the same compiler used on Linux -- available using a Unix-like command shell (MSYS). Since pre-compiled libraries for Csound on Windows are built in this way, you may need to use MinGW as well to link to them. If you have built Csound using another compiler, then you should be able to build Cscore with that compiler as well. -
--Compiling standalone Cscore programs using MinGW should be similar to the procedure for Linux above with library and header paths changed appropriately for where Csound is installed on the Windows system. (Please feel free to contribute more detailed instructions here as the editor has been unable to test Cscore on a Windows machine). -
-OS X
--The following commands assume that you have copied your file mycscore.c into the same directory as cscoremain.c and that you have opened a terminal to that same directory. In addition, the Apple-supplied developer tools (including the GCC compiler) should be installed on your system and you should have previously installed a binary distribution of Csound that placed the CsoundLib framework into /Library/Frameworks. -
--Use this command compile and link. (You may get a warning about "multiple definitions of symbol _cscore"). -
----gcc cscore.c cscoremain.c -o cscore -framework CsoundLib -I/Library/Frameworks/CsoundLib.framework/Headers--To run (sending the results to standard output): -
---./cscore test.sco-MacOS 9
-- You will need CodeWarrior or some other development environment installed on your computer (MPW may work). Download the source code distribution for OS 9 (it will have a name like Csound5.05_OS9_src.smi.bin). -
-- If using CodeWarrior, find and open the project file "Cscore5.cw8.mcp" in the folder "Csound5.04-OS9-source:macintosh:Csound5Library:". This project file is configured to use the source files cscore.c and cscoremain_MacOS9.c from the csound5 source tree and the Csound5Lib shared library produced by compiling Csound with the "Csound5.cw8.mcp" project file. You should substitute your own Cscore program file for cscore.c and either compile Csound5Lib first or substitute a copy of the library in the project from the binary distribution of Csound for OS 9. The file cscoremain_MacOS9.c contains specialized code for configuring CodeWarrior's SIOUX console library and allows commandline arguments to be entered before the program is run. -
--Once you have the proper files included in the project window, click the "Make" button and CodeWarrior should produce an application named “Cscore”. When you run this application, it first displays a window allowing you to type in the arguments to the main function. You only need to type in the filename or pathname to the input score -- do not type in "cscore". The input file should be in the same folder as the application or else you will need to type a full or relative pathname to the file. Output will be displayed in the console window. You can use the Save command from the File menu before quitting if you wish. Alternatively, in the commandline dialog, you can choose to redirect the output to a file by clicking on the File button on the right side of the dialog. (Note that the console window can only display about 32,000 characters, so writing to a file is necessary for long scores). -
-Making Cscore usable from within Csound
-- To operate from Csound, first follow the instructions for compiling Csound (see Building Csound) according to the operating system that you are using. Once you have successfully built an unmodified Csound system, then substitute your own cscore() function for the one in the file Top/cscore_internal.c, and rebuild Csound. -
-- The resulting executable is your own special Csound, usable as above. The -C flag will invoke your Cscore program after the input score is sorted into “score.srt”. The details of what happens when you run Csound with the -C flag are given in the next section. -
-- Csound 5 also provides an additional way to run your own Cscore program from within Csound. Using the API, a host application can set a Cscore callback function, which is a function that Csound will call instead of using the built-in cscore() function. One advantage of this approach is that it is not necessary to recompile the entirety of Csound. Another benefit is that the host application can select at runtime from more than one Cscore function to designate as the callback. The disadvantage is that you need to write a host application. -
-- A simple approach to using a Cscore callback via the API would be to modify the standard Csound main program -- which is a simple Csound host -- contained in the file frontends/csound/csound_main.c. Adding a call to csoundSetCscoreCallback() after the call to csoundCreate() but before the call to csoundCompile() should do the job. Recompiling this file and linking to an existing Csound library will make a commandline version of Csound that works similarly to the one described above. Don't forget to use the -C flag. -
-Notes about score formats and run-time behavior
-- As stated previously, the input files to Cscore may be in original or time-warped and pre-sorted form; this modality will be preserved (section by section) in reading, processing, and writing scores. Standalone processing will most often use unwarped sources and create unwarped new files. When running from within Csound, the input score will arrive already warped and sorted, and can thus be sent directly (normally section by section) to the orchestra. One advantage of this method of using Cscore is that all of the syntactical conveniences of the full Csound score language may be used -- macros, arithmetic expressions, carry, ramp, etc. -- since the score will go through the "Carry, Tempo, Sort" phases of score processing before being passed to the user-supplied Cscore program. -
-- When running within Csound, a list of events can be conveyed to a Csound orchestra using cscoreListPlay(). There may be any number of cscoreListPlay() calls in a Cscore program. Each list so conveyed can be either time-warped or not, but each list must be in strict p2-chronological order (either from presorting or using cscoreListSort()). If there is no cscoreListPlay() in a Cscore module run from within Csound, all events written out (via cscorePutEvent(), cscorePutString(), or cscoreListPut()) are written to a new score in the current directory with the name “cscore.out”. Csound then invokes the score sorter again before sending this new score to the orchestra for performance. The final, sorted, output score is written to a file named “cscore.srt”. -
-- A standalone Cscore program will normally use the “put” commands to write into its output file. If a standalone Cscore program calls cscoreListPlay(), the events thus intended for performance will be sent to the output in the same way as if cscoreListPut() had been called instead. -
-- A note list sent by cscoreListPlay() for performance should be temporally distinct from subsequent note lists. No note-end should extend past the next list's start time, since cscoreListPlay() will complete each list before starting the next (i.e. like a Section marker that doesn't reset local time to zero). This is important when using cscoreListGetNext() or cscoreListGetUntil() to fetch and process score segments prior to performance, because these functions may only read part of an unsorted section. -
-Writing a Cscore Control Program - - - - - - - - - - -- -- - - diff --git a/CscoreTop.html b/CscoreTop.html deleted file mode 100644 index fcc1000e393..00000000000 --- a/CscoreTop.html +++ /dev/null @@ -1,255 +0,0 @@ - - - - - -- The general format for a Cscore control program is: - -
----#include "cscore.h" -void cscore(CSOUND *cs) -{ - /* VARIABLE DECLARATIONS */ - /* PROGRAM BODY */ -}--
-- The include statement will define the event and list structures and all of the Cscore API functions for the program. The name of the user function needs to be cscore if it will be linked with the standard main program in
-cscormai.cor linked as the internal Cscore routine for a personal Csound executable. This cscore() function receives one argument fromcscormai.cor Csound -- CSOUND *cs -- which is a pointer to a Csound object. The pointer cs must be passed as the first parameter to every Cscore API function that the program calls. -- The following C program will read from a standard numeric score, up to (but not including) the first s or e statement, then write that data (unaltered) as output. -
--
----#include "cscore.h" -void cscore(CSOUND *cs) -{ - EVLIST *a; /* a is allowed to point to an event list */ - a = cscoreListGetSection(cs); /* read events in, return the list pointer */ - cscoreListPut(cs, a); /* write these events out (unchanged) */ - cscorePutString(cs, "e"); /* write the string e to output */ -}--
-- After execution of cscoreListGetSection(), the variable a points to a list of event addresses, each of which points to a stored event. We have used that same pointer to enable another list function -- cscoreListPut() -- to access and write out all of the events that were read. If we now define another symbol e to be an event pointer, then the statement - -
---e = a->e[4];-- - will set it to the contents of the 4th slot in the EVLIST structure, a. The contents is a pointer to an event, which is itself comprised of an array of parameter field values. Thus the term e->p[5] will mean the value of parameter field 5 of the 4th event in the EVLIST denoted by a. The program below will multiply the value of that pfield by 2 before writing it out. -
--
----#include "cscore.h" -void cscore(CSOUND *cs) -{ - EVENT *e; /* a pointer to an event */ - EVLIST *a; - a = cscoreListGetSection(cs); /* read a score as a list of events */ - e = a->e[4]; /* point to event 4 in event list a */ - e->p[5] *= 2; /* find pfield 5, multiply its value by 2 */ - cscoreListPut(cs, a); /* write out the list of events */ - cscorePutString(cs, "e"); /* add a "score end" statement */ -}--
-- Now consider the following score, in which p[5] contains frequency in Hz. - -
----f 1 0 257 10 1 -f 2 0 257 7 0 300 1 212 .8 -i 1 1 3 0 440 10000 -i 1 4 3 0 256 10000 -i 1 7 3 0 880 10000 -e--
-- If this score were given to the preceding main program, the resulting output would look like this: - -
----f 1 0 257 10 1 -f 2 0 257 7 0 300 1 212 .8 -i 1 1 3 0 440 10000 -i 1 4 3 0 512 10000 ; p[5] has become 512 instead of 256. -i 1 7 3 0 880 10000 -e--
-- Note that the 4th event is in fact the second note of the score. So far we have not distinguished between notes and function table setup in a numeric score. Both can be classed as events. Also note that our 4th event has been stored in e[4] of the structure. For compatibility with Csound pfield notation, we will ignore p[0] and e[0] of the event and list structures, storing p1 in p[1], event 1 in e[1], etc. The Cscore functions all adopt this convention. -
-- As an extension to the above, we could decide to use the same pointers a and e to examine each of the events in the list. Note that e was not set to the numeral 4, but to the location of the 4th slot in the list. To inspect p5 of the previous event in the list, we need only redefine e with the assignment - -
---e = a->e[3];-- -and reference the 5th slot of the pfield array using the expression - -
---e->p[5]--
-- More generally, we can use an integer variable as an index to the array e[], and access each event in sequence by using a loop and incrementing the index. The number of events stored in an EVLIST is contained in the nevents member of the struct. -
--
----int index; /* start with e[1] because e[0] is not used */ -for (index = 1; index <= a->nevents; index++) -{ - e = a->e[index]; - /* do something with e */ -}--
-- The above example starts with e[1] and increases the index each time through the loop (index++) until it is greater than a->nevents, the index of the last event in the list. The statements inside the for loop do execute a final time when index equals a->nevents. -
-- In the following program we will use the same input score. This time we will separate the ftable statements from the note statements. We will next write the three note-events stored in the list a to the output, then create a second score section consisting of the original pitch set and a transposed version of itself. This will bring about an octave doubling. -
-- Here, our index to the array is n and we increment n as part of a for block which iterates nevents times, allowing one statement to act upon the same pfield of each successive event. -
--
----#include "cscore.h" -void cscore(CSOUND *cs) -{ - EVENT *e, *f; - EVLIST *a, *b; - int n; - - a = cscoreListGetSection(cs); /* read score into event list "a" */ - b = cscoreListSeparateF(cs, a); /* separate f statements */ - cscoreListPut(cs, b); /* write f statements out to score */ - cscoreListFreeEvents(cs, b); /* and release the spaces used */ - e = cscoreDefineEvent(cs, "t 0 120"); /* define event for tempo statement */ - cscorePutEvent(cs, e); /* write tempo statement to score */ - cscoreListPut(cs, a); /* write the notes */ - cscorePutString(cs, "s"); /* section end */ - cscorePutEvent(cs, e); /* write tempo statement again */ - b = cscoreListCopyEvents(cs, a); /* make a copy of the notes in "a" */ - for (n = 1; n <= b->nevents; n++) /* iterate the following lines nevents times: */ - { - f = b->e[n]; - f->p[5] *= 0.5; /* transpose pitch down one octave */ - } - a = cscoreListAppendList(cs, a, b); /* now add these notes to original pitches */ - cscoreListPut(cs, a); - cscorePutString(cs, "e"); -}--
-- The output of this program is: -
--
----f 1 0 257 10 1 -f 2 0 257 7 0 300 1 212 .8 -t 0 120 -i 1 1 3 0 440 10000 -i 1 4 3 0 256 10000 -i 1 7 3 0 880 10000 -s -t 0 120 -i 1 1 3 0 440 10000 -i 1 4 3 0 256 10000 -i 1 7 3 0 880 10000 -i 1 1 3 0 220 10000 -i 1 4 3 0 128 10000 -i 1 7 3 0 440 10000 -e--
-- If the output is only being written to a file, then the unsorted order of the events is not a problem. The output is written to a file (or standard output) whenever the function cscoreListPut() is used. However, if this program were to be called during a Csound performance and the function cscoreListPlay() replaced cscoreListPut(), then the events would be sent to the orchestra instead of to a file and they should then be sorted beforehand by calling the function cscoreListSort(). The details of score output and playing when using Cscore from within Csound are described in the next section. -
-- Next we extend the above program by using the for loop to look at p[5] and p[6]. In the original score p[6] denotes amplitude. To create a diminuendo in the added lower octave, which is independent from the original set of notes, a variable called dim will be used. -
--
----#include "cscore.h" -void cscore(CSOUND *cs) -{ - EVENT *e, *f; - EVLIST *a, *b; - int n, dim; /* declare two integer variables */ - - a = cscoreListGetSection(cs); - b = cscoreListSeparateF(cs, a); - cscoreListPut(cs, b); - cscoreListFreeEvents(cs, b); - e = cscoreDefineEvent(cs, "t 0 120"); - cscorePutEvent(cs, e); - cscoreListPut(cs, a); - cscorePutString(cs, "s"); - cscorePutEvent(cs, e); /* write out another tempo statement */ - b = cscoreListCopyEvents(cs, a); - dim = 0; /* initialize dim to 0 */ - for (n = 1; n <= b->nevents; n++) - { - f = b->e[n]; - f->p[6] -= dim; /* subtract current value of dim */ - f->p[5] *= 0.5; /* transpose pitch down one octave */ - dim += 2000; /* increase dim for each note */ - } - a = cscoreListAppendList(cs, a, b); /* now add these notes to original pitches */ - cscoreListPut(cs, a); - cscorePutString(cs, "e"); -}--
-- Using the same input score again, the output from this program is: - -
----f 1 0 257 10 1 -f 2 0 257 7 0 300 1 212 .8 -t 0 120 -i 1 1 3 0 440 10000 -i 1 4 3 0 256 10000 -i 1 7 3 0 880 10000 -s -t 0 120 -i 1 1 3 0 440 10000 ; Three original notes at -i 1 4 3 0 256 10000 ; beats 1,4 and 7 with no dim. -i 1 7 3 0 880 10000 -i 1 1 3 0 220 10000 ; three notes transposed down one octave -i 1 4 3 0 128 8000 ; also at beats 1,4 and 7 with dim. -i 1 7 3 0 440 6000 -e--
-- In the following program the same three-note sequence will be repeated at various time intervals. The starting time of each group is determined by the values of the array cue. This time the dim will occur for each group of notes rather than each note. Note the position of the statement which increments the variable dim outside the inner for loop. -
--
----#include "cscore.h" -int cue[3] = {0,10,17}; /* declare an array of 3 integers */ -void cscore(CSOUND *cs) -{ - EVENT *e, *f; - EVLIST *a, *b; - int n, dim, cuecount; /* declare new variable cuecount */ - - a = cscoreListGetSection(cs); - b = cscoreListSeparateF(cs, a); - cscoreListPut(cs, b); - cscoreListFreeEvents(cs, b); - e = cscoreDefineEvent(cs, "t 0 120"); - cscorePutEvent(cs, e); - dim = 0; - for (cuecount = 0; cuecount <= 2; cuecount++) /* elements of cue are numbered 0, 1, 2 */ - { - for (n = 1; n <= a->nevents; n++) - { - f = a->e[n]; - f->p[6] -= dim; - f->p[2] += cue[cuecount]; /* add values of cue */ - } - printf("; diagnostic: cue = %d\n", cue[cuecount]); - dim += 2000; - cscoreListPut(cs, a); - } - cscorePutString(cs, "e"); -}--
-- Here the inner for loop looks at the events of list a (the notes) and the outer for loop looks at each repetition of the events of list a (the pitch group "cues"). This program also demonstrates a useful trouble-shooting device with the printf function. The semi-colon is first in the character string to produce a comment statement in the resulting score file. In this case the value of cue is being printed in the output to insure that the program is taking the proper array member at the proper time. When output data is wrong or error messages are encountered, the printf function can help to pinpoint the problem. -
-- Using the same input file, the C program above will generate the following score. Can you determine why the last set of notes starts at the wrong time and how to correct the problem? -
--
----f 1 0 257 10 1 -f 2 0 257 7 0 300 1 212 .8 -t 0 120 -; diagnostic: cue = 0 -i 1 1 3 0 440 10000 -i 1 4 3 0 256 10000 -i 1 7 3 0 880 10000 -; diagnostic: cue = 10 -i 1 11 3 0 440 8000 -i 1 14 3 0 256 8000 -i 1 17 3 0 880 8000 -; diagnostic: cue = 17 -i 1 28 3 0 440 4000 -i 1 31 3 0 256 4000 -i 1 34 3 0 880 4000 -e--
-Cscore - - - - - - - - - - -- -- - - diff --git a/DeprecatedTop.html b/DeprecatedTop.html index 420cbaecb2f..6cd0f877fd2 100644 --- a/DeprecatedTop.html +++ b/DeprecatedTop.html @@ -10,7 +10,7 @@ - +- - Cscore is an API (application programming interface) for generating and manipulating numeric score files. It is a part of the larger Csound API and includes a number of functions that can be called by a user-designed program written in the C language. Cscore can be invoked either as a standalone score preprocessor, or as part of a Csound performance by including the -C flag in its arguments: -
--
----
cscore[scorefilein] [> scorefileout]-
-(where cscore is the name of your user-written program), or
--
----
csound[-C] [otherflags] [orchname] [scorename]-
-- The available API functions augment the C language library functions; they can read either standard numeric scores or pre-sorted score files, can massage and expand the data in various ways, then make it available for performance by a Csound orchestra. -
-- The user-written control program is written in C, and is compiled and linked to the Csound library (or the csound commandline program) by the user. It is not essential to know the C language well to write this program, since the function calls have a simple syntax, and are powerful enough to do most of the complicated work. Additional power can come from C later as the need arises. -
-- The following sections explain all of the steps needed to make use of Cscore: -
----
-- Events, Lists, and Operations - Explains the syntax of Cscore functions and data structures.
-- Writing a Cscore Control Program - Illustrates by example how to write your own control program.
-- Compiling a Cscore Program - Outlines the steps for compiling and linking with the Csound library.
-- More Advanced Examples - Addresses advanced issues such as multiple input scores and the details of running Cscore inside of a Csound performance.
-- --- An event in Cscore is equivalent to one statement of a standard numeric score or a time-warped score (the format in which Csound writes a sorted score -- see any score.srt), and is stored internally in time-warped format. It is important to note that when Cscore is used in standalone-mode, it cannot understand any of the non-numeric "conveniences" that Csound allows in the input score format. Therefore, scores making use of features such as carry, ramp, expressions, and others will have to either be sorted first with the scsort utility or used with a modified Csound executable that contains the user's Cscore program. Score opcodes with macro arguments (r, m, n, and {}) are not understood. -
--Score events are each read in from an existing score file and stored in a C structure. The structures main components are an opcode and an array of pfield values. Cscore handles reading the events and storing them in memory for you. The format of the structure starts as follows: -
--
----typedef struct { - CSHDR h; /* space-managing header */ - char *strarg; /* address of optional string argument */ - char op; /* opcode-t, w, f, i, a, s or e */ - short pcnt; - MYFLT p2orig; /* unwarped p2, p3 */ - MYFLT p3orig; - MYFLT p[1]; /* array of pfields p0, p1, p2 ... */ -} EVENT;--
--MYFLT is either the C type float or double depending on how your copy of the Csound library was compiled. You should just declare any floating-point variables as MYFLT in your user program for compatibility. -
-- Any Cscore function that creates, reads, or copies an event will return a pointer to the storage structure holding the event data. The event pointer can be used to access any component of the structure, in the form of e->op or e->p[n]. Each newly stored event will give rise to a new pointer, and a sequence of new events will generate a sequence of distinct pointers that must themselves be stored. Groups of event pointers are stored in an event list, which has its own structure: -
--
----typedef struct { - CSHDR h; - int nslots; /* max events in this event list */ - int nevents; /* number of events present */ - EVENT *e[1]; /* array of event pointers e0, e1, e2.. */ -} EVLIST;--
-- Any Cscore function that creates or modifies a list will return a pointer to the new list. The list pointer can be used to access any of its component event pointers, in the form of a->e[n]. Event pointers and list pointers are thus primary tools for manipulating the data of a score file. Pointers and lists of pointers can be copied and reordered without modifying the data values they refer to. This means that notes and phrases can be copied and manipulated from a high level of control. Alternatively, the data within an event or group of events can be modified without changing the event or list pointers. The Cscore API functions enable scores to be created and manipulated in this way. -
--With Csound 5, the names of all of the Cscore API functions have changed to be more explicit. In addition, each function now requires a pointer to a CSOUND object as its first argument. The structure of the CSOUND object is unimportant (and indeed cannot be modified in a user program). How to obtain this CSOUND pointer will be shown in the next section. The Cscore functions and data structures are available in the
-cscore.hheader file, which you must include in your program code before you can you use them. --The names of the Cscore functions specify whether they operate on single events or event lists. In the following summary of available function calls, some simple naming conventions are used: -
--
----The symbol cs is a pointer to a CSOUND object (CSOUND *); -The symbols e, f are pointers to events (notes); -The symbols a, b are pointers to lists (arrays) of such events; -The symbol n is an integer parameter of type int; -"..." indicates a string parameter (either a constant or variable of type char *); -The symbol fp is a score input stream file pointer (FILE *); - -calling syntax description --------------- ----------- -/* Functions for working with single events */ -e = cscoreCreateEvent(cs, n); create a blank event with n pfields -e = cscoreDefineEvent(cs, "..."); defines an event as per the character string ... -e = cscoreCopyEvent(cs, f); make a new copy of event f -e = cscoreGetEvent(cs); read the next event in the score input file - cscorePutEvent(cs, e); write event e to the score output file - cscorePutString(cs, "..."); write the string-defined event to score output - -/* Functions for working with event lists */ -a = cscoreListCreate(cs, n); create an empty event list with n slots -a = cscoreListAppendEvent(cs, a, e); append event e to list a -a = cscoreListAppendStringEvent(cs, a, "..."); append a string-defined event to list a; -a = cscoreListCopy(cs, b); copy the list b (but not the events) -a = cscoreListCopyEvents(cs, b); copy the events of b, making a new list -a = cscoreListGetSection(cs); read all events from score input, up to next s or e -a = cscoreListGetNext(cs, nbeats); read next nbeats beats from score input (nbeats is MYFLT) -a = cscoreListGetUntil(cs, beatno); read all events from score input up to beat beatno (MYFLT) -a = cscoreListSeparateF(cs, b); separate the f statements from list b into list a -a = cscoreListSeparateTWF(cs, b); separate the t,w & f statements from list b into list a -a = cscoreListAppendList(cs, a, b); append the list b onto the list a -a = cscoreListConcatenate(cs, a, b); concatenate (append) the list b onto the list a (same as previous) - cscoreListSort(cs, a); sort the list a into chronological order by p[2] -n = cscoreListCount(cs, a); returns the number of events in list a -a = cscoreListExtractInstruments(cs, b, "..."); extract notes of instruments ... (no new events) -a = cscoreListExtractTime(cs, b, from, to); extract notes of time-span, creating new events (from and to are MYFLT) - cscoreListPut(cs, a); write the events of list a to the score output file - cscoreListPlay(cs, a); send events of list a to the Csound orchestra for - immediate performance (or print events if no orchestra) -/* Functions for reclaiming memory */ - cscoreFreeEvent(cs, e); release the space of event e - cscoreListFree(cs, a); release the space of list a (but not the events) - cscoreListFreeEvents(cs, a); release the events of list a, and the list space - -/* Functions for working with multiple input score files */ -fp = cscoreFileGetCurrent(cs); get the currently active input scorefile pointer - (initially finds the command-line input scorefile pointer) -fp = cscoreFileOpen(cs, "filename"); open another input scorefile (maximum of 5) - cscoreFileSetCurrent(cs, fp); make fp the currently active scorefile pointer - cscoreFileClose(cs, fp); close the scorefile relating to FILE *fp--
--Under Csound 4, the function names and parameters were as follows: -
--
----calling syntax description --------------- ----------- -e = createv(n); create a blank event with n pfields -e = defev("..."); defines an event as per the character string ... -e = copyev(f); make a new copy of event f -e = getev(); read the next event in the score input file -putev(e); write event e to the score output file -putstr("..."); write the string-defined event to score output -a = lcreat(n); create an empty event list with n slots - int n; -a = lappev(a,e); append event e to list a -a = lappstrev(a,"..."); append a string-defined event to list a; -a = lcopy(b); copy the list b (but not the events) -a = lcopyev(b); copy the events of b, making a new list -a = lget(); read all events from score input, up to next s or e -a = lgetnext(nbeats); read next nbeats beats from score input - float nbeats; -a = lgetuntil(beatno); read all events from score input up to beat beatno - float beatno; -a = lsepf(b); separate the f statements from list b into list a -a = lseptwf(b); separate the t,w & f statements from list b into list a -a = lcat(a,b); concatenate (append) the list b onto the list a -lsort(a); sort the list a into chronological order by p[2] -a = lxins(b,"..."); extract notes of instruments ... (no new events) -a = lxtimev(b,from,to); extract notes of time-span, creating new events - float from, to; -lput(a); write the events of list a to the score output file -lplay(a); send events of list a to the Csound orchestra for - immediate performance (or print events if no orchestra) -relev(e); release the space of event e -lrel(a); release the space of list a (but not the events) -lrelev(a); release the events of list a, and the list space -fp = getcurfp(); get the currently active input scorefile pointer - (initially finds the command-line input scorefile pointer) -fp = filopen("filename"); open another input scorefile (maximum of 5) -setcurfp(fp); make fp the currently active scorefile pointer -filclose(fp); close the scorefile relating to FILE *fp--
-
@@ -58,14 +58,14 @@Deprecate
Up -Next +Next cudasliding Home -abetarand +array
- +Description
Plugin opcode in widgets. This opcode is part of the plugin repository and has to be installed separately. These FLTK widgets do not work on the Mac. @@ -49,16 +49,16 @@
Description
- +Syntax
ihandle FLbox "label", itype, ifont, isize, iwidth, iheight, ix, iy [, image]ihandle FLbox istr, itype, ifont, isize, iwidth, iheight, ix, iy [, image]- +Initialization
- ihandle -- a handle value (an integer number) that unequivocally references a corresponding widget. This is used by other opcodes that modify a widget's properties (see Modifying FLTK Widget Appearance). It is automatically output by FLbox and must not be set by the user label. (The user label is a double-quoted string containing some user-provided text placed near the widget.) + ihandle -- a handle value (an integer number) that unequivocally references a corresponding widget. This is used by other opcodes that modify a widget's properties (see Modifying FLTK Widget Appearance). It is automatically output by FLbox and must not be set by the user label. (The user label is a double-quoted string containing some user-provided text placed near the widget.)
“label” -- a double-quoted string containing some user-provided text, placed near corresponding widget. @@ -266,7 +266,7 @@
Initialization
- +Performance
FLbox is useful to show some text in a window. The text is bounded by a box, whose aspect depends on itype argument. @@ -276,21 +276,21 @@
Performance
- +Examples
Here is an example of the FLbox opcode. It uses the file FLbox.csd.
- +- Example 310. Example of the FLbox opcode. + Example 312. Example of the FLbox opcode.
See the sections Real-time Audio and Command Line Flags for more information on using command line flags.
- +Credits
Author: Gabriel Maldonado
New in version 4.22
diff --git a/FLbutBank.html b/FLbutBank.html index f909750e607..6653e54c71a 100644 --- a/FLbutBank.html +++ b/FLbutBank.html @@ -39,7 +39,7 @@
- +Description
Plugin opcode in widgets. This opcode is part of the plugin repository and has to be installed separately. These FLTK widgets do not work on the Mac. @@ -49,16 +49,16 @@
Description
- +Syntax
kout, ihandle FLbutBank itype, inumx, inumy, iwidth, iheight, ix, iy, \ iopcode [, kp1] [, kp2] [, kp3] [, kp4] [, kp5] [....] [, kpN]- +Initialization
- ihandle -- a handle value (an integer number) that unequivocally references a corresponding widget. This is used by other opcodes that modify a widget's properties (see Modifying FLTK Widget Appearance). It is automatically output by FLbutBank and must not be set by the user label. (The user label is a double-quoted string containing some user-provided text placed near the widget.) + ihandle -- a handle value (an integer number) that unequivocally references a corresponding widget. This is used by other opcodes that modify a widget's properties (see Modifying FLTK Widget Appearance). It is automatically output by FLbutBank and must not be set by the user label. (The user label is a double-quoted string containing some user-provided text placed near the widget.)
itype -- an integer number denoting the appearance of the widget. The valid numbers are: @@ -99,7 +99,7 @@
Initialization
- +Performance
kout -- output value @@ -135,28 +135,28 @@
Performance
FLbutBank not only outputs a value but can also activate (or schedule) an instrument provided by the user each time a button is pressed. If the iopcode argument is set to a negative number, no instrument is activated so this feature is optional. In order to activate an instrument, iopcode must be set to 0 or to 105 (the ascii code of character “i”, referring to the i score opcode). P-fields of the activated instrument are kp1 (instrument number), kp2 (action time), kp3 (duration) and so on with user p-fields.- The itype argument sets the type of buttons identically to the FLbutton opcode. By adding 10 to the itype argument (i.e. by setting 11 for type 1, 12 for type 2, 13 for type 3 and 14 for type 4), it is possible to skip the current FLbutBank value when getting/setting snapshots (see General FLTK Widget-related Opcodes). You can also add 10 to "plastic" button types (31 for type 1, 32 for type 2, etc.) + The itype argument sets the type of buttons identically to the FLbutton opcode. By adding 10 to the itype argument (i.e. by setting 11 for type 1, 12 for type 2, 13 for type 3 and 14 for type 4), it is possible to skip the current FLbutBank value when getting/setting snapshots (see General FLTK Widget-related Opcodes). You can also add 10 to "plastic" button types (31 for type 1, 32 for type 2, etc.)
FLbutBank is very useful to retrieve snapshots.
- +Examples
Here is an example of the FLbutBank opcode. It uses the file FLbutBank.csd.
- +- Example 311. Example of the FLbutBank opcode. + Example 313. Example of the FLbutBank opcode.
See the sections Real-time Audio and Command Line Flags for more information on using command line flags.
- +Credits
Author: Gabriel Maldonado
New in version 4.22
diff --git a/FLbutton.html b/FLbutton.html index edf3f3de5d8..2840b8a274a 100644 --- a/FLbutton.html +++ b/FLbutton.html @@ -39,7 +39,7 @@
- +Description
Plugin opcode in widgets. This opcode is part of the plugin repository and has to be installed separately. These FLTK widgets do not work on the Mac. @@ -49,16 +49,16 @@
Description
- +Syntax
kout, ihandle FLbutton "label", ion, ioff, itype, iwidth, iheight, ix, \ iy, iopcode [, kp1] [, kp2] [, kp3] [, kp4] [, kp5] [....] [, kpN]- +Initialization
- ihandle -- a handle value (an integer number) that unequivocally references a corresponding widget. This is used by other opcodes that modify a widget's properties (see Modifying FLTK Widget Appearance). It is automatically output by FLbutton and must not be set by the user label. (The user label is a double-quoted string containing some user-provided text placed near the widget.) + ihandle -- a handle value (an integer number) that unequivocally references a corresponding widget. This is used by other opcodes that modify a widget's properties (see Modifying FLTK Widget Appearance). It is automatically output by FLbutton and must not be set by the user label. (The user label is a double-quoted string containing some user-provided text placed near the widget.)
“label” -- a double-quoted string containing some user-provided text, placed near the corresponding widget. @@ -158,7 +158,7 @@
Initialization
- +Examples
- Here is an example of the FLbutton opcode. It uses the file FLbutton.csd, and beats.wav. + Here is an example of the FLbutton opcode. It uses the file FLbutton.csd, and drumsMlp.wav.
- +- Example 312. Example of the FLbutton opcode. + Example 314. Example of the FLbutton opcode.
See the sections Real-time Audio and Command Line Flags for more information on using command line flags.
- +<CsoundSynthesizer> <CsOptions> @@ -258,7 +258,7 @@Examples
maxalloc insnum, icount instr 1 - asig diskin2 "beats.wav", p4, 0, 1 + asig diskin2 "drumsMlp.wav", p4, 0, 1 outs asig, asig endin @@ -285,7 +285,7 @@Examples
- +Credits
Author: Gabriel Maldonado
New in version 4.22
diff --git a/FLcloseButton.html b/FLcloseButton.html index c470ffa6327..f0b9c7ab970 100644 --- a/FLcloseButton.html +++ b/FLcloseButton.html @@ -40,7 +40,7 @@
- +Description
Plugin opcode in widgets. This opcode is part of the plugin repository and has to be installed separately. These FLTK widgets do not work on the Mac. @@ -51,15 +51,15 @@
Description
- +Initialization
- ihandle -- a handle value (an integer number) that unequivocally references a corresponding widget. This is used by other opcodes that modify a widget's properties (see Modifying FLTK Widget Appearance). It is automatically output by FLcloseButton and must not be set by the user label. (The user label is a double-quoted string containing some user-provided text placed near the widget.) + ihandle -- a handle value (an integer number) that unequivocally references a corresponding widget. This is used by other opcodes that modify a widget's properties (see Modifying FLTK Widget Appearance). It is automatically output by FLcloseButton and must not be set by the user label. (The user label is a double-quoted string containing some user-provided text placed near the widget.)
“label” -- a double-quoted string containing some user-provided text, placed near the corresponding widget. @@ -112,7 +112,7 @@
Initialization
- +Credits
Author: Steven Yi
New in version 5.05
diff --git a/FLcolor.html b/FLcolor.html index 40ba0ffce1a..f75c5e426d7 100644 --- a/FLcolor.html +++ b/FLcolor.html @@ -39,7 +39,7 @@
- +Description
Plugin opcode in widgets. This opcode is part of the plugin repository and has to be installed separately. These FLTK widgets do not work on the Mac. @@ -49,12 +49,12 @@
Description
- +Initialization
ired -- The red color of the target widget. The range for each RGB component is 0-255 @@ -76,7 +76,7 @@
Initialization
- +Performance
These opcodes modify the appearance of other widgets. There are @@ -93,7 +93,7 @@
Performance
- +Credits
Author: Gabriel Maldonado
New in version 4.22
diff --git a/FLcolor2.html b/FLcolor2.html index aaccce6b5ce..e4815577238 100644 --- a/FLcolor2.html +++ b/FLcolor2.html @@ -39,7 +39,7 @@
- +Description
Plugin opcode in widgets. This opcode is part of the plugin repository and has to be installed separately. These FLTK widgets do not work on the Mac. @@ -49,12 +49,12 @@
Description
- +Initialization
ired -- The red color of the target widget. The range for each RGB component is 0-255 @@ -67,7 +67,7 @@
Initialization
- +Performance
These opcodes modify the appearance of other widgets. There are @@ -78,7 +78,7 @@
Performance
- +Credits
Author: Gabriel Maldonado
New in version 4.22
diff --git a/FLcount.html b/FLcount.html index 9561d98821e..d7ab6bb41a3 100644 --- a/FLcount.html +++ b/FLcount.html @@ -39,7 +39,7 @@
- +Description
Plugin opcode in widgets. This opcode is part of the plugin repository and has to be installed separately. These FLTK widgets do not work on the Mac. @@ -49,13 +49,13 @@
Description
- +Syntax
kout, ihandle FLcount "label", imin, imax, istep1, istep2, itype, \ iwidth, iheight, ix, iy, iopcode [, kp1] [, kp2] [, kp3] [...] [, kpN]- +Initialization
ihandle -- a handle value (an integer number) that unequivocally references a corresponding widget. Used by further opcodes that changes some valuator's properties. It is automatically set by the corresponding valuator. @@ -95,7 +95,7 @@
Initialization
- +Examples
Here is an example of the FLcount opcode. It uses the file FLcount.csd.
- +- Example 313. Example of the FLcount opcode. + Example 315. Example of the FLcount opcode.
See the sections Real-time Audio and Command Line Flags for more information on using command line flags.
- +Initialization
ihandle -- a handle value (an integer number) that unequivocally references a corresponding widget. This is used by other opcodes that modify a widget's properties (see - Modifying FLTK Widget Appearance). It is automatically output by FLexecButton. + Modifying FLTK Widget Appearance). It is automatically output by FLexecButton.
“command” -- a double-quoted string containing a command to execute. @@ -105,21 +105,21 @@
Initialization
- +Examples
Here is an example of the FLexecButton opcode. It uses the file FLexecButton.csd.
- +- Example 314. Example of the FLexecButton opcode. + Example 316. Example of the FLexecButton opcode.
See the sections Real-time Audio and Command Line Flags for more information on using command line flags.
- +<CsoundSynthesizer> @@ -150,8 +150,8 @@Examples
;;; set FLexecButton colour FLcolor 255, 255, 0 ;;; when this button is pressed, fourier analysis is performed on the file -;;; "beats.wav", producing the analysis file "beats.pvx" - gipvoc FLexecButton "csound -U pvanal beats.wav beats.pvx", 60, 20, 20, 20 +;;; "drumsMlp.wav", producing the analysis file "beats.pvx" + gipvoc FLexecButton "csound -U pvanal drumsMlp.wav beats.pvx", 60, 20, 20, 20 ;;; set FLexecButton text FLsetText "PVOC", gipvoc ;;; when this button is pressed, instr 10000 is called, exiting @@ -249,7 +249,7 @@Examples
- +Credits
Author: Steven Yi
Example by: Jonathan Murphy
diff --git a/FLgetsnap.html b/FLgetsnap.html index 3e716babc97..7d28316deaa 100644 --- a/FLgetsnap.html +++ b/FLgetsnap.html @@ -39,7 +39,7 @@
- +Credits
Author: Gabriel Maldonado
New in version 4.22
diff --git a/FLgroup.html b/FLgroup.html index e48a3b5ac9e..c536e23bd88 100644 --- a/FLgroup.html +++ b/FLgroup.html @@ -39,7 +39,7 @@
- +Performance
Containers are useful to format the graphic appearance of the widgets. The most important container is FLpanel, that actually creates a window. It can be filled with other containers and/or valuators or other kinds of widgets. @@ -139,7 +139,7 @@
Performance
- +Credits
Author: Gabriel Maldonado
New in version 4.22
diff --git a/FLgroupEnd.html b/FLgroupEnd.html index 41914a8b31d..11d677c5236 100644 --- a/FLgroupEnd.html +++ b/FLgroupEnd.html @@ -39,7 +39,7 @@
- +Description
Plugin opcode in widgets. This opcode is part of the plugin repository and has to be installed separately. These FLTK widgets do not work on the Mac. @@ -49,7 +49,7 @@
Description
- +Performance
Containers are useful to format the graphic appearance of the widgets. The most important container is FLpanel, that actually creates a window. It can be filled with other containers and/or valuators or other kinds of widgets. @@ -68,7 +68,7 @@
Performance
- +Credits
Author: Gabriel Maldonado
New in version 4.22
diff --git a/FLgroup_end.html b/FLgroup_end.html index fc820464c09..b1bf3d64fd9 100644 --- a/FLgroup_end.html +++ b/FLgroup_end.html @@ -39,7 +39,7 @@
- +Description
Plugin opcode in widgets. This opcode is part of the plugin repository and has to be installed separately. These FLTK widgets do not work on the Mac. @@ -51,7 +51,7 @@
Description
- +Credits
Author: Gabriel Maldonado
New in version 4.22
diff --git a/FLhide.html b/FLhide.html index c846fcda8bb..191c795a34a 100644 --- a/FLhide.html +++ b/FLhide.html @@ -39,7 +39,7 @@
- +Description
Plugin opcode in widgets. This opcode is part of the plugin repository and has to be installed separately. These FLTK widgets do not work on the Mac. @@ -49,26 +49,26 @@
Description
- +Initialization
- ihandle -- a handle value (an integer number) that unequivocally references a corresponding widget. This is used by other opcodes that modify a widget's properties (see Modifying FLTK Widget Appearance). + ihandle -- a handle value (an integer number) that unequivocally references a corresponding widget. This is used by other opcodes that modify a widget's properties (see Modifying FLTK Widget Appearance).
- +Credits
Author: Gabriel Maldonado
New in version 4.22
diff --git a/FLhvsBox.html b/FLhvsBox.html index 225eae87177..c65558056df 100644 --- a/FLhvsBox.html +++ b/FLhvsBox.html @@ -39,7 +39,7 @@
- +Description
Plugin opcode in widgets. This opcode is part of the plugin repository and has to be installed separately. These FLTK widgets do not work on the Mac. @@ -49,12 +49,12 @@
Description
- +Initialization
ihandle – an integer number used a univocally-defined handle for identifying a specific HVS box (see below). @@ -70,7 +70,7 @@
Initialization
- +Performance
FLhvsBox is a widget able to visualize current position of the HVS cursor in an HVS box (i.e. a squared area containing a grid). The number of horizontal and vertical lines of the grid can be defined with the inumlinesX, inumlinesY arguments. This opcode has to be declared inside an FLpanel - FLpanelEnd block. See the entry for hvs2 for an example of usage of FLhvsBox. @@ -80,7 +80,7 @@
Performance
- +Credits
Author: Gabriel Maldonado
New in version 5.06
diff --git a/FLhvsBoxSetValue.html b/FLhvsBoxSetValue.html index 3ac8e14d5dc..47cd68c5223 100644 --- a/FLhvsBoxSetValue.html +++ b/FLhvsBoxSetValue.html @@ -39,7 +39,7 @@
- +Description
Plugin opcode in widgets. This opcode is part of the plugin repository and has to be installed separately. These FLTK widgets do not work on the Mac. @@ -49,19 +49,19 @@
Description
- +Initialization
ihandle – an integer number used a univocally-defined handle for identifying a specific HVS box (see below).
- +Performance
kx, ky– the coordinates of the HVS cursor position to be set. @@ -73,7 +73,7 @@
Performance
See the entry for hvs2 for an example of usage of FLhvsBoxSetValue.- +Credits
Author: Gabriel Maldonado
New in version 5.06
diff --git a/FLjoy.html b/FLjoy.html index 6cd4f8ea54e..224b60a55bd 100644 --- a/FLjoy.html +++ b/FLjoy.html @@ -39,7 +39,7 @@
- +Description
Plugin opcode in widgets. This opcode is part of the plugin repository and has to be installed separately. These FLTK widgets do not work on the Mac. @@ -49,13 +49,13 @@
Description
- +Syntax
koutx, kouty, ihandlex, ihandley FLjoy "label", iminx, imaxx, iminy, \ imaxy, iexpx, iexpy, idispx, idispy, iwidth, iheight, ix, iy- +Initialization
ihandlex -- a handle value (an integer number) that unequivocally references a corresponding widget. Used by further opcodes that changes some valuator's properties. It is automatically set by the corresponding valuator. @@ -157,7 +157,7 @@
Initialization
- +Examples
Here is an example of the FLjoy opcode. It uses the file FLjoy.csd.
- +- Example 315. Example of the FLjoy opcode. + Example 317. Example of the FLjoy opcode.
See the sections Real-time Audio and Command Line Flags for more information on using command line flags.
- +Credits
Author: Gabriel Maldonado
New in version 4.22
diff --git a/FLkeyIn.html b/FLkeyIn.html index 56ba90c14ad..97bbadc38a9 100644 --- a/FLkeyIn.html +++ b/FLkeyIn.html @@ -39,7 +39,7 @@
- +Examples
Here is an example of the FLkeyIn opcode. It uses the file FLkeyIn.csd.
- +- Example 316. Example of the FLkeyIn opcode. + Example 318. Example of the FLkeyIn opcode.
See the sections Real-time Audio and Command Line Flags for more information on using command line flags.
- +Credits
Author: Gabriel Maldonado
New in version 5.06
diff --git a/FLknob.html b/FLknob.html index 3d774c1b524..7ae2d22a05f 100644 --- a/FLknob.html +++ b/FLknob.html @@ -39,7 +39,7 @@
- +Description
Plugin opcode in widgets. This opcode is part of the plugin repository and has to be installed separately. These FLTK widgets do not work on the Mac. @@ -49,16 +49,16 @@
Description
- +Syntax
kout, ihandle FLknob "label", imin, imax, iexp, itype, idisp, iwidth, \ ix, iy [, icursorsize]- +Initialization
- ihandle -- a handle value (an integer number) that unequivocally references a corresponding widget. This is used by other opcodes that modify a widget's properties (see Modifying FLTK Widget Appearance). It is automatically utput by FLknob and must not be set by the user label. (The user label is a double-quoted string containing some user-provided text placed near the widget.) + ihandle -- a handle value (an integer number) that unequivocally references a corresponding widget. This is used by other opcodes that modify a widget's properties (see Modifying FLTK Widget Appearance). It is automatically utput by FLknob and must not be set by the user label. (The user label is a double-quoted string containing some user-provided text placed near the widget.)
“label” -- a double-quoted string containing some user-provided text, placed near the corresponding widget. @@ -189,7 +189,7 @@
Initialization
- +Examples
Here is an example of the FLknob opcode. It uses the file FLknob.csd.
- +- Example 317. Example of the FLknob opcode. + Example 319. Example of the FLknob opcode.
See the sections Real-time Audio and Command Line Flags for more information on using command line flags.
- +<CsoundSynthesizer> <CsOptions> @@ -293,13 +293,13 @@Examples
- +- Example 318. More complex example of the FLknob opcode. + Example 320. More complex example of the FLknob opcode.
- +Credits
Author: Gabriel Maldonado
New in version 4.22
diff --git a/FLlabel.html b/FLlabel.html index 238c3449fd9..c9760206403 100644 --- a/FLlabel.html +++ b/FLlabel.html @@ -39,7 +39,7 @@
- +Description
Plugin opcode in widgets. This opcode is part of the plugin repository and has to be installed separately. These FLTK widgets do not work on the Mac. @@ -49,12 +49,12 @@
Description
- +Initialization
isize -- size of the font of the target widget. Normal values are in the order of 15. Greater numbers enlarge font size, while smaller numbers reduce it. @@ -171,7 +171,7 @@
Initialization
- +Performance
FLlabel modifies a set of parameters related to the text label appearance of a widget, i.e. size, font, alignment and color of corresponding text. This opcode affects (almost) all widgets defined next its location. A user can put several instances of FLlabel in front of each widget he intends to modify. However, to modify a particular widget, it is better to use the opcode belonging to the second type (i.e. those containing the ihandle argument). @@ -181,7 +181,7 @@
Performance
- +Credits
Author: Gabriel Maldonado
New in version 4.22
diff --git a/FLloadsnap.html b/FLloadsnap.html index eb500bbc9cf..b8eac0d200b 100644 --- a/FLloadsnap.html +++ b/FLloadsnap.html @@ -39,7 +39,7 @@
- +Performance
FLloadsnap loads all snapshots contained in filename into the memory bank of current orchestra. @@ -91,7 +91,7 @@
Performance
- +Credits
Author: Gabriel Maldonado
New in version 4.22
diff --git a/FLmouse.html b/FLmouse.html index 357cc7fa06d..af1f529690b 100644 --- a/FLmouse.html +++ b/FLmouse.html @@ -39,7 +39,7 @@
- +Description
Plugin opcode in widgets. This opcode is part of the plugin repository and has to be installed separately. These FLTK widgets do not work on the Mac. @@ -49,12 +49,12 @@
Description
- +Initialization
imode – (optional, default = 0) Determines the mode for mouse location reporting. @@ -76,7 +76,7 @@
Initialization
- +Performance
kx, ky – the mouse coordinates, whose range depends on the imode argument (see above). @@ -88,21 +88,21 @@
Performance
- +Examples
Here is an example of the FLmouse opcode. It uses the file FLmouse.csd.
- +- Example 319. Example of the FLmouse opcode. + Example 321. Example of the FLmouse opcode.
See the sections Real-time Audio and Command Line Flags for more information on using command line flags.
- +Credits
Author: Gabriel Maldonado
New in version 5.06
diff --git a/FLpack.html b/FLpack.html index f9571c8dc37..6edf995b6ba 100644 --- a/FLpack.html +++ b/FLpack.html @@ -39,7 +39,7 @@
- +Description
Plugin opcode in widgets. This opcode is part of the plugin repository and has to be installed separately. These FLTK widgets do not work on the Mac. @@ -49,12 +49,12 @@
Description
- +Performance
FLpack provides the functionality of compressing and aligning widgets. @@ -138,7 +138,7 @@
Performance
- +Credits
Author: Gabriel Maldonado
New in version 4.22
diff --git a/FLpackEnd.html b/FLpackEnd.html index 2df82ef55c7..4a2d273f634 100644 --- a/FLpackEnd.html +++ b/FLpackEnd.html @@ -39,7 +39,7 @@
- +Description
Plugin opcode in widgets. This opcode is part of the plugin repository and has to be installed separately. These FLTK widgets do not work on the Mac. @@ -49,7 +49,7 @@
Description
- +Performance
Containers are useful to format the graphic appearance of the widgets. The most important container is FLpanel, that actually creates a window. It can be filled with other containers and/or valuators or other kinds of widgets. @@ -68,7 +68,7 @@
Performance
- +Credits
Author: Gabriel Maldonado
New in version 4.22
diff --git a/FLpack_end.html b/FLpack_end.html index 4e60ed36915..9dd9e97bd68 100644 --- a/FLpack_end.html +++ b/FLpack_end.html @@ -39,7 +39,7 @@
- +Description
Plugin opcode in widgets. This opcode is part of the plugin repository and has to be installed separately. These FLTK widgets do not work on the Mac. @@ -50,7 +50,7 @@
Description
for compatibility. See FLpackEnd- +Credits
Author: Gabriel Maldonado
New in version 4.22
diff --git a/FLpanel.html b/FLpanel.html index 20f69a6b390..a570c573cf9 100644 --- a/FLpanel.html +++ b/FLpanel.html @@ -39,7 +39,7 @@
- +Description
Plugin opcode in widgets. This opcode is part of the plugin repository and has to be installed separately. These FLTK widgets do not work on the Mac. @@ -49,12 +49,12 @@
Description
- +Initialization
“label” -- a double-quoted string containing some user-provided text, placed near the corresponding widget. @@ -113,7 +113,7 @@
Initialization
- +Performance
Containers are useful to format the graphic appearance of the widgets. The most important container is FLpanel, that actually creates a window. It can be filled with other containers and/or valuators or other kinds of widgets. @@ -151,21 +151,21 @@
Performance
- +Examples
Here is an example of the FLpanel opcode. It uses the file FLpanel.csd.
- +- Example 326. Example of the FLpanel opcode. + Example 329. Example of the FLpanel opcode.
See the sections Real-time Audio and Command Line Flags for more information on using command line flags.
- +Credits
Author: Gabriel Maldonado
New in version 4.22
diff --git a/FLpanelEnd.html b/FLpanelEnd.html index b88e6332d11..31fe34ac1a0 100644 --- a/FLpanelEnd.html +++ b/FLpanelEnd.html @@ -39,7 +39,7 @@
- +Description
Plugin opcode in widgets. This opcode is part of the plugin repository and has to be installed separately. These FLTK widgets do not work on the Mac. @@ -49,7 +49,7 @@
Description
- +Performance
Containers are useful to format the graphic appearance of the widgets. The most important container is FLpanel, that actually creates a window. It can be filled with other containers and/or valuators or other kinds of widgets. @@ -68,7 +68,7 @@
Performance
- +Credits
Author: Gabriel Maldonado
New in version 4.22
diff --git a/FLpanel_end.html b/FLpanel_end.html index 742e0292eb5..0ccd70b633e 100644 --- a/FLpanel_end.html +++ b/FLpanel_end.html @@ -39,7 +39,7 @@
- +Description
Plugin opcode in widgets. This opcode is part of the plugin repository and has to be installed separately. These FLTK widgets do not work on the Mac. @@ -52,7 +52,7 @@
Description
- +Credits
Author: Gabriel Maldonado
New in version 4.22
diff --git a/FLprintk.html b/FLprintk.html index 80c6fabd749..abbb09b51a0 100644 --- a/FLprintk.html +++ b/FLprintk.html @@ -39,7 +39,7 @@
- +Description
Plugin opcode in widgets. This opcode is part of the plugin repository and has to be installed separately. These FLTK widgets do not work on the Mac. @@ -49,12 +49,12 @@
Description
- +Initialization
itime -- how much time in seconds is to elapse between updated displays. @@ -67,7 +67,7 @@
Initialization
- +Credits
Author: Gabriel Maldonado
New in version 4.22
diff --git a/FLprintk2.html b/FLprintk2.html index d8a16b82fa2..22832775f2d 100644 --- a/FLprintk2.html +++ b/FLprintk2.html @@ -39,7 +39,7 @@
- +Description
Plugin opcode in widgets. This opcode is part of the plugin repository and has to be installed separately. These FLTK widgets do not work on the Mac. @@ -49,19 +49,19 @@
Description
- +Initialization
idisp -- a handle value that was output from a previous instance of the FLvalue opcode to display the current value of the current valuator in the FLvalue widget itself. If the user doesn't want to use this feature that displays current values, it must be set to a negative number by the user.
- +Credits
Author: Gabriel Maldonado
New in version 4.22
diff --git a/FLroller.html b/FLroller.html index e05868e0074..9c0ec596a60 100644 --- a/FLroller.html +++ b/FLroller.html @@ -39,7 +39,7 @@
- +Description
Plugin opcode in widgets. This opcode is part of the plugin repository and has to be installed separately. These FLTK widgets do not work on the Mac. @@ -49,16 +49,16 @@
Description
- +Syntax
kout, ihandle FLroller "label", imin, imax, istep, iexp, itype, idisp, \ iwidth, iheight, ix, iy- +Initialization
- ihandle -- a handle value (an integer number) that unequivocally references a corresponding widget. This is used by other opcodes that modify a widget's properties (see Modifying FLTK Widget Appearance). It is automatically output by FLroller and must not be set by the user label. (The user label is a double-quoted string containing some user-provided text placed near the widget.) + ihandle -- a handle value (an integer number) that unequivocally references a corresponding widget. This is used by other opcodes that modify a widget's properties (see Modifying FLTK Widget Appearance). It is automatically output by FLroller and must not be set by the user label. (The user label is a double-quoted string containing some user-provided text placed near the widget.)
“label” -- a double-quoted string containing some user-provided text, placed near the corresponding widget. @@ -147,7 +147,7 @@
Initialization
- +Examples
Here is an example of the FLroller opcode. It uses the file FLroller.csd.
- +- Example 327. Example of the FLroller opcode. + Example 330. Example of the FLroller opcode.
See the sections Real-time Audio and Command Line Flags for more information on using command line flags.
- +Credits
Author: Gabriel Maldonado
New in version 4.22
diff --git a/FLrun.html b/FLrun.html index 7db86d584ba..a9188fbd211 100644 --- a/FLrun.html +++ b/FLrun.html @@ -39,7 +39,7 @@
- +Description
Plugin opcode in widgets. This opcode is part of the plugin repository and has to be installed separately. These FLTK widgets do not work on the Mac. @@ -49,7 +49,7 @@
Description
- +Performance
This opcode must be located at the end of all widget declarations. It has no arguments, and its purpose is to start the thread related to widgets. Widgets would not operate if FLrun is missing.
- +Credits
Author: Gabriel Maldonado
New in version 4.22
diff --git a/FLsavesnap.html b/FLsavesnap.html index 77c96202639..6a7b3852242 100644 --- a/FLsavesnap.html +++ b/FLsavesnap.html @@ -39,7 +39,7 @@
- +Performance
FLsavesnap saves all snapshots currently created (i.e. the entire memory bank) into a file whose name is filename. Since the file is a text file, snapshot values can also be edited manually by means of a text editor. The format of the data stored in the file is the following (at present time, this could be changed in next Csound version): @@ -154,21 +154,21 @@
Performance
- +Examples
Here is a simple example of the FLTK snapshot saving. It uses the file FLsavesnap_simple.csd.
- +- Example 328. Example of FLTK snapshot saving. + Example 331. Example of FLTK snapshot saving.
See the sections Real-time Audio and Command Line Flags for more information on using command line flags.
- +<CsoundSynthesizer> <CsOptions> @@ -258,14 +258,14 @@Examples
- +- Example 329. Example of FLTK snapshot saving using snapshot groups. + Example 332. Example of FLTK snapshot saving using snapshot groups.
See the sections Real-time Audio and Command Line Flags for more information on using command line flags.
- +Credits
Author: Gabriel Maldonado
New in version 4.22
diff --git a/FLscroll.html b/FLscroll.html index b3f9b66d86f..c469df37056 100644 --- a/FLscroll.html +++ b/FLscroll.html @@ -39,7 +39,7 @@
- +Description
Plugin opcode in widgets. This opcode is part of the plugin repository and has to be installed separately. These FLTK widgets do not work on the Mac. @@ -49,12 +49,12 @@
Description
- +Performance
Containers are useful to format the graphic appearance of the widgets. The most important container is FLpanel, that actually creates a window. It can be filled with other containers and/or valuators or other kinds of widgets. @@ -108,21 +108,21 @@
Performance
- +Examples
Here is an example of the FLscroll opcode. It uses the file FLscroll.csd.
- +- Example 330. Example of the FLscroll opcode. + Example 333. Example of the FLscroll opcode.
See the sections Real-time Audio and Command Line Flags for more information on using command line flags.
- +Credits
Author: Gabriel Maldonado
New in version 4.22
diff --git a/FLscrollEnd.html b/FLscrollEnd.html index c8a1e75610c..be68c7189fe 100644 --- a/FLscrollEnd.html +++ b/FLscrollEnd.html @@ -39,7 +39,7 @@
- +Description
Plugin opcode in widgets. This opcode is part of the plugin repository and has to be installed separately. These FLTK widgets do not work on the Mac. @@ -49,7 +49,7 @@
Description
- +Performance
Containers are useful to format the graphic appearance of the widgets. The most important container is FLpanel, that actually creates a window. It can be filled with other containers and/or valuators or other kinds of widgets. @@ -68,7 +68,7 @@
Performance
- +Credits
Author: Gabriel Maldonado
New in version 4.22
diff --git a/FLscroll_end.html b/FLscroll_end.html index 1aa11bd8f15..34df4cdb67d 100644 --- a/FLscroll_end.html +++ b/FLscroll_end.html @@ -39,7 +39,7 @@
- +Description
Plugin opcode in widgets. This opcode is part of the plugin repository and has to be installed separately. These FLTK widgets do not work on the Mac. @@ -52,7 +52,7 @@
Description
- +Credits
Author: Gabriel Maldonado
New in version 4.22
diff --git a/FLsetAlign.html b/FLsetAlign.html index 884135f654c..3482a2cfe5e 100644 --- a/FLsetAlign.html +++ b/FLsetAlign.html @@ -39,7 +39,7 @@
- +Description
Plugin opcode in widgets. This opcode is part of the plugin repository and has to be installed separately. These FLTK widgets do not work on the Mac. @@ -49,12 +49,12 @@
Description
- +Initialization
ialign -- sets the alignment of the label text of widgets. @@ -101,7 +101,7 @@
Initialization
- +Credits
Author: Gabriel Maldonado
New in version 4.22
diff --git a/FLsetBox.html b/FLsetBox.html index 03fe32c9525..2ef300e5103 100644 --- a/FLsetBox.html +++ b/FLsetBox.html @@ -39,7 +39,7 @@
- +Description
Plugin opcode in widgets. This opcode is part of the plugin repository and has to be installed separately. These FLTK widgets do not work on the Mac. @@ -49,12 +49,12 @@
Description
- +Initialization
itype -- an integer number that modify the appearance of the target widget. @@ -131,7 +131,7 @@
Initialization
- +Credits
Author: Gabriel Maldonado
New in version 4.22
diff --git a/FLsetColor.html b/FLsetColor.html index 6afa89ed25b..799eeba4251 100644 --- a/FLsetColor.html +++ b/FLsetColor.html @@ -39,7 +39,7 @@
- +Description
Plugin opcode in widgets. This opcode is part of the plugin repository and has to be installed separately. These FLTK widgets do not work on the Mac. @@ -49,12 +49,12 @@
Description
- +Initialization
ired -- The red color of the target widget. The range for each RGB component is 0-255 @@ -70,21 +70,21 @@
Initialization
- +Examples
Here is an example of the FLsetcolor opcode. It uses the file FLsetcolor.csd.
- +- Example 331. Example of the FLsetcolor opcode. + Example 334. Example of the FLsetcolor opcode.
See the sections Real-time Audio and Command Line Flags for more information on using command line flags.
- +Credits
Author: Gabriel Maldonado
New in version 4.22
diff --git a/FLsetColor2.html b/FLsetColor2.html index b8e09f8ba84..c7305b3682a 100644 --- a/FLsetColor2.html +++ b/FLsetColor2.html @@ -39,7 +39,7 @@
- +Description
Plugin opcode in widgets. This opcode is part of the plugin repository and has to be installed separately. These FLTK widgets do not work on the Mac. @@ -49,12 +49,12 @@
Description
- +Initialization
ired -- The red color of the target widget. The range for each RGB component is 0-255 @@ -70,7 +70,7 @@
Initialization
- +Credits
Author: Gabriel Maldonado
New in version 4.22
diff --git a/FLsetFont.html b/FLsetFont.html index c1845cf61f3..f222e9d3ef7 100644 --- a/FLsetFont.html +++ b/FLsetFont.html @@ -39,7 +39,7 @@
- +Description
Plugin opcode in widgets. This opcode is part of the plugin repository and has to be installed separately. These FLTK widgets do not work on the Mac. @@ -49,12 +49,12 @@
Description
- +Initialization
ifont -- sets the the font type of the label of a widget. @@ -122,7 +122,7 @@
Initialization
- +Credits
Author: Gabriel Maldonado
New in version 4.22
diff --git a/FLsetPosition.html b/FLsetPosition.html index 6ed7ca14a78..ab0874e4529 100644 --- a/FLsetPosition.html +++ b/FLsetPosition.html @@ -39,7 +39,7 @@
- +Description
Plugin opcode in widgets. This opcode is part of the plugin repository and has to be installed separately. These FLTK widgets do not work on the Mac. @@ -49,12 +49,12 @@
Description
- +Initialization
ix -- horizontal position of upper left corner of the valuator, relative to the upper left corner of corresponding window (expressed in pixels). @@ -67,7 +67,7 @@
Initialization
- +Credits
Author: Gabriel Maldonado
New in version 4.22
diff --git a/FLsetSize.html b/FLsetSize.html index d34b2d3677d..b4dfde5f399 100644 --- a/FLsetSize.html +++ b/FLsetSize.html @@ -39,7 +39,7 @@
- +Description
Plugin opcode in widgets. This opcode is part of the plugin repository and has to be installed separately. These FLTK widgets do not work on the Mac. @@ -49,12 +49,12 @@
Description
- +Credits
Author: Gabriel Maldonado
New in version 4.22
diff --git a/FLsetSnapGroup.html b/FLsetSnapGroup.html index 145b905268e..19242f4f47a 100644 --- a/FLsetSnapGroup.html +++ b/FLsetSnapGroup.html @@ -39,7 +39,7 @@
- +Performance
For purposes of snapshot saving, widgets can be grouped, so that snapshots affect only a defined group of widgets. The opcode FLsetSnapGroup is used to specify the group for all widgets declared after it, until the next FLsetSnapGroup statement. @@ -88,7 +88,7 @@
Performance
- +Credits
Author: Gabriel Maldonado
New in version 4.22
diff --git a/FLsetText.html b/FLsetText.html index 4269c61b3e9..3d34239ad5b 100644 --- a/FLsetText.html +++ b/FLsetText.html @@ -39,7 +39,7 @@
- +Description
Plugin opcode in widgets. This opcode is part of the plugin repository and has to be installed separately. These FLTK widgets do not work on the Mac. @@ -49,13 +49,13 @@
Description
- +Initialization
“itext” -- a double-quoted string denoting the text of the label of the widget. @@ -68,21 +68,21 @@
Initialization
- +Examples
Here is an example of the FLsetText opcode. It uses the file FLsetText.csd.
- +- Example 332. Example of the FLsetText opcode. + Example 335. Example of the FLsetText opcode.
See the sections Real-time Audio and Command Line Flags for more information on using command line flags.
- +Credits
Author: Gabriel Maldonado
New in version 4.22
diff --git a/FLsetTextColor.html b/FLsetTextColor.html index bc37f1cad46..3384129eeb3 100644 --- a/FLsetTextColor.html +++ b/FLsetTextColor.html @@ -39,7 +39,7 @@
- +Description
Plugin opcode in widgets. This opcode is part of the plugin repository and has to be installed separately. These FLTK widgets do not work on the Mac. @@ -49,12 +49,12 @@
Description
- +Initialization
ired -- The red color of the target widget. The range for each RGB component is 0-255 @@ -70,7 +70,7 @@
Initialization
- +Credits
Author: Gabriel Maldonado
New in version 4.22
diff --git a/FLsetTextSize.html b/FLsetTextSize.html index 8d556764823..996af0ae315 100644 --- a/FLsetTextSize.html +++ b/FLsetTextSize.html @@ -39,7 +39,7 @@
- +Description
Plugin opcode in widgets. This opcode is part of the plugin repository and has to be installed separately. These FLTK widgets do not work on the Mac. @@ -49,12 +49,12 @@
Description
- +Initialization
isize -- size of the font of the target widget. Normal values are in the order of 15. Greater numbers enlarge font size, while smaller numbers reduce it. @@ -64,7 +64,7 @@
Initialization
- +Credits
Author: Gabriel Maldonado
New in version 4.22
diff --git a/FLsetTextType.html b/FLsetTextType.html index 7cc1da7a6f7..2e76f51502d 100644 --- a/FLsetTextType.html +++ b/FLsetTextType.html @@ -39,7 +39,7 @@
- +Description
Plugin opcode in widgets. This opcode is part of the plugin repository and has to be installed separately. These FLTK widgets do not work on the Mac. @@ -49,12 +49,12 @@
Description
- +Initialization
itype -- an integer number that modify the appearance of the target widget. @@ -140,7 +140,7 @@
Initialization
- +Credits
Author: Gabriel Maldonado
New in version 4.22
diff --git a/FLsetVal.html b/FLsetVal.html index 433add23cca..69eb1552211 100644 --- a/FLsetVal.html +++ b/FLsetVal.html @@ -39,7 +39,7 @@
- +Description
Plugin opcode in widgets. This opcode is part of the plugin repository and has to be installed separately. These FLTK widgets do not work on the Mac. @@ -49,19 +49,19 @@
Description
- +Initialization
ihandle -- an integer number (used as unique identifier) taken from the output of a previously located widget opcode (which corresponds to the target widget). It is used to unequivocally identify the widget when modifying its appearance with this class of opcodes. The user must not set the ihandle value directly, otherwise a Csound crash will occur.
- +Credits
Author: Gabriel Maldonado
New in version 4.22
diff --git a/FLsetVal_i.html b/FLsetVal_i.html index 66ebc422427..05b0c884062 100644 --- a/FLsetVal_i.html +++ b/FLsetVal_i.html @@ -39,7 +39,7 @@
- +Description
Plugin opcode in widgets. This opcode is part of the plugin repository and has to be installed separately. These FLTK widgets do not work on the Mac. @@ -49,19 +49,19 @@
Description
- +Initialization
ihandle -- an integer number (used as unique identifier) taken from the output of a previously located widget opcode (which corresponds to the target widget). It is used to unequivocally identify the widget when modifying its appearance with this class of opcodes. The user must not set the ihandle value directly, otherwise a Csound crash will occur.
- +Credits
Author: Gabriel Maldonado
New in version 4.22
diff --git a/FLsetsnap.html b/FLsetsnap.html index 3fd13e2c10c..6c4569da1a7 100644 --- a/FLsetsnap.html +++ b/FLsetsnap.html @@ -39,7 +39,7 @@
- +Performance
The FLsetsnap opcode stores current status of all valuators present in the orchestra into a snapshot location (in memory). Any number of snapshots can be stored in the current bank. Banks are structures that only exist in memory, there are no other reference to them other that they can be accessed by FLsetsnap, FLsavesnap, FLloadsnap and FLgetsnap opcodes. Only a single bank can be present in memory. @@ -122,7 +122,7 @@
Performance
- +Credits
Author: Gabriel Maldonado
New in version 4.22
diff --git a/FLshow.html b/FLshow.html index d3d494dbc51..d730fd0b1f2 100644 --- a/FLshow.html +++ b/FLshow.html @@ -39,7 +39,7 @@
- +Description
Plugin opcode in widgets. This opcode is part of the plugin repository and has to be installed separately. These FLTK widgets do not work on the Mac. @@ -49,19 +49,19 @@
Description
- +Initialization
ihandle -- an integer number (used as unique identifier) taken from the output of a previously located widget opcode (which corresponds to the target widget). It is used to unequivocally identify the widget when modifying its appearance with this class of opcodes. The user must not set the ihandle value directly, otherwise a Csound crash will occur.
- +Credits
Author: Gabriel Maldonado
New in version 4.22
diff --git a/FLslidBnk.html b/FLslidBnk.html index e2c8837f99a..5c7d89dc6f0 100644 --- a/FLslidBnk.html +++ b/FLslidBnk.html @@ -39,7 +39,7 @@
- +Description
Plugin opcode in widgets. This opcode is part of the plugin repository and has to be installed separately. These FLTK widgets do not work on the Mac. @@ -49,13 +49,13 @@
Description
- +Syntax
FLslidBnk "names", inumsliders [, ioutable] [, iwidth] [, iheight] [, ix] \ [, iy] [, itypetable] [, iexptable] [, istart_index] [, iminmaxtable]- +Initialization
“names” -- a double-quoted string containing the names of each slider. Each slider can have a different name. Separate each name with “@” character, for example: “frequency@amplitude@cutoff”. It is possible to not provide any name by giving a single space “ ”. In this case, the opcode will automatically assign a progressive number as a label for each slider. @@ -137,7 +137,7 @@
Initialization
- +Examples
Here is an example of the FLslidBnk opcode. It uses the file FLslidBnk.csd.
- +- Example 333. Example of the FLslidBnk opcode. + Example 336. Example of the FLslidBnk opcode.
See the sections Real-time Audio and Command Line Flags for more information on using command line flags.
- +Credits
Author: Gabriel Maldonado
New in version 4.22
diff --git a/FLslidBnk2.html b/FLslidBnk2.html index d3e99a8ec5a..c1ea299a591 100644 --- a/FLslidBnk2.html +++ b/FLslidBnk2.html @@ -39,7 +39,7 @@
- +Description
Plugin opcode in widgets. This opcode is part of the plugin repository and has to be installed separately. These FLTK widgets do not work on the Mac. @@ -49,13 +49,13 @@
Description
- +Syntax
FLslidBnk2 "names", inumsliders, ioutable, iconfigtable [,iwidth, iheight, ix, iy, istart_index]FLslidBnk2 istring, inumsliders, ioutable, iconfigtable [,iwidth, iheight, ix, iy, istart_index]- +Initialization
“names” -- a double-quoted string containing the names of each slider. Each slider can have a different name. Separate each name with “@” character, for example: “frequency@amplitude@cutoff”. It is possible to not provide any name by giving a single space “ ”. In this case, the opcode will automatically assign a progressive number as a label for each slider. @@ -101,7 +101,7 @@
Initialization
- +Examples
Here is an example of the FLslidBnk2 opcode. It uses the file FLslidBnk2.csd.
- +- Example 334. Example of the FLslidBnk2 opcode. + Example 337. Example of the FLslidBnk2 opcode.
See the sections Real-time Audio and Command Line Flags for more information on using command line flags.
- +Credits
Author: Gabriel Maldonado
New in version 5.06
diff --git a/FLslidBnk2Set.html b/FLslidBnk2Set.html index 967be2789ee..9aefb609d3d 100644 --- a/FLslidBnk2Set.html +++ b/FLslidBnk2Set.html @@ -39,7 +39,7 @@
- +Description
Plugin opcode in widgets. This opcode is part of the plugin repository and has to be installed separately. These FLTK widgets do not work on the Mac. @@ -49,12 +49,12 @@
Description
- +Initialization
ihandle - handle of the sliderBnk (to be used to set its values). @@ -73,7 +73,7 @@
Initialization
- +Performance
FLslidBnk2Set modifies the values of a slider bank (created with FLslidBnk2 or with FLvslidBnk2) according to an array of values stored into table ifn. It actually allows to update an FLslidBnk2 (or FLvslidBnk2) bank of sliders (for instance, using the slider8table opcode) to a set of values located in a table. User has to set ihandle argument to the handle got from FLslidBnkGetHandle opcode. It works at init-rate only. It is possible to reset only a range of sliders, by using the optional arguments istartIndex, istartSlid, inumSlid @@ -86,7 +86,7 @@
Performance
- +Credits
Author: Gabriel Maldonado
New in version 5.06
diff --git a/FLslidBnk2Setk.html b/FLslidBnk2Setk.html index 8a7ae801328..9b446956888 100644 --- a/FLslidBnk2Setk.html +++ b/FLslidBnk2Setk.html @@ -39,7 +39,7 @@
- +Description
Plugin opcode in widgets. This opcode is part of the plugin repository and has to be installed separately. These FLTK widgets do not work on the Mac. @@ -49,12 +49,12 @@
Description
- +Initialization
ihandle - handle of the sliderBnk (to be used to set its values). @@ -73,7 +73,7 @@
Initialization
- +Performance
ktrig – the output of FLslidBnk2Setk consists of a trigger that informs if sliders have to be updated or not. A non-zero value forces the slider to be updated. @@ -86,21 +86,21 @@
Performance
- +Examples
Here is an example of the FLslidBnk2Setk opcode. It uses the file FLslidBnk2Setk.csd.
- +- Example 335. Example of the FLslidBnk2Setk opcode. + Example 338. Example of the FLslidBnk2Setk opcode.
See the sections Real-time Audio and Command Line Flags for more information on using command line flags.
- +Credits
Author: Gabriel Maldonado
New in version 5.06
diff --git a/FLslidBnkGetHandle.html b/FLslidBnkGetHandle.html index f1c1b610cab..13a74c50892 100644 --- a/FLslidBnkGetHandle.html +++ b/FLslidBnkGetHandle.html @@ -39,7 +39,7 @@
- +Description
Plugin opcode in widgets. This opcode is part of the plugin repository and has to be installed separately. These FLTK widgets do not work on the Mac. @@ -49,19 +49,19 @@
Description
- +Performance
There are no k-rate arguments, even if cells of the output table (or the zak space) are updated at k-rate. @@ -74,7 +74,7 @@
Performance
- +Credits
Author: Gabriel Maldonado
New in version 5.06
diff --git a/FLslidBnkSet.html b/FLslidBnkSet.html index 16b4fdc2795..7ab304ed735 100644 --- a/FLslidBnkSet.html +++ b/FLslidBnkSet.html @@ -39,7 +39,7 @@
- +Description
Plugin opcode in widgets. This opcode is part of the plugin repository and has to be installed separately. These FLTK widgets do not work on the Mac. @@ -49,12 +49,12 @@
Description
- +Initialization
ihandle - handle of the sliderBnk (to be used to set its values). @@ -73,7 +73,7 @@
Initialization
- +Performance
FLslidBnkSet modifies the values of a slider bank (created with FLslidBnk or with FLvslidBnk) according to an array of values stored into table ifn. It actually allows to update an FLslidBnk (or FLvslidBnk) bank of sliders (for instance, using the slider8table opcode) to a set of values located in a table. User has to set ihandle argument to the handle got from FLslidBnkGetHandle opcode. It works at init-rate only. It is possible to reset only a range of sliders, by using the optional arguments istartIndex, istartSlid, inumSlid @@ -83,7 +83,7 @@
Performance
- +Credits
Author: Gabriel Maldonado
New in version 5.06
diff --git a/FLslidBnkSetk.html b/FLslidBnkSetk.html index 1a78cf9c8d8..5b5f33c84f4 100644 --- a/FLslidBnkSetk.html +++ b/FLslidBnkSetk.html @@ -39,7 +39,7 @@
- +Description
Plugin opcode in widgets. This opcode is part of the plugin repository and has to be installed separately. These FLTK widgets do not work on the Mac. @@ -49,12 +49,12 @@
Description
- +Initialization
ihandle - handle of the sliderBnk (to be used to set its values). @@ -73,7 +73,7 @@
Initialization
- +Performance
ktrig – the output of FLslidBnkSetk consists of a trigger that informs if sliders have to be updated or not. A non-zero value forces the slider to be updated. @@ -86,7 +86,7 @@
Performance
- +Credits
Author: Gabriel Maldonado
New in version 5.06
diff --git a/FLslider.html b/FLslider.html index ff3b0a4b2f2..ff79f82f48c 100644 --- a/FLslider.html +++ b/FLslider.html @@ -39,7 +39,7 @@
- +Description
Plugin opcode in widgets. This opcode is part of the plugin repository and has to be installed separately. These FLTK widgets do not work on the Mac. @@ -49,16 +49,16 @@
Description
- +Syntax
kout, ihandle FLslider "label", imin, imax, iexp, itype, idisp, iwidth, \ iheight, ix, iy- +Initialization
- ihandle -- a handle value (an integer number) that unequivocally references a corresponding widget. This is used by other opcodes that modify a widget's properties (see Modifying FLTK Widget Appearance). It is automatically output by FLslider and must not be set by the user label. (The user label is a double-quoted string containing some user-provided text placed near the widget.) + ihandle -- a handle value (an integer number) that unequivocally references a corresponding widget. This is used by other opcodes that modify a widget's properties (see Modifying FLTK Widget Appearance). It is automatically output by FLslider and must not be set by the user label. (The user label is a double-quoted string containing some user-provided text placed near the widget.)
“label” -- a double-quoted string containing some user-provided text, placed near the corresponding widget. @@ -193,7 +193,7 @@
Initialization
- +Examples
Here is an example of the FLslider opcode. It uses the file FLslider.csd.
- +- Example 336. Example of the FLslider opcode. + Example 339. Example of the FLslider opcode.
See the sections Real-time Audio and Command Line Flags for more information on using command line flags.
- +<CsoundSynthesizer> <CsOptions> @@ -300,13 +300,13 @@Examples
- +- Example 337. More complex example of the FLslider opcode. + Example 340. More complex example of the FLslider opcode.
- +Credits
Author: Gabriel Maldonado
New in version 4.22
diff --git a/FLtabs.html b/FLtabs.html index 15bb1314ac9..a8734156f5b 100644 --- a/FLtabs.html +++ b/FLtabs.html @@ -39,7 +39,7 @@
- +Description
Plugin opcode in widgets. This opcode is part of the plugin repository and has to be installed separately. These FLTK widgets do not work on the Mac. @@ -49,12 +49,12 @@
Description
- +Performance
Containers are useful to format the graphic appearance of the widgets. The most important container is FLpanel, that actually creates a window. It can be filled with other containers and/or valuators or other kinds of widgets. @@ -96,7 +96,7 @@
Performance
- +Examples
Here is an example of the FLtabs opcode. It uses the file FLtabs.csd.
- +- Example 338. Example of the FLtabs opcode. + Example 341. Example of the FLtabs opcode.
See the sections Real-time Audio and Command Line Flags for more information on using command line flags.
- +Credits
Author: Gabriel Maldonado
New in version 4.22
diff --git a/FLtabsEnd.html b/FLtabsEnd.html index 52d316d0f86..f90f4e70844 100644 --- a/FLtabsEnd.html +++ b/FLtabsEnd.html @@ -39,7 +39,7 @@
- +Description
Plugin opcode in widgets. This opcode is part of the plugin repository and has to be installed separately. These FLTK widgets do not work on the Mac. @@ -49,7 +49,7 @@
Description
- +Performance
Containers are useful to format the graphic appearance of the widgets. The most important container is FLpanel, that actually creates a window. It can be filled with other containers and/or valuators or other kinds of widgets. @@ -68,7 +68,7 @@
Performance
- +Credits
Author: Gabriel Maldonado
New in version 4.22
diff --git a/FLtabs_end.html b/FLtabs_end.html index 5fc7c658a15..d7d63f3d747 100644 --- a/FLtabs_end.html +++ b/FLtabs_end.html @@ -39,7 +39,7 @@
- +Description
Plugin opcode in widgets. This opcode is part of the plugin repository and has to be installed separately. These FLTK widgets do not work on the Mac. @@ -51,7 +51,7 @@
Description
- +Credits
Author: Gabriel Maldonado
New in version 4.22
diff --git a/FLtext.html b/FLtext.html index 595b591280f..e04efd61242 100644 --- a/FLtext.html +++ b/FLtext.html @@ -39,7 +39,7 @@
- +Description
Plugin opcode in widgets. This opcode is part of the plugin repository and has to be installed separately. These FLTK widgets do not work on the Mac. @@ -49,16 +49,16 @@
Description
- +Initialization
- ihandle -- a handle value (an integer number) that unequivocally references a corresponding widget. This is used by other opcodes that modify a widget's properties (see Modifying FLTK Widget Appearance). It is automatically output by FLtext and must not be set by the user label. (The user label is a double-quoted string containing some user-provided text placed near the widget.) + ihandle -- a handle value (an integer number) that unequivocally references a corresponding widget. This is used by other opcodes that modify a widget's properties (see Modifying FLTK Widget Appearance). It is automatically output by FLtext and must not be set by the user label. (The user label is a double-quoted string containing some user-provided text placed near the widget.)
“label” -- a double-quoted string containing some user-provided text, placed near corresponding widget. @@ -109,7 +109,7 @@
Initialization
- +Examples
Here is an example of the FLtext opcode. It uses the file FLtext.csd.
- +- Example 339. Example of the FLtext opcode. + Example 342. Example of the FLtext opcode.
See the sections Real-time Audio and Command Line Flags for more information on using command line flags.
- +Credits
Author: Gabriel Maldonado
New in version 4.22
diff --git a/FLupdate.html b/FLupdate.html index c65fec9c3b2..3309b136419 100644 --- a/FLupdate.html +++ b/FLupdate.html @@ -39,7 +39,7 @@
- +Description
Plugin opcode in widgets. This opcode is part of the plugin repository and has to be installed separately. These FLTK widgets do not work on the Mac. @@ -49,7 +49,7 @@
Description
- +Syntax
diff --git a/FLvalue.html b/FLvalue.html index 683439be814..7c1dc5a4c55 100644 --- a/FLvalue.html +++ b/FLvalue.html @@ -39,7 +39,7 @@
- +Description
Plugin opcode in widgets. This opcode is part of the plugin repository and has to be installed separately. These FLTK widgets do not work on the Mac. @@ -49,12 +49,12 @@
Description
- +Initialization
ihandle -- handle value (an integer number) that unequivocally references the corresponding valuator. It can be used for the idisp argument of a valuator. @@ -77,10 +77,10 @@
Initialization
- +Performance
- FLvalue shows the current values of a valuator in a text field. It outputs ihandle that can then be used for the idisp argument of a valuator (see the FLTK Valuators section). In this way, the values of that valuator will be dynamically be shown in a text field. + FLvalue shows the current values of a valuator in a text field. It outputs ihandle that can then be used for the idisp argument of a valuator (see the FLTK Valuators section). In this way, the values of that valuator will be dynamically be shown in a text field.
@@ -99,21 +99,21 @@
Performance
- +Examples
Here is an example of the FLvalue opcode. It uses the file FLvalue.csd.
- +- Example 345. Example of the FLvalue opcode. + Example 348. Example of the FLvalue opcode.
See the sections Real-time Audio and Command Line Flags for more information on using command line flags.
- +Credits
Author: Steven Yi
New in version 5.05
diff --git a/FLvslidBnk.html b/FLvslidBnk.html index d1ca5f91a22..a2d525906dd 100644 --- a/FLvslidBnk.html +++ b/FLvslidBnk.html @@ -39,7 +39,7 @@
- +Description
Plugin opcode in widgets. This opcode is part of the plugin repository and has to be installed separately. These FLTK widgets do not work on the Mac. @@ -49,13 +49,13 @@
Description
- +Syntax
FLvslidBnk "names", inumsliders [, ioutable] [, iwidth] [, iheight] [, ix] \ [, iy] [, itypetable] [, iexptable] [, istart_index] [, iminmaxtable]- +Initialization
“names” -- a double-quoted string containing the names of each slider. Each slider can have a different name. Separate each name with “@” character, for example: “frequency@amplitude@cutoff”. It is possible to not provide any name by giving a single space “ ”. In this case, the opcode will automatically assign a progressive number as a label for each slider. @@ -137,7 +137,7 @@
Initialization
- +Examples
Here is an example of the FLvslidBnk opcode. It uses the file FLvslidBnk.csd.
- +- Example 346. Example of the FLvslidBnk opcode. + Example 349. Example of the FLvslidBnk opcode.
See the sections Real-time Audio and Command Line Flags for more information on using command line flags.
- +Credits
Author: Gabriel Maldonado
New in version 5.06
diff --git a/FLvslidBnk2.html b/FLvslidBnk2.html index 32a9a58a212..60dd00ac2ef 100644 --- a/FLvslidBnk2.html +++ b/FLvslidBnk2.html @@ -39,7 +39,7 @@
- +Description
Plugin opcode in widgets. This opcode is part of the plugin repository and has to be installed separately. These FLTK widgets do not work on the Mac. @@ -49,12 +49,12 @@
Description
- +Syntax
FLvslidBnk2 "names", inumsliders, ioutable, iconfigtable [,iwidth, iheight, ix, iy, istart_index]- +Initialization
“names” -- a double-quoted string containing the names of each slider. Each slider can have a different name. Separate each name with “@” character, for example: “frequency@amplitude@cutoff”. It is possible to not provide any name by giving a single space “ ”. In this case, the opcode will automatically assign a progressive number as a label for each slider. @@ -95,7 +95,7 @@
Initialization
- +Credits
Author: Gabriel Maldonado
New in version 5.06
diff --git a/FLxyin.html b/FLxyin.html index 62f7bc16100..c63de401010 100644 --- a/FLxyin.html +++ b/FLxyin.html @@ -39,7 +39,7 @@
- +Description
Plugin opcode in widgets. This opcode is part of the plugin repository and has to be installed separately. These FLTK widgets do not work on the Mac. @@ -49,13 +49,13 @@
Description
- +Syntax
koutx, kouty, kinside FLxyin ioutx_min, ioutx_max, iouty_min, iouty_max, \ iwindx_min, iwindx_max, iwindy_min, iwindy_max [, iexpx, iexpy, ioutx, iouty]- +Initialization
ioutx_min, ioutx_max - the minimum and maximum limits of the interval to be output (X or horizontal axis). @@ -77,7 +77,7 @@
Initialization
- +Performance
koutx, kouty - output values, scaled according to user choices. @@ -93,21 +93,21 @@
Performance
- +Examples
Here is an example of the FLxyin opcode. It uses the file FLxyin.csd.
- +- Example 347. Example of the FLxyin opcode. + Example 350. Example of the FLxyin opcode.
See the sections Real-time Audio and Command Line Flags for more information on using command line flags.
- +<CsoundSynthesizer> <CsOptions> @@ -156,13 +156,13 @@Examples
- +- Example 348. Example of the FLxyin opcode. + Example 351. Example of the FLxyin opcode.
- +Credits
Author: Gabriel Maldonado
New in version 5.06
diff --git a/FaustTop.html b/FaustTop.html new file mode 100644 index 00000000000..549f15d3239 --- /dev/null +++ b/FaustTop.html @@ -0,0 +1,82 @@ + + + + + +Faust Opcodes + + + + + + + + + + ++ ++ + + diff --git a/GEN01.html b/GEN01.html index 61e3b6c3119..c02fa96e528 100644 --- a/GEN01.html +++ b/GEN01.html @@ -39,19 +39,19 @@The Faust opcodes allows access from within Csound to the Faust language. Faust (Functional Audio Stream) is a functional programming language for sound synthesis and audio processing: https://faust.grame.fr/.
+The following opcodes are available:
++++
+- +
+faustaudio - Instantiates and runs a compiled Faust program.
+- +
+faustcompile - Produce a instantiable DSP process from a Faust program.
+- +
+faustdsp - Instantiates a Faust program.
+- +
+faustctl - Adjusts a given control in a Faust DSP instance.
+- +
+faustgen - Compiles, Instantiates and runs a compiled Faust program.
+- +
+faustplay - Runs an instantiated Faust program.
+
- +Performance
size -- number of points in the table. Ordinarily a power of 2 or a power-of-2 plus 1 (see f statement); the maximum tablesize is 16777216 (224) points. The allocation of table memory can be deferred by setting this parameter to 0; the size allocated is then the number of points in the file (probably not a power-of-2), and the table is not usable by normal oscillators, but it is usable by a loscil unit. The soundfile can also be mono or stereo. @@ -141,19 +141,19 @@
Performance
- +Examples
Here is an example of the GEN01 routine. It uses the files gen01.csd and several sound files.
- +- Example 1276. An example of the GEN01 routine. + Example 1291. An example of the GEN01 routine.
- +<CsoundSynthesizer> <CsOptions> @@ -190,9 +190,9 @@Examples
endin </CsInstruments> <CsScore> -f 1 0 131072 1 "beats.wav" 0 0 0 ;non-deferred sound +f 1 0 131072 1 "drumsMlp.wav" 0 0 0 ;non-deferred sound f 2 0 0 1 "flute.aiff" 0 0 0 ;& deferred sounds in -f 3 0 0 1 "beats.ogg" 0 0 0 ;different formats +f 3 0 0 1 "drumsMlp.ogg" 0 0 0 ;different formats i 1 0 1 1 i 1 + 1 2 @@ -212,9 +212,9 @@Examples
-+
-f 1 0 131072 1 "beats.wav" 0 0 0 - non-deferred sound
+f 1 0 131072 1 "drumsMlp.wav" 0 0 0 - non-deferred sound
@@ -230,9 +230,9 @@
Examples
-+
-f 3 0 0 1 "beats.ogg" 0 0 0 - deferred sound
+f 3 0 0 1 "drumsMlp.ogg" 0 0 0 - deferred sound
@@ -240,7 +240,7 @@
Examples
- +Examples
Here is an example of the GEN02 routine. It uses the files gen02.csd.
- +- Example 1277. Example of the GEN02 routine. + Example 1292. Example of the GEN02 routine.
See the sections Real-time Audio and Command Line Flags for more information on using command line flags.
- +Credits
December 2002. Thanks to Rasmus Ekman, corrected the limit of the PMAX variable.
diff --git a/GEN03.html b/GEN03.html index b04cfee887e..59b5db9902b 100644 --- a/GEN03.html +++ b/GEN03.html @@ -39,19 +39,19 @@
- +Examples
Here is an example of the GEN03 generator. It uses the file gen03.csd.
- +- Example 1278. Example of the GEN03 generator. + Example 1293. Example of the GEN03 generator.
See the sections Real-time Audio and Command Line Flags for more information on using command line flags.
- +See Also
GEN13, diff --git a/GEN04.html b/GEN04.html index 09bf72e5f0c..26c81bf7dc5 100644 --- a/GEN04.html +++ b/GEN04.html @@ -39,19 +39,19 @@
- +Examples
Here is a simple example of the GEN04 routine. It uses the files gen04.csd.
- +- Example 1279. An example of the GEN04 routine. + Example 1294. An example of the GEN04 routine.
- +<CsoundSynthesizer> <CsOptions> diff --git a/GEN05.html b/GEN05.html index 53dab4f6cda..5fff501a95b 100644 --- a/GEN05.html +++ b/GEN05.html @@ -39,19 +39,19 @@
- +Initialization
size -- number of points in the table. Must be a power of 2 or power-of-2 plus 1 (see f statement). @@ -105,19 +105,19 @@
Initialization
- +Examples
Here is a simple example of the GEN05 routine. It uses the files gen05.csd.
- +- Example 1280. An example of the GEN05 routine. + Example 1295. An example of the GEN05 routine.
- +See Also
GEN06, diff --git a/GEN06.html b/GEN06.html index 7687dcc3c1d..741cafd0c4e 100644 --- a/GEN06.html +++ b/GEN06.html @@ -39,19 +39,19 @@
- +Description
This subroutine will generate a function comprised of segments of cubic polynomials, spanning specified points just three at a time.
- +Initialization
size -- number of points in the table. Must be a power off or power-of-2 plus 1 (see f statement). @@ -84,19 +84,19 @@
Initialization
- +Examples
Here is an example of the GEN06 routine. It uses the files gen06.csd.
- +- Example 1281. An example of the GEN06 routine. + Example 1296. An example of the GEN06 routine.
- +See Also
GEN05, diff --git a/GEN07.html b/GEN07.html index a936ba7c35c..be3db236bde 100644 --- a/GEN07.html +++ b/GEN07.html @@ -39,19 +39,19 @@
- +Initialization
size -- number of points in the table. Must be a power of 2 or power-of-2 plus 1 (see f statement). @@ -96,19 +96,19 @@
Initialization
- +Examples
Here is an example of the GEN07 routine. It uses the files gen07.csd.
- +- Example 1282. An example of the GEN07 routine. + Example 1297. An example of the GEN07 routine.
- +See Also
GEN05, diff --git a/GEN08.html b/GEN08.html index 636edebc402..e28fd4d7573 100644 --- a/GEN08.html +++ b/GEN08.html @@ -39,19 +39,19 @@
- +Description
This subroutine will generate a piecewise cubic spline curve, the smoothest possible through all specified points.
- +Initialization
size -- number of points in the table. Must be a power of 2 or power-of-2 plus 1 (see f statement). @@ -96,19 +96,19 @@
Initialization
- +Examples
Here is an example of the GEN08 routine. It uses the files gen08.csd.
- +- Example 1283. An example of the GEN08 routine. + Example 1298. An example of the GEN08 routine.
- +See Also
GEN05, diff --git a/GEN09.html b/GEN09.html index 6864080089b..53f6463e684 100644 --- a/GEN09.html +++ b/GEN09.html @@ -39,19 +39,19 @@
- +Description
These subroutines generate composite waveforms made up of weighted sums of simple sinusoids. The specification of each contributing partial requires 3 p-fields using GEN09.
- +Initialization
size -- number of points in the table. Must be a power of 2 or power-of-2 plus 1 (see f statement). @@ -97,21 +97,21 @@
Initialization
- +Examples
Here is an example of the GEN09 routine. It uses the files gen09.csd.
- +- Example 1284. Example of the GEN09 routine. + Example 1299. Example of the GEN09 routine.
See the sections Real-time Audio and Command Line Flags for more information on using command line flags.
- +See Also
GEN10, diff --git a/GEN10.html b/GEN10.html index d3e39986505..7558e24f3b5 100644 --- a/GEN10.html +++ b/GEN10.html @@ -39,19 +39,19 @@
- +Description
These subroutines generate composite waveforms made up of weighted sums of simple sinusoids. The specification of each contributing partial requires 1 pfield using GEN10.
- +Initialization
size -- number of points in the table. Must be a power of 2 or power-of-2 plus 1 (see f statement). @@ -91,19 +91,19 @@
Initialization
- +Examples
Here is an example of the GEN10 routine. It uses the files gen10.csd.
- +- Example 1285. An example of the GEN10 routine. + Example 1300. An example of the GEN10 routine.
- +See Also
GEN09, diff --git a/GEN11.html b/GEN11.html index e958cd49515..19127fb4636 100644 --- a/GEN11.html +++ b/GEN11.html @@ -39,19 +39,19 @@
- +Description
This subroutine generates an additive set of cosine partials, in the manner of Csound generators buzz and gbuzz.
- +Initialization
size -- number of points in the table. Must be a power of 2 or power-of-2 plus 1 (see f statement). @@ -99,19 +99,19 @@
Initialization
- +Examples
Here is an example of the GEN11 routine. It uses the files gen11.csd.
- +- Example 1286. An example of the GEN11 routine. + Example 1301. An example of the GEN11 routine.
- +See Also
GEN10 diff --git a/GEN12.html b/GEN12.html index bdebc49982c..52c7b9216ae 100644 --- a/GEN12.html +++ b/GEN12.html @@ -39,19 +39,19 @@
- +Description
This generates the log of a modified Bessel function of the second kind, order 0, suitable for use in amplitude-modulated FM.
- +Initialization
size -- number of points in the table. Must be a power of 2 or a power-of-2 plus 1 (see f statement). The normal value is power-of-2 plus 1. @@ -93,20 +93,20 @@
Initialization
- +Examples
Here is an example of the GEN12 generator. It uses the file gen12.csd.
- +- Example 1287. Example of the GEN12 generator. + Example 1302. Example of the GEN12 generator.
See the sections Real-time Audio and Command Line Flags for more information on using command line flags.
- +Credits
Example is, with minor modifications, taken from The Csound Book (page 87). diff --git a/GEN13.html b/GEN13.html index 7d37ea5c725..caa0021ae9b 100644 --- a/GEN13.html +++ b/GEN13.html @@ -39,19 +39,19 @@
- +Description
Uses Chebyshev coefficients to generate stored polynomial functions which, under waveshaping, can be used to split a sinusoid into harmonic partials having a pre-definable spectrum.
- +Initialization
size -- number of points in the table. Must be a power of 2 or a power-of-2 plus 1 (see f statement). The normal value is power-of-2 plus 1. @@ -80,20 +80,20 @@
Initialization
- +Examples
Here is an example of the GEN13 generator. It uses the file gen13.csd.
- +- Example 1288. Example of the GEN13 generator. + Example 1303. Example of the GEN13 generator.
See the sections Real-time Audio and Command Line Flags for more information on using command line flags.
- +See Also
GEN03, diff --git a/GEN14.html b/GEN14.html index 9146448289f..b7162b37d1e 100644 --- a/GEN14.html +++ b/GEN14.html @@ -39,19 +39,19 @@
- +Description
Uses Chebyshev coefficients to generate stored polynomial functions which, under waveshaping, can be used to split a sinusoid into harmonic partials having a pre-definable spectrum.
- +Initialization
size -- number of points in the table. Must be a power of 2 or a power-of-2 plus 1 (see f statement). The normal value is power-of-2 plus 1. @@ -109,20 +109,20 @@
Initialization
- +Examples
Here is an example of the GEN14 generator. It uses the file gen14.csd.
- +- Example 1289. Example of the GEN14 generator. + Example 1304. Example of the GEN14 generator.
See the sections Real-time Audio and Command Line Flags for more information on using command line flags.
- +See Also
GEN03, diff --git a/GEN15.html b/GEN15.html index 47c057c7835..47a3cb45956 100644 --- a/GEN15.html +++ b/GEN15.html @@ -39,19 +39,19 @@
- +Description
This subroutine creates two tables of stored polynomial functions, suitable for use in phase quadrature operations.
- +Initialization
size -- number of points in the table. Must be a power of 2 or a power-of-2 plus 1 (see f statement). The normal value is power-of-2 plus 1. @@ -103,19 +103,19 @@
Initialization
- +Examples
Here is an example of the GEN15 routine. It uses the files gen15.csd.
- +- Example 1290. An example of the GEN15 routine. + Example 1305. An example of the GEN15 routine.
- +See Also
GEN13, and diff --git a/GEN16.html b/GEN16.html index ddda607e811..a0d62514cde 100644 --- a/GEN16.html +++ b/GEN16.html @@ -39,19 +39,19 @@
- +- +- Example 1291. A simple example of the GEN16 routine. + Example 1306. A simple example of the GEN16 routine.
- +Credits
diff --git a/GEN17.html b/GEN17.html index dd95dc3f8ce..2294d0b4d6f 100644 --- a/GEN17.html +++ b/GEN17.html @@ -39,19 +39,19 @@
- +Initialization
size -- number of points in the table. Must be a power of 2 or a power-of-2 plus 1 (see f statement). The normal value is power-of-2 plus 1. @@ -81,7 +81,7 @@
Initialization
- +Examples
@@ -97,13 +97,13 @@
Examples
Here is a complete example of the GEN17 routine. It uses the files gen17.csd.- +- Example 1292. An example of the GEN17 routine. + Example 1307. An example of the GEN17 routine.
- +See Also
GEN02 diff --git a/GEN18.html b/GEN18.html index 38110489e57..fb03a7d4839 100644 --- a/GEN18.html +++ b/GEN18.html @@ -39,19 +39,19 @@
- +Description
Writes composite waveforms made up of pre-existing waveforms. Each contributing waveform requires 4 pfields and can overlap with other waveforms.
- +Initialization
size -- number of points in the table. Must be a power-of-2 (see f statement). @@ -70,7 +70,7 @@
Initialization
- +Examples
@@ -87,13 +87,13 @@
Examples
Here is an example of the GEN18 routine. It uses the files gen18.csd.- +- Example 1293. An example of the GEN18 routine. + Example 1308. An example of the GEN18 routine.
- +Deprecated Names
GEN18 was called GEN22 in version 4.18. The name was changed due to a conflict with DirectCsound.
- +Credits
diff --git a/GEN19.html b/GEN19.html index e36a7508eb0..185b0c78283 100644 --- a/GEN19.html +++ b/GEN19.html @@ -39,19 +39,19 @@
- +Description
These subroutines generate composite waveforms made up of weighted sums of simple sinusoids. The specification of each contributing partial requires 4 p-fields using GEN19.
- +Initialization
size -- number of points in the table. Must be a power of 2 or power-of-2 plus 1 (see f statement). @@ -100,19 +100,19 @@
Initialization
- +Examples
Here is an example of the GEN19 routine. It uses the files gen19.csd.
- +- Example 1294. An example of the GEN19 routine. + Example 1309. An example of the GEN19 routine.
- +See Also
GEN09 and diff --git a/GEN20.html b/GEN20.html index 3ea43932170..9e6a55974ad 100644 --- a/GEN20.html +++ b/GEN20.html @@ -39,19 +39,19 @@
- +Description
This subroutine generates functions of different windows. These windows are usually used for spectrum analysis or for grain envelopes.
- +Initialization
size -- number of points in the table. Must be a power of 2 ( + 1). @@ -105,7 +105,7 @@
Initialization
- +Examples
@@ -179,14 +179,14 @@
Examples
- +- Example 1295. Example of the GEN20 routine. + Example 1310. Example of the GEN20 routine.
See the sections Real-time Audio and Command Line Flags for more information on using command line flags.
- +<CsoundSynthesizer> <CsOptions> @@ -205,7 +205,7 @@Examples
instr 1 -insnd = 10 ;"fox.wav" +insnd = 10 ;"marimba.aif" ibasfrq = 44100 / ftlen(insnd) ;use original sample rate of insnd file kamp expseg .001, p3/2, .7, p3/2, .8 ;envelope @@ -225,7 +225,7 @@Examples
<CsScore> f1 0 512 20 2 ;Hanning window f2 0 512 20 6 1 ;Gaussian window -f10 0 16384 1 "fox.wav" 0 0 0 +f10 0 16384 1 "marimba.aif" 0 0 0 i1 0 5 1 ;use Hanning window i1 + 5 2 ;use Gaussian window @@ -260,7 +260,7 @@Examples
- +Credits
diff --git a/GEN21.html b/GEN21.html index 04dedb824bc..1d4e06b6553 100644 --- a/GEN21.html +++ b/GEN21.html @@ -39,19 +39,19 @@
- +Description
This generates tables of different random distributions. (See also betarand, bexprnd, cauchy, exprand, gauss, linrand, pcauchy, poisson, trirand, unirand, and weibull)
- +Initialization
time and size are the usual GEN function arguments. level defines the amplitude. Note that GEN21 is not self-normalizing as are most other GEN functions. type defines the distribution to be used as follow: @@ -107,7 +107,7 @@
Initialization
- +Examples
@@ -127,14 +127,14 @@
Examples
Here is a complete example of the GEN21 routine. It uses the file gen21.csd.- +- Example 1296. Example of the GEN21 routine. + Example 1311. Example of the GEN21 routine.
See the sections Real-time Audio and Command Line Flags for more information on using command line flags.
- +Credits
diff --git a/GEN22.html b/GEN22.html index cb894b175d6..6a59f08ccbd 100644 --- a/GEN22.html +++ b/GEN22.html @@ -39,7 +39,7 @@
- +Description
Deprecated as of version 4.19. Use the GEN18 routine instead. diff --git a/GEN23.html b/GEN23.html index 020855c93d3..4cd191a1035 100644 --- a/GEN23.html +++ b/GEN23.html @@ -39,19 +39,19 @@
- +Examples
Here is an example of the GEN23 generator. It uses the file gen23.csd and spectrum.txt.
- +- Example 1297. Example of the GEN23 generator. + Example 1312. Example of the GEN23 generator.
See the sections Real-time Audio and Command Line Flags for more information on using command line flags.
- +Credits
diff --git a/GEN24.html b/GEN24.html index a73139f7d82..9c014e7b2a7 100644 --- a/GEN24.html +++ b/GEN24.html @@ -39,19 +39,19 @@
- +Description
This subroutine reads numeric values from another allocated function-table and rescales them according to the max and min values given by the user.
- +Initialization
#, time, size -- the usual GEN parameters. See f statement. @@ -82,20 +82,20 @@
Initialization
- +Examples
Here is an example of the GEN24 opcode. It uses the file gen24.csd.
- +- Example 1298. Example of the GEN24 generator. + Example 1313. Example of the GEN24 generator.
See the sections Real-time Audio and Command Line Flags for more information on using command line flags.
- +Credits
Author: Gabriel Maldonado
New in Csound version 4.16
diff --git a/GEN25.html b/GEN25.html index 8c6a2e7e894..88c5d1b495f 100644 --- a/GEN25.html +++ b/GEN25.html @@ -39,19 +39,19 @@
- +Description
These subroutines are used to construct functions from segments of exponential curves in breakpoint fashion.
- +Initialization
size -- number of points in the table. Must be a power of 2 or power-of-2 plus 1 (see f statement). @@ -81,20 +81,20 @@
Initialization
- +Examples
Here is an example of the GEN25 generator. It uses the file gen25.csd.
- +- Example 1299. Example of the GEN25 generator. + Example 1314. Example of the GEN25 generator.
See the sections Real-time Audio and Command Line Flags for more information on using command line flags.
- +Credits
diff --git a/GEN27.html b/GEN27.html index bfb55a695f5..187c87dd465 100644 --- a/GEN27.html +++ b/GEN27.html @@ -39,19 +39,19 @@
- +Initialization
size -- number of points in the table. Must be a power of 2 or power-of-2 plus 1 (see f statement). @@ -81,20 +81,20 @@
Initialization
- +Examples
Here is an example of the GEN27 generator. It uses the file gen27.csd.
- +- Example 1300. Example of the GEN27 generator. + Example 1315. Example of the GEN27 generator.
See the sections Real-time Audio and Command Line Flags for more information on using command line flags.
- +Credits
diff --git a/GEN28.html b/GEN28.html index 1dbef8a759e..9e88afba40e 100644 --- a/GEN28.html +++ b/GEN28.html @@ -39,7 +39,7 @@
- +Description
This function generator reads a text file which contains sets of three values representing the xy coordinates and a time-tag for when the signal should be placed at that location, allowing the user to define a time-tagged trajectory. The file format is in the form: @@ -80,12 +80,12 @@
Description
- +Initialization
size -- number of points in the table. Must be 0. GEN28 takes 0 as the size and automatically allocates memory. @@ -95,7 +95,7 @@
Initialization
- +Examples
@@ -126,14 +126,14 @@
Examples
Here is an example of the GEN28 routine. It uses the file gen28.csd.- +- Example 1301. Example of the gen28 generator. + Example 1316. Example of the gen28 generator.
See the sections Real-time Audio and Command Line Flags for more information on using command line flags.
- +<CsoundSynthesizer> <CsOptions> @@ -160,7 +160,7 @@Examples
kx init 0 ky init 0 ktime line 0, 5, 5 ;same time as in table 1 (="move") -asig diskin2 "beats.wav", 1, 0, 1 ;sound source is looped +asig diskin2 "drumsMlp.wav", 1, 0, 1 ;sound source is looped a1, a2, a3, a4 space asig, 1, ktime, .1, kx, ky ;use table 1 = GEN28 ar1, ar2, ar3, ar4 spsend ;send to reverb @@ -203,7 +203,7 @@Examples
- +Credits
diff --git a/GEN30.html b/GEN30.html index a17280dd778..fb86f2fc6bf 100644 --- a/GEN30.html +++ b/GEN30.html @@ -39,19 +39,19 @@
- +Examples
Here is an example of the GEN30 routine. It uses the files gen30.csd.
- +- Example 1302. Example of the GEN30 routine. + Example 1317. Example of the GEN30 routine.
See the sections Real-time Audio and Command Line Flags for more information on using command line flags.
- +Credits
Author: Istvan Varga
New in version 4.16
diff --git a/GEN31.html b/GEN31.html index 4ec439e7846..a44d8b05a51 100644 --- a/GEN31.html +++ b/GEN31.html @@ -39,19 +39,19 @@
- +Description
This routine is similar to GEN09, but allows mixing any waveform specified in an existing table.
- +Examples
Here is an example of the GEN31 routine. It uses the files gen31.csd.
- +- Example 1303. Example of the GEN31 routine. + Example 1318. Example of the GEN31 routine.
See the sections Real-time Audio and Command Line Flags for more information on using command line flags.
- +Credits
Author: Istvan Varga
New in version 4.15
diff --git a/GEN32.html b/GEN32.html index a9868edf109..51a746e3848 100644 --- a/GEN32.html +++ b/GEN32.html @@ -39,19 +39,19 @@
- +Description
This routine is similar to GEN31, but allows specifying source ftable for each partial. Tables can be resampled either with FFT, or linear interpolation.
- +Performance
srca, srcb -- source table number. A negative value can be used to read the table with linear interpolation (by default, the source waveform is transposed and phase shifted using FFT); this is less accurate, but faster, and allows non-integer and negative partial numbers. @@ -67,20 +67,20 @@
Performance
- +Examples
Here is an example of the GEN32 routine. It uses the file gen32.csd.
- +- Example 1304. Example of the gen32 generator. + Example 1319. Example of the gen32 generator.
See the sections Real-time Audio and Command Line Flags for more information on using command line flags.
- +Credits
Author: Rasmus Ekman
Programmer: Istvan Varga
diff --git a/GEN33.html b/GEN33.html index 795049cd225..d8d98f2bde0 100644 --- a/GEN33.html +++ b/GEN33.html @@ -39,7 +39,7 @@
- +Description
These routines generate composite waveforms by mixing simple sinusoids, similarly to GEN09, but the parameters of the partials are specified in an already existing table, which makes it possible to calculate any number of partials in the orchestra. @@ -49,12 +49,12 @@
Description
- +Initialization
size -- number of points in the table. Must be power of two and at least 4. @@ -100,20 +100,20 @@
Initialization
- +Examples
Here is an example of the GEN33 routine. It uses the file gen33.csd.
- +- Example 1305. Example of the gen33 generator. + Example 1320. Example of the gen33 generator.
See the sections Real-time Audio and Command Line Flags for more information on using command line flags.
- +Credits
diff --git a/GEN34.html b/GEN34.html index dd237babc2b..d1885adf1a3 100644 --- a/GEN34.html +++ b/GEN34.html @@ -39,7 +39,7 @@
- +Description
These routines generate composite waveforms by mixing simple sinusoids, similarly to GEN09, but the parameters of the partials are specified in an already existing table, which makes it possible to calculate any number of partials in the orchestra. @@ -49,12 +49,12 @@
Description
- +Initialization
size -- number of points in the table. Must be power of two or a power of two plus 1. @@ -100,20 +100,20 @@
Initialization
- +Examples
Here is an example of the GEN34 routine. It uses the file gen34.csd.
- +- Example 1306. Example of the gen34 generator. + Example 1321. Example of the gen34 generator.
See the sections Real-time Audio and Command Line Flags for more information on using command line flags.
- +Credits
diff --git a/GEN40.html b/GEN40.html index 4f5b69488d3..5632c42d38a 100644 --- a/GEN40.html +++ b/GEN40.html @@ -39,19 +39,19 @@
- +Description
Generates a continuous random distribution function starting from the shape of a user-defined distribution histogram.
- +Performance
The shape of histogram must be stored in a previously defined table, in fact shapetab argument must be filled with the number of such table. @@ -64,20 +64,20 @@
Performance
- +Examples
Here is an example of the GEN40 generator. It uses the file gen40.csd.
- +- Example 1307. Example of the GEN40 generator. + Example 1322. Example of the GEN40 generator.
See the sections Real-time Audio and Command Line Flags for more information on using command line flags.
diff --git a/GEN41.html b/GEN41.html index b7b34f781d3..62ae855b859 100644 --- a/GEN41.html +++ b/GEN41.html @@ -39,19 +39,19 @@
- +Description
Generates a discrete random distribution function by giving a list of numerical pairs.
- +Performance
The first number of each pair is a value, and the second is the probability of that value to be chosen by a random algorithm. Even if any number can be assigned to the probability element of each pair, it is suggested to give it a percent value, in order to make it clearer for the user. @@ -61,20 +61,20 @@
Performance
- +Examples
Here is an example of the GEN41 generator. It uses the file gen41.csd.
- +- Example 1308. Example of the GEN41 generator. + Example 1323. Example of the GEN41 generator.
See the sections Real-time Audio and Command Line Flags for more information on using command line flags.
diff --git a/GEN42.html b/GEN42.html index ca7788cde7f..4ce3adbbd3d 100644 --- a/GEN42.html +++ b/GEN42.html @@ -39,19 +39,19 @@
- +Description
Generates a random distribution function of discrete ranges of values by giving a list of groups of three numbers.
- +Performance
The first number of each group is a the minimum value of the range, the second is the maximum value and the third is the probability of that an element belonging to that range of values can be chosen by a random algorithm. Probabilities for a range should be a fraction of 1, and the sum of the probabilities for all the ranges should total 1.0. @@ -61,20 +61,20 @@
Performance
- +Examples
Here is an example of the GEN42 generator. It uses the file gen42.csd.
- +- Example 1309. Example of the GEN42 generator. + Example 1324. Example of the GEN42 generator.
See the sections Real-time Audio and Command Line Flags for more information on using command line flags.
diff --git a/GEN43.html b/GEN43.html index 639f835d90e..82e10b858b5 100644 --- a/GEN43.html +++ b/GEN43.html @@ -39,7 +39,7 @@
- +Examples
Here is an example of the GEN43 routine. It uses the files gen43.csd. @@ -106,13 +106,13 @@
Examples
- +- Example 1310. An example of the GEN43 routine. + Example 1325. An example of the GEN43 routine.
diff --git a/GEN44.html b/GEN44.html index c5300a58459..87c2abde5b4 100644 --- a/GEN44.html +++ b/GEN44.html @@ -39,27 +39,27 @@
- +Performance
The file named in version 1 or the file stiff.num in the second case is read to create the matrix.
- +Matrix Format
The first line of the file should be @@ -68,9 +68,10 @@
Matrix Format
” and it creates a square matrix of the indicated size. This is followed by lines of two or three numbers, - the first two denoting a connection from the first to the second - and the third is a weight. If the third is omitted it is taken as - value 1. The list is terminated by a + the first two denoting a connection from the first to the second. + The third number is a weight; a weight of 2 is like having two links so more + information gets distributed, while a zero weight means no link. If this third + number is omitted it is taken as value 1. The list is terminated by a “ </MATRIX> ” @@ -116,30 +117,35 @@Matrix Format
- +Examples
Here is an example of the GEN44 generator. It uses the file gen44.csd.
- ++- Example 1311. Example of the GEN44 generator. + Example 1326. Example of the GEN44 generator.
+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 --limiter=0.95 ;;;realtime audio out & and limit loud sounds +;-iadc ;;;uncomment -iadc if realtime audio input is needed too +; For Non-realtime ouput leave only the line below: +; -o gen44.wav -W ;;; for file output any platform </CsOptions> <CsInstruments> sr = 44100 ksmps = 32 nchnls = 1 -0dbfs = 1 +0dbfs = 1 instr scan @@ -156,8 +162,7 @@+Examples
;scanu2 init,irate,ifndisplace,ifnmass,ifnmatrix,ifncentr,ifndamp,kmass,kmtrxstiff, ; kcentr, kdamp, ileft, iright, kpos, kdisplace, ain, idisp, id -scanu2 -1, irate, 6, 2, 3, 4, 5, kmass, kstiff, kcenter, kdamp, .2, .7, kpos, -kdisplace, a0, 1, 2 +scanu2 -1, irate, 6, 2, 3, 4, 5, kmass, kstiff, kcenter, kdamp, .2, .7, kpos, kdisplace, a0, 1, 2 ;ar scans kamp, kfreq, ifntraj, id a1 scans ampdbfs(p4), cpspch(p5), 7, 2 @@ -168,26 +173,15 @@Examples
</CsInstruments> <CsScore> ; Initial displacement condition -f1 0 16 10 1 ; sine hammer - -; Masses -f2 0 16 -7 1 16 1 - -; Spring matrices -f3 0 0 -44 "string_with_extras-16.matrxT" - -; Centering force -f4 0 16 -7 1 16 1 ; uniform initial centering - -; Damping -f5 0 16 -7 1 16 1 ; uniform damping - +f1 0 16 10 1 ; sine hammer +f2 0 16 -7 1 16 1 ; Masses +f3 0 0 -44 "string_with_extras-16.matrxT" ; Spring matrices +f4 0 16 -7 1 16 1 ; Centering force, uniform initial centering +f5 0 16 -7 1 16 1 ; Damping, uniform damping ; Initial displacement - (displacement, vel, and acceleration ; Acceleration is from stiffness matrix pos effect - increases acceleration f6 0 16 -7 .01 16 .01 ; uniform initial velocity-displacement - -; Trajectories -f7 0 16 -5 .001 16 16 +f7 0 16 -5 .001 16 16 ; Trajectories i"scan" 0 2 -6 7.00 i"scan" 2 2 -6 5.00 @@ -196,7 +190,71 @@Examples
i"scan" 8 2 -6 10.00 e +</CsScore> +</CsoundSynthesizer> ++
++ Here is another example of GEN44. It uses the file gen44-2.csd. The matrix file has 1024 masses. +
++ ++ Example 1327. Second example of the GEN44 generator. +
+++ ++<CsoundSynthesizer> +<CsOptions> +; Select audio/midi flags here according to platform +-odac --limiter=0.95 ;;;realtime audio out & and limit loud sounds +;-iadc ;;;uncomment -iadc if realtime audio input is needed too +; For Non-realtime ouput leave only the line below: +; -o gen44-2.wav -W ;;; for file output any platform +</CsOptions> +<CsInstruments> + +sr = 44100 +ksmps = 32 +nchnls = 2 +0dbfs = 1 + +; by Menno Knevel 2024 + +instr 1 ; move the grain table + +initial ftgenonce 1, 0, 1024, 10, 1 ; initial position = sine wave +idispl ftgenonce 2, 0, 1024, -7, .01, 1024, .01 ; displace +imass ftgenonce 3, 0, 1024, -7, 5, 1024, 5 ; masses +icent ftgenonce 4, 0, 1024, -7, .01, 1024, .1 ; centering +idamp ftgenonce 5, 0, 1024, -7, -.1, 1024, -.21 ; damping +itraj ftgenonce 6, 0, 1024, -7, 0, 1024, 1024 ; trajectory +iw ftgenonce 7, 0, 1024, 20, 2 ; Hanning window for GEN20 +a0 = 0 ; no audio injection +kline line .07, p3, 0 ; simple envelope +;scanu2 init, irate, ifndisplace, ifnmass, imatrix, ifncentr, ifndamp, kmass, kmtrxstiff, kcentr, kdamp, ileft, iright, kpos, kdisplace, ain, idisp, id +scanu2 1, .003, 2, 3, 100, 4, 5, 10, 6, 0.1, .9, .5, .1, 0, 0, a0, 0, -1 +aL grain2 p4, p4, 2, 25, 1, 7 +aR grain2 p4, p4, 2, 25, 1, 7 +aL dcblock aL +aR dcblock aR +outs aL * kline, aR * kline + +endin + +</CsInstruments> +<CsScore> +f100 0 0 -44 "circularstring_1024.matrxT" ; text matrix, to be found in manual/examples + +i1 0 20 466.16376098248423 +e </CsScore> </CsoundSynthesizer>@@ -207,10 +265,21 @@Examples
- + ++See also
+ +More information on the Scanned Synthesis opcodes: Working with Scanned Synthesis, written by Steven Yi, and some tutorials by Richard Boulanger.
+- +Examples
Here is an example of the GEN49 routine. It uses the files gen49.csd.
- +- Example 1312. An example of the GEN49 routine. + Example 1328. An example of the GEN49 routine.
- +Credits
Written by John ffitch
February 2009.
diff --git a/GEN51.html b/GEN51.html index 37720758f36..6df19629c85 100644 --- a/GEN51.html +++ b/GEN51.html @@ -39,7 +39,7 @@
- +Description
This subroutine fills a table with a fully customized micro-tuning @@ -49,12 +49,12 @@
Description
- +Syntax
f # time size -51 numgrades interval basefreq basekey tuningRatio1 tuningRatio2 .... tuningRationN- +Performance
The first four parameters (i.e. p5, p6, p7 and p8) define the following @@ -106,19 +106,19 @@
Performance
f1 0 64 -51 24 1.5 440 48 1 1.01 1.02 1.03 ..etc...- +Examples
Here is an example of the GEN51 routine. It uses the files gen51.csd.
- +- Example 1313. An example of the GEN51 routine. + Example 1329. An example of the GEN51 routine.
diff --git a/GEN52.html b/GEN52.html index 274fb424116..18d75950365 100644 --- a/GEN52.html +++ b/GEN52.html @@ -40,7 +40,7 @@
- +Description
GEN52 creates an interleaved multichannel table from the specified @@ -60,12 +60,12 @@
Description
- +Syntax
f # time size 52 nchannels fsrc1 offset1 srcchnls1 [fsrc2 offset2 srcchnls2 ... fsrcN offsetN srcchnlsN]- +Example
; source tables @@ -81,14 +81,14 @@Example
Here is a complete example of the GEN52 generator. It uses the file gen52.csd.- +- Example 1314. Example of the GEN52 generator. + Example 1330. Example of the GEN52 generator.
See the sections Real-time Audio and Command Line Flags for more information on using command line flags.
diff --git a/GEN53.html b/GEN53.html index 9a3e953530a..c41e5623c21 100644 --- a/GEN53.html +++ b/GEN53.html @@ -41,7 +41,7 @@
- +Description
GEN53 creates an impulse response function table with either a @@ -52,7 +52,7 @@
Description
- +Example
Here is a complete example of the GEN53 generator. It uses the file gen53.csd.
- +- Example 1315. Example of the GEN53 generator. + Example 1331. Example of the GEN53 generator.
See the sections Real-time Audio and Command Line Flags for more information on using command line flags.
diff --git a/GENexp.html b/GENexp.html index f909fd170c2..26a9e422ce5 100644 --- a/GENexp.html +++ b/GENexp.html @@ -39,19 +39,19 @@
- +Examples
Here is a simple example of the GENexp routine. It uses the file genexp.csd.
- +- Example 1317. Example of the GENexp routine. + Example 1333. Example of the GENexp routine.
See the sections Real-time Audio and Command Line Flags for more information on using command line flags.
- +diff --git a/GENfarey.html b/GENfarey.html index 5a7e6460202..bfbdec70af2 100644 --- a/GENfarey.html +++ b/GENfarey.html @@ -39,7 +39,7 @@See Also
GENexp and @@ -155,7 +155,7 @@
See Also
More information on this routine: http://www.csoundjournal.com/issue11/distortionSynthesis.html, written by Victor Lazzarini
- +Examples
@@ -259,16 +259,16 @@
Examples
- +- Example 1320. A simple example of the GENfarey routine. + Example 1336. A simple example of the GENfarey routine.
See the sections Real-time Audio and Command Line Flags for more information on using command line flags.
- +<CsoundSynthesizer> <CsOptions> @@ -307,14 +307,14 @@Examples
Here is a complete example of the GENfarey routine. It uses the files genfarey-2.csd.- +- Example 1321. Another example of the GENfarey routine. + Example 1337. Another example of the GENfarey routine.
See the sections Real-time Audio and Command Line Flags for more information on using command line flags.
++Credits
diff --git a/GENpadsynth.html b/GENpadsynth.html index 33ba03d3fc3..284811e23ac 100644 --- a/GENpadsynth.html +++ b/GENpadsynth.html @@ -39,7 +39,7 @@
- +Syntax
f # score_time table_size "padsynth" fundamental_frequency partial_bandwidth partial_scale harmonic_stretch profile_shape profile_shape_parameter partial1_amplitude [partial2_amplitude ...]- +Initialization
table_size -- Function table size. Should be large, @@ -130,19 +130,19 @@
Initialization
- +Examples
Here is an example of the GENpadsynth routine. It uses the files padsynth_gen.csd.
- +- Example 1323. An example of the GENpadsynth routine. + Example 1339. An example of the GENpadsynth routine.
- +Credits
Written by Michael Gogins
New in version 6.05
diff --git a/GENquadbezier.html b/GENquadbezier.html index 6bf74781b42..dc5bcb25fac 100644 --- a/GENquadbezier.html +++ b/GENquadbezier.html @@ -39,7 +39,7 @@
- +Initialization
x2, x3, etc. -- Locations in table at which to attain the following y value. Must be in increasing order. It is assumed that x1 equals 0. If the last value is less than size, then the rest will be set to zero. Should not be negative. @@ -70,20 +70,20 @@
Initialization
- +Examples
Here is a simple example of the GENquadbezier routine. It uses the file genquadbezier.csd.
- +- Example 1319. Example of the GENquadbezierroutine. + Example 1335. Example of the GENquadbezierroutine.
See the sections Real-time Audio and Command Line Flags for more information on using command line flags.
- +Credits
Written by Guillermo Senna
2016
diff --git a/GENsone.html b/GENsone.html index 0537e312bb2..472f26e3988 100644 --- a/GENsone.html +++ b/GENsone.html @@ -39,19 +39,19 @@
- +Examples
Here is an example of the GENsone routine. It uses the files gensone.csd.
- +- Example 1318. An example of the GENsone routine. + Example 1334. An example of the GENsone routine.
diff --git a/GENtanh.html b/GENtanh.html index 96f867a30b2..0938fb0e305 100644 --- a/GENtanh.html +++ b/GENtanh.html @@ -39,19 +39,19 @@
- +Examples
Here is a simple example of the GENtanh routine. It uses the file gentanh.csd.
- +- Example 1316. Example of the GENtanh routine. + Example 1332. Example of the GENtanh routine.
See the sections Real-time Audio and Command Line Flags for more information on using command line flags.
diff --git a/GENwave.html b/GENwave.html index dc79b795502..df5db370e31 100644 --- a/GENwave.html +++ b/GENwave.html @@ -39,7 +39,7 @@
- +Description
Creates a compactly supported wavelet, scaling function or wavelet @@ -62,12 +62,12 @@
Description
- +Examples
Here is an example of the GENwave routine. It uses the file genwave.csd.
- +- Example 1322. Example of the GENwave routine. + Example 1338. Example of the GENwave routine.
@@ -106,7 +106,7 @@
Examples
command line flags.- +Credits
Written by Gleb Rogozinsky
Saint-Petersburg University of Film and Television
diff --git a/ImageopcodesTop.html b/ImageopcodesTop.html index a0ade49cec1..145c996f7a7 100644 --- a/ImageopcodesTop.html +++ b/ImageopcodesTop.html @@ -8,8 +8,8 @@ - - + + @@ -19,8 +19,8 @@Image processing opcodes -