Skip to content
Matthew Davidson edited this page Apr 4, 2018 · 15 revisions

Gridlab Connect


Gridlab Connect devices are designed for ensemble collaboration, generally sharing 'notepool' data over UDP. Gridlab UDP Connect sets up the network configuration and is a prerequisite for any collaboration. Once the network is set up, additional devices can be used to manipulate notepool data in real time. Connect MIDI allows a MIDI controller (or MIDI clip from Live) to control the notepool. Gridlab Connect Grid allows the Grid to edit the current notepool from the Grid interface.

Gridlab Connect UDP, Gridlab Connect Grid and Gridlab Connect MIDI can safely be placed on the same MIDI track, they'll just pass though MIDI information. As a best practice for Gridlab setup, I generally prefer to have a single monome-controlled device per Live Track so I can make use of track focusing. Usually the only reason to have two monome devices on the same track is if an monome-controlled instrument or midi device is followed by an monome-controlled effects processor.

Devices that receive notepool data (but can be used without Gridlab Connect)

  • Gridlab Connect Fourths
  • Gridlab Connect Press Cafe
  • Gridlab Polygome
  • Gridlab Sequencer 16P

Compatibilty


Devices that are useable without a monome device

  • Arclab Electric Dharma Wheels-S
  • Arclab Electric Dharma Wheels-FM
  • Arclab Quad LFO
  • Gridlab Sequencer 16P
  • Gridlab Chords-S

Devices that are not multi-instance compatible

  • Gridlab StepFilter
  • Gridlab Alfred

Future Development


Grid Devices Roadmap

  • Probability Drum Machine

Arc Devices Roadmap

  • Aleatoric Gradients - rotating gradients generate notes and triggers

Arc and Grid Roadmap

  • Bartok - grid recalls notes/chords and patterns, arc provides articulation
  • 808/909 - drum machine emulation - voice in focus projects parameters to arc encoders (need to obtain an 808/909 to emulate)
  • Plane-V Sequencer
  • Architecture Sequencer
Clone this wiki locally