There is no need to learn C in order to use Csound, unless you want to
write code to become part of Csound, or to write plugin opcodes that
need to run fast.

For languages to use for writing pieces that use Csound, the best
ones, in decreasing order of utility, are, in my opinion,

(1) JavaScript (because you get 3D graphics, HTML, user-defined and
user-styled widgets, and the ability to write compositional code in
JavaScript for nothing).
(2) LuaJIT (because it runs faster by far than Python or even
JavaScript and has many libraries; it comes with Csound on WIndows).
(2) Python (tied with LuaJIT, because it has the largest set of
libraries including music libraries such as Music21).
(3) Scheme/Lisp because of the deep tradition of algorithmic music
libraries especially OpenMusic.
(4) Java (runs fast, available for free, has some good music libraries).

Regards,
Mike

-----------------------------------------------------
Michael Gogins
Irreducible Productions
http://michaelgogins.tumblr.com
Michael dot Gogins at gmail dot com


On Wed, Jun 8, 2016 at 10:41 AM, Hlöðver Sigurðsson  wrote:
> oscil:a() is a new functional syntax, it's really no different from asig
> oscil, just looks more like a syntax from Scala, Haskell (or sorry to say
> it; Supercollider). My tip would be not to learn C to master Csound, that's
> in my opinion almost completly unnecessary. Go rather for Python, at least
> you can work with it well from within Csound. The only gain by learning
> general purpose programming language for something like Csound would just be
> general discipline of mental problemsolveing. I think that this
> misconception of Csound being tightly close with C (in terms of syntax) is
> in a way damaging. Csound is clear, expressive, rich and powerful for its
> domain, audio calculation.
>
> https://csound.github.io/docs/manual/functional.html
>
> 2016-06-08 16:24 GMT+02:00 Joe . :
>>
>> Hi everybody. Some questions:
>>
>> I recently like all of us enjoyed Steven Yi's UDO, and in it I saw the
>> oscil:a() way of writing. I was not aware that Csound code could be written
>> this way. Is there an article, a web page that documents the different ways
>> code can be written and interpreted in the same way?
>>
>> What do curly brackets do?
>>
>> Would you guys suggest learning C if you really want to master Csound? Do
>> you think this is possible without taking academic courses on it?
>>
>> thanks
>> Joe
>> 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

I think that depends on the user.

I have written or collaborated on writing several because I needed for
my own music features that did not exist in Csound at that time: the
fluidsynth opcodes, the STK opcodes, the Jacko opcodes, the linear
algebra opcodes, the Lua opcodes, the mixer opcodes, the signal flow
graph opcodes, and the vst4cs opcodes (I was not the main author). The
ones that I am still using regularly are the fluid opcodes, the STK
opcodes, the signal flow graph opcodes, and the vst4cs opcodes.

If you are comfortable writing in C or C++ then it is probably easier
to write opcodes this way instead of as user-defined opcodes in the
Csound orchestra language because, even with the many improvements it
now features, it's still a bit clunky in comparison with C and
certainly will not run as fast.

If you are not experienced writing code for digital signal processing,
then learning what the existing opcodes and how they are will be more
useful.

But if you want to learn to write DSP code, then writing plugin
opcodes in C or C++ is a good way to do it.

Regards,
Mike



-----------------------------------------------------
Michael Gogins
Irreducible Productions
http://michaelgogins.tumblr.com
Michael dot Gogins at gmail dot com


On Wed, Jun 8, 2016 at 11:41 AM, Joe .  wrote:
> Thanks guys. How often do users find it necessary to write their own
> opcodes? I was asking about C because of this.
>
> /* Joe */
>
> On Wed, Jun 8, 2016 at 11:18 PM, Forrest Curo  wrote:
>>
>> Install the program first, then try a few examples...
>>
>> These are good for seeing some ways of doing specific things:
>> http://iainmccurdy.org/csound.html
>>
>> You probably don't want to "master" it; but if you start learning a few
>> ways of using it you can learn more as needed.
>>
>> The floss manual gives you a good overall description of how it works; you
>> will need to learn the differences between 'opcodes' that work at different
>> rates.
>>
>> pd aka 'pure data' may be a better program to start with if you're new to
>> programming -- because it lets you 'draw' your program, put different pieces
>> together like tinker toys -- and does a lot of the same stuff. Csound gives
>> you better control (and has a friendlier mailing list, in my experience) and
>> the manual
>> http://csound.github.io/docs/manual/index.html
>> is much better organized.
>>
>>
>> On Wed, Jun 8, 2016 at 7:41 AM, Hlöðver Sigurðsson 
>> wrote:
>>>
>>> oscil:a() is a new functional syntax, it's really no different from asig
>>> oscil, just looks more like a syntax from Scala, Haskell (or sorry to say
>>> it; Supercollider). My tip would be not to learn C to master Csound, that's
>>> in my opinion almost completly unnecessary. Go rather for Python, at least
>>> you can work with it well from within Csound. The only gain by learning
>>> general purpose programming language for something like Csound would just be
>>> general discipline of mental problemsolveing. I think that this
>>> misconception of Csound being tightly close with C (in terms of syntax) is
>>> in a way damaging. Csound is clear, expressive, rich and powerful for its
>>> domain, audio calculation.
>>>
>>> https://csound.github.io/docs/manual/functional.html
>>>
>>> 2016-06-08 16:24 GMT+02:00 Joe . :
>>>>
>>>> Hi everybody. Some questions:
>>>>
>>>> I recently like all of us enjoyed Steven Yi's UDO, and in it I saw the
>>>> oscil:a() way of writing. I was not aware that Csound code could be written
>>>> this way. Is there an article, a web page that documents the different ways
>>>> code can be written and interpreted in the same way?
>>>>
>>>> What do curly brackets do?
>>>>
>>>> Would you guys suggest learning C if you really want to master Csound?
>>>> Do you think this is possible without taking academic courses on it?
>>>>
>>>> thanks
>>>> Joe
>>>> 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

On Wed, 8 Jun 2016, Joe . wrote:

> 
> What do curly brackets do? 
>

Thhe {{{....}}} structure is a string as alternative to "...."

In a score { and } indicate eponential ramps up and down.

All in the manual

Others have aswered your other questions I think

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

On Wed, 8 Jun 2016, Joe . wrote:

> Thanks guys. How often do users find it necessary to write their own opcodes?
> I was asking about C because of this. 
>

i am only answering this for completeess/fun.

i find it easier to write an opcode tha to struggle understsanding UDOs, 
but I am very far to the left field in this -- been writing code for over 
50 years (nearer 60) and it is also my hobby.  A day without code is a day 
wasted.

But no need to write C if you do not need to; others could implement stuff 
for you.  Like Mike I have written or rewritten many opcodes, in my case 
often on request as well as for my own uses.

==John ff

Feel free to ignore this message!

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

Am 08.06.2016 um 22:25 schrieb jpff:
>
>
> On Wed, 8 Jun 2016, Joe . wrote:
>
>>
>> What do curly brackets do? 
>>
>
> Thhe {{{....}}} structure is a string as alternative to "...."
>
> In a score { and } indicate eponential ramps up and down.
Interesting (exponential ramps are new to me).
>
> All in the manual

My search engine suggested this page
https://csound.github.io/docs/manual/ScoreRamping.html
which states that ( and ) have to be used for exponential ramps.

Are maybe both allowed?

Best regards,
Wolf

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

Curly brackets are for multiline string literals, e.g. for blocks of code in other languages embedded in Csound.

Could be my bad memory but I thought that curly brackets meant something

Sent from TypeApp

Hi Michael,

Am 10.06.2016 um 12:47 schrieb Michael Gogins:
> Curly brackets are for multiline string literals, e.g. for blocks of code
> in other languages embedded in Csound.
Thanks for the clarification.
I'd suggest one more snippet to show (, ), and ~ in action. This makes
it much easier for the "hurried reader", because text perfectly swallows
these tiny characters.

Best,
Wolf

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

Apologies for my misinformation

In a score "The { and } statements can be used to repeat a group of score 
statements. "

As ever I looked it up in the manual after I was awake
==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