Does UDO allow less processing?
or just User Opcodes ?
I have question about (USER DEFINED OPCODES)
I’m not sure I follow the question? Can you try to rephrase it?
1 Like
Sorry I speak english little bit
like When I use “USER DEFINED OPCODES” I want to know about
USER DEFINED OPCODES Will give you use less cpu ?
or Just build your own opcode for easy use
thank you
No problem 
UDOs will never perform as fast as native opcodes in Csound. If you write your own oscillator as a UDO, it is very unlikely it will run as fast as oscil, oscili. Also, UDOs will not perform as well as instrument code. But don’t let this put you off using them. They are great for developing modular and reusable code. And they can make code easier to maintain and debug. 
1 Like
Btw, you can always write your own opcodes in C/C++. If you find your UDO or Csound code is too slow, that’s another option.
1 Like
It’s like u make 3 opcodes as madsr, vso2, lowres to mix all of this to 1 opcode which u want by u can define your name opcode ?
You can do this yes. And then use your custom udo each time you need such functionality.
1 Like
So. if UDOs great for developing modular and if use UDOs for Digital Synth or Granular synth… it’s works ?
UDO is a tool as one of many , to optimize and unify code. you can use it or not depend from your target.