Hey All,

FWIW, I often take advantage of both systems in a piece.  Sometimes I'll create a bunch of synths in SC that can be triggered by OSC and use Chuck as a score language.  If I'm doing a lot of string/data processing, then I'll use Python to trigger them.  But that's part of my practice, since many of my pieces involve interesting bits of hardware, I have to utilize OSCulator, SC, Chuck, and Puredata all for one piece of music.  

So, for the sake of completeness, I'll back the notion that you don't actually have to make an exclusive choice between environments.  ;)  The right tool for the job, right?

-Mike

-- 
Michael Clemow

http://michaelclemow.com
http://abattoirprojects.com

On Friday, August 10, 2012 at 7:33 AM, Kassen wrote:

On 10 August 2012 04:11, David Ogborn <ogbornd@mcmaster.ca> wrote:
Great answer - I'm going to save it and quote it whenever needed! :)

Thanks Dan & David,

Credit where it's due; this was more or less the conclusion of the
debates I had with SC expert James 'DewdropWorld' Harkins.
We found that the differences we and others with some expertise noted
didn't really matter at all for those picking up either language.
New users (who adopt either) simply seem to find that one is quite
straightforward and the other doesn't make a lot of sense. We didn't
notice any obvious structure or pattern in that. It's a interesting
phenomenon.

It'd be nice to try to figure out whether things like lessons or
online tutorials, examples or more experienced friends influence this.
What I can tell though is that passionate online debates don't seem to
have any effect on this at all; they can take away misconceptions
about what is possible but not change what people find fun or easy.

Yours,
Kas.
_______________________________________________
chuck-users mailing list
chuck-users@lists.cs.princeton.edu
https://lists.cs.princeton.edu/mailman/listinfo/chuck-users