It's tough to make a direct comparison. They're very different systems. Here are a couple thoughts:
- From what I recall, ChucK doesn't really have any equivalent to CSound's score -- you just procedurally schedule changes. If you've every seen JSyn [1], I think ChucK is roughly equivalent to it, but with the language adapted to be more music centric than Java. JMSL [2] is roughly a Java equivalent to CSound's score file, and I don't know of anything in ChucK that fills that role.
- CSound is not really built for modularity or flexible routing between components. ChucK is better in that regard.
- CSound also has the benefit of a couple decades worth of usage and all sorts of interesting corners to its ecosystem.
I'm sorry if this isn't a very coherent comparison. I haven't used CSound in a few years, and ChucK in even longer. If you're doing classical music, I imagine you'll value CSound's scoring capabilities over ChucK's synthesis flexibility.
- From what I recall, ChucK doesn't really have any equivalent to CSound's score -- you just procedurally schedule changes. If you've every seen JSyn [1], I think ChucK is roughly equivalent to it, but with the language adapted to be more music centric than Java. JMSL [2] is roughly a Java equivalent to CSound's score file, and I don't know of anything in ChucK that fills that role.
- CSound is not really built for modularity or flexible routing between components. ChucK is better in that regard.
- CSound also has the benefit of a couple decades worth of usage and all sorts of interesting corners to its ecosystem.
I'm sorry if this isn't a very coherent comparison. I haven't used CSound in a few years, and ChucK in even longer. If you're doing classical music, I imagine you'll value CSound's scoring capabilities over ChucK's synthesis flexibility.
[1] http://www.softsynth.com/jsyn/
[2] http://www.algomusic.com/jmsl/