Learn Importing and Exporting Packages

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

Importing and Exporting Packages

How to share the state of RNBO Move Takeover as a package that anyone can import

With the release of Move Takeover 0.0.1-beta.23 which includes an Updated Web Interface, you can now share your graphs and patchers, along with their dependencies.

Package Export

To export a package, open the RNBO Web Interface and navigate to the Manage Resources area.

01-graphs.png


From here you click on the menu drop down at the right side of either a Graph or Patcher and click Download.

02-download.png

This will prompt you to download a .rnbopack file, save that somewhere on your computer. This file can then be used to do Package Import.

Package Import

As with Exporting, detailed above, importing happens from the Manage Resources area.

When you're in Manage Resources, you should see an Upload button in the upper right hand corner. From there you should select Upload Package.

03-import.png

If you click that button you should see a dialog that asks you to either drag a file or click to choose (via a file browser).

04-drag.png

Select or drag a .rnbopack file there and you should see another dialog that indicates what is in the package and potentially any conflicts that you might have (see the Notes about Conflicts below). FYI, currently chrome fails on drag and drop so you'll have to use the file chooser instead.

05-configure.png

You can click Cancel to abort the installation or Upload to send the package to the runner and install it. If you upload and everything works as expected, you should see a status screen that eventually indicates success.

06-success.png

At this point you should have the packaged resources available for your use, you can load a graph or patcher that was contained in the package.

Example

The .rnbopack below is an example package that you can try uploading. It contains a graph that has a few patchers in it that let you play a Karplus Strong synth tuned with Scala. It visualizes the tuning and your playing on the pads.

Notes

  • Conflicts - at this point we don't have any sort of conflict resolution strategy. If you install a package that have patchers, graphs, soundfiles that have the same names as those that already exist on your device they will be overwritten when you install the package. We hope to provide alternative solutions in the future but in the mean time, take care. One thing you can do is cancel out of the installation and rename your patchers and graphs, then upload again. We don't have a solution for datafiles yet though.
  • Package Contents - When you export a Package we collect all the dependencies for that resource that you're downloading. In the future we may make this more configurable. These dependencies include:
    • Presets (Graph and Patcher)
    • Patchers
      • The compiled binary libraries but also the .rnbopat and configuration data.
    • Graphs
    • Data Files referenced by your patchers and/or presets
  • Versioning - We don't have a way to migrate a package at this point. So if you export a package with a runner that is running RNBO 1.4.3 you cannot expect to install that on a runner running 1.4.4 etc. You have to go back to the original source device, upgrade it, migrate its data and then re-export. We hope to improve this in the
    future.