> error:  too many input args, line 7180:
>         FLsetVal        gkupdate1, kVU, gihsBasSynampD

According to the code FLsetVal takes 2 i-rate arguments, as it did in
csound4; that explains many many errors

> Failed to find opcode_size in library: ./csound: undefined symbol: 
> opcode_size

That is an artifact of the way opcode loading is done, which is not
how I think it should be

> error:  no legal opcode, line 6880:
>         tablew          kcps, kndx, ifn                         ;

Thsi is a bug.  tableiw and tablew are in the code, but not the
correct specification (I think).  Will adjust

> error:  no legal opcode, line 10464:
> a1      fof2    iamp, gkGrn1grfq, kform, gkGrn1oct_mc, kband, kris, 
> kdur, kdec, iolaps, ifna, ifnb, itotdur, kphs, gkGrn1gli

True.  There is no fof2

==John ffitch

jpff@codemist.co.uk wrote:

>>error:  too many input args, line 7180:
>>        FLsetVal        gkupdate1, kVU, gihsBasSynampD
>>    
>>
>
>According to the code FLsetVal takes 2 i-rate arguments, as it did in
>csound4; that explains many many errors
>
According to the Conder manual:


    Syntax

*FLsetVal* ktrig, kvalue, ihandle

...


    Initialization

/ihandle/ -- an integer number (used as unique identifier) taken from 
the output of a previously located widget opcode (which corresponds to 
the target widget). It is used to unequivocally identify the widget when 
modifying its appearance with this class of opcodes. The user must not 
set the /ihandle/ value directly, otherwise a Csound crash will occur.


    Performance

/ktrig/ -- not implemented yet.

/kvalue/ -- not implemented yet.



So I'm a little confused now. ImproSculpt was running under 4.2x without 
problems with FLsetVal, but something's changed somewhere.

>>Failed to find opcode_size in library: ./csound: undefined symbol: 
>>opcode_size
>>    
>>
>
>That is an artifact of the way opcode loading is done, which is not
>how I think it should be
>

Is the error message significant ?

I have 'export OPCODEDIR=/home/dlphilp/csound5/Opcodes' in .bashrc, but 
I've yet to find if that's the correct invocation. I ask again, what are 
the new environment variables and how are they defined ? (I've seen 
OPCODIR and OPCODE_DIR in past messages, I don't know which is correct). 
Is there a similar path definition for the Plugins directory ?

>>error:  no legal opcode, line 6880:
>>        tablew          kcps, kndx, ifn                         ;
>>    
>>
>
>Thsi is a bug.  tableiw and tablew are in the code, but not the
>correct specification (I think).  Will adjust
>
I'm now working with Oeyvind's latest version, it looks like the tablew 
stuff is removed or redefined. The calls to tablewa cause no trouble.

>>error:  no legal opcode, line 10464:
>>a1      fof2    iamp, gkGrn1grfq, kform, gkGrn1oct_mc, kband, kris, 
>>kdur, kdec, iolaps, ifna, ifnb, itotdur, kphs, gkGrn1gli
>>    
>>
>
>True.  There is no fof2
>
Ouch. It appears that ImproSculpt actually uses fof2's k-rate kphs, so a 
simple conversion to the fof opcode doesn't look so simple. Can fof2 be 
re-incorporated for Csound5 ?

Btw, the output from the latest ImproSculpt version includes these errors:

    error:  no legal opcode, line 17180:
    aoutR buthp     aoutR, klfroll
    error:  no legal opcode, line 17186:
    kVU     maxk    aoutL, gkupdate1, 0
    error:  no legal opcode, line 17294:
    a4      clip    a4*0.6, 0, 32000, 0.9

which is really weird because I could swear that yesterday I saw maxk in 
the list. I think I'm still confused WRT the correct settings for the 
new environment variables...

Thanks for the help, John, but alas, it looks like ImproSculpt will have 
to wait for Csound5 to acquire the capabilities of CsoundAV before Linux 
users can run it again.

Incidentally, realtime audio output from Csound5 is really bad. I tried 
various settings for -b and -B yesterday but could not eliminate 
underruns and badly broken audio. I used '-o devaudio', perhaps I should 
be trying another output designator, something specific to Portaudio ? I 
see where PA defines the available devices, but no instructions yet on 
how to select any particular device. At the risk of heresy I'll again 
respectfully recommend considering direct support for JACK.

Best regards,

dp

Hi Dave,

OPCODEDIR is the environment variable to set.  As you have it set,
csound should try to load everything that is in the
/home/dlphilp/csound5/Opcodes directory. I'm confused by your question
for "the Plugins directory" though as the OPCODEDIR is the path for
opcode plugins.

What I have set is:

export OPCODEDIR=/usr/local/lib/csound

and when I do a compile of csound5 I copy *.so into that directory. 
(Granted, I should probably use /usr/local/share/csound ...).

Hope that helps!

steven

> I have 'export OPCODEDIR=/home/dlphilp/csound5/Opcodes' in .bashrc, but 
> I've yet to find if that's the correct invocation. I ask again, what are 
> the new environment variables and how are they defined ? (I've seen 
> OPCODIR and OPCODE_DIR in past messages, I don't know which is correct). 
> Is there a similar path definition for the Plugins directory ?
>