The decoder can be used directly within REAPER; this is achievable because tracks can be defined as having multiple channels allowing individual track components to be bussed to other tracks. Having created a track, clicking IO allows the number of Track Channels to be defined.

It helps if we understand what it is we need to acheive, conceptually, in Reaper. Below is a diagram showing what we need to do in order to implement Ambisonics encoding and decoding in Reaper (or anything else, for that matter). In the example below, there are two audio tracks and the decoder is outputting to six speakers. Notice that all audio tracks output 4 channels (this is 1st order Ambisonics), and these are sent to a group of Busses (the B-format busses). These are then passed to the decoder, which in turn, outputs the audio to the speakers. If we wanted to archive our audio, we would record the B-format Buss signals, allowing us to decode the piece to any speaker array later on.


If a multi-output ambisonic encoder is inserted as an FX element upon an audio track with multiple channels, the encoder outputs can be managed as separate components by sending to the Track Channels:


If new tracks are created to manage the b-format outputs:


The audio track outputs can then be routed to these tracks prior to sending to a decoder after making parameter adustments, such as panning.


Each of the b-format tracks can then be routed to the decoder track; for example here the X channel is illustrated:

The decoder track is setup to receive the b-format channels on the appropriate track channel inputs:


The decoder channels may then be routed:


then REAPER can output to the physical audio interface:


In this example the b-format outputs are managed as separate tracks for the sake of clarity but could easily be managed as stereo pairs and the LFE channel is filtered from the omni channel W:

PART V - Plogue Bidule