rhoadley.net   music   research   courses   software   blogs

ARU    Seminars    Comp&Imp    NMP    CMC2a    CBHH
Sensor Technology    Sonic Art    Major Project    MA Resources

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

Max/MSP Resources:     Home     Blog-wp     Forum     Examples     Projects     Tasks     Tutorials

Max/MSP Tasks

The Breakbeat Cutting Task

Task 1 Name: Breakbeat-Cutting in MaxMSP Set: w1i Due: w3i Weighting: 10% Courses: cmc2a
Prev Task: Next Task: Introduction to Pure Data
Task Summary All CMC2a tasks VLE

This task involves understanding cutting and reforming soundfiles.

A few examples

Find a soundfile that includes at least one four-beat bar...

bbcutmax

To cover:

  • In the above extract, the buffer~ called bbcut is used to store either the soundfile called sandbeat_m.aiff or the soundfile called tlonbeat_m.aiff. The right outlet of a buffer~ object sends out a bang when it has finished loading the object, and in this case it's used to bang an info~ object. The latter is referring to the bbcut buffer~ and, when banged, it informs us of the sample's rate and length (from the first and seventh outlets respectively). Check the help file of info~ for more information.

  • The length of the sample is then sent to a / (division) object, which in this case divides the length by 8. In this case each soundfile is eight beats long, but you can change the divisor using the number box above. The resulting figure is then put into a value object (v for short) - effectively this is a variable called beattime which can then be used elsewhere in the patch.

  • Loadbang and functional presets.

The Task

  • The key to this task is the examination of soundfiles. You need to load a soundfile into a buffer~ object, find out its duration and then play back portions of the soundfile based on length. You may also read the file directly with sfplay~. Above is one version of how you might go about this.

  • You should now be able to use this information to drive an sfplay~, groove~ or index~ object (the latter allows sample by sample editing).

  • Using one of these objects create a patch that allows control over the cutting of these beats. At its simplest, contruct a patch which allows the user to choose which beat is played. This could then be looped.

  • You should also try automating the procedure: allow a random or urn object to control which beat is chosen.

  • With groove~ you would need to set the start and end loop points.

  • With sfplay~ you would set cues (see preloading and jumping in the sfplay~ help file).

  • With index~ you can deal with things on a sample by sample basis. Use count~ to loop through specific sectors of the buffer.

  • For extra points you could try more than one of these methods.

  • Think about how you might generate 'fills' and 'rolls' and try to implement them.

  • Make a demo recording of your patch working. Please keep the size down to a minimum (maximum duration approximately 10 seconds). Use adoutput~ for the easiest way of doing this:

    record a demo

  • Please ensure that, in as far as you are able, your patches work immediately they are opened. If your patch or patches use audio files, include short samples that are 'preloaded', (but also include methods for loading user samples, too). Include functioning presets.

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

Finally

  • Compress (zip) your patches, demos, etc. into one file called your_student_number_"breakbeat" (e.g. 0504335_breakbeat.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 Thursday 15th December 2011

You might also be interested in:

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.