Learn Exporting to Move

Getting Started

Welcome to RNBO

Quickstart

RNBO Basics

Key Differences

Why We Made RNBO

Coding Resources

Fundamentals

Audio IO

Messages to rnbo~

Using Parameters

MIDI in RNBO

Messages and Ports

Polyphony and Voice Control

Audio Files in RNBO

Using Buffers

Using the FFT

Export Targets

Export Targets Overview

VST/AudioUnit
Max External Target
Raspberry Pi Target
Ableton Move Target

Move Intro and Setup

Using RNBO Takeover Mode

Exporting to Move

Importing and Exporting Packages

Patching for the Move

Custom User Views

The Web Export Target
The C++ Source Code Target

Code Export

Working with JavaScript
Working with C++

Special Topics

Sample Accurate Patching
Scala and Custom Tuning

RNBO and Max for Live

RNBO Raspberry Pi OSCQuery Runner

Metadata

Export Description

Raspberry Pi GPIO

Updating the RNBO Package

Exporting to Move

How to export a rnbo~ patcher to the Move

Prerequisites

⁠Exporting to Move requires RNBO 1.4.3, please install it via the Max Package Manager.

  1. Open the package manager in Max and select the RNBO package.
  2. If the version next to the install button is 1.4.3, click it to install. Otherwise:
    1. Click Show All Available Versions
    2. Click 1.4.3 to install.

Patcher Export

If this is your first export, please download the feedback synth example patcher as an example patcher. This is a slightly modified version that has internal polyphony and listens on MIDI channel 16 by default in order to integrate better with the Move. The steps below however apply to all patchers.

  1. Open the feedback-synth-internal-poly.maxpat in Max 9
    01-migrating.png

     
  2. Double click the [rnbo~] object to open the RNBO patcher
  3. From the right Toolbar click the Show Export Sidebar icon to see a list of available export targets.
    02-export-icon.png

     
  4. Note that your Move might not show up automatically. First try hitting the refresh button and waiting for a moment. If that doesn't work, you have to be add it manually to the list. To add the Move click +Add in the Devices category and enter move.local in the now shown prompt
    03-devices.png

     
  5. Once the Move is added, double click its entry in the Export Sidebar in order to open the Target Export Configuration
  6. As for the example patcher all config values are set to reasonable defaults we can directly proceed to exporting the patcher to the Move by clicking
    04-runman.png
    Run on Selected Target at the bottom of the Export Sidebar
  7. After the export completes you should be able to hear some synth sounds when you hit the pads on your Move

Difference between Running vs Exporting a Patcher

The Export Sidebar currently offers two options at the bottom to export a patcher:

  1. 05-run.png
    Run on Selected Target: export the patcher and replace the currently loaded graph on the Move with a graph that contains a single RNBO Device node of your patcher with the default connections set up so it’s ready to play and interact with
  2. 06-export.png
    Export to Selected Target: export the patcher to the Move but do not alter the currently loaded graph. This will solely add the patcher to the Move and allow you to add a RNBO Device node to the graph using the Web Interface. You can use the Post Export Reload options to reload a loaded graph and update any device instances that you've updated with your export.

Additional Resources

Exporting to the Move utilizes the general infrastructure and concept of RNBO Export Targets. For more information and details on the export configuration please refer to the documentation below: