Hi Fergal,

A fair number of opcodes are still builtin to csound, so it is
possilbie that the orchestra uses just those that are builtin except
ftgen. The error message itself indicates that for some reason or
another, OPCODEDIR was not set when the framework was installed.

Did you have any other versions of csound5 installed before installing
the one you have now?  I remember there being some bug mentioned that
was Mac related and having to run the installer twice.  You might want
to try deleting any installed csound and reinstalling from scratch.

Hope that helps!
steven


On 2/23/06, Fergal Dowling <fergaldowling@ear.ie> wrote:
> Hi,
>
> Recently updated to Csound5 (Csound5.00_OSX10.3) on Mac OSX 10.3.9.
> All is fine except that I get the following warning with ftgen.
>
> error:  no legal opcode, line 12:
> gitemp ftgen 20, 0, 1024, 9, 1, 1, 0
>          instr   1
>          ################################################################
>          #               WARNING: OPCODEDIR IS NOT SET !                #
>          # Csound requires this environment variable to be set to find  #
>          # its plugin libraries. If it is not set, you may experience   #
>          # missing opcodes, audio/MIDI drivers, or utilities.           #
>          ################################################################
>
> The orc runs fine with this line (gitemp ftgen 20, 0, 1024, 9, 1, 1, 0)
> commented out, that is to say, no other opcodes in this orchestra cause
> this warning. On environmental variables, the readme says,
> "The Csound 5 framework sets the plugin opcode directory
> automatically, so you do not have to do anything about it.
> It is located inside the CsoundLib.Framework folder, under
> Resources/Opcodes (Opcodes64 for doubles version)."
>
> Any ideas why ftgen casues this?
> Thanks,
> Fergal Dowling
>
>
>
>