11–20 of 94 posts
What does it do? These hint at some neat possibilities but I still don't get it: a sound and music computing system a tool for composing electro-acoustic pieces real-time
Earlier quoted context omitted.
Have you tried other musical programming languages like supercollider and puredata? I find them to be quite a bit crazier. Csound is ridiculously straight forward in comparison. Absurdly more comprehensible to me
I suppose I should say the language itself is hindered by the horrible GUI application it runs in, the interface is ancient and dated, and the application crashed constantly on Mac. I took a class that that required the use of CSound, so I haven't explored the various options
Earlier quoted context omitted.
Have you tried other musical programming languages like supercollider and puredata? I find them to be quite a bit crazier. Csound is ridiculously straight forward in comparison. Absurdly more comprehensible to me
supercollider is way better than csound
I've given sc 5 years, usually I'll try to use it, give it a few days of effort to do what I want, then give up, rewrite what I want in C, and be done with it in an hour
Some people love it. More power to them. I wish I was one of them
Earlier quoted context omitted.
I suppose I should say the language itself is hindered by the horrible GUI application it runs in, the interface is ancient and dated, and the application crashed constantly on Mac. I took a class that that required the use of CSound, so I haven't explored the various options
Just do it with makefiles, the workflow is pretty similar to C
"One of the main principles in Csound development is to guarantee backwards compatibility. You can still render a Csound source file from 1986 on the latest Csound release, and you should be able to render a file written today with the latest Csound in 2036."
I wish more "modern" languages and frameworks put in the effort on this point as well.
Earlier quoted context omitted.
Just do it with makefiles, the workflow is pretty similar to C
the gui is pretty useful though because it allow you to look up help for statements in your code. this is necessary to do anything because everything is completely unintuitive and nonsensical, so you constantly need to be racing through the docs to make anything interesting
I dunno, have things gotten less fun?
csound is trash edit: whoever flagged me is being paid off by csound
While conceptually sound, CSound offers an unintuitive interface and program flow in my opinion. Also the lack of ability to do more "human-readable" actions like use music notes out of the box is a point of frustration (although it is possible with some extra steps.)
Earlier quoted context omitted.
supercollider is way better than csound
I honestly find it way way easier to do FFTW manually in C and then convert the output with ffmpeg then use supercollider, like by a significant number of orders of magnitude. I've given sc 5 years, usually I'll try to use it, give it a few days of effort to do what I want, then give up, rewrite what I want in C, and be done with it in an hour Some people love it. More power to them. I wish I was one of them
What does it do? These hint at some neat possibilities but I still don't get it: a sound and music computing system a tool for composing electro-acoustic pieces real-time
Basically it's for creating music programmatically, conceptually it's solid although it does lack some major features (you have to convert frequencies to notes, and as far as I'm aware there's no inherent option to use the note itself).
Earlier quoted context omitted.
Have you tried other musical programming languages like supercollider and puredata? I find them to be quite a bit crazier. Csound is ridiculously straight forward in comparison. Absurdly more comprehensible to me
supercollider is way better than csound
You like supercollider. That's fine but it doesn't make csound "trash." You want a gui. That's fine, but csound users like myself and others here prefer a solid scripting environment.