Skip to main content ANU School of Computing

Outline

  • Due date: Thursday May 6, 3pm–6pm (week 9, note the slightly later finish time)
  • Mark weighting: 20%
  • Submission: submit your assignment according to the instructions below
  • Policies: for late policies, academic integrity policies, etc. see the policies page

Description

In the week 9 workshop session everyone will give an in-class demo of their work-in-progress (WIP) for the final LENS performance. It’s not expected to be an “artistic performance” like the final performance will be, you’re encouraged to talk through what it can do so far, how it will evolve as the final performance approaches, and even raise open questions you have about the rest of the design process.

If you’re not sure exactly what to cover in your demo, here are a few questions to help you get started (note: this is not a checklist—just some stimulus material to sharpen your thinking).

  • are there any artists/pieces which you’ve used for inspiration? how will your performance/artefact explore & extend the things in that work? (it’s ok to show short clips of these artists alongside your actual WIP demo)

  • is there a key idea or concept that’s at the heart of your performance/artefact?

  • what’s unique about your performance/artefact—what is it that makes yours stand out from the crowd?

  • how are you going to make it a compelling overall performance (including the visual aspect)?

Once everyone has presented their demo, you’ll have the rest of the workshop timeslot to wander around and play with other people’s LENS artefacts. Remember, you need at least one of your classmates to be involved as an ensemble member—this is a great chance to pitch to them!

Specification

You must present your LENS artefact to the rest of the class in a 5 minute in-class demo, followed by 5 minutes of questions. You can bring your own laptop/other gear, and we will connect it to the PA (we’ll discuss the “tech rider” stuff in the week 8 workshop).

In addition to the demo, you must submit (by 11:59pm on Wednesday May 5—the day before the demo day) all the necessary patch files/code/sounds/video assets associated with your demo.

This demo should not be a ppt presentation—this is expected to be a live demo, although you can show off your artefact in whatever way seems best to you.

Submission process

You must submit your artefact files through GitLab. All students will present their work to the rest of the LENS cohort during the week 9 workshop timeslot the following day.

This is like any in-class presentation—if you do not attend you will be considered to have not submitted anything.

Marking criteria

Your demo will be assessed based the following marking criteria (based on the course learning outcomes):

  • technical quality & ambition of your artefact/performance with regards to the fundamental concepts in music computing covered in this course

  • understanding and engagement with the design and performance challenges around computer music interfaces

  • scope for collaborative ensemble interaction in your performance

  • clarity of communication in your in-class demo presentation

Peer feedback

Part of demo day is seeing what everyone else is working on and being able to give feedback & encouragement. To do this, everyone will fill out a short “peer feedback” sheet during the demo day (to be handed in at the end of the class—we’ll collate the responses and make sure everyone gets their feedback).

You’re not grading your classmates—you don’t give a mark, and the feedback you give isn’t incorporated into the grades. The purpose of the feedback is for you to help one another out in creating the best LENS performances you can, and perhaps to help you to reflect on what makes a compelling LENS performance.

bars search times creative-commons creative-commons-by creative-commons-nc creative-commons-sa