rhoadley.net   music   research   software   blogs

aru    seminars    m&t    critski    focm1a    cmc    circuit bending    mic2b    sensor technology    comp 3    sonic art    major project
youtube    vimeo    facebook

Resources:    Bioacoustics    Jitter    MaxMSP    OSC    Physical    PD       CBHH    sTech    SuperCollider    C/Xcode

Final Submission Information for Creative Music Computing 2b

What you need to submit

Tasks

You need to undertake nine tasks, of which you will be required to submit four, each of which is worth 10% of the whole.

Projects

In addition you need to submit either one or two individual projects: a project focused on Jitter and/or a project focused on Processing or SuperCollider. You may also submit a project combining these (and other) technologies. It is highly recommended that you use all software at some point in these projects.

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. At the end of each of the first and second semesters you will be required to perform one of your projects from that semester. So, at the end of the course you should be prepared to perform one of your projects.

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).

Important information to bear in mind

  • You'll be provided with a computer, a sound card and relevant drivers, an Ozone, 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).
  • For the performance, you may use one of the keyboards provided. Should you require the information - its eight pots use the following numbers (but do check these first):
    74 71 81 91 16 80 19 2
    (that is, these are the numbers that you should put into your route object to use the eight pan pots).
  • Remember that, should we use the laptop, the laptop's 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.

Semester 2 Performance

NB details for Semester 2 Performances, if any, tbc

  • There is a full list of performances here.
  • 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 on Tuesday 8th May 2018, 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 on WebCT. You are strongly advised to include duplicates or backups to avoid media failure.

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, Processing or SuperCollider distribution). Include a reference to it and where it can be obtained originally.

Any queries, email me or post an equiry on the course forum.