I would like to raise an issue concerning a tutorial on Sonic Pi:
In my experience (at the University courses I give and in my own practice) there are (at least and by no means exhaustively) two ways of approaching a tutorial. In the case of Sonic Pi you could say:
- the coding perspective
- the musical perspective
Definetely there is no clear borderline between these two but for the sake of clarity let me give an example:
- you can ask, what sort of things can I do with Sonic Pi (e. g. play samples and manipulate the rate or what can I do with
- you can ask, how can I approach a given task within the musical context (e. g. blend in part of the music or how to create a bassline while live coding)
It is a bit like buying a car: Some ask things like: How fast can it speed up or how much space is in the trunk, does it look expensive and others will (more practically) ask, can I store my 4 suitcases in it and can I easily back in a parking space with this car.
Usually my students have some more or less concrete ideas they would like to hear as music (meaning: would like to code) within Sonic Pi. That goes not without problems but it is a legitimate request. I more and more tend to - at the one hand - start coding and let Sonic Pi guide me in the creative process (that’s asking the question: where does Sonic Pi want me to go); but - on the other hand - occasionally I have a specific idea about what my composition or live coding should sound like (that is more like asking to solve a specific challenge).
I tried to collect some solutions concerning the ‘musical perspective’ here (an ongoing project and definitely under construction).
What do you think about that?
Should a tutorial reflect these positions?
Do you have other ‘perspectives’ and ‘learning objectives’ you think would be important to be covered?