FL opcodes work OK with QuteCsound, just 'run in terminal' instead.
Manual example is not great. Opcodes work alright.
Victor
----- Original Message -----
From: Jim Aikin <midiguru23@sbcglobal.net>
Date: Wednesday, January 5, 2011 5:37 pm
Subject: [Csnd] Re: wguide2 broken?
To: csound@lists.bath.ac.uk
> On 1/5/2011 12:43 AM, Iain McCurdy [via Csound] wrote:
> > Hi Jim,
> >
> > You might like to try this example:
> > http://www.iainmccurdy.org/csoundrealtimeexamples/waveguides/wguide2.csd
> > it should let you explore a little of what the opcode does...
>
> It might, if I could get it to run. I'm using QuteCsound exclusively,
> and it doesn't like the FL opcodes. At least, that seems to be the
> source of the problem. I tried switching them on in the Configure box,
> and I tried the Run in Term button. No luck. So I remain entirely in the
> dark.
>
> However: If I infer from your message that the opcode works, then
> clearly the example in the manual is broken. Can someone suggest a way
> to fix it (and preferably without using opcodes that are incompatible
> with the basic Windows front end)?
>
> Maybe somebody can take a look at the example and spot immediately what
> the problem is. If so, let me know and I'll make changes.
>
> --JA
>
>
>
> View this message in context: Re: wguide2 broken?
> Sent from the Csound - General mailing list archive at Nabble.com.
Dr Victor Lazzarini, Senior Lecturer, Dept. of Music,
National University of Ireland, Maynooth