Difference between revisions of "256a-fall-2024/final"
(→Final Deliverables + Presentation) |
(→Final Deliverables + Presentation) |
||
| (8 intermediate revisions by the same user not shown) | |||
| Line 13: | Line 13: | ||
** a playlist generator | ** a playlist generator | ||
** a music recommendation system | ** a music recommendation system | ||
| + | ** a design that uses external hardware other than computer/laptop | ||
* do this in ChuGL | * do this in ChuGL | ||
| Line 20: | Line 21: | ||
== Milestone 1: Project Proposal + Something Working == | == Milestone 1: Project Proposal + Something Working == | ||
| − | '''due: Wednesday (11/20)''' | + | '''due: Wednesday (11/20) 11:59:59PM''' |
| + | *Note that milestone 1 and 2 are back to back due to Thanksgiving break; extensions for milestone 1 won't be possible. | ||
| − | * deliverables: three ideas, sketched out | + | * '''[Part 1: Project Proposal]''' deliverables: three ideas, sketched out |
** maximally different from each other | ** maximally different from each other | ||
** try to articulate as much specificity as possible! | ** try to articulate as much specificity as possible! | ||
| Line 28: | Line 30: | ||
** a short paragraph explaining each idea | ** a short paragraph explaining each idea | ||
* upload your ideas / design sketches on your final project webpage. | * upload your ideas / design sketches on your final project webpage. | ||
| − | + | ||
| − | * a working version of your core mechanics and experience | + | * '''[Part 2: Something Working]''' a working version of your core mechanics and experience |
** this should include basic elements of audio, graphics, interaction | ** this should include basic elements of audio, graphics, interaction | ||
** as usual, a short video demo (0.5 - 1.5 minutes) | ** as usual, a short video demo (0.5 - 1.5 minutes) | ||
| Line 35: | Line 37: | ||
== Milestone 2: Minimal Essential System == | == Milestone 2: Minimal Essential System == | ||
| − | '''due: Monday (12/2)''' | + | '''due: Monday (12/2) 11:59:59PM''' |
* the minimal essential system: an unpolished version of the essential experience; i.e., all core elements working and working together | * the minimal essential system: an unpolished version of the essential experience; i.e., all core elements working and working together | ||
| Line 53: | Line 55: | ||
2) a polished project webpage, including a) one or more screenshot, b) the polished video demo, c) name and description of the project, d) how to run/use, and e) your project files (without intermediate files) and an executable (please specify which platform). | 2) a polished project webpage, including a) one or more screenshot, b) the polished video demo, c) name and description of the project, d) how to run/use, and e) your project files (without intermediate files) and an executable (please specify which platform). | ||
| − | 3) (in-class) a 3-6 minute final presentation that includes a) your polished video demo (or a live-demo, if you'd prefer) b) brief description of what it is and why you made this c) Q&A, as time allows. This portion will take place starting 12:15pm Friday (12/ | + | 3) (in-class) a 3-6 minute final presentation that includes a) your polished video demo (or a live-demo, if you'd prefer) b) brief description of what it is and why you made this c) Q&A, as time allows. This portion will take place starting 12:15pm Friday (12/13) in the CCRMA Stage (3rd Floor). |
Submit your final project webpage URL to Canvas. Please note that there is no late submission for this, as we will be evaluating your final project, presentation, video, and webpage content on the same day, and submitting your course grade soon thereafter. | Submit your final project webpage URL to Canvas. Please note that there is no late submission for this, as we will be evaluating your final project, presentation, video, and webpage content on the same day, and submitting your course grade soon thereafter. | ||
Latest revision as of 11:46, 5 December 2024
Contents
Final Project: Design Your Own Interactive Audiovisual Software Tool
"Design and prototype an interactive software tool, using ChuGL and integrating real-time audio, graphics, and interaction."
- what must your final project have:
- real-time audio/music, graphics, interaction
- a software system
- what can it be?
- tool, toy, game, instrument, interactive essay
- or some other, unclassifiable artifact
- what it CANNOT be:
- a sequencer (though it can contain a sequencer)
- a playlist generator
- a music recommendation system
- a design that uses external hardware other than computer/laptop
- do this in ChuGL
- for reference, check out final projects from previous years:
- https://ccrma.stanford.edu/courses/256a-fall-2023/projects/
- (and you can follow the link to see 2022, 2021, 2020, 2019, 2018, 2017, etc...)
Milestone 1: Project Proposal + Something Working
due: Wednesday (11/20) 11:59:59PM
- Note that milestone 1 and 2 are back to back due to Thanksgiving break; extensions for milestone 1 won't be possible.
- [Part 1: Project Proposal] deliverables: three ideas, sketched out
- maximally different from each other
- try to articulate as much specificity as possible!
- ideas sketched out (analog or digital)
- a short paragraph explaining each idea
- upload your ideas / design sketches on your final project webpage.
- [Part 2: Something Working] a working version of your core mechanics and experience
- this should include basic elements of audio, graphics, interaction
- as usual, a short video demo (0.5 - 1.5 minutes)
- update your webpage
Milestone 2: Minimal Essential System
due: Monday (12/2) 11:59:59PM
- the minimal essential system: an unpolished version of the essential experience; i.e., all core elements working and working together
- as usual, a short video demo (1 - 2 minutes)
- update your webpage
Final Deliverables + Presentation
- all materials (webpage, video, screenshots, descriptions, code): due on Canvas on Thursday (12/12) 11:59:59PM
- final presentations: Friday (12/13) starting at 12:15pm in the CCRMA Stage
More specifically, below are your expected deliverables:
1) a polished video demonstrating your final project. Footage of your project should be shown in fullscreen. Please take some time to craft a compelling video narrative that showcases your work.
HINT: for your final deliverable consider working backwards from your polished video demo, as a "vertical slice" of the whole system. In other words, don't worry about building out a fully featured system—nor is there likely time to do so; focus instead on designing a polished narrative of your system in action that is representative of the larger system and intended experience. For example, consider an musical/audiovisual narrative with beginning, middle, end (e.g., if you are building a music-making tool or toy), or a play-through of a mini-level (say, if you are building a game)—and prioritize only those features that contribute to this "vertical slice".
2) a polished project webpage, including a) one or more screenshot, b) the polished video demo, c) name and description of the project, d) how to run/use, and e) your project files (without intermediate files) and an executable (please specify which platform).
3) (in-class) a 3-6 minute final presentation that includes a) your polished video demo (or a live-demo, if you'd prefer) b) brief description of what it is and why you made this c) Q&A, as time allows. This portion will take place starting 12:15pm Friday (12/13) in the CCRMA Stage (3rd Floor).
Submit your final project webpage URL to Canvas. Please note that there is no late submission for this, as we will be evaluating your final project, presentation, video, and webpage content on the same day, and submitting your course grade soon thereafter.
