There are three main reasons for writing your own opcode in my book: 1: The existing opcode has a collection of additional options that slow your case down 2: You need a combination of 2 or 3 opcodes and you have real time issues 3: There is no opcode to do what you want without contorted code -- in which case it may be useful of others. If you have not written much C code then it is an interesting educational exercise, but not necessarily a performance gain. ==John ff Quoting Rory Walsh : > You can take it that the code for opcodes is pretty well written and > optimized. In most cases if it can be done in Csound the gains in > writing your own opcode will be negligible in terms of performance. > There may be times however when you may need a new purpose built > opcode. Information about building your own can also be found in the > floss manual. If you're learning C, I'd recommend looking over it. > > On 2 June 2014 22:16, fauveboy wrote: >> Thank you for these links I've taken a look and its made me wonder if its >> usual to tailor ones own opcode for efficiency, is that done often, if it is >> how? >> >> >> >> -- >> View this message in context: >> http://csound.1045644.n5.nabble.com/Realtime-Sampling-advice-needed-tp5735601p5735668.html >> Sent from the Csound - General mailing list archive at Nabble.com. >> >> >> Send bugs reports to >> https://github.com/csound/csound/issues >> 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 > https://github.com/csound/csound/issues > Discussions of bugs and features can be posted here > To unsubscribe, send email sympa@lists.bath.ac.uk with body > "unsubscribe csound"