Final Submission Information for Creative Music Computing 2a
What you need to submit
A logbook containing:
Tasks
You should attempt eight tasks, of which you are required to submit at least four, each of which is worth 15% of the whole.
Projects
In addition you need to submit one project using MaxMSP or MaxMSP and Max for Live/Ableton and/or SuperCollider (or both) for 40%. You may use other software if discussed first with the module tutor.
For each project, you should create a composition or performance technology. These may be based on work you have undertaken during the tasks. Indeed the role of the latter is to introduce you to technologies that you may find interesting and wish to develop in the projects. The Individual Project is distinct in that there are no restrictions on what you do, other than that the project should be based on one or more of the technologies used during the course.
You may be interested in looking at the assessment criteria for this course which can be found in Artefact Creation (document available via University Login only).
The Logbook
All work on tasks and presentations as well as documentation of your projects should be collected together into a Logbook. You can optionally include a physical copy of the logbook, but an electronic verision must be submitted. You are encouraged to submit the logbook and any additional material on a thumb drive.
The logbook is worth 60% of your total mark.
The logbook should include:
A week by week log of your work and activities. It is recommended that you maintain your logbook each week.
photographs and videos of each task, including screenshots of any code that you have used
a written description of aims, int entions and outcomes
a critical evaluation of compositions and patches. You should reference other examples and practitioners in the field to contextualise your work in the light of others' work.
You may use up to 500 words (~250 words tasks, ~250 words critical reflection).
The logbook can be compiled using any word processing software, but can only be submitted as a pdf document. Refer to submitted movies from within the logbook, and include the movies separately in the submission. Images can, of course, be included in the logbook.
There is an absolute limit of 700MB data per submission. Submissions which include more than this amount of data will lost 5% of marks per 50MB exceeded. So, a 750MB submission would lose 5%, an 850MB submission 15%;
Please ensure that any videos you include are compressed (e.g. mp4), rather than dv. We are not interested in super-high-quality video for assessment purposes.
All documentation must be submitted in electronic versions.
A recorded version of your composition/performance;
Guidelines on how to use the item (these should be checked with a colleague to ensure that they are properly usable). Please include photographs/videos of the item in operation, including any software or firmware developed.
For information about the presentation, please see below.
All assignments should be submitted to the i-centre by 2pm on 2pm Tuesday December 19th 2017
You need to submit four assessible tasks, plus one project - you choose.
All material should be submitted in the form of a logbook (see above).
Important information to bear in mind
If required, you'll be provided with a computer, a sound card and relevant drivers, a keyboard, a microphone and a data projector to project your screen as you work. If you require anything else you need to provide it (additional data projectors are available from Media Productions).
Remember that, should we use a laptop, its screen size/resolution is different from the desktop computers'. Don't use the full screen of the desktop computers - keep things towards the upper left.
If you require any extra facilities, such as multiple microphones, you need to let me know.
The Performance is an assessment occasion, so you may improve either your MaxMSP or SuperCollider patch(es) in the period leading up to it. These improvements will only be relevant to your assessment if you perform!
You will need to test your patch on the Department laptop if you are using it. Remember that the laptop's screen size/resolution is different from the desktop computers' and that the laptop is less powerful.
You are strongly advised to check your patch and its associated resources (externals, audio objects, etc.) on as many machines as possible before this.
You need to let me or the technician know as soon as possible if you require any special resources. You will be provided with the laptop, a microphone and a PA - any other equipment, including cables, you will need to provide yourself unless you confirm in advance that it can and will be made available.
You should be available for performance at least 30 minutes before your projected slot.
You should be available for performance until at least 30 minutes after your projected slot.
At the concert you will have five minutes to get yourself ready and perform. Please be punctual. Punctuality and fluidity will be factors in your assessment.
Physical Submission
You are required to submit the following on 2pm Tuesday December 19th 2017, according to the usual submission rules:
A recording/demo of your composition/performance/patches
These are not replacements for the performances.
These should be submitted as aiff or wav files.
The Patches Themselves
...with the documentation specified below...
You should ensure that your patches have sufficient information available and is set-up so that it can be used effectively quickly and without problem. If necessary include notes that you have made regarding your own control of the patches during performance.
Documentation
All written, electronic documentation should be submitted in doc, text, or rtf formats (one only!).
For projects include a summary of what you meant to achieve and how you achieved it (or not). Include reasons for failures or successes and details of any information you would have found helpful on the course. Word count for these summaries should be in the order of 200 words.
Include, ideally within the patches themselves (for instance, as comments or within a subpatch), a set of instructions concerning your program. Ideally you should detail each program function including menu items, command buttons, set-up requirements, etc. Imagine yourself to be someone who has never come across your program before and so will want to know, quickly and efficiently, what can and can't be done. It is in this regard that beta-testing is of considerable value.
Include a copy of any external object(s) used (that is, any object that is not a part of the most recent standard MaxMSP or SuperCollider distribution). Include a reference to it and where it can be obtained originally.
Any queries, email me or post an enquiry on the course forum.