Metropolis
Version 1

by Beau Sievers
http://www.beausievers.com/
beau@beausievers.com

	To run Metropolis, either open the Metropolis application or open 
"maxfiles/purplemorcellator.pat" using Max/MSP or the Max/MSP runtime. To start clicking, turn up 
the Master Level on the right and then check the on/off checkbox on the upper left.

	Metropolis has five sound generating modules. By default, a steady pulse of four clicks per bar 
is routed to module 1. To route different pulses to the modules, use the routing matrix. For 
example, clicking on the intersection of 7 clicks per bar and module 3 will route a pulse of 7 
clicks per bar to module 3.

	Each module has a purple drop-down menu listing the sounds available to that module. By 
default, each module loads all of the sounds in the "MetropolisSounds" directory. To use different 
sounds, drag and drop the folder containing your sounds from the finder on to the drop zone on any 
of the Metropolis sound generating modules.

	In addition to pulses of 1 through 19 (and 32) clicks per bar, Metropolis supports the 
definition of two simultaneous custom pulse rates. These are defined in the "Custom Ratios" 
number boxes on the upper left panel, and show up on the routing matrix as "c1" and "c2," 
respectively. The pulse rate for each custom ratio is the current milliseconds per beat value 
multiplied by the custom ratio value. For example, if the current tempo was 1000 ms per beat, and 
custom ratio 1 was set to 1.5, then a pulse rate of 1500 ms per beat would be available on the 
routing matrix at "c1."

	To turn on MIDI output, select an appropriate MIDI output device and check the "MIDI output 
on/off" box on the light purple left panel. Beneath each sound generating module lies a collection 
of MIDI output preference for that module. By default, each click generates a MIDI note with a 
note number of 60, a velocity of 100, and a duration of 250 ms on MIDI channel 1.


Quirks:

	- There is a 1 in 10000 chance that, upon opening Metropolis, two of the sound generating 
modules will be assigned the same buffer name. In the event that this happens, click the buffer 
name on one of the modules and assign a new name. This will be fixed in future versions.