Hey hey,
the metro opcode's initphase parameter works in a strange way. It has a range 
of 0 to 1. With the following code I would expect kt2 to play .1 seconds after 
kt1:
kt1 metro 1
kt2 metro 1, .1

But it take (1 - .1) for kt2 to play .1 seconds after kt1 .

Is it me thinking queer or is this not supposed to happen?

Best wishes,

Jeanette

-- 
  * Website: http://juliencoder.de - for summer is a state of sound
  * Youtube: https://www.youtube.com/channel/UCMS4rfGrTwz8W7jhC1Jnv7g
  * SoundCloud: https://soundcloud.com/jeanette_c
  * Twitter: https://twitter.com/jeanette_c_s
  * Audiobombs: https://www.audiobombs.com/users/jeanette_c
  * GitHub: https://github.com/jeanette-c

We still move to a rhythm just like this
We still dream of sharing our first kiss <3
(Britney Spears)

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

this is consistent for me.  it is like a phasor, and once the phasor 
hits zero, it outputs the metro signal.


On 12/06/2020 17:25, Jeanette C. wrote:
> Hey hey,
> the metro opcode's initphase parameter works in a strange way. It has a 
> range of 0 to 1. With the following code I would expect kt2 to play .1 
> seconds after kt1:
> kt1 metro 1
> kt2 metro 1, .1
> 
> But it take (1 - .1) for kt2 to play .1 seconds after kt1 .
> 
> Is it me thinking queer or is this not supposed to happen?
> 
> Best wishes,
> 
> Jeanette
> 

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