Max/MSP Tutorials

Final Submission Information for Introduction to Creative Computing

You may be interested in looking at the assessment criteria for this course which can be found here.

For the performance, we're using one of the Endirol keyboards. It's eight pans use the following numbers:
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 the laptop's screen size/resolution is different from the G5s. Don't use the full screen of the G5 - keep things towards the upper left.

NB in 2005-6 the performance only applies to the 20 credit version

On Tuesday, 16th May, between 11 and 1 you need to come and transfer your patch onto the Department laptop and test it.
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 Mateusz 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.

You are required to submit the following on the Friday of week 12, according to the usual submission rules:

This should be as an aiff or wav file on CD. You are strongly advised to include duplicates or backups to avoid media failure.
Information regarding recording from you patch to file can be found here.
NB Late amendment! You are strongly recommended to check out the "adoutput~" object for this purpose!

...with the documentation specified below...
You should ensure that your patch has 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 patch during performance.

All written, electronic documentation should be submitted in doc, text, or rtf formats (one only!).
Include a printed 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. This material should also be included electronically on the CD mentioned above.
Include, ideally within the program itself (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 standard Max/MSP Distribution). Include a reference to it and where it can be obtained originally.

Your CD should be very clearly labelled with your name, student number and the course name.
You should include amongst your documentation a clear list of everything that is on the CD.
Make sure that the information included on your CD is clear.