Dear list,

I am trying to explore the squinewave-opcode, but only the example of 
the manual works fine for me, while my own attempts to use this opcode 
keep failing for some reason.

The following part of the orc...

afreq        upsamp        kfreq
asqareness    upsamp        ksqareness
asymmetry    upsamp        ksymmetry

adry        squinewave    afreq, asqareness, asymmetry

...produces this error message:

error:  Unable to find opcode entry for 'squinewave' with matching 
argument types:
Found: a squinewave aaa
        adry squinewave afreq ...
Line: 18
  from file 
/home/janjacobhofmann/Musik/blue-files/tempCsd7012903907802324955.csd (1)
Parsing failed due to syntax errors
Stopping on parser failure
cannot compile orchestra


...while changing the opcode-arguments to...


adry        squinewave    440, 1, 1

...creates this message:


error:  Unable to find opcode entry for 'squinewave' with matching 
argument types:
Found: a squinewave ccc
        adry squinewave 440 ...
Line: 19
  from file 
/home/janjacobhofmann/Musik/blue-files/tempCsd5677331623537944165.csd (1)
Parsing failed due to syntax errors
Stopping on parser failure
cannot compile orchestra

Has someone a hint for me what I am missing? Should I not also be able 
to use k-rate-arguments, if even a-rate is permitted for this opcode? I 
am using Csound 6.13.

Best,

Jan Jacob


-- 

sound      |      movement       |       object      |      space
sonic architecture     |      site: http://www.sonicarchitecture.de
spatial electronic composition    |    higher order ambisonic music

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

My reading of the code says it needs 4 inputs of type aaa and a or k

On Thu, 18 Jul 2019, Jan Jacob Hofmann wrote:

> Dear list,
>
> I am trying to explore the squinewave-opcode, but only the example of the 
> manual works fine for me, while my own attempts to use this opcode keep 
> failing for some reason.
>
> The following part of the orc...
>
> afreq        upsamp        kfreq
> asqareness    upsamp        ksqareness
> asymmetry    upsamp        ksymmetry
>
> adry        squinewave    afreq, asqareness, asymmetry
>
> ...produces this error message:
>
> error:  Unable to find opcode entry for 'squinewave' with matching argument 
> types:
> Found: a squinewave aaa
>        adry squinewave afreq ...
> Line: 18
>  from file 
> /home/janjacobhofmann/Musik/blue-files/tempCsd7012903907802324955.csd (1)
> Parsing failed due to syntax errors
> Stopping on parser failure
> cannot compile orchestra
>
>
> ...while changing the opcode-arguments to...
>
>
> adry        squinewave    440, 1, 1
>
> ...creates this message:
>
>
> error:  Unable to find opcode entry for 'squinewave' with matching argument 
> types:
> Found: a squinewave ccc
>        adry squinewave 440 ...
> Line: 19
>  from file 
> /home/janjacobhofmann/Musik/blue-files/tempCsd5677331623537944165.csd (1)
> Parsing failed due to syntax errors
> Stopping on parser failure
> cannot compile orchestra
>
> Has someone a hint for me what I am missing? Should I not also be able to use 
> k-rate-arguments, if even a-rate is permitted for this opcode? I am using 
> Csound 6.13.
>
> Best,
>
> Jan Jacob
>
>
> -- 
>
> sound      |      movement       |       object      |      space
> sonic architecture     |      site: http://www.sonicarchitecture.de
> spatial electronic composition    |    higher order ambisonic music
>
> Csound mailing list
> Csound@listserv.heanet.ie
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> Send bugs reports to
>       https://github.com/csound/csound/issues
> Discussions of bugs and features can be posted here
>

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Re-confirming John's assessment, the opcode entry in Csound's code is
defined as x which is a mandatory argument of either type k- or a-.

For Jan Jacob: You can add a 0 at the end like so:

adry        squinewave    afreq, asqareness, asymmetry, 0

and it should work.

The manual needs correction.

On Thu, Jul 18, 2019 at 1:45 PM  wrote:
>
> On Thu, Jul 18, 2019 at 05:27:17PM +0100, john wrote:
> > My reading of the code says it needs 4 inputs of type aaa and a or k
>
> Looks like the manual is wrong, as it explicitly says the fourth parameter
> is optional.
> >
> > >
> > >error:  Unable to find opcode entry for 'squinewave' with matching
> > >argument types:
> > >Found: a squinewave aaa
> > >       adry squinewave afreq ...
>
> I find this message confusing,  Wouldn't it be preferable to show what's
> required?
>
>         -- Pete --
>
> Csound mailing list
> Csound@listserv.heanet.ie
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> Send bugs reports to
>         https://github.com/csound/csound/issues
> Discussions of bugs and features can be posted here

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Syntax
aout [, asyncout] squinewave acps, aClip, aSkew [, asyncin] [, 
iMinSweep] [, iphase]

The 4th arg [asyncin] is *supposed* to be optional a-rate,
but there is (was) no code for this in Csound's internal opcode argument 
representation.

Therefore it's actually a required argument until such representation is 
implemented,
even if asyncin is not required for operation.
Best option is just enter a 0 as Steven suggested.

I seem to recall I asked about this at one time and it was supposed to 
be added "soon".
Guessing it would be generally useful in principle, but in reality very 
few ops use it,
so dev time is better spent fixing real problems.
(I don't have my email history while on holidays so can't check what was 
said, and btw nvm ;) )

Please if someone could add a note to set it to 0, or change the syntax 
in docs.
I don't have the right toolset on this machine.

Also grateful if it could be added to Dynamic Spectrum Oscillators page, 
at
https://csound.com/docs/manual/SiggenDynamic.html
- right now it's not linked anywhere, can only be found by going through 
the full opcode listing.

Thanks,
     /rasmus


2019-07-18 22:16 skrev Steven Yi:
> Re-confirming John's assessment, the opcode entry in Csound's code is
> defined as x which is a mandatory argument of either type k- or a-.
> 
> For Jan Jacob: You can add a 0 at the end like so:
> 
> adry        squinewave    afreq, asqareness, asymmetry, 0
> 
> and it should work.
> 
> The manual needs correction.
> 
> On Thu, Jul 18, 2019 at 1:45 PM  wrote:
>> 
>> On Thu, Jul 18, 2019 at 05:27:17PM +0100, john wrote:
>> > My reading of the code says it needs 4 inputs of type aaa and a or k
>> 
>> Looks like the manual is wrong, as it explicitly says the fourth 
>> parameter
>> is optional.
>> >
>> > >
>> > >error:  Unable to find opcode entry for 'squinewave' with matching
>> > >argument types:
>> > >Found: a squinewave aaa
>> > >       adry squinewave afreq ...
>> 
>> I find this message confusing,  Wouldn't it be preferable to show 
>> what's
>> required?
>> 
>>         -- Pete --
>> 
>> Csound mailing list
>> Csound@listserv.heanet.ie
>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> Send bugs reports to
>>         https://github.com/csound/csound/issues
>> Discussions of bugs and features can be posted here
> 
> Csound mailing list
> Csound@listserv.heanet.ie
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> Send bugs reports to
>         https://github.com/csound/csound/issues
> Discussions of bugs and features can be posted here

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Easier to add a second entry to the opcode.  Will look at doing that tomorrow.

⁣Sent from TypeApp ​

On Jul 19, 2019, 00:44, at 00:44, re  wrote:
>Syntax
>aout [, asyncout] squinewave acps, aClip, aSkew [, asyncin] [, 
>iMinSweep] [, iphase]
>
>The 4th arg [asyncin] is *supposed* to be optional a-rate,
>but there is (was) no code for this in Csound's internal opcode
>argument 
>representation.
>
>Therefore it's actually a required argument until such representation
>is 
>implemented,
>even if asyncin is not required for operation.
>Best option is just enter a 0 as Steven suggested.
>
>I seem to recall I asked about this at one time and it was supposed to 
>be added "soon".
>Guessing it would be generally useful in principle, but in reality very
>
>few ops use it,
>so dev time is better spent fixing real problems.
>(I don't have my email history while on holidays so can't check what
>was 
>said, and btw nvm ;) )
>
>Please if someone could add a note to set it to 0, or change the syntax
>
>in docs.
>I don't have the right toolset on this machine.
>
>Also grateful if it could be added to Dynamic Spectrum Oscillators
>page, 
>at
>https://csound.com/docs/manual/SiggenDynamic.html
>- right now it's not linked anywhere, can only be found by going
>through 
>the full opcode listing.
>
>Thanks,
>     /rasmus
>
>
>2019-07-18 22:16 skrev Steven Yi:
>> Re-confirming John's assessment, the opcode entry in Csound's code is
>> defined as x which is a mandatory argument of either type k- or a-.
>> 
>> For Jan Jacob: You can add a 0 at the end like so:
>> 
>> adry        squinewave    afreq, asqareness, asymmetry, 0
>> 
>> and it should work.
>> 
>> The manual needs correction.
>> 
>> On Thu, Jul 18, 2019 at 1:45 PM  wrote:
>>> 
>>> On Thu, Jul 18, 2019 at 05:27:17PM +0100, john wrote:
>>> > My reading of the code says it needs 4 inputs of type aaa and a or
>k
>>> 
>>> Looks like the manual is wrong, as it explicitly says the fourth 
>>> parameter
>>> is optional.
>>> >
>>> > >
>>> > >error:  Unable to find opcode entry for 'squinewave' with
>matching
>>> > >argument types:
>>> > >Found: a squinewave aaa
>>> > >       adry squinewave afreq ...
>>> 
>>> I find this message confusing,  Wouldn't it be preferable to show 
>>> what's
>>> required?
>>> 
>>>         -- Pete --
>>> 
>>> Csound mailing list
>>> Csound@listserv.heanet.ie
>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>> Send bugs reports to
>>>         https://github.com/csound/csound/issues
>>> Discussions of bugs and features can be posted here
>> 
>> Csound mailing list
>> Csound@listserv.heanet.ie
>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> Send bugs reports to
>>         https://github.com/csound/csound/issues
>> Discussions of bugs and features can be posted here
>
>Csound mailing list
>Csound@listserv.heanet.ie
>https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>Send bugs reports to
>        https://github.com/csound/csound/issues
>Discussions of bugs and features can be posted here

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Perfect, thanks beforehand!

- and apologies if there's additional work, the squarewave_init function 
is not set up to handle the shifted last arguments (iMinSweep and 
iphase) if asyncin is missing.

     /rasmus


2019-07-19 02:47 skrev John ff:
> Easier to add a second entry to the opcode.  Will look at doing that 
> tomorrow.
> 
> ⁣Sent from TypeApp ​
> 
> On Jul 19, 2019, 00:44, at 00:44, re  wrote:
>> Syntax
>> aout [, asyncout] squinewave acps, aClip, aSkew [, asyncin] [,
>> iMinSweep] [, iphase]
>> 
>> The 4th arg [asyncin] is *supposed* to be optional a-rate,
>> but there is (was) no code for this in Csound's internal opcode
>> argument
>> representation.
>> 
>> Therefore it's actually a required argument until such representation
>> is
>> implemented,
>> even if asyncin is not required for operation.
>> Best option is just enter a 0 as Steven suggested.
>> 
>> I seem to recall I asked about this at one time and it was supposed to
>> be added "soon".
>> Guessing it would be generally useful in principle, but in reality 
>> very
>> 
>> few ops use it,
>> so dev time is better spent fixing real problems.
>> (I don't have my email history while on holidays so can't check what
>> was
>> said, and btw nvm ;) )
>> 
>> Please if someone could add a note to set it to 0, or change the 
>> syntax
>> 
>> in docs.
>> I don't have the right toolset on this machine.
>> 
>> Also grateful if it could be added to Dynamic Spectrum Oscillators
>> page,
>> at
>> https://csound.com/docs/manual/SiggenDynamic.html
>> - right now it's not linked anywhere, can only be found by going
>> through
>> the full opcode listing.
>> 
>> Thanks,
>>     /rasmus
>> 
>> 

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here