- Performance Dates: 3 (11am, 3pm), 4 (11am, 3pm), 7 (3pm) November 2022
- Artefact Submission Date: 23:59 14/11/2022
- Mark weighting: 50%
- Submission: submit your assignment according to the instructions below
- Policies: Late submission not permitted.
At the end of semester your LENS performance will be assessed in terms of quality of the artefact itself and through a live performance.
We are looking for performances (and associated artefacts) that are sophisticated in terms of fundamental concepts in music computing, have a high design/compositional quality, and that allow a high level of expression and collaboration during performance.
Your LENS performance consists of:
- an in-person ensemble performance that you will participate in with your group
- performance materials submitted through GitLab
There are two representations of your LENS performance: the ensemble performance at the final gig, and the performance materials you’ll submit through GitLab.
Your performance is the primary representation of your work. As described in the marking criteria this includes all aspects of the performance.
Your ensemble performance:
- must involve at least three LENS members (but hopefully all members of your group)
- must be created with one of the computer music languages studied this semester
- must be 5-7 minutes in length
- must be presented at a LENS performance in the exam period
We’ll make a video & audio recording of the performances for archival purposes and also to put on the YouTube channel.
You will perform a concert with the members of your group. Each group member must present their own work and be prepared to participate in at least two other pieces. By default we expeect everybody in the group to be in everybody else’s pieces.
You must submit your performance materials through GitLab in the
final-performance folder in your submission repo
Your performance materials:
- must be submitted on Gitlab
- must include all patches, code, sound files, scores, instructions required to produce your performance
- must include a
README.mdfile explaining how to get your performance up and running.
Please use good judgement about the size of media files you upload to GitLab. It’s ok if you need to upload large files (e.g., up to 100MB or so), but better if you can keep sound files smaller.
|Nov 4||3pm||808 Cowbells|
- Venue is Llewellyn Hall, ANU School of Music for all performances
- 2 hours before performance time: You can access the venue to plug in, get comfy and make sure all sound and vision is working.
- 1 hour before performance time: run-through in reverse order
- We will start at 5-minutes after the performance time (in case audience arrives and wants to sit down etc)
Concert day is likely to be intense, try to get good sleep, eat properly, and bring a water bottle.
Your performance will be a public event! Feel free to advertise it, create a poster, and invite up to 100 of your best friends and foes.
We will provide for each laptop:
- HDMI input
- 3.5mm stereo (headphone) cable
- power point
We will also provide a WiFi router with internet.
You need to provide whatever adapters or cables that are necessary to connect HDMI and a 3.5mm headphone jack to your computer, you should also bring your power adapter.
By default, we expect every member of the ensemble to connect their laptop to all of: HDMI, 3.5mm headphone jack, and a power point and leave it plugged in for the duration of your setup, run through and performance.
- We will provide a big PA system and foldback speakers in the venue.
- There will be technical support available at the performance (from our staff and and School of Music technical staff), support is limited to connectivity issues, not stability of your piece :-)
- You will need to confirm the order of works in your group’s concert and any special instructions for the HDMI and audio inputs by the week 12 workshop.
If you have trouble getting your laptop to output HDMI or audio over a 3.5mm headphone jack, please sort this out well before the final performance.
Your LENS artefact will be assessed based on the representations above. The marking criteria (based on the course learning outcomes) are:
(50%) sophistication and ambition with regards to sound and music computing concepts
(20%) technical quality (e.g., stability, level of polish, absence of bugs/jankiness, staging)
(20%) demonstrated capacity for expression (creative control) and collaboration during live performance
(10%) presentation and communication through performance materials
We prefer ACM reference format: https://www.acm.org/publications/authors/reference-formatting
Some example references are as follows:
# References 1. Alice McGuffing. 2022. Ideas for creating the animated ripple effect 2. Jerry Wang. 2022. Background Artwork (`artwork.jpg`) 3. Howzit (StackOverflow user). 2018. p5js-image-array (CC BY-SA 2.5). Retrieved from: <https://stackoverflow.com/questions/51233447/p5js-image-array> 4. p5 Reference. No Date. MouseWheel Example (CC BY-NC 4.0). Retrieved from: <https://p5js.org/reference/#/p5.Element/mouseWheel> 5. Scott Bauer. 2004. Photo of Potatoes (Public Domain). Retrieved from: <https://en.wikipedia.org/wiki/Potato#/media/File:Patates.jpg> 6. Aaron Wu. 2018. Boat Photo on Unsplash. Retrieved from: <https://unsplash.com/photos/_8rjlHwN4uk> 7. Wikipedia. 2022. J M W Turner Article. Retrieved from: <https://en.wikipedia.org/wiki/J._M._W._Turner>