The Task
Sound Synthesis and Integration
- Create a patch which takes a stream of numbers between 0.0 and 1.0 as input, and calculates a changing sound (MSP signal) from it. For instance, the sound might be silent if the number is 0.0, and loudest when it is 1.0. Alternatively you might choose to rescale the value so that it controls frequency, rate, stereo position, etc... Finally, you might choose to generate a set of values based on the image matrix and use these values to control, for example, a set of filters. The options are, literally, endless.
- Decide whether you want to use synthesis, sampling or both.
- Optionally consider using an envelope, so that your sound consists of a "note" with a fixed duration, rather than a continuous drone. You can do this using the object line~ to create an envelope, as illustrated in the MSP tutorial patch from class, or optionally also look at function and adsr~ objects.
- Recommended objects: Sound Synthesis: tri~, square~, saw~, pink~, biquad~, rect~; More advanced sound synthesis: resonators~, oscbank~ ; Envelope: line~, function, adsr~; (See also MSP examples for ideas such as FM synthesis if interested); Sound Sampling: sfplay~, index~, groove~, noise~...
- Test your sound patch on a standard video stream (e.g. quicktime movie). Revise it until you like how it sounds (subject to the requirements here).
- Connect your results from all Jitter tasks to create a system for transforming video to sound. First test using a single copy of the analysis and synthesis patches. Once it is working, you will need as many copies of these as you have video streams coming out of your decomposition patch.
- Examples, etc., are here.
- Patch samples
Please ensure that, in as far as you are able, your patches work immediately they are opened. If your patch or patches use audio or video files, include short samples that have been 'preloaded' or reference to a stored one. Also include methods for loading user samples, too. Include functioning presets.
- Media files
You must submit media files, such as video, audio or image files, but please ensure that video files are compressed to a reasonable degree. You should never submit dv files, but compress these to mp4. You should submit no file that is greater in size than 25MB/minute.
- Added value
By completing the details of the task you will achieve at least a pass mark. By imaginatively and creatively considering how you might implement the task originally you can add value to your submission, and this added value may increase your mark significantly. Even when making videos of short demonstration tasks try to consider musical and performance criteria.
- Don't just investigate the help file for a particular object - investigate the help files of the linked objects as well. Using these, developing your ideas into something individual and unique will give you many more points and may well help you decide what you want to do for your final project(s).
- Find the music
One particular way of adding value is to make sure that your submission is satisfying musically as well as working technically. Many people are able to make the technologies work, but fewer are able to make them work in a way that enhances the musicality of the result. No matter how technically brilliant, a submission with poor musical results is unlikely to do so well.
Finally
- Compress (zip) your patches, demos, etc. into one file called your_student_number_"jitter4" (e.g. 0504335_jitter4.zip), include a readme with your name and student number and, if necessary, how to use or just open the patch.
- Submit a copy of the files to the i-Centre on 2pm on Tuesday 8th May 2018
|