Thanks for the comments, Sam!
The DAW feedback was useful to me at all stages, because I had a target point I was trying to get to little by little, and the visualization helped me pace myself (to make sure I was getting there in the right time scale and wasn’t making any jumps from one execution to the next that were too dramatic). It also helped me make decisions about when to time the execution of my new code. Towards the end, when I was manipulating effects envelopes, the visualization was key in helping me see what the effective range of values were in each envelope so that I could decide how to change their scaling. However, I’m not sure that the visualization was as useful to the audience throughout the performance as it was to me — that would require a research study, which I’d definitely like to undertake in the near future.
EarSketch still just supports samples. Because of our primary target in computer science education, we’ve stayed away from paradigms which might require MIDI-like control of synths and a corresponding knowledge of music on the level of pitches and notated durations. Most of our teachers for EarSketch, in fact, are CS teachers who don’t know much about music, and a lot of our teacher training workshops are spent addressing their fears that they won’t be able to teach it because of that.
—Jason
> On Oct 2, 2015, at 4:37 PM, Dr. Sam Aaron <samaaron_at_gmail.com> wrote:
>
> Looks great, EarSketch has really come on leaps and bounds recently. Seems like you’ve managed to get rid of most of the stutter on a code refresh - well done!
>
> I think that early on in the video the visual feedback was really useful, although as the patterns got more complex it was harder to follow what was going on (in both the code and the graphics). Although this is to be expected as someone that’s not fluent in the system. I’m interested to know your opinion on how useful both the code and the graphics were in that middle section. Did they help inform your next decision?
>
> Finally, I was wondering - does EarSketch have support for ‘synths’ or is it just samples at this stage?
>
> Anyway, keep up the awesome work!
>
> Sam
>
>
>> On 2 Oct 2015, at 21:17, Jason Freeman <mail_at_jasonfreeman.net> wrote:
>>
>> 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/5ikAJJ4klatAyyYcsXnswe
>
> 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/4MKTUr3FC2dhmf6ophVMJl
To leave livecode, email livecode_at_group.lurk.org with the following email subject: unsubscribe
Received on Fri Oct 02 2015 - 20:47:51 BST