At the moment I am using git mainly to keep a record of my live coding.
Chuck Live Coding as part of HELOpg
https://github.com/witt0191/Chuck-Live-Coding-Record
Obviously using git it is easy to revert back to earlier versions
which allows the idea of recapitulation and chorus playing. My
intention is to expand the script so it track running shreds against
the git file hash so you can directly interact with the versioning.
Something I have always wanted to try is a collaborative, distributed
performance using version control to link the two performances.
Thinking back the Audicles version control was one of the things that
first interested me in ChucK
On Tue, Nov 29, 2011 at 10:48 AM, Kassen
On 29/11/2011, Scott Hewitt
wrote: Am very interested in looking into terminal based chuck ides
Me too, and as there are more posts to this topic I get more interested in exactly what people are doing and why. Some of this strikes me as quite exotic (but maybe I just got a bit baffled at the HUGE number Renato is sending into the blown bottle's vibrato gain :-) ).
Do I understand correctly that you are using Git so you can easily return to older version of the code, maybe so you can do the equivalent of traditional musical structures that regularly return to thems or choruses? It's a bit of a shame that the Audcle's take on version control wasn't explored in more depth. Maybe the Audicle was a bit too far ahead of its time, at the time.
Kas. _______________________________________________ chuck-users mailing list chuck-users@lists.cs.princeton.edu https://lists.cs.princeton.edu/mailman/listinfo/chuck-users