Hi Jason,
looks great! From my perspective as a SuperCollider live coder I really
like that you are able to *see* ahead of time instead of just listening *in
time*. From my performer perspective, this might be something I would like
to have too, especially as I can sill reshape the future time I was able to
see.
I think a cool feature could be to quantize changes to the timeline, e.g.
run the code and compute a future timeline but the new timeline will just
be swapped in at the next bar (or each 4 bars). It could also be
interesting to be able to preview the results of code, so it would be
displayed as an overlay to the actual sounding timeline, so that I can
inspect it visually but the old audio timeline is still playing (until I
decide that I want to hear the new timeline).
Cool stuff! Cheers,
Patrick
2015-10-02 22:17 GMT+02:00 Jason Freeman <mail_at_jasonfreeman.net>:
> Hi all,
>
> Some of you know about EarSketch (http://earsketch.gatech.edu), the
> browser-based coding environment that includes a Python / JavaScript API,
> sound library, and DAW-style view for algorithmic composition. We’ve been
> developing it for the last few years at Georgia Tech, and it’s primarily
> targeted towards students in intro computer science courses, with an eye
> towards increasing engagement and participation in computing by populations
> traditionally underrepresented in computer science.
>
> We’ve recently begun exploring the potential of EarSketch as a live coding
> environment too. Last week, I performed a live coding set in concert with
> EarSketch for the first time and wanted to share a screencast with you:
>
> https://www.youtube.com/watch?v=5ThWr3stq9M
>
> We still have some work to do in making live coding smoother in EarSketch,
> and I still have some practice to do as a performer, but…I wanted to share
> because I think the unusual structure of the environment has interesting
> implications for live coding, i.e.
>
> * all the music is based on DAW-like operations: placing audio files on a
> multi-track timeline, splicing them, adding effects, etc.
> * time is organized as a DAW timeline that loops
> * the results of code execution are visualized (for both the live coder
> and the audience) in a DAW-style display
>
> Hope you find these ideas interesting!
>
> Best,
> —Jason
> --
>
> Read the whole topic here: livecode:
> http://lurk.org/r/topic/5kYLYw3lYMBKIOfyIrgzg4
>
> To leave livecode, email livecode_at_group.lurk.org with the following email
> subject: unsubscribe
>
--
Read the whole topic here: livecode:
http://lurk.org/r/topic/o5mxajyrCelUrWS6goDem
To leave livecode, email livecode_at_group.lurk.org with the following email subject: unsubscribe
Received on Fri Oct 02 2015 - 21:14:44 BST