I use loops a lot, and often use event_i in loops to create notes. the
problem is that when used this way, it seems that p2 value for time doesn´t
seem to represent beats anymore, but absolute seconds. See my example below.
I can´t change the tempo in the loop with a t statement in score, it just
makes the loop shorter. I have to use a variable "gitempo", that is 60/
desired tempo, and multiply every value with this. If it is only straight
quarters, I only need to divide it once, itime= index*gitempo, but if I have
eights etc, I need to mulitply every note with gitempo. 
I guess there is an easier way, but I haven´t figured it out. Any
suggestions?

;Tempo is MM 90. Instrument 1 makes a loop and calls instrument 10 with 2
notes via event_i.
;Changing t in score doesn´t affect tempo for notes in loop. 




sr 	= 44100
ksmps 	= 10
nchnls 	= 1
0dbfs  	= 1

gisine		ftgen 0,0,2^12,10,1
gitempo		= 60/90
instr 1
index = 0
		loop:
    	itime = index*gitempo
    	idur	= 0.2
    	event_i "i",10,itime,idur
    	event_i "i",10,itime+0.5*gitempo,idur
    	loop_lt index,1,10,loop
    	endin

instr 10
asig	poscil 0.5,440,gisine
kenv linseg 0,0.01,1,p3-0.02,1,0.01,0
asig = asig*kenv
out		asig
endin




t 0 60
i 1 0 10





--
View this message in context: http://csound.1045644.n5.nabble.com/event-i-in-loop-and-tempo-tp5728786.html
Sent from the Csound - General mailing list archive at Nabble.com.

They're is no better way, because the events in Csound at run time are the result of applying the tempo to the original score events to get absolute times.

Regards,
Mike

i also think that your code is good. if you like, you could simply write
itempo = 90
and then in the instrument
itime = index*(60/gitempo)
etc. this way you have to set only one metronome number, and this is 
even more straightforward than writing t 0 90, in my opinion.

if your tempo changes like a line (becoming faster or slower), you can 
apply this easily, or if you want to get slight irregularities in your 
loop (like every living drummer would have), you can change your code 
without many efforts.

so i think you went the right path: leaving the score opens you up many 
possibilities, and you can code what you like to have, instead of 
depending on the rather limited extend of the score language.

best -

	joachim


Am 27.10.2013 11:44, schrieb Michael Gogins:
> They're is no better way, because the events in Csound at run time are
> the result of applying the tempo to the original score events to get
> absolute times.
>
> Regards,
> Mike
>
> On Oct 27, 2013 3:10 AM, "orebronerd"  > wrote:
>
>     I use loops a lot, and often use event_i in loops to create notes. the
>     problem is that when used this way, it seems that p2 value for time
>     doesn´t
>     seem to represent beats anymore, but absolute seconds. See my
>     example below.
>     I can´t change the tempo in the loop with a t statement in score, it
>     just
>     makes the loop shorter. I have to use a variable "gitempo", that is 60/
>     desired tempo, and multiply every value with this. If it is only
>     straight
>     quarters, I only need to divide it once, itime= index*gitempo, but
>     if I have
>     eights etc, I need to mulitply every note with gitempo.
>     I guess there is an easier way, but I haven´t figured it out. Any
>     suggestions?
>
>     ;Tempo is MM 90. Instrument 1 makes a loop and calls instrument 10
>     with 2
>     notes via event_i.
>     ;Changing t in score doesn´t affect tempo for notes in loop.
>     
>     
>     
>     
>     sr      = 44100
>     ksmps   = 10
>     nchnls  = 1
>     0dbfs   = 1
>
>     gisine          ftgen 0,0,2^12,10,1
>     gitempo         = 60/90
>     instr 1
>     index = 0
>                      loop:
>              itime = index*gitempo
>              idur    = 0.2
>              event_i "i",10,itime,idur
>              event_i "i",10,itime+0.5*gitempo,idur
>              loop_lt index,1,10,loop
>              endin
>
>     instr 10
>     asig    poscil 0.5,440,gisine
>     kenv linseg 0,0.01,1,p3-0.02,1,0.01,0
>     asig = asig*kenv
>     out             asig
>     endin
>
>
>     
>     
>     t 0 60
>     i 1 0 10
>     
>     
>
>
>
>     --
>     View this message in context:
>     http://csound.1045644.n5.nabble.com/event-i-in-loop-and-tempo-tp5728786.html
>     Sent from the Csound - General mailing list archive at Nabble.com.
>
>
>     Send bugs reports to the Sourceforge bug trackers
>     csound6:
>     https://sourceforge.net/p/csound/tickets/
>     csound5:
>     https://sourceforge.net/p/csound/bugs/
>     Discussions of bugs and features can be posted here
>     To unsubscribe, send email sympa@lists.bath.ac.uk
>      with body "unsubscribe csound"
>
>

Thank you for your replies. I thought event_i generated sort of "hidden"
score events, that would be affected by the t statement, but obiously it
doesn´t. (It says in the manual that "event_i generates a score event from
an instrument.") 
As Joachim mentioned, I can add randomness etc if I use loops with event_i,
and I´m very much into that, so I think I will stick with loops.
 I am not sure if I understand Joachims comment about writing itime =
index*(60/gitempo) (instead of "itime = index*gitempo" as it stands now?).
If I try that with my code, it just stops after one note. 
It seems that either way I still have to correct all 1/8th:s 1/16th:s etc
that I use in the loop with a tempo factor. If I only use 1/4:ths I just
have to correct for tempo once, but that is seldom the case. Too bad. :-)



--
View this message in context: http://csound.1045644.n5.nabble.com/event-i-in-loop-and-tempo-tp5728786p5728796.html
Sent from the Csound - General mailing list archive at Nabble.com.