Description

mp.pstoInterface is a bpatcher designed to speed up your interactions with pattrstorage. Quickly generate presets, name them meaningfully, create new preset files. Also, be sure that every change is saved to disk immediately.

Instructions

Give mp.pstoInterface a filepath and you’ll be certain that the preset you’re writing to is saved where you want it.

Designed for use as a bpatcher. Download mp.pstointerface.

mp.adstatus~ turns the DAC~ on and off, delivers a reading of the CPU usage, gives the user options to choose sample rate, input device and sound card and helps to avoid clicks when turning the DAC~ on and off.

Instructions

You’ll probably find it most useful to put this at the top level of your patch and connect the left outlet to a *~ before you hit your dac~, this way you’ll not have clicks when you turn the DAC~ on and off. If you’re going to make a standalone app, this will be very useful because you can quickly change audio card use. The patch is reliant on mp.key, mp.quickfade, and mp.assignment2, all available from this site.

Download here; sd.caad.ed.ac.uk/maxhelp/wp-content/uploads/2011/11/mp.adstatus.zip

Description

mp.midiinputdevices is a handy bpatcher designed to list all of the midiinput devices that are connected to your system.

Instructions

mp.midiinputdevices is pattrstorage ready so you can store the name of the specified device in your preset tree. This means, when you change midi input device, you just need to make a new preset to recall it.

Description

mp.quickfade~ is designed to make sure you’re able to fade out audio before a message is sent. It should help prevent clicks when turning sound processing structures on and off, when turning on the DAC~ or, as in the example above, remove clicks when recording into buffers or making sound files.

Instructions

Use mp.quickfade~ with a toggle. Sending a 1, ramps a signal up to 1 over your preferred number of milliseconds, it also send the 1 out of the right outlet immediately. Send mp.quickfade~ a 0 and the signal will ramp to 0 over your set number of milliseconds and then send the 0.

Description

mp.key is a handy widget for getting the keyname from the ascii value (UK keyboards only, you’ll need to modify tinpark_alphabet.txt if you want make this work for other keyboard layouts.

Instructions

Drop into places where you want to get data from your ascii keyboard. Unzip the whole lot into a place where Max can find it.  mp.key is reliant on tinpark_alphabet.txt. mp.key was designed to work with mp.assignment2 also available on this site.

Description

mp.grainwindow~ is a helpful bpatcher that gives you fast access to 16 standard window shapes.  Each window is 512 samples long. You can also draw up to four of your own buffer windows and use these as a lookup tables, sequences or quirky waveshapes. These are not saved by default when the patch closes.

Instructions

Connect the left outlet of the bpatcher to a wave~ object.  This tells the wave object which buffer to read through.  Ramp through the wave~ object with a phasor~ or other oscillator.  Wave~ interpolates between samples so even though the windows are only 512 samples long, wave~ will smooth between points at very slow rates.  Use this as a window for grains~ or as an amplitude or modulation envelope as shown in the accompanying help file.

mp-grainwindow~ < download

max-sends.pl

In Max you can just double click on a send or receive object and a little box pops up showing its partners and which patch they’re in.  But if the matching send/receive is in another patch that’s not open it doesn’t show up.

I wrote this perl script for those occasions when you’ve maybe got dozens of files and don’t know which patch the matching send/receive is in–it’s especially useful when there are several sends/receives using the same global.  Works with signal send~s too.

Instructions

See top of max-sends.pl

Description

mdeGranular~ is an external coded in C to efficiently perform time granulation of sampled sound in real-time.

Instructions

mdeGranular~  see separate webpage for details.

Description

midi-faders-js

• allows you to use your midi faders/knobs in virtual banks so you’re no longer limited to the 8 or 16 controllers on your hardware;
• maps your controllers to user-defined sends and allows you to specify meaningful labels for each controller in each bank;
• allows you to map the 0-127 MIDI numbers to any arbitrary floating-point range using, if desired, an exponential curve for more natural mapping of controller to parameter values;
• remembers the values of your faders/knobs so that shifting banks does not result in a sudden jump to remote values (you have to move the fader to its previous value before it will start sending out values again).
• allows universal faders which act the same across all banks, and linked faders that assign the same functionality of a fader in one bank to that of any fader in a different bank.

Most of the control logic is programmed in JavaScript.  See the comments at the top of midi-faders.js for a further description of what this software does and how.

Instructions

To integrate this into your own max patch you’ll probably want to put the midi-faders-js-interface patch in a bpatcher, centring the visible part on the yellow box that displays fader labels and values.  A required argument to the patch is the mapping file (see midi-faders.js comments again); you will probably want to edit the umenu names to reflect your mapping setup.

You’ll then need to replace the ld2-midi-controller object in midi-faders-js-interface with your own controller map.  The trick here is to make sure that no matter what channel/controller number your faders are actually sending, that they map to channel messages 1-16 going into the [js midi-faders.js] object.  This channel number must be sent before the 0-127 value associated with it.

Changing banks is then a matter of selecting an item from the umenu (or typing + or – to step through them).

There’s also a fake-faders patch included in this package.  This is simply an on-screen mouse-draggable set of faders that you can use to test (or perform with) when your MIDI controllers aren’t at hand.

Description

mpassignment2 is a little bpatcher that allows you to connect input devices and assign them to whatever you like. Behaves in a similar way to midi learn functions in software like Ableton or Logic. Because it is tied into the pattrstorage system, the assignment can change dynamically. This means a parameter in Max can be controlled by any input device and this can change during performance, or if you have different input devices available on different occasions, or if you decide you don’t like the mapping you originally designed, you don’t need to edit the patch just make a new preset for it.

Instructions:

Lock your patch, click on the mp.assignment2 bpatcher, it will go red. Move a fader, joystick or keyboard and the input device has been assigned.

Requires tinpark_alphabet.txt to work. This is included inside the download.