Importing and Exporting Packages

With the release of the 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.

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

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.

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).

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.

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.

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.

• graph-TunedKS-rnbo-1.4.3.rnbopack

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, and they don't match the exact version you have, 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. We do warn you before overwriting content.
• 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.4 we don't have a way to batch re-compile the content with a future RNBO version. But with RNBO 1.4.4 and later we strive to be "major.minor" forward compatible, so if you export a package on 1.4.4, you should be able to load it on a runner running RNBO 1.4.5 or any RNBO before 1.5.0.