Revision as of 17:24, 12 January 2023

Programming Etude #1: "Poets of Sound and Time"

Music and AI (Music356/CS470) | Winter 2023 | by Ge Wang

In this programming exercise, you are to write two chuck programs to help you create some experimental poetry involving text, sound, and time.

Tools to Play With

• first, download the latest official ChucK release -- This will install both command line chuckand the graphical IDE miniAudicle (on macOS and Windows).
• next, get the latest bleeding edge secret chuck build for this course -- Some important things to note:
  • this is the command line chuck, which you will need for this etude (you can use miniAudicle as a text editor only, as it does not have the new functionalities we need); you can either put the bleeding-edge chuck in your homework folder or (if you are feeling brave) you can overwrite your installed command line chuck. Depending on where you put this bleeding-edge build, you will need to explicitly run it (for example, > ./chuck program.ck will explicitly run chuck from the current directory, rather than the system-installed chuck).
  • NOTE: using command line chuck makes it possible to get console input, which is not available from the miniAudicle IDE.
  • NOTE: Windows users can either use the default cmd command prompt, or might consider downloading a terminal emulator.

Things to Think With

• watch Allison Parrish's "Experimental Creative Writing with the Vectorized Word" (video)

Express Yourself!

Using the ChucK/ChAI starter code for Word2Vec...

• write code to help you create some experimental poetry involving text, sound, and time.
  • text: use the Word2Vec object in ChucK and one of the datasets to help you generate some poetry
  • sound: use sound synthesis and map the words (e.g., using their vectors to control parameters such as pitch, volume, timbre, etc.) to sound
  • time: don't forget about time! make words appear when you want them to; synchronize words with sound; visually and sonically "rap" the words in time!
• create two poetic programs / works / performances:
  • make them as different as possible
  • for example one poem can be fully generated (you only need to run the chuck code, and the poem starts) and the other one interactive (incorporates input from the user, either through a a text prompt, or another means of input such as mouse / keypresses)

Some Prompts / Bad Ideas

• a poem can be about anything; hint: try starting with how you feel about a particular thing, person, or event
• starting with an existing poem and use word2vec to morph it over time
• an experimental love poem
• stream of consciousness
• remember "Jabberwocky" by Lewis Carroll? maybe your poem doesn't need to make sense to everyone
• HINT: try to take advantage of the medium: in addition to printing out text to a terminal (both a limitation and a creative constraint/opportunity) you have control over sound and time at your disposal
• HINT: experiment with the medium to embody your message -- for example, a poem about chaos where the words gradually become disjointed and nonsensical

Starter Code and Examples

• here are some starter code:
• and some examples
• free to incorporate these or use them as starting points

Reflections

• write ~250 words of reflection on your etude. It can be about your process, or the product, or the medium, or anything else. For example, how did your poems make you feel? Did you show them to a friend? What was their reaction? What makes something "poetry" (versus, say, "prose")?

Deliverables

• create a CCRMA webpage for this etude
  • the URL should live at https://ccrma.stanford.edu/~YOURUSERID/356/etude1 or https://ccrma.stanford.edu/~YOURUSERID/470/etude1
  • you may use Medium or another publishing platform (in this case, please still link to this from your CCRMA webpage)
• your Etude #1 webpage is to include
  • a title and short description of the exercise (free free to link to this wiki page)
  • your ChucK code
  • your poems in some form (this will depend on what you chose to do; since sound and time are involved, you could include a screen capture with sound)
  • any acknowledgements (people, code, or other things that helped you through this)
  • your 250-word reflection
• submit to Canvas only your webpage URL