Table of Contents
sessions: PERFORMANCE
Session 09 - Wed 10th June
SESSION SECTIONS
PART ONE
<note> TECH SUPPORT - PERFORMANCE PREP
drop-in session for students with specific tech questions
(1 hr)
</note>
<note WARNING> PERFORMANCE - VJ
(45 mins)
Students take turns to share the screen as part of a collective VJ performance
songs submitted beforehand - convert to AIFF
audio streamed via ListenTo plugin
<hi cyan > Listen To link - setup https://listento.audiomovers.com/ </hi>
<hi lime > Tracks from students </hi>
</note>
PART TWO
<note important >DEMONSTRATION - ???
Make a simple VJ interface
</note>
<note tip >EXERCISE - CRITIQUE / FEEDBACK FORM
DURING:
Vote here - https://www.menti.com/zc2wbptq7f
DURING: Make quick notes for each person on their performance:
WWW (What Works Well…)
EBI (Even Better If…)
- be specific, be critical, be supportive
Consider:
VISUALS - Aesthetics, media
MIX - the performance, syncronisation, mood
POST: DISCUSSION: Ask the group
- What did you think was effective?
- could you work out technically what was going on?
QUESTION: Looking at the performances as a whole experience, including your own, what have you learned?
<hi cyan> LINK - FORM - https://forms.gle/qR8zn6KeDBBV5nDF7 </hi>
<hi cyan> LINK - MENTI https://www.menti.com/zc2wbptq7f </hi>
</note>
PART THREE
<note>ASSESSMENT FEEDBACK
- update the students on the assessment feedback - when to expect grades
- invite them to contact you (by Friday) if they want some 1-to-1 feedback on Monday - I will make slots
- ask Katie to stick behind to go over a technical problem I've spotted
<hi yellow> POINTS TO CONSIDER: </hi>
BASICS
- file_naming naming files properly - 'unitiled' vs Surname_FirstName-Project_Name-v1
- File Sizes - try and be efficient 30mb max per project - upload your videos to vimeo / youtube / gdrive - make sure you compress pdfs for screen - dependencies videos - double check they are compressed / size - or link me to a google drive to get them
- Deliverables - have you sent the requested files? - izz file, dependencies, documentation, statement
IZZY BEST PRACTISE
- Scene Naming - give your scenes a name - descriptive/ evocative / useful
- Comment Actor - use the comment actor - to help make notes
- Tidy Your Patch - less like opening a bomb - at least re-order the patch to make sense - think also about the media needed in your final version - get rid of unnecessary movs
DESIGN DECISIONS
- Iteration, Iteration, Iteration - test, try-out, do many versions
- Design Layout - (eg, proposals) - simple - be specific - don't include unnecssary information. most important info FRONT AND CENTRE
- Value Scaling - Limit Scale Value actor - not many people attempting this, and only a couple doing it well - everyone needs to get a hang of this concept
CONTEXT
Research - research beyond the specific 'generative art' task? - process document is a chance to show it in context and give your perspective
Critical thinking - provide a statement on your work - can be simple be give your thoughts, what you were aiming for, what you learned
</note>
<note warning >ASSIGNMENT - SCALING
complete the 10 scaling tasks in the NEW ACTIVITY PATCH
- submit your patch to me
consider reviewing the previous videos on SCALING
<hi magenta> PATCH - Activity Patch - Scaling Exercises </hi>
<hi yellow > VIDEO - SCALING VALUES - https://www.youtube.com/watch?v=WuPpy461cIo</hi>
<hi yellow > VIDEO Troikatronix - VALUE SCALING - pt 1 - https://www.youtube.com/watch?v=yoPw9c4XZCg </hi>
<hi yellow > VIDEO Troikatronix - VALUE SCALING - pt 2 - https://www.youtube.com/watch?v=_GEpgHlvgSo </hi>
</note>
<note warning >HOMEWORK - ELECTRIC BOX
play this game to help bost your systems thinking
<hi cyan> Electric Box - http://www.engineering.com/GamesPuzzles/ElectricBox.aspx </hi>
</note>
