What happens if I do a csound.CompileOrc(instrument) where the (named)
instrument already exists? Will it be replaced?

Richard



--
View this message in context: http://csound.1045644.n5.nabble.com/CompileOrc-with-same-named-instrument-tp5730955.html
Sent from the Csound - General mailing list archive at Nabble.com.

yes, it gets replaced. The replacement only affects new instances.


On 25 Dec 2013, at 21:22, zappfinger  wrote:

> What happens if I do a csound.CompileOrc(instrument) where the (named)
> instrument already exists? Will it be replaced?
> 
> Richard
> 
> 
> 
> --
> View this message in context: http://csound.1045644.n5.nabble.com/CompileOrc-with-same-named-instrument-tp5730955.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"
> 
> 

Good to know. It already looked that way.
I want to make a flexible synth based on the signalflow opcodes, but these
must be defined in instrument 0 and I don't think I can change the
connections on the fly can I?
So a solution would be to defined 'fixed' instrument names, but change their
content...

Richard




--
View this message in context: http://csound.1045644.n5.nabble.com/CompileOrc-with-same-named-instrument-tp5730955p5730958.html
Sent from the Csound - General mailing list archive at Nabble.com.

Instrument 0 works in a similar way. 
The only difference is that there’s no perf time, only an init-pass. So you can
recompile it as the others, and it runs the init pass as soon as you compile it.

The only thing to remember with global code is that system parameters such as sr, kr etc can only be
set in the first compilation. Otherwise, you can compile and run it.

Victor

On 25 Dec 2013, at 22:16, zappfinger  wrote:

> Good to know. It already looked that way.
> I want to make a flexible synth based on the signalflow opcodes, but these
> must be defined in instrument 0 and I don't think I can change the
> connections on the fly can I?
> So a solution would be to defined 'fixed' instrument names, but change their
> content...
> 
> Richard
> 
> 
> 
> 
> --
> View this message in context: http://csound.1045644.n5.nabble.com/CompileOrc-with-same-named-instrument-tp5730955p5730958.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"
> 
> 

The signal flow graph opcodes are supposed to be thread safe so what you want to do should be possible.  Let me know what happens when you try it.

Regards,
Mike