I am getting a strange bug with fsig and I can't
trace it. Here's what's happening:

1. If I use the opcode pvsosc, I get a 'no legal
opcode', even though it's in the list.

2. If I use an expression as one of its arguments
I get a 'illegal character'

3. if however I create an fsig, whatever name it might
be, even with 0 framesize, the errors above disappear.

So, somehow, by invoking pvsinit before pvsosc, I get
the parser to recognise the opcode. That's very strange
isn't it? I looked at the pvsbasic.c

Here's the CSD that is giving the error. Uncomment
f10 pvsinit 0 to get it to work



-d -odac -B1024 -iadditivesynthesis.aiff


sr=44100
ksmps=100
nchnls=1

gklevel init 0
gks chnexport "meter",3


instr 1
;f1 pvsinit 0
ain in
k1 linenr 1, 0.1,0.1, 0.1
kf linsegr 500, 0.1, 4000, 1.5, 1000, 0.1, 100
fam pvsanal ain, 1024,256,1024,1
fex pvsosca k1*p4, p5, 1, 1024,256,1024,1
fvo pvsvoc  fam,fex,1,1
a1 pvsynth fvo
ks rms a1
gklevel = gklevel + ks
   out a1
endin

instr 100
gks = gklevel
gklevel = 0
endin




f1 0 16384 10 1
i100 0 360
e



-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net