> hi tito -
> thanks for the interesting discussion. my understanding is so far, that
> an instrument event, which is sent at a certain time in performance (=
> at a certain k-cycle)  to instrument 3, cannot reach instrument
> instrument 1 and 2 in this k-cycle, because the instruments are
> evaluated by their number (so the evaluation of instr 1 and 2 have
> already been finished at this point).
> is this wrong?
> 	joachim

Here is an example:

- sorting the score (i1 < i2 < i3 ... f0 < ...)

- i3 0 1

   csound->icurTime = 0

   ->  i3 init pass
       event_i (eventOpcodeI is the init function)

       -> insert_score_event_at_sample(csound, event_for_i1 , csound->icurTime)
       -> insert_score_event_at_sample(csound, event_for_i2 , csound->icurTime)

   ->  i1 init pass
   ->  i2 init pass

- kperf increment csound->icurTime

  csound->icurTime += csound->ksmps;

and the game continues. With the following csd file

<CsoundSynthesizer>
<CsInstruments>
sr     = 44100
ksmps  = 64

instr 1
ires timek
print ires
endin

instr 2
ires timek
print ires
endin

instr 3
ires timek
print ires
event_i "i", 2, 0, p3
event_i "i", 1, 0, p3
turnoff
endin

</CsInstruments>
<CsScore>
;; ksmps = 64
i3 [1-1/64]  1
i3 [1-1/100] 1
i3 1         1
i3 [1+1/100] 1
i3 [1+1/64]  1
</CsScore>
</CsoundSynthesizer>

csound test.csd
...
new alloc for instr 3:
instr 3:  ires = 678.000
new alloc for instr 2:
instr 2:  ires = 678.000
new alloc for instr 1:
instr 1:  ires = 678.000
B  0.984 ..  0.990 T  0.990 TT  0.990 M:      0.0
instr 3:  ires = 682.000
new alloc for instr 2:
instr 2:  ires = 682.000
new alloc for instr 1:
instr 1:  ires = 682.000
B  0.990 ..  1.000 T  1.000 TT  1.000 M:      0.0
instr 3:  ires = 689.000
new alloc for instr 2:
instr 2:  ires = 689.000
new alloc for instr 1:
instr 1:  ires = 689.000
B  1.000 ..  1.010 T  1.010 TT  1.010 M:      0.0
instr 3:  ires = 696.000
new alloc for instr 2:
instr 2:  ires = 696.000
new alloc for instr 1:
instr 1:  ires = 696.000
B  1.010 ..  1.016 T  1.016 TT  1.016 M:      0.0
instr 3:  ires = 700.000
new alloc for instr 2:
instr 2:  ires = 700.000
new alloc for instr 1:
instr 1:  ires = 700.000

I have inverted the order of i1 and i2 in i3 to show you that it's
important only the order of the `insert_score_event_at_sample` calls
(after the initial sorting of the score).

Sorry for the pseudocode but I think that you and many others in this
list are smart guys.

tito


Send bugs reports to the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"