MSP

This patch is an abstraction for supplying an amplitude factor to control the level of an audio signal. The output of this abstraction is intended to go to a *~ object to scale the volume of a sound. The amplitude factor is expressed in decibels, which is generally a more intuitive way to refer to the volume of a sound. The abstraction fades to the new amplitude in a specified amount of time. Perceptually, a linear fade in decibels (which yields an exponential fade in amplitude) sounds smoother than a linear fade in amplitude.

This patch records while the spacebar is held down, and starts looping when the spacebar is released. 

This example shows how you can alter the phase of a wave by milliseconds using delay~. The object mstosamps~ converts milliseconds to samples which then are smoothed by line~ to avoid clicks. (See MSP Basics Tutorial 2 for an example and explanation of linear interpolation using line~.)

Here are a few behaviors of the cycle~ object worth knowing.

The examples above show two different ways that you can trigger sound files while keeping in sync with a particular beat when the durations of the sound files are not perfect multiples of the beat duration, hence triggering the next sound file at the ending point of the current sound file results in the next sound file being started off the beat.

This example shows how to change and reset the wavetable that a cycle~ object is linked to. Sending cycle~ a message set followed by the buffer name can change its wavetable reference and the set message will reset the wavetable.

This example shows how to link waveform~ loop points and jit.qt.movie loop points. For information about QuickTime time formats, see "Appendix A of the Jitter Tutorials: QuickTime Confidential".

This example shows how to play part of a sample in Max. Simply put, to play a sound from point A to point B, nothing beats play~, you just tell it "start ". However, if you must use groove~, then you need to provide a stopping command at the right moment somehow.

To set a list of cue points in an audio file and have them played in order, use either sfplay~ (with a set of cues established by preload messages to sfplay~ or to sflist~) or buffer~ (with start messages to play~, the parameters of which are stored in a coll).

To create an inlet for a subpatch that accepts both signals and data, try using t signal. See the patch example for this implementation within the subpatcher.