Is there an easy way to direct a score to more than one instrument?
Say I have instr 1 and 2 , and I want to send the score for instr 1 also to
instr 2.

Richard

--
View this message in context: http://csound.1045644.n5.nabble.com/send-score-to-multiple-instruments-tp5143890p5143890.html
Sent from the Csound - General mailing list archive at Nabble.com.


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"

Try event in instr 1 to callinstr 2

Or is that not what you want?


> Is there an easy way to direct a score to more than one instrument?
> Say I have instr 1 and 2 , and I want to send the score for instr 1 also
> to
> instr 2.
>
> Richard
>
> --


>
>




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"

yes, event_i is a simple solution.
	j


Am 14.01.2012 00:04, schrieb jpff@cs.bath.ac.uk:
> Try event in instr 1 to callinstr 2
> 
> Or is that not what you want?
> 
> 
>> Is there an easy way to direct a score to more than one instrument?
>> Say I have instr 1 and 2 , and I want to send the score for instr 1 also
>> to
>> instr 2.
>>
>> Richard
>>
>> --
> 
> 
>>
>>
> 
> 
> 
> 
> 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"
> 
> 


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"

Yes, but then I would have to change instr 1 to do that. Or add an
intermediate instr that can send it to 1 and 2.
I was thinking something in line with massign. 

--
View this message in context: http://csound.1045644.n5.nabble.com/send-score-to-multiple-instruments-tp5143890p5144620.html
Sent from the Csound - General mailing list archive at Nabble.com.


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"

I've never seen this trick. What does it do?

Richard

--
View this message in context: http://csound.1045644.n5.nabble.com/send-score-to-multiple-instruments-tp5143890p5144869.html
Sent from the Csound - General mailing list archive at Nabble.com.


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"

for this solution, i think the instrument which calls the subinstrument,
should have the lowest number, to ensure that what you send to the
master instrument arrives at the same k-cycle in the subinstruments. so:
instr 1
event_i ...
endin

	joachim


Am 14.01.2012 10:16, schrieb Tito Latini:
> Trick II
> 
> 
> 
> 
> 
> instr 1
> prints "start 1\n"
> endin
> 
> instr 2
> prints "start 2\n"
> endin
> 
> instr 3
> event_i "i", 1, 0, p3
> event_i "i", 2, 0, p3
> turnoff
> endin
> 
> 
> 
> i3 0 1
> i3 + .
> i3 + .
> 
> 
> 
> 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"
> 
> 


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"

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

Am 15.01.2012 12:15, schrieb Tito Latini:
>> for this solution, i think the instrument which calls the subinstrument,
>> should have the lowest number, to ensure that what you send to the
>> master instrument arrives at the same k-cycle in the subinstruments. so:
>> instr 1
>> event_i ...
>> endin
>>
>> 	joachim
> 
> No, the example is correct and I still have to wake up me
> 
> event_i is the i-time version of event opcode (no k-cycles)
> 
> instr 3
> 0 eventOpcodeI -> isntr 1 init pass
> 0 eventOpcodeI -> instr 2 init pass
> 
> 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"
> 
> 


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"

thanks very much for the explanation and the instructive example! i can
see better now that csounds clock stays at the same time. nevertheless
the order of executing the i-statements is not interrupted because of
the event_i insertion:



-m0


instr 1
prints "i am instrument 1\n"
endin
instr 2
prints "i am instrument 2 before calling instr 1\n"
event_i "i", 1, 0, 1
prints "i am instrument 2 after calling instr 1\n"
endin
instr 3
prints "i am instrument 3\n"
endin


i 2 0 1
i 3 0 1



this prints:
i am instrument 2 before calling instr 1
i am instrument 2 after calling instr 1
i am instrument 3
i am instrument 1

so all the instruments at the same time finish their initialization
pass, before instr 1 can start its initialization. this is clearly
written in the manual, as "The event is added to the queue at
initialisation time."

i just needed some time to understand correctly. thanks for helping ...=)

	joachim


Am 15.01.2012 15:53, schrieb Tito Latini:
> It's a better test (kr ~ 689 with ksmps=64)
> 
> i3 [1-1/100]  1 
> i3 [1-1/800]  1
> i3 1          1
> i3 [1+1/800]  1
> i3 [1+1/100]  1
> 
> 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"
> 
> 


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"