Skip to content

Example project: "Getting started with orchestration"

We have produced an example Audio Orchestrator project called "Getting started with orchestration" that shows off some of the features of the technology and the production tool. You can use this as a starting point for learning about how to use the tool.

Project overview

This example demonstrates some straightforward behaviours and the use of radio buttons as a user control. If you preview the demo in your browser, the audio will guide you through the steps required to connect an aux device and help you check that sound can be heard on the connected device. You’ll also see a set of radio button controls in action and you’ll be able to use them to switch different audio objects on and off.

In the sections below, we'll talk you through the Audio Orchestrator project for the "Getting started with orchestration" example.

Opening the project

Once you've opened Audio Orchestrator, click "Open" and navigate to the example project file Getting_started_with_orchestration.orc.

The Sequences page

You’ll land on the Sequences page and see that the demo is made up of six sequences. These independent sections of content have either one or two sequence destinations assigned (shown in brackets next to the "Sequence destinations" sections of the sequence cards). Click on the sequence destination dropdowns to view these assignments to get a feel for the user journey through the experience. You’ll see the button text associated with each sequence and the sequence destination assigned to each button.

In the sequence settings dropdowns, you’ll see that some sequences are set to loop until the listener makes a choice with the button(s) displayed on the main device throughout, while others are set to display the button(s) only at the end of a sequence, when the audio has finished playing out. In the sequence named "Connection Successful", you’ll see that the settings are set to neither loop nor wait for the listener. In this case the sequence will play a section of content then automatically move on to its destination sequence without any input from the listener.

Screenshot of the Audio Orchestrator sequences page, showing cards for the first four sequences in the "Getting started with orchestration" example project The Sequences page

The Controls page

If you move to the Controls page, you’ll see there is a radio buttons control named "Select to switch instrument tracks". This text is displayed to the listener along with the options you set up—in this case there are four labelled options, with the default option set to "Drums and bass". Note that this control is set to display on aux devices only, and will only be displayed to the listener while the sequence named "Radio Buttons" is playing out.

Screenshot of a controls card, showing labels for the options that the listener can select, as well as various other settings Setting up a control for switching instrument tracks

The Audio page

Moving to the Audio page, you’ll see the collection of audio files that have been imported into the project as audio objects for the sequence named "Intro". You’ll also see that there are tabs for each of the sequences that were specified on the Sequences page.

If you click through each tab, you’ll see that each sequence contains a number of audio objects and that each audio object has a panning option and the two fixed behaviours. These fixed behaviours determine:

  • where each audio object is allocated based on device role i.e. whether the audio is sent to the main device, an aux device or to any device; and
  • the number of devices the audio object can be allocated to.

"Intro" sequence: panning and fixed behaviours

Looking again at the "Intro" sequence, you’ll see that there is a stereo audio file named 01_Intro_Main.wav and that its fixed behaviours are set to "Main device only" and "One device only", meaning that it will only ever play from the main device. In contrast, the second object 02_Intro_Aux_M.wav is a mono audio file with a panning setting you can adjust. In this case, it is panned centrally, and the fixed behaviours are set such that it will only be played from aux devices, but played from all of the aux devices that are connected.


The example project was updated with the v0.18.0 release of Audio Orchestrator to use stereo files rather than split mono files. Older versions of the example project may have mono files panned left and right rather than stereo files.


Note the naming convention that has been used when creating these audio files: the suffix "_M" has been used so that Audio Orchestrator can automatically determine that the audio object should be panned centrally. You can also use the suffixes "_L" and "_R" to specify whether an audio object should be panned fully left or fully right respectively. You can also set these manually and adjust the degree of left and right panning (click on the panning value to access the adjustment slider). See the Audio page for more information.

Screenshot of the Audio page, showing panning and fixed behaviours with various settings Panning and fixed behaviour settings in the "Intro" sequence

"Radio Buttons" sequence: using control-linked behaviours

If you click on the "Radio Buttons" tab, you’ll see that in addition to the fixed behaviours, control-linked behaviours have been authored for four of the audio objects. These behaviours determine whether an audio object plays out or not based on the actions of the listener, and have been applied to the audio files that the listener will be able to switch on and off using the radio buttons control you saw on the Controls page. If you click on one of the orange control-linked behaviours, you’ll see that each object has been set as Allowed or Prohibited according to its associated control option. For example, the audio file 9_Radio_Buttons_Aux_1.wav is a shaker instrument track; the control-linked behaviour has been set so that the audio object is allowed when the user selects the option "Shakers", and prohibited for the other three control options.

Screenshot of the settings for a control-linked behaviour, showing allowed and prohibited options for all of the linked control values Control linked behaviour applied to an object in the "Radio Buttons" sequence

The Appearance page

On the Appearance page you’ll see the title, subtitle, and introduction text that will be displayed to the user, along with the start and join button labels (in this case we are using the default button labels). You’ll also see the selected accent colour and the cover image that will appear on all devices (again, we're using the default image in this case).

Screenshot of the Appearance page, showing the various text boxes. accent colour selection, and the cover image The Appearance page

The Export page

The Export page shows the validation status for all of the settings and sequences—you should see that all of these are green. At the bottom of the page, you’ll see the options to either preview the experience or to export the project.

Screenshot of the Export page, showing valid settings and sequences, and buttons to start a preview or export the experience The Export page

Click "Start preview". Audio Orchestrator will take a short moment to prepare the project, and will then allow you to open the preview in your Internet browser to see the demo in action.

Screenshot of the Export as preview modal dialog, showing a completed progress bar, a QR code, and buttons for stopping the preview or opening it in the browser Export as preview modal dialogue

Click "Start new session" to begin, and listen to the instructions to follow along with the demo.

Three screenshots of the prototype application. The leftmost image shows the cover image, start button, and join button. The centre image shows the cover image, transport controls, and sequence destinations. The rightmost image shows the joining link, QR code, and connected devices. The previewed "Getting started with orchestration" application. Left: start a new session or join an existing one. Centre: the playing page. Right: joining instructions, also showing how many devices are connected.