The initphase parameter of the metro opcode is a bit confusing for me:
ktrig  metro	 1, 0
gives the same result as
ktrig  metro	 1, 1
Just a very small number like 0.0000001 gives the expected output (the  
first trigger impulse after one second).
Would it not be better to set initphase = 0 in a way that the first  
trigger impulse comes after 1/kcps seconds?

Best -

	joachim

------------------------------------------------------------------------------
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

I don't think so -- usually phase 0 and 1 are considered equal and the
impulse occurs at the beginning of a cycle for an impulse signal.  But I can
see how it might be useful to delay the first trigger.  Just adding
0.0000001 to the initial phase or putting the impulse at the end of the
cycle gets into some subtle issues of which sample the impulse should occur
on though.  And either approach would break backwards compatibility for the
opcode.

Perhaps an optional parameter could be added to metro to skip the first
impulse with modifying the timing of subsequent impulses.

Anthony Kozar
mailing-lists-1001 AT anthonykozar DOT net
http://anthonykozar.net/


joachim heintz wrote on 3/28/09 11:19 AM:

> The initphase parameter of the metro opcode is a bit confusing for me:
> ktrig  metro     1, 0
> gives the same result as
> ktrig  metro     1, 1
> Just a very small number like 0.0000001 gives the expected output (the
> first trigger impulse after one second).
> Would it not be better to set initphase = 0 in a way that the first
> trigger impulse comes after 1/kcps seconds?


------------------------------------------------------------------------------
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

I understand what you mean. An optional parameter seems a good way for  
me. If not, I'd appeciate an additional explanation in the manual,  
that the extreme points 0 and 1 are in this case the same.

	joachim



Am 30.03.2009 um 02:14 schrieb Anthony Kozar:

> I don't think so -- usually phase 0 and 1 are considered equal and the
> impulse occurs at the beginning of a cycle for an impulse signal.   
> But I can
> see how it might be useful to delay the first trigger.  Just adding
> 0.0000001 to the initial phase or putting the impulse at the end of  
> the
> cycle gets into some subtle issues of which sample the impulse  
> should occur
> on though.  And either approach would break backwards compatibility  
> for the
> opcode.
>
> Perhaps an optional parameter could be added to metro to skip the  
> first
> impulse with modifying the timing of subsequent impulses.
>
> Anthony Kozar
> mailing-lists-1001 AT anthonykozar DOT net
> http://anthonykozar.net/
>
>
> joachim heintz wrote on 3/28/09 11:19 AM:
>
>> The initphase parameter of the metro opcode is a bit confusing for  
>> me:
>> ktrig  metro     1, 0
>> gives the same result as
>> ktrig  metro     1, 1
>> Just a very small number like 0.0000001 gives the expected output  
>> (the
>> first trigger impulse after one second).
>> Would it not be better to set initphase = 0 in a way that the first
>> trigger impulse comes after 1/kcps seconds?
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel


------------------------------------------------------------------------------
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net