Thank you Pete and thank you everyone for your answers.
Let me say I use the Steven Yi's livecoding. I open csound and a server, I charge all my instrument and stuff and than I start livecoding.
Using this method, allows me to control and send message to csound from all kind of platform. In this particular case, I am trying to send from reaper some slice of "livecoding" written in a timeline: I send all the different code, every slice is under a different instrument that it is sent with his "schedule" and his time in the timeline.
Anyway, this kind of problem is there even in a "classical way": I use VIM to send messages to csound.
It is really strange, because now I tried again (on the live.csound site and on my computer) and sometimes I get all my three different numbers and sometimes I get only one (the same number). This is complicated because I cannot anymore addressing to different instrument because the last one is suppressing the others!
As I said, I need to use named instruments when I livecode because csound charge all my orchestra at the beginning, addressing a number to all my named instruments.
Could be, but off the top of my head, the sequence in a single thread is:
compile all instruments, assigning the names to numbers
run instr0 and the schedule calls
resulting in what Pete Goodeve has reported. There's probably more differences between the two. Maybe we need Steven to look into this as it involves his live coding setup.
Prof. Victor Lazzarini
Maynooth University
Ireland
Shouldn’t be an issue with the csound-live-code, it’s just sending messages via UDP. I would guess that this may be related to csoundCompileOrcAsync (which UDP server uses), and that was mentioned to have an issue by Eduardo on the dev list and that I had replied to:
I’m not sure if that was ever addressed? Also, I think some part of this was modified during a pull request but I can’t recall exactly. Jacopo: Which version of Csound are you using?