Learn Raspberry Pi Debug Interface

Getting Started

Welcome to RNBO

Quickstart

RNBO Basics

Key Differences

Why We Made RNBO

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
The Web Export Target
The C++ Source Code Target

Code Export

Working with JavaScript
Working with C++

Advanced

Abstractions

Transports and Synchronization

Gen in RNBO

Delays in RNBO

Max Projects and RNBO

Presets With Snapshots

Send and Receive

Working with Lists

Object Properties

Architecture

Patcher UI

RNBO Patcher Bottom Toolbar

RNBO Patcher Left Toolbar

RNBO Patcher Right Toolbar

RNBO Export Sidebar Overview

Signal Probe

Objects for Visualizing Signal Data in RNBO

Codebox

Getting Started with Codebox

Understanding Storage: let, const, @state, @param

Building a Note Controller with Codebox

Templates

Using the Audio Plugin/Desktop Application Template

Programming a Custom UI with JUCE

Using the Web Page Template

Projects

MIDI Synthesizer

MIDI Sequencer

Special Topics

Sample Accurate Patching
Scala and Custom Tuning

RNBO and Max for Live

RNBO Raspberry Pi OSCQuery Runner

Raspberry Pi Debug Interface

Metadata

Export Description

Raspberry Pi GPIO

Updating the RNBO Package

Raspberry Pi Debug Interface

The RNBO Runner on the Raspberry Pi can be controlled directly using OSCQuery, by sending messages over HTTP, UDP or WebSockets .

The OSCQuery package, which allows users to interact with the OSC namespace of RNBO patches running on the Raspberry Pi, includes an easy-to-use debug interface that can be accessed from a web browser called the rnbo-runner-panel. This debug interface exposes some of the most useful parts of the exported RNBO patcher through a simple interface.

Accessing the Debug Interface

The RNBO disk image for the Raspberry Pi includes this debug interface, and runs an HTTP server that serves the page on port 3000. The interface can be accessed using either the device hostname or IP address followed by the port number. So if your pi had the hostname c74rpi and the IP address 192.168.88.111 , then from any device on your local network you could visit http://c74rpi:3000 or http://192.168.88.1111:3000 to see this page. The Raspberry Pi configuration page in the export sidebar includes a link to the debug interface, and you can click on this link to launch the page in your default browser.

rnbo_rpi06.png

After a successful export to the Raspberry Pi, you will also see an Open Interface button that will open the debug interface in your default browser.

rnbo_rpi07.png

Purpose

The primary purpose of this page is to help debug a RNBO export once it's running on a Raspberry Pi. It provides a simple interface to most of the endpoints exposed by the RNBO Runner. The interface should automatically include any parameters, inports, and outports in your RNBO patch. Note that this interface is not really intended to be used in a performance, and is mostly a thin wrapper around a handful of API calls to the RNBO Runner.

How to find out more

The debug interface is just one way to query and control the exported patch using OSCQuery. Any application that can interface with the runner over HTTP, UDP or WebSockets can interact with the exported patch in the same way. If you wanted to build your own custom web interface, you could fork the RNBO Runner Debug Interface repository and modify it however you want. Of course, a website is just one possible interface. See the OSCQuery reference guide for more information about how to query the RNBO Runner, and how to control it.