back to list

Rational Interval Tester Csound tool (high fifths for Gene)

🔗Cameron Bobro <misterbobro@yahoo.com>

12/23/2006 9:43:22 AM

Here you go! If you don't already have Csound (and WinXsoundPro
frontend if you're in Windows) on your machine, shame on you!

The .orc, copy and paste....
----------------------------------------------------------------

;Rational Interval testing Csound instrument by Cameron Bobro

sr = 48000
kr = 48000
ksmps = 1
nchnls = 1

instr 1

kpitch = p5*(p6/p7)

kenv1 expseg .0001,(p3*.1)+.1, 1, p3*.2, .4, (p3*.5)-.1, .5,
p3*.2, .0001
kamp = p4*kenv1

kpwm1 poscil3 .1,.21,1
kpw1 = .31 + kpwm1
kpwm2 poscil3 .1, .13, 2
kpw2 = .84 + kpwm2

;ares vco2 kamp, kcps, imode, kpw, kphs [, inyx]
apuls1 vco2 kamp*.6, kpitch, 2, kpw1
apuls2 vco2 kamp*.4, kpitch, 2, kpw2

;asig moogladder ain, kcf, kres
alpf1 moogladder apuls1, 3456,.1

aout dcblock alpf1
out aout

endin

------------------------------------------------------
and here's the .sco, copy and paste....
-------------------------------------------------------

;Rational Interval testing Csound score by Cameron Bobro
;If it's too slow or quick for you, simply change the bpm
;rate (directly below) from 60 to whatever tickles your fancy.

t 0 60

;here are the function tables, change them if you know what
;you're doing (of course, if you really know what you're
;doing you'll realize that they are perfect. :-P )

f 1 0 8388608 9 1 1 0
f 2 0 8388608 9 1 1 33

; here are some rational "high fifths". If mirrored against 3/2,
;you'll get tempered lower fifths, often of a "meantone" nature.

; 3/2 701.955 cents perfect fifth
; 864/575 704.963 cents Bobro's fifth :-P
; 176/117 706.880 cents
; 325/216 707.290 cents
; 450/299 707.735 cents
; 414/275 708.239 cents mirror of 5/17 meantone
; 529/351 710.156 cents
; 104/69 710.298 cents
; 299/198 713.574 cents

;below, we have:
;instrument #, start time, end time, volume, base freq. of 1/1,
;followed by Nominator and Denominator of ratio. "." means
;"same as above".

i 1 0 16 3866 208 1 1
i 1 3 13 2765 . 3 2
i 1 16 16 3868 . 1 1
i 1 19 13 2765 . 864 575
i 1 32 16 3868 . 1 1
i 1 35 13 2765 . 176 117
i 1 48 16 3868 . 1 1
i 1 51 13 2765 . 325 216
i 1 64 16 3868 . 1 1
i 1 67 13 2765 . 450 299
i 1 80 16 3868 . 1 1
i 1 83 13 2765 . 414 275
i 1 96 16 3868 . 1 1
i 1 99 13 2765 . 529 351
i 1 112 16 3868 . 1 1
i 1 115 13 2765 . 104 69
i 1 128 16 3868 . 1 1
i 1 131 13 2765 . 299 198

e

🔗monz <monz@tonalsoft.com>

12/23/2006 4:07:28 PM

hi Cameron,

--- In tuning@yahoogroups.com, "Cameron Bobro" <misterbobro@...> wrote:
>
> Here you go! If you don't already have Csound (and WinXsoundPro
> frontend if you're in Windows) on your machine, shame on you!
>
> The .orc, copy and paste....
> ----------------------------------------------------------------
>
> <snip>
>
> ------------------------------------------------------
> and here's the .sco, copy and paste....
> -------------------------------------------------------
>
> <snip>

Apparently you don't know about the .csd "unified"
Csound file format, which united the .orc and .sco
in one file.

You have to use a few tags in angle brackets to delimit
the different sections, and save it with .csd extension:

; --- begin .csd template -----

<CsoundSynthesizer>

<CsOptions>
; command-line options go here
</CsOptions>

<CsInstruments>
; [filename].orc file goes here
</CsInstruments>

<CsScore>
; [filename].sco file goes here
</CsScore>

</CsoundSynthesizer>

; --- end .csd template ---

Blank lines are optional, i put them in for clarity.

I also find it useful to separate the different sections
of the file with horizontal double-lines ... this is the
template that i actually use to create my own .csd files:

; ---- begin monz's .csd template --------

;***************************************************************************
;[filename].csd
;[description].

<CsoundSynthesizer>

;===========================================================================

<CsOptions>

-W -s -o [filename].wav

</CsOptions>

;===========================================================================

<CsInstruments>

;/* [filename].orc */

;Initialize the global variables.

sr = 44100
kr = 4410
ksmps = 10
nchnls = 1

;Instrument #1 - an unfiltered noise waveform.

instr 1
;

;OUTPUT OPCODE AMP
asig

out asig
endin

</CsInstruments>

;===========================================================================

<CsScore>

;/* [filename].sco */

;p1 p2 p3

e

</CsScore>

;===========================================================================

</CsoundSynthesizer>
;***************************************************************************

; ---- end monz's .csd template ----

BTW, another plug for Tonescape: it can export Tonescape files
as Csound .csd files.

-monz
http://tonalsoft.com
Tonescape microtonal music software

🔗Cameron Bobro <misterbobro@yahoo.com>

12/24/2006 3:40:28 AM

Of course I'm aware of the .csd format, I just think it's not as
useful as the original .orc/.sco format, especially if you're doing
very large projects, mixing and matching instruments and scores.
This could be a habit/geist thing, coming from pen and paper scoring,
I must admit.

It's great that Tonescape can export .csd files, that's an awesome
feature from where I'm standing (even though I'd convert them
to .orc/.sco in WinXsound :-) )

-Cameron Bobro

--- In tuning@yahoogroups.com, "monz" <monz@...> wrote:
>
> hi Cameron,
>
>
> --- In tuning@yahoogroups.com, "Cameron Bobro" <misterbobro@>
wrote:
> >
> > Here you go! If you don't already have Csound (and WinXsoundPro
> > frontend if you're in Windows) on your machine, shame on you!
> >
> > The .orc, copy and paste....
> > ----------------------------------------------------------------
> >
> > <snip>
> >
> > ------------------------------------------------------
> > and here's the .sco, copy and paste....
> > -------------------------------------------------------
> >
> > <snip>
>
>
>
> Apparently you don't know about the .csd "unified"
> Csound file format, which united the .orc and .sco
> in one file.
>
> You have to use a few tags in angle brackets to delimit
> the different sections, and save it with .csd extension:
>
> ; --- begin .csd template -----
>
> <CsoundSynthesizer>
>
> <CsOptions>
> ; command-line options go here
> </CsOptions>
>
> <CsInstruments>
> ; [filename].orc file goes here
> </CsInstruments>
>
> <CsScore>
> ; [filename].sco file goes here
> </CsScore>
>
> </CsoundSynthesizer>
>
> ; --- end .csd template ---
>
>
> Blank lines are optional, i put them in for clarity.
>
> I also find it useful to separate the different sections
> of the file with horizontal double-lines ... this is the
> template that i actually use to create my own .csd files:
>
>
> ; ---- begin monz's .csd template --------
>
> ;******************************************************************
*********
> ;[filename].csd
> ;[description].
>
> <CsoundSynthesizer>
>
>
> ;==================================================================
=========
>
>
> <CsOptions>
>
> -W -s -o [filename].wav
>
> </CsOptions>
>
>
> ;==================================================================
=========
>
>
> <CsInstruments>
>
> ;/* [filename].orc */
>
> ;Initialize the global variables.
>
> sr = 44100
> kr = 4410
> ksmps = 10
> nchnls = 1
>
>
> ;Instrument #1 - an unfiltered noise waveform.
>
> instr 1
> ;
>
> ;OUTPUT OPCODE AMP
> asig
>
> out asig
> endin
>
>
> </CsInstruments>
>
>
> ;==================================================================
=========
>
>
> <CsScore>
>
> ;/* [filename].sco */
>
>
> ;p1 p2 p3
>
> e
>
> </CsScore>
>
>
> ;==================================================================
=========
>
>
> </CsoundSynthesizer>
> ;******************************************************************
*********
>
> ; ---- end monz's .csd template ----
>
>
> BTW, another plug for Tonescape: it can export Tonescape files
> as Csound .csd files.
>
>
> -monz
> http://tonalsoft.com
> Tonescape microtonal music software
>

🔗monz <monz@tonalsoft.com>

12/24/2006 12:06:36 PM

Hi Cameron,

--- In tuning@yahoogroups.com, "Cameron Bobro" <misterbobro@...> wrote:

> Of course I'm aware of the .csd format, I just think it's
> not as useful as the original .orc/.sco format, especially
> if you're doing very large projects, mixing and matching
> instruments and scores.

OK, i can see your point there.

> This could be a habit/geist thing, coming from pen
> and paper scoring, I must admit.

I can definitely relate to that!

> It's great that Tonescape can export .csd files, that's
> an awesome feature from where I'm standing (even though
> I'd convert them to .orc/.sco in WinXsound :-) )

It's good that that's so easy to do!
The simplest way to translate from one file format to another
is to simply delete a few extraneous lines of code!
;-)

-monz
http://tonalsoft.com
Tonescape microtonal music software