SevenUp Live is an application written for the monome and Ableton Live's MaxForLive that places 7 unique pieces of functionality into any number of 8x8 grids. With it, your monome is fully integrated into your Ableton workflow, allowing you to sequence beats, chop up loops, record melodies, and send control signals. Each SevenUp component is represented as a device in Live that retains all of Live's native functionality like preset saving/loading and automation.

Check out some videos to see what you can do with SevenUp.

If you're looking for SevenUp 1.0 which launched as a separate Java application and does not require MaxForLive, you can find it here.


In order to use SevenUp Live you'll need:

  • One or more monomes (any models will do)
  • Ableton Live 8.2.2 or greater with MaxForLive installed
  • Max 5 or 6 installed
  • SerialOSC installed and running. Be sure to follow the instructions and install all necessary prerequisites. The zeroconf MAX external must be installed for your monome to be discovered.
  • Java Runtime Environment 1.5 or greater (most people will have this installed already)

Download and Installation

Download the latest version (2.0.5d) of 7up .


  1. Unzip the package to a directory of your choosing
  2. Copy all the files in the "Supporting" folder into Max's ".../java/lib" folder. If you are upgrading your instance of SevenUp, be sure to clear out any existing SevenUp .jar files first.
    • For Windows this will be C:\Program Files\Cycling '74\Max 6.0\Cycling '74\java\lib
    • For Mac this will be /Applications/Max6/Cycling '74/java/lib
  3. Install the included Live pack "SevenUp 2.0.5 Template.alp" by opening Ableton Live and choosing "Install Live Pack..." from the file menu. 
  4. Open the newly installed project, SevenUp 2.0.5 Template.als, navigate to File -> Manage Files....  You should now see a column on the right with some options.   Press "Manage Project" and then the "Export" button which is located at the bottom.  This is important in order to install the SevenUp presets and devices into your device library.
    • If you are upgrading your installation, as opposed to installing from scratch, delete your existing "SevenUp" folders under "Max Instruments" and "Max Effects" first before exporting.

Getting Started

Now that you've exported the SevenUp devices, samples, and presets into your library, you can add SevenUp into any new or existing project.  Open up a new project and we'll walk through creating a basic set.

  1. Open Ableton Live, open your device list and navigate to Instruments -> Max Instrument -> SevenUp and drag the SevenUpCore device into a new track.
    • This is the brain of 7up and should always be loaded first before any other SevenUp components.  Only load one "SevenUpCore" into any set at a time.
  2. You should now see the following in your device chain:
  3. Choose the monome you would like to connect to from the drop-down and press "Connect"
  4. Once your monme is listed as "Connected", press the "Start/Stop" button to enable 7up on the monome.  You should see the monome light up at this point.
  5. Next, we'll try using a simple component, the Stepper. The Stepper allows you to create patterns of samples, typically beats.
  6. In order to do this, Navigate to Devices -> Instruments -> Drum Rack -> SevenUp -> "Stepper Drum Rack" and drag it into a new track.
  7. Next, navigate to Devices -> Midi Effects -> Max Midi Effect -> SevenUp -> Stepper and drag it in front of the "Stepper Drum Rack".
  8. Press play and you should notice that the rows of your monome are blinking in time with Ableton.
  9. Try pressing the buttons of the *first 7 columns* of the monome and notice that they'll each play a corresponding sample in the drum rack. You should be able to hear sound at this point and your setup should now look something like this:

Great! Now you're using 7up Live.  Read on to learn more about navigating through 7up and using the remaining components.

SevenUp Concepts

0. Navigation

Learning how to navigate through SevenUp is simple as soon as you understand that the right-most column of any 8x8 grid is *always* a navigation column that allows you to enter into different modes of SevenUp.  There will be at most 1 solid light in that column and it's location designates which mode you're in.  Blinking lights in that column indicate sub-functions specific to that mode.  In order to change from one mode to another, simply press the solid light once, and then choose a different mode to enter.

It's also important to know how to navigate throught the components in Ableton Live.  The important thing to know is that the SevenUp component that you dragged in first is the "Core".  All other components communicate through it.  In some cases, components are configured entirely from the core, in other cases, components are configured from their individual interface.

1. Stepper

Nav Position
MaxForLive Component? Yes
Saves with Presets Nothing
Saves with Patches Patterns

The stepper is the first mode that you enter after initializing SevenUp. It's purpose is to sequence patterns of samples to be triggered.  Once you've laid out a group of samples to trigger, also known as a pattern, they will be triggered from top to bottom in time with Ableton's transport.  You have the ability to store up to 7 different patterns by clicking on any sub-menu in the nav menu (sub-menu buttons are those that are NOT solid in the nav menu).  The layout of the stepper interface is shown below:

In order to add a stepper to your set, make sure you have already added the SevenUp Core to your set (see the "Getting Started" section) and follow these instructions:

  1. Navigate to Devices -> Instruments -> Drum Rack -> SevenUp -> Stepper Drum Rack and drag it into a new track.
  2. Next, navigate to Devices -> Midi Effects -> Max Midi Effect -> SevenUp -> Stepper and drag it in front of the "Stepper Drum Rack".
  3. Press play and you should notice that the rows of your monome are blinking in time with Ableton.
  4. Try pressing the buttons of the *first 7 columns* of the monome and notice that they'll each play a corresponding sample in the drum rack (Notes C3-F#4)

Additional  Notes:

  • You can copy 1 pattern to another by holding down the first pattern and then pressing another pattern. 
  • You can clear a pattern by holding down that pattern's button for 3 seconds. 
  • When you press a sample trigger, it will first be flashing to indicate low velocity, pressing it again will make it solid to indicate a high velocity.
  • Tip: Try placing a "Pitch" or "Chord" midi effect after the stepper. Now you can add samples to additional slots in the drum rack and trigger them using the same Stepper.

Patterns stored in the Stepper are meant to be sequenced using Sequencer mode which is explained next.

2. Sequencer

Nav Position 2
MaxForLive Component? No
Saves with Presets n/a
Saves with Patches Sequences of Patterns

The Sequencer allows you to sequence groups of patterns.  This is helpful in order to break up the repetetiveness of an 8-step pattern.  In this mode, each column on the left-side corresponds to one of the seven possible patterns.  Each row then corresponds to playing one measure of that pattern.  The diagram below shows a sequence that plays: Pattern 1, Pattern 2, Pattern 1, Pattern 3, Pattern 1, Pattern 2, Pattern 1, Pattern 4.

This mode does not have a corresponding MaxForLive component and is simply controlled using the second mode of SevenUp. Your arrangements of sequences will be stored in SevenUp patches but NOT in SevenUp presets.

Additional notes about the sequencer:

  • You can trigger individual banks of sequences from the Masterizer mode
  • You can trigger an individual pattern row to play by pressing it's solid button in the left area

3. Controller

Nav Position
MaxForLive Component? Yes
Saves with Presets Nothing
Saves with Patches Nothing
Alternate Components RackMacroController

The Controller allows you to MIDI map 7 banks of 7 sliders to various knobs in Ableton for a grand total of 49 unique sliders. When used in conjunction with the "Tilt" tab of the SevenUp Core component and the SevenUpADCController component, the monome's ADC ports and accelerometer can be used to control knobs as well. While in the Masterizer mode, you can re-trigger the banks of controllers that you have positioned.

In order to use the controller you'll need to do the following:

  1. Open Ableton Live's MIDI preferences for a single virtual midi device, enable its "Track" output and its "Remote" input ONLY. An example is shown below:
  2. Navigate to Devices -> Midi Effects -> Max Midi Effect -> SevenUp -> Controller and drag it into a new track.
  3. Navigate to Devices -> Instruments -> External Instrument and drag it into the same track and select the MIDI device from step 1. At this point your device chain should look like this:
  4. Enter "MIDI" mode by clicking the "MIDI" icon in the top right.  Select a knob, slider, or button and press a control slider on your monome.  You should notice that the parameter is mapped to a MIDI control.

Tilt Control

If your monome has an accelerometer, you can use the values being sent over the ADC ports in order to control knobs in Ableton. In order to do this:

  1. Make sure that you have your ADC ports enabled in monomeserial
  2. Navigate to the "Tilt" tab in the SevenUp Core component and click the "Calibrate" button.
  3. On the monome, navigate to "Controller" mode (nav slot 3). In order to send ADC or Accelerometer values, you must hold down a sub-nav button while in Controller mode (the ones that are blinking quickly in the right column) you should see the tilt sliders move in SevenUp Core. Depending on which sub-nav button you hold down, different MIDI control values will be sent.
  4. In order to get a full range of motion, tilt your monome 360 degrees on both the X and Y axis so that SevenUp can learn where the min and max values lie.
  5. Once you've finished calibration, click the "On" button.
  6. In order to send these values to knobs in Ableton, the process is very similar to the steps above for the normal controller except you'll want to use a new MIDI channel so that the control values don't conflict with the normal controller. Drag an SevenUpADCController component into a new track, then add an external instrument, then send select a virtual midi device with which to receive midi signals. See the steps above for more detail.

Additional notes about the controller:

  • You are able to push out the current values in a single bank from the Masterizer
  • By default, when using tilt it may be difficult to MIDI map the X axis and Y axis independently because their values are sent at the same time. You can mute one axis at a time in monomeserial by unchecking it's ADC port.

4. Looper

Nav Position 4
MaxForLive Component? Yes
Saves with Presets Loop length, loop type
Saves with Patches No

The looper mode allows you to play up to 7 different loops at any offset.  This allows you to chop up loops similar to MLR.  Each column on the left hand side corresponds to a loop. If you press any row in a loop column, the loop will play at that offset. Each column also has a corresponding row in the right nav column which can also be used to start and stop the loop.

It's important to understand that loops loaded into the looper must already match your BPM (which may require consolidating a loop). Also, because SevenUp has no way of knowing how long your loop in Ableton is, you must use the Looper interface to assign each loop's length measured by bars.

In order to use the loop, follow these steps:

  1. Navigate to Devices -> Instruments -> Drum Rack -> SevenUp -> Looper and drag it into a new track
  2. Navigate to Devices -> Midi Effects -> Max Effect -> SevenUp -> SevenUpLooper and drag it into the same track before the drum rack.  Your device chain should now look like this:
  3. Notice that when you turn the knobs on the looper device, the macro knobs of the drum rack also move and change the "Start Offset" knobs of the individual Simpler devices held within.  By pressing different rows and columns on the monome, you'll be starting different loops at different offsets respectively.
    • Please note that because the loops provided in the preset were consolidated at 70bpm, they will only sound correct at 70 (or 140) bpm.

Additional notes about the Looper:

  • In order to change the loop mode and loop length of the Looper while in "Slave" mode, you'll need to navigate to the SevenUpLive core and click on the "Looper" tab:
  • The master/slave button is covered in the "advanced topics" section.  It's recommended that you leave it in "Slave" mode if you are just starting with SevenUp
  • The interface gives you the option to add loops to different choke groups. Only 1 loop in a particular choke group can be playing at once. For instance if loops 2 and 3 are both part of choke group 1, playing loop 2 will stop loop 3 and vice versa.

Loop Modes

Each of the 7 loops may be played in one of five different loop modes: Loop, Shot, Momentary, Hit, and Slice:

  • Loop - Triggers the loop once wherever the button is pressed.  When a loop reaches the end, it will start back from the beginning automatically.
  • Step - At every step, the loop will be re-triggered at the cooresponding offset.  When the loop reaches the end, it will start from the beginning.
  • Shot - When a loop reaches the end, it will stop
  • Momentary - The loop is only played while you continue to hold down the button
  • Hit - When used with the Sampler (as opposed to the Simpler) this can play different samples for each button
  • Slice - This will play just the section of the loop that was pressed and stop

Importing Samples into the Looper

One caveat when working with the looper is that your samples must be "consolidated" (written to disk) at the tempo you're working with before they will loop at that tempo. (Yes, we are working on solving this which is possible with M4L). This means that if you have a sample that was created at 110 BPM and a project that's at 130 BPM, in the Looper your sample will play at 110 BPM even if it plays at 130 BPM while in arrangement or session view.

In order to consolidate a sample and place it in the loop, follow these steps:

  1. Drag your sample into Ableton's session view (the horizontal one), right-click your sample and choose "Consolidate" or select it and press "Ctrl-J".
  2. Select the track with the looper and navigate to the Simpler whose sample you want to replace
  3. Drag the consolidated track into the sample window of the Simpler as shown below:

5. Loop Recorder

Nav Positionon 5
MaxForLive Component? No
Saves with Presets n/a
Saves with Patches Recorded sequences

The Loop Recorder mode allows you to record yourself playing the Looper. In order to record:

  1. Press the currently selected sub-navigation button to arm it for recording. The currently selected sub-navigation button is the on in the right-most column that is blinking quickly.
  2. Once armed, it should start blinking slowly, this means that it's ready for recording. Start playing some loops in the left 7 columns.
  3. Once finished recording, press the same sub-navigation button again to stop recording and start playing back what you recorded.

Pressing a sub-nav button while it's recorded track is playing will clear that track and arm it once again for recording.  If you want to start and stop recorded sequences without clearing them, use the Masterizer mode explainer later.

6. Melodizer 1 & 2

Nav Positionon 6 & 7
MaxForLive Component? Yes
Saves with Presets Slot #
Saves with Patches Recorded sequences

The Melodizer allows you to record and play sequences of melodies in any key of any scale. This is done by using the monome like a keyboard with only 7 keys moving horizontally and 6 octaves moving vertically.

The interface is split into 3 different areas: sequences, keys, and notes. The sequences are listed out vertically within the navigation column and represent banks that can hold a recorded sequence of notes. To begin recording, press the currently selected sequence once to cue, start playing your pattern, and then press again to stop and playback. The keys area at the bottom allows you to switch the key of the scale you chose in the SevenUp interface (for example D major instead of C major which is the default). Pressing within the notes area allows you to play the notes of the currently selected scale and key with each row representing a single octave.

In order to use the melodizer, follow these steps:

  1. Navigate to Devices -> MIDI Effects -> Max Effects-> SevenUp -> SevenUpMelodizer and drag it into a new track.
  2. Select "Slot 1" and "Melodizer 1" within the interface of the Melodizer
  3. Drag any instrument after the Melodizer.  Your device chain should now look like this:
  4. Check to ensure that your monome is currently using Melodizer 1 (the 6th navigation row should be solid) and that you're using sequence 1 (the 1st navigation row should be blinking quickly).
  5. Press any buttons in the top left quadrant and you should hear sound coming out of your VST or instrument.  If you want to record these notes, first press your sequence slot to cue it and then press it again when you want to stop recording.
  6. In order to change the current scale, recording mode, and other options, navigate to where you placed the SevenUpLive core device and click the "Melodizer 1" tab:

The SevenUpLive core interface provides a number of options for how you want the Melodizer to record and play back sequences.  These are covered in the "Advanced Concepts" section.

7. Clip Launcher

Nav Positionon
MaxForLive Component? Yes
Saves with Presets Nothing
Saves with Patches Recorded sequences

The SevenUp Clip Launcher component allows you to launch clips with your monome and receive feedback on the state of your clips as either cued, stopped, or playing. "Clip mode" is only available for Melodizer1 and there can be only 1 "ClipLaunch" component in your set, otherwise they will conflict with each other. By dropping it into your set, Melodizer 1 will switch to clip mode automatically.

Please note that once you drag in the Clip Launcher you should first remove any Melodizer 1 components or turn them off. Also, if you have recorded patterns in Melodizer 1, these notes will fire clips now instead of playing notes.

In order to start using the Clip Launcher:

  1. Navigate to Devices -> Midi Effects -> Max Effects -> SevenUp -> Clip Launcher and drag it into a new Midi Track
    • This should switch Melodizer 1 into CLIP mode automatically. Go to the Melodizer1 tab pane in SevenUpLive core to make sure that the Toolmode is set to "Clip".
  2. Switch your current mode to Melodizer 1 (6th row in nav column).  When the active pattern slot (the fast blinking pad in the nav column) is 1, then you are viewing tracks 1-6 as columns, and clips/scenes 1-7 as rows.
    • The bottom-most row of the pads is used to stop clips in each track column, except for the bottom pad of the 7th column which is used to stop all clips.
    • The 7th column from left is used to trigger scenes 1-7.
  3. If you were to move to the second pattern slot in the navigation column, you'd be working with Tracks 1-6 and Scenes 8-14.  It all breaks down like this:
    • Pattern Slot Tracks Scenes
      1 1-6 1-7
      2 1-6 8-14
      3 1-6  15-21
      4 7-12 1-7
      5 7-12 8-14
      6 7-12 15-21
      7 n/a (reserved) n/a (reserved)
  4. Now make sure you have pattern slot 1 selected and drag an audio or midi clip the first track and first scene of your set.
  5. After a few seconds, you should see the clip positions reflected on the monome.  Idle clips are shown on the monome blinking quickly, cued clips blink slowly, and playing clips are solid.  If you press the pad on the monome representing your clip, it should play. If you press the pad at the very bottom of the column, it should stop the clip.
  6. Now if you add 2 more clips to tracks 2 and 3, you should see 3 lights on your monome.  By pressing the first row of the 7th column, you can launch the entire scene, thus playing all 3 clips at once.
  7. By pressing on a blinking pattern slot, you can cue the Clip Launcher to record your button presses just as you would with the Melodizers or the Loop Recorder.

Please note that it's recommended you turn the Clip Launcher power button OFF to stop polling for new clip positions when it's not necessary in order to save on processing time.

8. Masterizer

Nav Positionon
MaxForLive Component? No
Saves with Presets Nothing
Saves with Patches Nothing

The purpose of the masterizer is to provide an interface where you can control what is going on in each of the other modes.  It's for this reason that the Masterizer interface is the least intuitive.  The left side of the Masterizer mode uses each column to control another mode as such:

  • Column 1:
    • This column shows the current sequence that is playing.  You can change sequences by pressing a button in this column.  Notice that the sequence waits for the current pattern to finish before changing
    • This column allows you to trigger control banks 1-7.  Any control bank that has values set will show as flashing.
  • Column 3:
    • This column allows you to start or stop loops.
  • Column 4:
    • This column allows you to start or stop looprecorder sequences
  • Column 5:
    • This column allows you to enable or disable melodizer 1 sequences.  If there is a recorded sequence, it will show up as a flashing light.
  • Column 6:
    • Same as column 5 but for melodizer 2.
  • Column 7:
    • This column displays the current location of the Ableton Live track.  This is useful when using effects that rely on the position of the Live song.
  • Column 8:
    • The sub-nav buttons of the Masterizer send MIDI notes C4-G4 on Channel 8 in order to allow transport control.  For instance, the top most button could be mapped to "Play", the second button to "Stop", and the 3rd button to "Locator 1".  Each of these buttons must be pressed TWICE to activate.  This is to prevent accidentally pressing transport buttons which could potentially make a big mess out of a performance. Because there is no Masterizer component itself, these notes are sent through the Controller


Saving Patches and Presets

Patches and presets are two ways of storing information about your SevenUp Live set and it's important to understand the difference between them.

Presets - Presets are a pre-existing concept in Ableton Live that allow you to store the current configuration of a device into your project library.  Presets store things like the current drop-down options of a device, or the positions of its knobs.  In order to store a preset, click on the "Save" icon in the top right of any Ableton or SevenUp device.  Presets, however, do NOT store things like the patterns of sequences you recorded in SevenUp, that's why we need patches.

Patches - Patches are XML files that you can save on your hard disk in order to save and load SevenUp information like Melodzier and Loop Recorder sequences.  In order to save a patch, navigate to the SevenUp Live core, click the "Patches" tab, press the "Save Patch" button, and choose a location on your hard drive to save your patch.  Loading patches is handled in a similar fashion:

Additional notes about patches and presets:

  • If you have previously saved a patch in SevenUpCore...then you save the core as a preset...the preset will load that patch everytime you load it.


If the tips below don't solve your problem, try the Monome forums

Basic Troubleshooting

The best way to trouble-shoot 7up devices is to look at the Max output which can be accessed by right-clicking in title bar of SevenUpCore and choose "Open MAX Window". Here you will see if the 7up Java libraries have not been installed correctly or if you're missing key SerialOSC components.

MIDI Mapping tilt control

When mapping tilt, 7up will send multiple CC values at once which can cause the wrong CC to be mapped to your knob/button of choice. Ableton will map to the last CC message it sees, but you can go back to a previous CC by using the "UNDO" (Command-z) to go back through the mappings till you get to the right one.

My loop(s) always play at the same start point no matter where I press on the monome

Loops are triggered at different points because the Looper component controls the macro knobs of the drum rack after it which in turn controls the start offset knobs of the Simplers in the drum rack. If any of the links in this chain become broken, the start offset knobs of your Simplers will stop responding and your loops will always play at the same point. This is fairly simple to fix. If you move your Looper knobs and the Drum Rack macro knobs don't move...

  • This may be the case if you either dropped the Looper into the track before you dropped the Drum Rack into the track or if you deleted the Drum Rack and created a new one. To fix this, simply delete the Looper and drag in a new one.
  • If you move your Drum Rack macro knobs and your Simpler start offset knobs don't move...
    • This may be the case if you replaced one of the Simplers entirely rather than replacing just the sample inside of it or if you didn't use the provided Drum Rack preset. The start offset knobs are controlled using maco mapping, so to fix this simply right click on each Simpler's start knob in order and choose "Map to macro 1", "Map to macro 2", etc. *IMPORTANT* once this is done, you'll need to click the "Map Mode" button on the Drum Rack, go to the "Macro Mappings" window on the left and change each of the "Max" values that you just mapped to "99.2%". Crazy right?
  • Alternate Components

    SevenUp components are modular and extensible. This means that they can be interchanged with components created by us and others in order to extend or radically alter SevenUp's functionality. This documents components outside of the standard set mentioned above.

    Controller - Rack Macro Controller (Audio and Midi)

    The rack macro controllers are alternate controllers that make it easy to map 7up Controller sliders to the macro knobs of a drum rack or instrument rack. In order to use them, simply drag them immediately before the drum rack or instrument rack.

    The MIDI version will drag into a MIDI track and the audio version will drag into an audio track.


    This device allows users to create an instance of 7up that connects using MonomeSerial which has been deprecated in favor of SerialOSC. However, one advantage of using MonomeSerial is that you can trick 7up into thinkin that it is connecting to 1 monome when you have multiple monomes plugged in. For more details, see Using Multiple Monomes


    Provides support for the Snyderphonics Manta. Must have a v2 Manta with dual color leds. Choose mantav2 from SevenUpCoreClassic pick list. Must drop Manta7up.amxd into your Live set somewhere. Choose "connect" to connect to the Manta first before starting 7up.

    Using Multiple Monomes


    When using SevenUpCore with SerialOSC, you can use the Griddle app to merge multiple physical monomes into a single virtual monome.


    When using SevenUpClassic with MonomeSerial, you can manipulate the start offsets of your monomes in order, for example, to turn two Monome 64's into a single 128. In this fashion, 1 monome 64 could be looking at the Stepper while another could be looking at the Controller.

    In order to set this specific example up:

    1. Plug all monomes you plan on using into your computer
    2. Open MonomeSerial and configure the "Starting Column" and "Starting Row" of each monome to be unique and consecutive.  For instance, if you have 2 64's, set the first's start column/row to 0/0 and the second's to 0/8.  This way, they can be uniquely addressed by SevenUp
    3. Start Ableton Live, load in the SevenUpLive core, and before you press start/stop connections, choose "Monome128V" from the monome virtual grid size dropdown.
      1. In this case we use 128V (which stands for vertical) because we set the start *row* of the second 64 to 8.  If we had set the start *column* to 8 instead, we could have selected "Monome128H" (horizontal).
    4. Press "Start/Stop Connections" and you should see the blinking 7 appears on both monomes

    Different combinations of monomes and monome types can be used with SevenUp.

    Change Log

    • 2.0 - 11/29/2009 - Initial release of 2.0
    • 2.0.1 - 12/02/2009 - Fixed timing issue causing double-hits when pressing play. Fixed offset issue when playing sequences in loop recorder.
    • 2.0.2 - 12/16/2009 - Bug fixes to loop recorder. Added MindShuffler component.
    • 2.0.3 - 1/2/2010 - Tilt support added. Bug fixes to looper. Optional use of midi clock notes to drive SevenUp's clock which allows users to use groove.
    • 2.0.4 - 1/24/2010 - Improved MIDI communication with Max 5.1.2. Added auto-configure option which works with monoroute
    • 2.0.5 - 2/27/2012 -
      • Added Max 6 support
      • Split out SevenUpCore and SevenUpClassic. Classic uses MonomeSerial while Core uses SerialOSC. Core is recommended.
      • Added velocity support to melodizers
      • Multi-level LED support for v2 monomes
      • Added tilt support for SerialOSC
      • Added Manta Support. Must have a v2 Manta with dual color leds. Choose mantav2 from SevenUpCoreClassic pick list. Must drop Manta7up.amxd into your Live set somewhere. Choose "connect" to connect to the Manta first before starting 7up.
      • Changed clip launcher to use solid for stopped clips rather than blinking
      • Fixed tilt support for gs128
      • Fixed loop recorder bug where choke group interactions were not being properly recorded.
      • Fixed SevenUpCoreClass host/listen port configuration did not allow for ports above 9999. Now can go up to 400000.
      • Fixed clip launcher being a resource hog by not polling anymore but using observers instead.


    Source code is available here:

    For technical support, your best option is to post on the Monome forums