If we are going to adjust the BPM, the adjustment we are going to make needs to represent at least this many milliseconds per MIDI clock tick (to reduce jitter).

Register a handler function f to be called whenever a MIDI aftertouch (polyphonic key pressure) message is received from the specified device, on the specified channel and note number. Any subsequent MIDI message which matches will be passed to f as its single argument.

The first MIDI input source whose device matches the device-filter (using filter-devices) will be chosen.

Register a handler function f to be called whenever a MIDI controller change message is received from the specified device, on the specified channel and controller number. Any subsequent MIDI message which matches will be passed to f as its single argument.

The first MIDI input source whose device matches the device-filter (using filter-devices) will be chosen.

Register a handler function f to be called whenever any MIDI message is received from the specified device. Any subsequent MIDI message which matches will be passed to f as its single argument.

The first MIDI input source whose device matches the device-filter (using filter-devices) will be chosen.

Add a function to be called whenever the specified device disappears from the MIDI environment. The device argument is a :midi-device map from overtone.midi representing device whose removal is of interest. The function must return quickly so as not to stall the delay of other MIDI events; lengthy operations must be performed on another thread.

Add a function to be called whenever any MIDI message is received. The function will be called with the message, and must return quickly, so as to not block delivery to other recipients.

Add a function to be called whenever a new device appears in the MIDI environment. It will be passed a single argument, the :midi-device map from overtone.midi representing the new device. It must return quickly so as not to stall the delay of other MIDI events; lengthy operations must be performed on another thread.

Register a handler function f to be called whenever a MIDI note message is received from the specified device, on the specified channel and note number. Any subsequent MIDI message which matches will be passed to f as its single argument.

The first MIDI input source whose device matches the device-filter (using filter-devices) will be chosen.

Register a handler function f to be called whenever a MIDI System Exclusive message is received from the specified device. Any subsequent MIDI message which matches will be passed to f as its single argument.

The first MIDI input source whose device matches the device-filter (using filter-devices) will be chosen.

Given a BPM, calculate the interval between MIDI clock pulses in milliseconds.

Checks whether a MIDI device was returned by the CoreMIDI4J MIDI extension.

Return true if the CoreMIDI4J MIDI extension is present.

Returns a function which implements a simple tempo-tap algorithm on the supplied metronome.

Returns the set of MIDI input ports which are currently delivering MIDI clock messages.

Returns the set of MIDI input ports which are currently delivering beat phase information in the format provided by the Afterglow Traktor controller mapping.

Returns a description of a filter used to narrow down MIDI devices, if one was supplied, or the empty string if none was.

If we are going to adjust the BPM, the adjustment must be at least this many times the standard deviation in observed clock pulse timings, so we can avoid jitter due to unstable timing.

Return only those devices matching the supplied device-filter.

The elements of devices must all be :midi-device maps as returned by overtone.midi.

If device-filter is nil or an empty string, devices is returned unfiltered. Otherwise it can be one of the following things:

• A java.util.regex.Pattern, which will be matched against each device name and description. If either match succeeds, the device will be included in the results.

• A String, which will be turned into a Pattern which matches in a case-insensitive way, as above. So if the device name or filter contains the string, ignoring case, the device will be included.

• A javax.sound.midi.MidiDevice instance, which will match only the device that it implements.

• A javax.sound.midi.MidiDevice.Info instance, which will match only the device it describes.

• A :midi-device map, which will match only itself.

• A vector of device filters, which will match any device that matches any filter.

• A function, which will be called with each device, and the device will be included if the function returns a true value.

Anything else will be converted to a string and matched as above.

Find the first MIDI input port matching the specified device-filter using filter-devices, or throw an exception if no matches can be found. The exception can be suppressed by passing a false value for the optional second argument required.

Find the first MIDI output port matching the specified device-filter using filter-devices, or throw an exception if no matches can be found. The exception can be suppressed by passing a false value for the optional second argument required.

A simple protocol for our clock sync object, allowing it to be started and stopped, and the status checked.

Report on the next MIDI control or note message received, to aid in setting up a mapping to a button, fader, or knob. Call this, then twiddle the knob, press the button, or move the fader, and see what Afterglow received. Pass a timeout in ms to control how long it will wait for a message (the default is ten seconds). This is an upper limit; if a message is received before the timeout, it will be reported immediately.

Given an interval between MIDI clock pulses in milliseconds, calculate the implied beats per minute value, to the nearest hundredth of a beat.

Return true if we seem to be running on a Mac.

Contains a filter which selects midi inputs and outputs we actually want to use. The first time the value is dereferenced, a filter appropriate to the current environment will be created, and that filter will be returned whenever the value is dereferenced again.

• If this is a Mac, and the CoreMIDI4J MIDI extension is present and working, the filter will accept only its devices.

• Otherwise, if the Humatic MMJ extension is operating (also on a Mac), the filter which will accept only MMJ’s versions of ports which it offers in parallel with the standard implementation, but will accept the standard SPI’s implementation of ports which MMJ does not offer.

• Otherwise, the filter accepts all ports.

Checks whether a MIDI device was returned by the Humatic mmj MIDI extension.

Return true if the Humatic mmj MIDI extension is present.

Make sure the MIDI input ports are open and ready to distribute events. Returns the :midi-device maps returned by overtone.midi representing the opened inputs.

Make sure the MIDI output ports are open and ready to receive events. Returns the :midi-device maps returned by overtone.midi representing the opened outputs.

Unregister a handler previously registered with add-aftertouch-mapping.

The first MIDI input source whose device matches the device-filter (using filter-devices) will be chosen.

Unregister a handler previously registered with add-control-mapping.

The first MIDI input source whose device matches the device-filter (using filter-devices) will be chosen.

Unregister a handler previously registered with add-device-mapping.

The first MIDI input source whose device matches the device-filter (using filter-devices) will be chosen.

No longer call the specified function if specified device disappears from the MIDI environment. The device argument is a :midi-device map from overtone.midi representing device whose removal is no longer of interest.

Remove a function that was being called whenever any MIDI message is received.

Stop calling the specified function to be called whenever a new device appears in the MIDI environment.

Unregister a handler previously registered with add-note-mapping.

The first MIDI input source whose device matches the device-filter (using filter-devices) will be chosen.

Unregister a handler previously registered with add-sysex-mapping.

The first MIDI input source whose device matches the device-filter (using filter-devices) will be chosen.

Checks whether two :midi-device maps seem to refer to the same device, in a slightly more efficient way than comparing the entire map.

How often should we scan for changes in the MIDI environment (devices that have been disconnected, or new devices which have connected). This is used only when CoreMIDI4J is not installed, sine CoreMIDI4J gives us proactive notification of changes to the MIDI environment. The value is in milliseconds, so the default means to check every two seconds. Changes to this value will take effect after the next scan completes.

Called either periodically to check for changes, or, if CoreMidi4J is installed, proactively in response to a reported change in the MIDI environment. Updates our notion of what MIDI devices are available, and notifies registered listeners of any changes.

Also sets up the thread used to process incoming MIDI events if that is not already running, and arranges for this function to be called as needed to keep up with future changes in the MIDI environment.

Calculate the standard deviation of a set of samples.

Returns a sync function that will cause the beats-per-minute setting of the supplied metronome to track the MIDI clock messages received from the named MIDI source. This is intended for use with afterglow.show/sync-to-external-clock.

The device-filter argument is only needed if there is more than one connected device sending MIDI clock messages when this function is invoked; it will be used to filter the eligible devices using filter-devices. An exception will be thrown if there is not exactly one matching eligible MIDI clock source.

Watches for a device that matches device-filter (using filter-devices). If it is present when this function is called, or whenever a matching device is connected in the future (as long as none already was), found-fn will be called, with no arguments. This is useful for setting up MIDI mappings to the device whenever it is present. If the device is disconnected and later reconnected, found-fn will be called again, so those bindings can be counted on to be present whenver the device is available.

If there is any cleanup that you need to perform when the device is disconnected, you can pass the optional keyword argument :lost-fn along with a function to be called (also with no arguments) whenever a device reported by found-fn has disappeared. You do not need to use :lost-fn to clean up MIDI bindings created by found-fn, because Afterglow automatically cleans up any MIDI bindings for devices which have been disconnected. But if you have your own data structures or state that you want to update, you can use :lost-fn to do that.

In order to give the newly-attached device time to stabilize before trying to send messages to it, watch-for waits for a second after it is seen before calling found-fn. If your device needs more (or less) time to stabilize, you can pass a number of milliseconds after the optional keyword argument :sleep-time to configure this delay.

The return value of watch-for is a function that you can call to cancel the watcher if you no longer need it.