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

Jitter Resources:     Home     Blog     Forum     Examples     Projects     Tasks     Tutorials


Jitter Tasks

The Image to Sound Task

Through a series of tasks, develop a simple demonstration of image to sound conversion. Part 1: Getting Started

Task 1 Name: Image to Sound 1 Set: w1 Due: w2 Weighting: 0% Courses: cmc2b
Prev Task: Next Task: Image to Sound 2
Task Summary All CMC tasks VLE




The Task

  • Create a skeleton for your main patch in the following way:

  • Create a video input section using both jit.qt.grab and jit.qt.movie, which takes video from either camera input or a quicktime movie. This can be copied from one of the jitter help files, but you should only include controls that you will be using. Be sure to include a jit.pwindow to preview the movie output.

  • Create three subpatches: One for video decomposition, One for video analysis, and One for sound synthesis. The subpatches will be empty for now. Create a sound output section, utilizing the dac~ object. You'll want to route all audio from here. You may want to consider the number of output channels you want to use - but always remember to allow for a system to degrade gracefully if you only have stereo to play with.

  • Some more examples, etc., are here. Bear in mind that you'll need to download some external objects to make some of the patches here work.

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

  • 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_"jitter1" (e.g. 0504335_jitter1.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

You might also be interested in:

  • Jitter tutorials

The Projects

The projects and tasks are designed to help you through the various courses and materials that you'll have to deal with, and also to provide an active and practical element to what could otherwise become a rather dry and technical exercise. Tasks are small exercises - you may be asked to complete one or two per week. Projects are larger and carry a higher percentage of the mark. We will undertake two, three, four or more projects and tasks. The final project is usually an individual choice project, and will be worth significantly more than the others in terms of percentages in your portfolio. We will usually try to set aside a time to perform the projects in a public setting.