Questions: Max/MSP and Pure Data

Question 1

What is the fundamental difference between a Max MSP audio-rate object (denoted with ~) and a control-rate message object?

• A. Audio-rate objects process at the sample rate (e.g., 44,100 operations per second); message objects operate at a lower control rate for event-based logic
• B. Audio-rate objects can only process sounds; message objects can process MIDI and audio equally
• C. The tilde (~) indicates the object is more expensive and should be used sparingly
• D. Message objects operate faster than audio-rate objects

Answer: (A)

In Max/MSP, the tilde (~) suffix marks audio-rate signal processing objects that operate every sample. Message/control-rate objects fire at intervals or in response to events — suitable for MIDI, parameter control, and logic, but not audio sample-by-sample processing.

Question 2

True or false: Pure Data (Pd) and Max/MSP share the same conceptual architecture because they were created by the same developer.

• T. True
• F. False

Answer: True

Miller Puckette created Max at IRCAM in the 1980s, then created Pure Data as a free, open-source reimplementation of the same dataflow concept. Both share the patching paradigm, object types, and fundamental signal/control architecture, though their syntax and GUI differ.

Question 3

What is the pfft~ object in Max/MSP, and what does it enable?

Model answer: pfft~ implements a phase vocoder framework — it divides the audio into overlapping FFT frames, applies user-defined spectral processing inside the sub-patch, and reconstructs the audio. This enables operations on individual frequency bins: spectral freezing, convolution, pitch-shifting, spectral morphing.

The phase vocoder works in the frequency domain. pfft~ handles the analysis (FFT), frame management, and synthesis (IFFT), leaving the per-bin processing to the user's sub-patch. This makes spectral audio manipulation accessible without implementing FFT infrastructure from scratch.

Question 4

A composer wants to build a generative music system that produces note events based on probability tables that change in response to external sensor data. Which approach in Max/MSP best supports this?

• A. Use a static audio file with the probability tables pre-encoded as amplitude values
• B. Use message-rate objects (table, prob, uzi, metro) for the generative logic and connect to MIDI or audio synthesis objects via control-to-audio conversion
• C. Write the probability logic in a VST plugin and host it inside Max
• D. Max/MSP cannot process sensor data — use Pure Data instead

Answer: (B)

Generative logic (probability, randomness, Markov chains, timing) operates at control rate in Max/MSP, using message objects. The control-rate output triggers notes or parameter changes in audio-rate synthesizers via conversion objects. Sensor data (OSC, serial) arrives as message-rate data and integrates naturally.