Hi everyone,

I would like to ask, what Gen routine(s) do you prefer, and why?

Also, I see that some opcodes, such as VCO, require a function table, even though the waveform is to be indicated directly in the syntax. Is this for bit-quality purposes?

For example, here's an instrument where the waveform is a sawtooth, but the function table uses Gen 10 and a sinewave. Apparently the sinewave is ignored. -->

<CsoundSynthesizer>

<CsOptions>
-d -odac
</CsOptions>

<CsInstruments>
sr = 44100
ksmps = 32
nchnls = 2
0dbfs = 1

instr 1
kamp    linsegr    0,.2,.9,.7,.9,.5,0
kfreq    linsegr    330,.5,550,.2,220

a1    vco    kamp,kfreq,1    ;saw-wave
outs    a1,a1
endin

</CsInstruments>

<CsScore>

f1    0    16384    10    1

;p1    p2    p3

i1    0    8

</CsScore>

</CsoundSynthesizer>

brian

Ok, but if I don't provide the f1 table, the vco opcode gives an error. Is there a reason why I must provide f1, other than to avoid an error?

On Fri, 28 Dec 2018 13:35:30 +0000, Rory Walsh wrote:

You're not passing a function table to vco in this case. You are simply telling it to generate a sawtooth waveform. The 5th input parameter to vco sets the function table but you haven't set it.

On Fri, 28 Dec 2018 at 13:29, <brian@amsynth.com> wrote:

Hi everyone,

I would like to ask, what Gen routine(s) do you prefer, and why?

Also, I see that some opcodes, such as VCO, require a function table, even though the waveform is to be indicated directly in the syntax. Is this for bit-quality purposes?

For example, here's an instrument where the waveform is a sawtooth, but the function table uses Gen 10 and a sinewave. Apparently the sinewave is ignored. -->

 

-d -odac



sr = 44100
ksmps = 32
nchnls = 2
0dbfs = 1

instr 1
kamp    linsegr    0,.2,.9,.7,.9,.5,0
kfreq    linsegr    330,.5,550,.2,220

a1    vco    kamp,kfreq,1    ;saw-wave
outs    a1,a1
endin





f1    0    16384    10    1

;p1    p2    p3

i1    0    8

 

brian

 

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

The vco2 opcode creates default internal function tables that the user
can override in the orchestra header using vco2init, and then access
using regular table opcodes after obtaining the table number with
vco2ft or vco2ift.

Whenever you use wavetables, there are several things to do for
optimal accuracy. First, unless the table stores a very discontinuous
signal, always use an interpolating oscillator. This will drastically
improve the signal to noise ratio of the oscillator (yes, all
wavetable oscillators are noisy due to rounding errors in calculating
phase). Second, use the biggest table that you reasonably can, I
always use 2 to the 16th power or 65536.

Regards,
Mike
-----------------------------------------------------
Michael Gogins
Irreducible Productions
http://michaelgogins.tumblr.com
Michael dot Gogins at gmail dot com

On Fri, Dec 28, 2018 at 9:17 AM Rory Walsh  wrote:
>
> I always thought that parameter was optional, but then I wonder why you have to pass a pulse width for a sawtooth waveform? My advice would be to ditch the use of vco and vco2 which is faster and I think easier to use.
>
> On Fri, 28 Dec 2018 at 13:54,  wrote:
>>
>> Ok, but if I don't provide the f1 table, the vco opcode gives an error. Is there a reason why I must provide f1, other than to avoid an error?
>>
>>
>>
>> On Fri, 28 Dec 2018 13:35:30 +0000, Rory Walsh wrote:
>>
>> You're not passing a function table to vco in this case. You are simply telling it to generate a sawtooth waveform. The 5th input parameter to vco sets the function table but you haven't set it.
>>
>> On Fri, 28 Dec 2018 at 13:29,  wrote:
>>>
>>> Hi everyone,
>>>
>>> I would like to ask, what Gen routine(s) do you prefer, and why?
>>>
>>> Also, I see that some opcodes, such as VCO, require a function table, even though the waveform is to be indicated directly in the syntax. Is this for bit-quality purposes?
>>>
>>> For example, here's an instrument where the waveform is a sawtooth, but the function table uses Gen 10 and a sinewave. Apparently the sinewave is ignored. -->
>>>
>>>
>>>
>>>
>>>
>>>
>>> -d -odac
>>>
>>>
>>>
>>> sr = 44100
>>> ksmps = 32
>>> nchnls = 2
>>> 0dbfs = 1
>>>
>>> instr 1
>>> kamp    linsegr    0,.2,.9,.7,.9,.5,0
>>> kfreq    linsegr    330,.5,550,.2,220
>>>
>>> a1    vco    kamp,kfreq,1    ;saw-wave
>>> outs    a1,a1
>>> endin
>>>
>>>
>>>
>>>
>>>
>>> f1    0    16384    10    1
>>>
>>> ;p1    p2    p3
>>>
>>> i1    0    8
>>>
>>>
>>>
>>>
>>>
>>> brian
>>>
>>>
>>> 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

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

Thanks Rory and Mike!

Using wavetables in very interesting indeed, and I will have to look into it further.

For now, I see that just using vco2 allows me to avoid using a function table at all. I think this is best for now-- I'm only on page 4 of the tutorial! :D

brian

On Fri, 28 Dec 2018 14:54:34 +0100, brian@AMSYNTH.COM wrote:

Ok, but if I don't provide the f1 table, the vco opcode gives an error. Is there a reason why I must provide f1, other than to avoid an error?

 

On Fri, 28 Dec 2018 13:35:30 +0000, Rory Walsh wrote:

You're not passing a function table to vco in this case. You are simply telling it to generate a sawtooth waveform. The 5th input parameter to vco sets the function table but you haven't set it.

On Fri, 28 Dec 2018 at 13:29, <brian@amsynth.com> wrote:

Hi everyone,

I would like to ask, what Gen routine(s) do you prefer, and why?

Also, I see that some opcodes, such as VCO, require a function table, even though the waveform is to be indicated directly in the syntax. Is this for bit-quality purposes?

For example, here's an instrument where the waveform is a sawtooth, but the function table uses Gen 10 and a sinewave. Apparently the sinewave is ignored. -->

 

-d -odac



sr = 44100
ksmps = 32
nchnls = 2
0dbfs = 1

instr 1
kamp    linsegr    0,.2,.9,.7,.9,.5,0
kfreq    linsegr    330,.5,550,.2,220

a1    vco    kamp,kfreq,1    ;saw-wave
outs    a1,a1
endin





f1    0    16384    10    1

;p1    p2    p3

i1    0    8

 

brian

 

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

and poscil as standard oscillator, not oscil ...



On 28/12/18 18:07, Rory Walsh wrote:
> I always recommend that beginners to use vco2 so they don't have to
> worry about aliasing.
>
> On Fri, 28 Dec 2018 at 15:46,  > wrote:
>
>     __
>
>     Thanks Rory and Mike!
>
>     Using wavetables in very interesting indeed, and I will have to look
>     into it further.
>
>     For now, I see that just using vco2 allows me to avoid using a
>     function table at all. I think this is best for now-- I'm only on
>     page 4 of the tutorial! :D
>
>     brian
>
>
>
>     On Fri, 28 Dec 2018 14:54:34 +0100, brian@AMSYNTH.COM
>      wrote:
>
>>     Ok, but if I don't provide the f1 table, the vco opcode gives an
>>     error. Is there a reason why I must provide f1, other than to
>>     avoid an error?
>>
>>
>>
>>     On Fri, 28 Dec 2018 13:35:30 +0000, Rory Walsh wrote:
>>
>>         You're not passing a function table to vco in this case. You
>>         are simply telling it to generate a sawtooth waveform. The 5th
>>         input parameter to vco sets the function table but you haven't
>>         set it.
>>
>>         On Fri, 28 Dec 2018 at 13:29, >         > wrote:
>>
>>             Hi everyone,
>>
>>             I would like to ask, what Gen routine(s) do you prefer,
>>             and why?
>>
>>             Also, I see that some opcodes, such as VCO, require a
>>             function table, even though the waveform is to be
>>             indicated directly in the syntax. Is this for bit-quality
>>             purposes?
>>
>>             For example, here's an instrument where the waveform is a
>>             sawtooth, but the function table uses Gen 10 and a
>>             sinewave. Apparently the sinewave is ignored. -->
>>
>>
>>
>>
>>
>>
>>             -d -odac
>>
>>
>>
>>             sr = 44100
>>             ksmps = 32
>>             nchnls = 2
>>             0dbfs = 1
>>
>>             instr 1
>>             kamp    linsegr    0,.2,.9,.7,.9,.5,0
>>             kfreq    linsegr    330,.5,550,.2,220
>>
>>             a1    vco    kamp,kfreq,1    ;saw-wave
>>             outs    a1,a1
>>             endin
>>
>>
>>
>>
>>
>>             f1    0    16384    10    1
>>
>>             ;p1    p2    p3
>>
>>             i1    0    8
>>
>>
>>
>>
>>
>>             brian
>>
>>
>>             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
>
> 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

May I suggest squinewave in this context?

It's bandlimited, performs like poscil for sinewave, also 
saw-square-pulse and intermediate waveforms.
And has hardsync (also bandlimited but sharp pulse).

Easy to overlook in manual since it doesn't appear on any overview 
pages.

     /re

2018-12-28 21:55 skrev joachim heintz:
> and poscil as standard oscillator, not oscil ...
> 
> 
> 
> On 28/12/18 18:07, Rory Walsh wrote:
>> I always recommend that beginners to use vco2 so they don't have to
>> worry about aliasing.
>> 
>> On Fri, 28 Dec 2018 at 15:46, > > wrote:
>> 
>>     __
>> 
>>     Thanks Rory and Mike!
>> 
>>     Using wavetables in very interesting indeed, and I will have to 
>> look
>>     into it further.
>> 
>>     For now, I see that just using vco2 allows me to avoid using a
>>     function table at all. I think this is best for now-- I'm only on
>>     page 4 of the tutorial! :D
>> 
>>     brian
>> 
>> 
>> 
>>     On Fri, 28 Dec 2018 14:54:34 +0100, brian@AMSYNTH.COM
>>      wrote:
>> 
>>>     Ok, but if I don't provide the f1 table, the vco opcode gives an
>>>     error. Is there a reason why I must provide f1, other than to
>>>     avoid an error?
>>> 
>>> 
>>> 
>>>     On Fri, 28 Dec 2018 13:35:30 +0000, Rory Walsh wrote:
>>> 
>>>         You're not passing a function table to vco in this case. You
>>>         are simply telling it to generate a sawtooth waveform. The 
>>> 5th
>>>         input parameter to vco sets the function table but you 
>>> haven't
>>>         set it.
>>> 
>>>         On Fri, 28 Dec 2018 at 13:29, >>         > wrote:
>>> 
>>>             Hi everyone,
>>> 
>>>             I would like to ask, what Gen routine(s) do you prefer,
>>>             and why?
>>> 
>>>             Also, I see that some opcodes, such as VCO, require a
>>>             function table, even though the waveform is to be
>>>             indicated directly in the syntax. Is this for bit-quality
>>>             purposes?
>>> 
>>>             For example, here's an instrument where the waveform is a
>>>             sawtooth, but the function table uses Gen 10 and a
>>>             sinewave. Apparently the sinewave is ignored. -->
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>>             -d -odac
>>> 
>>> 
>>> 
>>>             sr = 44100
>>>             ksmps = 32
>>>             nchnls = 2
>>>             0dbfs = 1
>>> 
>>>             instr 1
>>>             kamp    linsegr    0,.2,.9,.7,.9,.5,0
>>>             kfreq    linsegr    330,.5,550,.2,220
>>> 
>>>             a1    vco    kamp,kfreq,1    ;saw-wave
>>>             outs    a1,a1
>>>             endin
>>> 
>>> 
>>> 
>>> 
>>> 
>>>             f1    0    16384    10    1
>>> 
>>>             ;p1    p2    p3
>>> 
>>>             i1    0    8
>>> 
>>> 
>>> 
>>> 
>>> 
>>>             brian
>>> 
>>> 
>>>             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
>> 
>> 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

Some of these look really interesting. My version of Csound here is 6.08. (Debian)

I may move to the Debian testing release (Buster). For now, I'll use what 6.08 gives me, which is a lot!

As recommended here, I'll use primarily vco2 and poscil, rather than vco and oscil.

Any other GEN routines that are suggested or very popular? I see many, but are they all used often?

brian

On Sat, 29 Dec 2018 09:02:07 +0000, Rory Walsh wrote:

True. It should be added to the dynamic spectrum oscillators section. 

On Sat, 29 Dec 2018 at 01:10, re <re@abc.se> wrote:

May I suggest squinewave in this context?

It's bandlimited, performs like poscil for sinewave, also
saw-square-pulse and intermediate waveforms.
And has hardsync (also bandlimited but sharp pulse).

Easy to overlook in manual since it doesn't appear on any overview
pages.

     /re

2018-12-28 21:55 skrev joachim heintz:
> and poscil as standard oscillator, not oscil ...
>
>
>
> On 28/12/18 18:07, Rory Walsh wrote:
>> I always recommend that beginners to use vco2 so they don't have to
>> worry about aliasing.
>>
>> On Fri, 28 Dec 2018 at 15:46, <brian@amsynth.com
>> brian@amsynth.com>> wrote:
>>
>>     __
>>
>>     Thanks Rory and Mike!
>>
>>     Using wavetables in very interesting indeed, and I will have to
>> look
>>     into it further.
>>
>>     For now, I see that just using vco2 allows me to avoid using a
>>     function table at all. I think this is best for now-- I'm only on
>>     page 4 of the tutorial! :D
>>
>>     brian
>>
>>
>>
>>     On Fri, 28 Dec 2018 14:54:34 +0100, brian@AMSYNTH.COM
>>     brian@AMSYNTH.COM> wrote:
>>
>>>     Ok, but if I don't provide the f1 table, the vco opcode gives an
>>>     error. Is there a reason why I must provide f1, other than to
>>>     avoid an error?
>>>
>>>
>>>
>>>     On Fri, 28 Dec 2018 13:35:30 +0000, Rory Walsh wrote:
>>>
>>>         You're not passing a function table to vco in this case. You
>>>         are simply telling it to generate a sawtooth waveform. The
>>> 5th
>>>         input parameter to vco sets the function table but you
>>> haven't
>>>         set it.
>>>
>>>         On Fri, 28 Dec 2018 at 13:29, <brian@amsynth.com
>>>         brian@amsynth.com>> wrote:
>>>
>>>             Hi everyone,
>>>
>>>             I would like to ask, what Gen routine(s) do you prefer,
>>>             and why?
>>>
>>>             Also, I see that some opcodes, such as VCO, require a
>>>             function table, even though the waveform is to be
>>>             indicated directly in the syntax. Is this for bit-quality
>>>             purposes?
>>>
>>>             For example, here's an instrument where the waveform is a
>>>             sawtooth, but the function table uses Gen 10 and a
>>>             sinewave. Apparently the sinewave is ignored. -->
>>>
>>>
>>>
>>>
>>>
>>>
>>>             -d -odac
>>>
>>>
>>>
>>>             sr = 44100
>>>             ksmps = 32
>>>             nchnls = 2
>>>             0dbfs = 1
>>>
>>>             instr 1
>>>             kamp    linsegr    0,.2,.9,.7,.9,.5,0
>>>             kfreq    linsegr    330,.5,550,.2,220
>>>
>>>             a1    vco    kamp,kfreq,1    ;saw-wave
>>>             outs    a1,a1
>>>             endin
>>>
>>>
>>>
>>>
>>>
>>>             f1    0    16384    10    1
>>>
>>>             ;p1    p2    p3
>>>
>>>             i1    0    8
>>>
>>>
>>>
>>>
>>>
>>>             brian
>>>
>>>
>>>             Csound mailing list Csound@listserv.heanet.ie
>>>             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
>>>         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
>>>     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
>>     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
>> 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

thanks for the hint, i wasn't aware of it at all.



On 29/12/18 02:09, re wrote:
> May I suggest squinewave in this context?
>
> It's bandlimited, performs like poscil for sinewave, also
> saw-square-pulse and intermediate waveforms.
> And has hardsync (also bandlimited but sharp pulse).
>
> Easy to overlook in manual since it doesn't appear on any overview pages.
>
>     /re
>
> 2018-12-28 21:55 skrev joachim heintz:
>> and poscil as standard oscillator, not oscil ...
>>
>>
>>
>> On 28/12/18 18:07, Rory Walsh wrote:
>>> I always recommend that beginners to use vco2 so they don't have to
>>> worry about aliasing.
>>>
>>> On Fri, 28 Dec 2018 at 15:46, >> > wrote:
>>>
>>>     __
>>>
>>>     Thanks Rory and Mike!
>>>
>>>     Using wavetables in very interesting indeed, and I will have to look
>>>     into it further.
>>>
>>>     For now, I see that just using vco2 allows me to avoid using a
>>>     function table at all. I think this is best for now-- I'm only on
>>>     page 4 of the tutorial! :D
>>>
>>>     brian
>>>
>>>
>>>
>>>     On Fri, 28 Dec 2018 14:54:34 +0100, brian@AMSYNTH.COM
>>>      wrote:
>>>
>>>>     Ok, but if I don't provide the f1 table, the vco opcode gives an
>>>>     error. Is there a reason why I must provide f1, other than to
>>>>     avoid an error?
>>>>
>>>>
>>>>
>>>>     On Fri, 28 Dec 2018 13:35:30 +0000, Rory Walsh wrote:
>>>>
>>>>         You're not passing a function table to vco in this case. You
>>>>         are simply telling it to generate a sawtooth waveform. The 5th
>>>>         input parameter to vco sets the function table but you haven't
>>>>         set it.
>>>>
>>>>         On Fri, 28 Dec 2018 at 13:29, >>>         > wrote:
>>>>
>>>>             Hi everyone,
>>>>
>>>>             I would like to ask, what Gen routine(s) do you prefer,
>>>>             and why?
>>>>
>>>>             Also, I see that some opcodes, such as VCO, require a
>>>>             function table, even though the waveform is to be
>>>>             indicated directly in the syntax. Is this for bit-quality
>>>>             purposes?
>>>>
>>>>             For example, here's an instrument where the waveform is a
>>>>             sawtooth, but the function table uses Gen 10 and a
>>>>             sinewave. Apparently the sinewave is ignored. -->
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>             -d -odac
>>>>
>>>>
>>>>
>>>>             sr = 44100
>>>>             ksmps = 32
>>>>             nchnls = 2
>>>>             0dbfs = 1
>>>>
>>>>             instr 1
>>>>             kamp    linsegr    0,.2,.9,.7,.9,.5,0
>>>>             kfreq    linsegr    330,.5,550,.2,220
>>>>
>>>>             a1    vco    kamp,kfreq,1    ;saw-wave
>>>>             outs    a1,a1
>>>>             endin
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>             f1    0    16384    10    1
>>>>
>>>>             ;p1    p2    p3
>>>>
>>>>             i1    0    8
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>             brian
>>>>
>>>>
>>>>             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
>>>
>>> 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

What should be added (a paragraph or so) ad wherein the manual?  I do not 
now enough to ck this alone
==JPff

On Sat, 29 Dec 2018, Rory Walsh wrote:

> True. It should be added to the dynamic spectrum oscillators section. 
> 
> On Sat, 29 Dec 2018 at 01:10, re  wrote:
>       May I suggest squinewave in this context?
>
>       It's bandlimited, performs like poscil for sinewave, also
>       saw-square-pulse and intermediate waveforms.
>       And has hardsync (also bandlimited but sharp pulse).
>
>       Easy to overlook in manual since it doesn't appear on any overview
>       pages.
>
>            /re
>
>       2018-12-28 21:55 skrev joachim heintz:
>       > and poscil as standard oscillator, not oscil ...
>       >
>       >
>       >
>       > On 28/12/18 18:07, Rory Walsh wrote:
>       >> I always recommend that beginners to use vco2 so they don't
>       have to
>       >> worry about aliasing.
>       >>
>       >> On Fri, 28 Dec 2018 at 15:46,        >> > wrote:
>       >>
>       >>     __
>       >>
>       >>     Thanks Rory and Mike!
>       >>
>       >>     Using wavetables in very interesting indeed, and I will
>       have to
>       >> look
>       >>     into it further.
>       >>
>       >>     For now, I see that just using vco2 allows me to avoid
>       using a
>       >>     function table at all. I think this is best for now-- I'm
>       only on
>       >>     page 4 of the tutorial! :D
>       >>
>       >>     brian
>       >>
>       >>
>       >>
>       >>     On Fri, 28 Dec 2018 14:54:34 +0100, brian@AMSYNTH.COM
>       >>      wrote:
>       >>
>       >>>     Ok, but if I don't provide the f1 table, the vco opcode
>       gives an
>       >>>     error. Is there a reason why I must provide f1, other than
>       to
>       >>>     avoid an error?
>       >>>
>       >>>
>       >>>
>       >>>     On Fri, 28 Dec 2018 13:35:30 +0000, Rory Walsh wrote:
>       >>>
>       >>>         You're not passing a function table to vco in this
>       case. You
>       >>>         are simply telling it to generate a sawtooth waveform.
>       The
>       >>> 5th
>       >>>         input parameter to vco sets the function table but you
>       >>> haven't
>       >>>         set it.
>       >>>
>       >>>         On Fri, 28 Dec 2018 at 13:29,        >>>         > wrote:
>       >>>
>       >>>             Hi everyone,
>       >>>
>       >>>             I would like to ask, what Gen routine(s) do you
>       prefer,
>       >>>             and why?
>       >>>
>       >>>             Also, I see that some opcodes, such as VCO,
>       require a
>       >>>             function table, even though the waveform is to be
>       >>>             indicated directly in the syntax. Is this for
>       bit-quality
>       >>>             purposes?
>       >>>
>       >>>             For example, here's an instrument where the
>       waveform is a
>       >>>             sawtooth, but the function table uses Gen 10 and a
>       >>>             sinewave. Apparently the sinewave is ignored. -->
>       >>>
>       >>>
>       >>>
>       >>>
>       >>>
>       >>>
>       >>>             -d -odac
>       >>>
>       >>>
>       >>>
>       >>>             sr = 44100
>       >>>             ksmps = 32
>       >>>             nchnls = 2
>       >>>             0dbfs = 1
>       >>>
>       >>>             instr 1
>       >>>             kamp    linsegr    0,.2,.9,.7,.9,.5,0
>       >>>             kfreq    linsegr    330,.5,550,.2,220
>       >>>
>       >>>             a1    vco    kamp,kfreq,1    ;saw-wave
>       >>>             outs    a1,a1
>       >>>             endin
>       >>>
>       >>>
>       >>>
>       >>>
>       >>>
>       >>>             f1    0    16384    10    1
>       >>>
>       >>>             ;p1    p2    p3
>       >>>
>       >>>             i1    0    8
>       >>>
>       >>>
>       >>>
>       >>>
>       >>>
>       >>>             brian
>       >>>
>       >>>
>       >>>             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
>       >>
>       >> 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
>

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