Csound Csound-dev Csound-tekno Search About

RE: Long Tone Problem

Date1998-03-31 12:48
FromJamie Bullock
SubjectRE: Long Tone Problem

----------
From: 	tolve[SMTP:tlv@tuna.net]
Sent: 	31 March 1998 00:44
To: 	d1st@earthlink.net; csound@maths.ex.ac.uk
Subject: 	Re: Long Tone Problem

try removing carriage returns from linseg.

tolve

david f. wrote:
>Hi to All -
>
>I've been trying to build a simple set of sustained tones that move through
>various timed glissandi stages (see enclosed files). I keep getting a fatal
>error message stating "low on ARGSPACE". Apparently my linsegs are too long.
>Am I up against a wall? If so, can anyone see a more elegant way to achieve
>this? Am I missing something obvious?
>
>Thanks
>
>David F.
>
>
>;ORC
>sr = 44100
>kr = 4410
>ksmps = 10
>nchnls = 2
>
>	instr 1
>kamp1 linseg p4, p3, p4
>kamp2 linseg p4*0, p3, p4*0
>kcps     linseg p5, p3*7/64, p5, p3*1/64, p5*9/10, p3*7/64, p5*9/10, p3*1/64,
>p5, p3*7/64, p5, p3*1/64, p5*9/10, p3*7/64, p5*9/10, p3*1/64, p5, p3*7/64, p5,
>p3*1/64, p5*9/10, p3*7/64, p5*9/10, p3*1/64, p5, p3*7/64, p5, p3*1/64,
>p5*9/10, p3*7/64, p5*9/10, p3*1/64, p5
>aout1  oscil  kamp1, kcps, 1
>aout2  oscil  kamp2, kcps, 1
>	outs 	aout1, aout2
>	endin
>
>
>	instr 2
>kamp1 linseg p4, p3, p4
>kamp2 linseg p4*0, p3, p4*0
>kcps     linseg p5*6/5, p3*3/64, p5*6/5, p3*1/64, p5*4/3, p3*3/64, p5*4/3,
>p3*1/64, p5*6/5, p3*3/64, p5*6/5, p3*1/64, p5*9/8, p3*3/64, p5*9/8, p3*1/64,
>p5*6/5, p3*3/64, p5*6/5, p3*1/64, p5*4/3, p3*3/64, p5*4/3, p3*1/64, p5*6/5,
>p3*3/64, p5*6/5, p3*1/64, p5*9/8, p3*3/64, p5*9/8, p3*1/64, p5*6/5, p3*3/64,
>p5*6/5, p3*3/64, p5*6/5, p3*1/64, p5*4/3, p3*3/64, p5*4/3, p3*1/64, p5*6/5,
>p3*3/64, p5*6/5, p3*1/64, p5*9/8, p3*3/64, p5*9/8, p3*1/64, p5*6/5, p3*3/64,
>p5*6/5, p3*1/64, p5*4/3, p3*3/64, p5*4/3, p3*1/64, p5*6/5, p3*3/64, p5*6/5,
>p3*1/64, p5*9/8, p3*3/64, p5*9/8, p3*1/64, p5*6/5, p3*3/64, p5*6/5
>aout1  oscil  kamp2, kcps, 1
>aout2  oscil  kamp1, kcps, 1
>	outs 	aout1, aout2
>	endin
>
>	instr 3
>kamp1 linseg p4, p3, p4
>kamp2 linseg p4*0, p3, p4*0
>kcps     linseg p5*3/2, p3*3/64, p5*3/2, p3*1/64, p5*5/3, p3*3/64, p5*5/3,
>p3*1/64, p5*3/2, p3*3/64, p5*3/2, p3*1/64, p5*3/2, p3*3/64, p5*3/2, p3*1/64,
>p5*3/2, p3*3/64, p5*3/2, p3*1/64, p5*5/3, p3*3/64, p5*5/3, p3*1/64, p5*3/2,
>p3*3/64, p5*3/2, p3*1/64, p5*3/2, p3*3/64, p5*3/2, p3*1/64, p5*3/2,
>p3*3/64, p5*3/2
>aout1  oscil  kamp1, kcps, 1
>aout2  oscil  kamp2, kcps, 1
>	outs 	aout1, aout2
>	endin
>
>
>-------------------------------------------------------------------------------
>--------
>;SCO
>f1 0 8192 10 1 .5 .3333 .25 .2 .1667
>t 0 25
> ;inst    start   dur   ampl             freq
>  i1            0       16       3000      174.6141
>  i2            0       16       3000      174.6141
>  i3            0       16       3000      174.6141
>
>
>e



Alternatively create your linseg envelope by using GEN07 (ie. something like f2 0 128 7  ) in your score ; if you have WCShell, you can draw it! Then index the table from the orchestra using something like :
			
			kndx line 0,idur, 
			kcps tablei kndx, 
kcps=kcps*p5 This seems more efficient to me! JamieB

Date1998-04-01 14:24
FromPeter Whincop
Subjectmail archives
Hi,

I have had three problems witht the list archives. (1) Sometimes James's
server doesn't permit me access, generally when I most desperately need to
read something, say, about convolve; (2) The messages are often not
referenced correctly from the indices, especially when following a thread
from inside a message; and (3) Right now (1330 April 1, and this is no
joke) there are almost no messages listed.

I was hoping someone might look into this.

Thanks,

Peter