Delving deeper into OpCode

Delving deeper into OpCode

Date	2016-05-27 22:54
From	bubget
Subject	Delving deeper into OpCode
	Hi everyone! My first mail here... I am enchanted as of yet with Csound... The only "problem" I have so far is that it seems that the OpCode really hides the inner workings of the synth/effects etc... I want to learn about DSP, so I was wondering:is there a way to examine the code that created the opcodes? I am mainly interested in the granular and fft codes as of now. >From what I am aware, the code is written in C(?) Thanks for your time, I hope my query is clear -- View this message in context: http://csound.1045644.n5.nabble.com/Delving-deeper-into-OpCode-tp5749925.html Sent from the Csound - General mailing list archive at Nabble.com. Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Date	2016-05-28 00:13
From	jpff
Subject	Re: Delving deeper into OpCode
	Te sources are freely available and chaptes in te Csound Book eplain the detailed architecture, and elsewhere -- papers on Linux Audio Confeence for xample ==John ff Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Date	2016-05-28 11:21
From	Rory Walsh
Subject	Re: Delving deeper into OpCode
	The Audio Programming Book is also full of DSP wonder. Also looks at other library. Victor's SndObj library is a good place to learn, and check out Paul Batchelor's Soundpipe library. It borrows some code from Csound and other places but presents it without the overhead. On 28 May 2016 at 00:13, jpff <jpff@codemist.co.uk> wrote: Te sources are freely available and chaptes in te Csound Book eplain the detailed architecture, and elsewhere -- papers on Linux Audio Confeence for xample ==John ff Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Date	2016-05-28 19:36
From	bubget
Subject	Re: Delving deeper into OpCode
	Thank you both for your responses! Rory, when you say the source code is freely available... do you mean the .csd files for example? For example, partikkel-2.csd has lots of parameters in the code....but I still can´t see whats actually happening...The algorithm is hidden.. For example if you take a look at the paulstretch code in python, you can see the algorithm clearly.. This is what I am referring to.. It is also highly possible that due to inexperience I am totally missing it... jpff....thanks, great resources...I´ll check them out. -- View this message in context: http://csound.1045644.n5.nabble.com/Delving-deeper-into-OpCode-tp5749925p5749930.html Sent from the Csound - General mailing list archive at Nabble.com. Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Date	2016-05-28 20:54
From	John
Subject	Re: Delving deeper into OpCode
	The sources in C are on github as https://github.com/csound/csound And the manual as well if you look ==John On 28 May 2016, at 19:38, bubget <wstlopez@GMAIL.COM> wrote: Thank you both for your responses! Rory, when you say the source code is freely available... do you mean the .csd files for example? For example, partikkel-2.csd has lots of parameters in the code....but I still can´t see whats actually happening...The algorithm is hidden.. For example if you take a look at the paulstretch code in python, you can see the algorithm clearly.. This is what I am referring to.. It is also highly possible that due to inexperience I am totally missing it... jpff....thanks, great resources...I´ll check them out. -- View this message in context: http://csound.1045644.n5.n abble.com/Delving-deeper-into-OpCode-tp5749925p5749930.html Sent from the Csound - General mailing list archive at Nabble.com. Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Date	2016-05-28 21:52
From	T Lopez
Subject	Re: Delving deeper into OpCode
	Thank you! You are a star! On 28 May 2016 21:54, "John" <jpff@codemist.co.uk> wrote: The sources in C are on github as https://github.com/csound/csound And the manual as well if you look ==John On 28 May 2016, at 19:38, bubget <wstlopez@GMAIL.COM> wrote: Thank you both for your responses! Rory, when you say the source code is freely available... do you mean the .csd files for example? For example, partikkel-2.csd has lots of parameters in the code....but I still can´t see whats actually happening...The algorithm is hidden.. For example if you take a look at the paulstretch code in python, you can see the algorithm clearly.. This is what I am referring to.. It is also highly possible that due to inexperience I am totally missing it... jpff....thanks, great resources...I´ll check them out. -- View this message in context: http://csound.1045644.n5.nabble.com/Delving-deeper-into-OpCode-tp5749925p5749930.html Sent from the Csound - General mailing list archive at Nabble.com. Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Date	2016-05-28 23:01
From	Rory Walsh
Subject	Re: Delving deeper into OpCode
	I meant the c source code. But check out the UDO database for Csound implementations of different effects. On 28 May 2016 21:52, "T Lopez" <wstlopez@gmail.com> wrote: Thank you! You are a star! On 28 May 2016 21:54, "John" <jpff@codemist.co.uk> wrote: The sources in C are on github as https://github.com/csound/csound And the manual as well if you look ==John On 28 May 2016, at 19:38, bubget <wstlopez@GMAIL.COM> wrote: Thank you both for your responses! Rory, when you say the source code is freely available... do you mean the .csd files for example? For example, partikkel-2.csd has lots of parameters in the code....but I still can´t see whats actually happening...The algorithm is hidden.. For example if you take a look at the paulstretch code in python, you can see the algorithm clearly.. This is what I am referring to.. It is also highly possible that due to inexperience I am totally missing it... jpff....thanks, great resources...I´ll check them out. -- View this message in context: http://csound.1045644.n5.nabble.com/Delving-deeper-into-OpCode-tp5749925p5749930.html Sent from the Csound - General mailing list archive at Nabble.com. Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Date	2016-05-29 00:28
From	Paul Batchelor
Subject	Re: Delving deeper into OpCode
	As Rory mentioned, much of the audio modules in Soundpipe use code from Csound. It is the DSP code without the Csound interface: https://www.github.com/paulbatchelor/soundpipe Check out the modules folder. -P On May 28, 2016 3:01 PM, "Rory Walsh" <rorywalsh@ear.ie> wrote: I meant the c source code. But check out the UDO database for Csound implementations of different effects. On 28 May 2016 21:52, "T Lopez" <wstlopez@gmail.com> wrote: Thank you! You are a star! On 28 May 2016 21:54, "John" <jpff@codemist.co.uk> wrote: The sources in C are on github as https://github.com/csound/csound And the manual as well if you look ==John On 28 May 2016, at 19:38, bubget <wstlopez@GMAIL.COM> wrote: Thank you both for your responses! Rory, when you say the source code is freely available... do you mean the .csd files for example? For example, partikkel-2.csd has lots of parameters in the code....but I still can´t see whats actually happening...The algorithm is hidden.. For example if you take a look at the paulstretch code in python, you can see the algorithm clearly.. This is what I am referring to.. It is also highly possible that due to inexperience I am totally missing it... jpff....thanks, great resources...I´ll check them out. -- View this message in context: http://csound.1045644.n5.nabble.com/Delving-deeper-into-OpCode-tp5749925p5749930.html Sent from the Csound - General mailing list archive at Nabble.com. Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Date	2016-05-29 12:06
From	bubget
Subject	Re: Delving deeper into OpCode
	Perfect! That´s what i was looking for guys! Thankssss... One last question, C is used because Csound is written in C, correct? Otherwise, C++ may be a better choice? -- View this message in context: http://csound.1045644.n5.nabble.com/Delving-deeper-into-OpCode-tp5749925p5749939.html Sent from the Csound - General mailing list archive at Nabble.com. Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Date	2016-05-29 12:12
From	Victor Lazzarini
Subject	Re: Delving deeper into OpCode
	It's not a case of a better choice, it's about what you're comfortable with. You can write opcodes in C or C++. Some of us use C, others use C++. Victor Lazzarini Dean of Arts, Celtic Studies, and Philosophy Maynooth University Ireland > On 29 May 2016, at 12:06, bubget wrote: > > Perfect! That´s what i was looking for guys! Thankssss... > > One last question, C is used because Csound is written in C, correct? > Otherwise, C++ may be a better choice? > > > > -- > View this message in context: http://csound.1045644.n5.nabble.com/Delving-deeper-into-OpCode-tp5749925p5749939.html > Sent from the Csound - General mailing list archive at Nabble.com. > > Csound mailing list > Csound@listserv.heanet.ie > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND > Send bugs reports to > https://github.com/csound/csound/issues > Discussions of bugs and features can be posted here Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Date	2016-05-29 12:16
From	T Lopez
Subject	Re: Delving deeper into OpCode
	Ok! Thanks for the clarification!! On 29 May 2016 13:13, "Victor Lazzarini" <Victor.Lazzarini@nuim.ie> wrote: It's not a case of a better choice, it's about what you're comfortable with. You can write opcodes in C or C++. Some of us use C, others use C++. Victor Lazzarini Dean of Arts, Celtic Studies, and Philosophy Maynooth University Ireland > On 29 May 2016, at 12:06, bubget <wstlopez@GMAIL.COM> wrote: > > Perfect! That´s what i was looking for guys! Thankssss... > > One last question, C is used because Csound is written in C, correct? > Otherwise, C++ may be a better choice? > > > > -- > View this message in context: http://csound.1045644.n5.nabble.com/Delving-deeper-into-OpCode-tp5749925p5749939.html > Sent from the Csound - General mailing list archive at Nabble.com. > > Csound mailing list > Csound@listserv.heanet.ie > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND > Send bugs reports to > https://github.com/csound/csound/issues > Discussions of bugs and features can be posted here Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here