Hi,

there is something i do not understand about the jitter2 opcode. I want to
use it to modulate the frequency of a phaser, but i want it to do its thing
at very slow speeds (0.05 - .4).
I like what i hear, but think the random modulation is kicking in too late
in the note. Only higher speeds values makes the random generation produce
values earlier in the note, but i want slow changes.

Perhaps someone can have a look what is going on? I have attached a csd that
prints the changing jitter2 values. Could it be a bug or is there some kind
of delay built in?

the file:  jitter2.csd
  





--
View this message in context: http://csound.1045644.n5.nabble.com/jitter2-tp5750412.html
Sent from the Csound - General mailing list archive at Nabble.com.

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

T first k-cycle of jitter2 is always zero as I read the code.  Tat seems 
odd to me but seems it is written that way (technically dfdmax[123] start 
at zero)

Is that a posssible explanation?

On Sun, 3 Jul 2016, Menno Knevel wrote:

> Hi,
>
> there is something i do not understand about the jitter2 opcode. I want to
> use it to modulate the frequency of a phaser, but i want it to do its thing
> at very slow speeds (0.05 - .4).
> I like what i hear, but think the random modulation is kicking in too late
> in the note. Only higher speeds values makes the random generation produce
> values earlier in the note, but i want slow changes.
>
> Perhaps someone can have a look what is going on? I have attached a csd that
> prints the changing jitter2 values. Could it be a bug or is there some kind
> of delay built in?
>
> the file:  jitter2.csd
> 
>
>
>
>
>
> --
> View this message in context: http://csound.1045644.n5.nabble.com/jitter2-tp5750412.html
> Sent from the Csound - General mailing list archive at Nabble.com.
>
> 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

Worse than I thought -- it is zero unti te end of the shortest first 
cycle.

On Sun, 3 Jul 2016, jpff wrote:

> T first k-cycle of jitter2 is always zero as I read the code.  Tat seems odd 
> to me but seems it is written that way (technically dfdmax[123] start at 
> zero)
>
> Is that a posssible explanation?
>

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

i guess that is the reason why it is not producing values right away..
Can this be changed/rectified?  
Perhaps for compatibility reasons there could be an optional parameter that
defaults to the present situation?



--
View this message in context: http://csound.1045644.n5.nabble.com/jitter2-tp5750412p5750415.html
Sent from the Csound - General mailing list archive at Nabble.com.

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 it has uninitialised values affecting the output......

On Sun, 3 Jul 2016, jpff wrote:

> Worse than I thought -- it is zero unti te end of the shortest first cycle.
>
> On Sun, 3 Jul 2016, jpff wrote:
>
>> T first k-cycle of jitter2 is always zero as I read the code.  Tat seems 
>> odd to me but seems it is written that way (technically dfdmax[123] start 
>> at zero)
>> 
>> Is that a posssible explanation?
>> 
>
> 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

I will look at it -- and initialise the values as well.

I haveit written -- can you test?

On Sun, 3 Jul 2016, Menno Knevel wrote:

> i guess that is the reason why it is not producing values right away..
> Can this be changed/rectified?
> Perhaps for compatibility reasons there could be an optional parameter that
> defaults to the present situation?
>
>
>
> --
> View this message in context: http://csound.1045644.n5.nabble.com/jitter2-tp5750412p5750415.html
> Sent from the Csound - General mailing list archive at Nabble.com.
>
> 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

it sound much cleaner - it is better.
But
i still have to wait a long time before the jitter kicks in. I do understand
that the starting value = 0 as there is no offset, but it stays at 0 too
long. That is not what i' d expect. I would prefer that a delay could be
set...

I see that you have added something to the jitter2 parameters: what does the
"o" in "kkkkkkko" stand for?




--
View this message in context: http://csound.1045644.n5.nabble.com/jitter2-tp5750412p5750450.html
Sent from the Csound - General mailing list archive at Nabble.com.

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

forgot to mention: my ksmps = 256



--
View this message in context: http://csound.1045644.n5.nabble.com/jitter2-tp5750412p5750451.html
Sent from the Csound - General mailing list archive at Nabble.com.

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 additional argument is exactly what i was looking for. Thanks John,
problem solved.



--
View this message in context: http://csound.1045644.n5.nabble.com/jitter2-tp5750412p5750452.html
Sent from the Csound - General mailing list archive at Nabble.com.

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

I will try to document it

Sent from TypeApp