
percussion (drum set) with variations in the details of the kit combined with a. GUI Patcher was the first example of a graphical approach to Max that Users today know very well. specifically Max MSP, that was unknown to me at the outset of the study. But the most important aim of Patcher was the control of objects in Max/Msp. Jonny is no longer using Nigel’s Crumar Multiman-S / Orchestrator his keyboard setup now consists exclusively of the Ondomo and his Fatar Keys SL-161. best synchro between files, according to me, would be done by global saw oscillators driving “sample scanner” units to read the “cv” files. Features Patcher was designed for an integrated system that include Max/Msp and an external midi controllable synthesizer. Its rolling table is wheeled closer to Thom’s piano for Videotape, when Jonny plays a Max/MSP drum machine patch.longer files (but still quite small, we’re talking around a 1-second file in 44100Hz for a 64 step sequence).In Live the midi out is then routed to the Live 10.1 Max DS Drum rack. For each of the receives there is a chain to turn the received Bang into a midi note using 'makenote', 'pak', 'midiformat' and finally output to Live's midiout object.

#MAX MSP DRUM MACHINE PATCH PATCH#

patching a bit messy (when 1024 is not a multiple of the sequence steps, timing of the events has to be adjusted + or - 1 “sample”).same length for every file so they could be easily be synced when read with sample players.Ĭons of the fixed total amount of samples :.Pros of the fixed total amount of samples : Using the reference material for each object thereon is adequate to help you properly hook things together.
#MAX MSP DRUM MACHINE PATCH MANUAL#
That would make the patching cleaner and would allow to create very long CV sequences (songs ?) without losing precision in timing. I read the Max manual from beginning to end just for the Max portion, not Jitter, MSP, etc. But I am thinking of having a fixed number of samples per step instead. I chose the smallest value that can be displayed on the er-301, and also, it keeps files very small. I still wonder about one important design choice : currently, regardless of the sequence length, the generated file is 1024 samples long and the data is “stretched” into it. The setup is controlled by a Max/MSP patch, which works with a combination of machine-listening techniques, timed events, and direct intervention by the. Wow, coming from you, that makes me so happy ! In all seriousness, I think the patching is a bit clumsy, but as long as it works…It’s not like it was a performance instrument.
