SpatialWorkstation_Guide
SpatialWorkstation_Guide
Release 3.0
Nov 08, 2017
SPATIAL WORKSTATION USER GUIDE
1 Introduction 1
1.1 What did you download? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.2 Binaural Audio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.3 Ambisonics and B-format Audio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.4 Room Modelling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
2 Getting Started 2
2.1 Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
2.2 Setup (macOS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
2.3 Setup (Windows) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
3 Workflow 4
3.1 Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
3.2 Delivery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
3.3 Playback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
4 Components 6
4.1 FB360 Spatialiser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
4.2 FB360 Converter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
4.3 FB360 Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
4.4 FB360 Loudness . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
4.5 VR Video Player . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
6 Using Reaper 19
6.1 Project Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
6.2 Mastering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
6.3 Mixing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
6.4 Ambisonics/B-Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
6.5 Working With Video . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
6.6 Exporting/Bouncing A Mix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
7 Video Player 22
7.1 Video Format And Codec . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
7.2 Opening A Video . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
7.3 Navigating A 360 Video . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
8 Encoder 23
8.1 Encoding Assets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
8.2 Running the Encoder from the Command Line . . . . . . . . . . . . . . . . . . . . 26
v3.0
Copyright 2017 Two Big Ears Ltd.
Support, Bug Reports and Help: Support Group
1 Introduction
Thanks for downloading the FB360 Spatial Workstation. The suite consists of plugins for DAWs, a VR video player
and a cross-platform native engine that makes it easy to design and deliver content for cinematic VR and 360 video
projects. For any issues, help or bug reports, go to the support group.
Real-time binaural audio works using HRTFs (or Head Related Transfer Functions). HRTFs work by filtering an
audio signal to recreate the complex cues that help us, as humans, localise sounds. The cues are influenced by
multiple factors, including the listening environment and the shape of your body, head and ears. In reality, we move
our heads and reorient ourselves to localise sounds. We constantly try to bring sounds (or the objects that are
creating such sounds) into our line of sight to overcome the ambiguity of spatialisation. Some of the long standing
problems of binaural audio can be overcome with head tracking technology, as found on virtual and augmented
reality devices. The FB360 Spatial Workstation allows you to position sounds in 3D space within your DAW and then
export the mix into a range of formats, including Ambisonics used by popular 360 and VR video platforms and the
.tbe format which can be used with the FB360 audio engine within your app to reconstruct a full 3D audio mix based
on the user’s head orientation.
Ambisonics is a way of describing a full 3D sound field. It uses a number of interdependent audio tracks which can
be decoded into various other end-user formats for consumption, e.g. binaural or 5.1, meaning only one Ambisonic
recording or mix needs to be made for multiple different use cases. Another major feature is that an Ambisonic mix
can be dynamically decoded to incorporate the listener’s head rotation. Currently, first and second order Ambisonics
is widely in use. First order requires four channels of audio, which is often called B-format. Second order
Ambisonics requires 9 channels of audio, the extra 5 channels providing greater spatial accuracy than standard first
order. Care should be exercised as there are currently two different common channel ordering and weighting
conventions for the B-format:
1. The traditional B-format, as output by many commercial microphones, is defined using the channel ordering
and weighting proposed by Furse and Malham (often abbreviated to FuMa). We will refer to this convention as
B-format (FuMa).
2. A more extendable convention to the traditional B-format (FuMa) has been proposed, know as ambiX. This is
characterised by a different channel ordering and weighting. We will refer to this convention as B-format
(ambiX). The Spatial Workstation uses 2nd order ambiX as the output of the Spatialiser plugin and for
exporting the spatial audio mix.
Depending on how your recorded your B-format audio you may need to rotate it: see Rotating the Ambisonic field
for details.
The Ambisonic field must be defined on a set of 3D axes (X, Y, Z). For a listener at the centre of the field, the
B-format convention used is X: front to back, Y: left to right, and Z: up-down. The X, Y, Z Ambisonic channels contain
information about the sound field along the corresponding axis (they essentially represent what a figure-of-eight
microphone might pick up along that axis). The W channel can be thought of as an omni directional channel.
• B-format (FuMa) lists the channels in order: W, X, Y, Z. The W channel also has a -3 dB gain applied.
• The ambiX convention lists the channels using the Ambisonics Channel Number (ACN) ordering: W, Y, Z, X.
The channels also use SN3D normalisation (which for first order Ambisonics simply means that the four
channels have a uniform gain normalisation).
A majority of the binaural solutions only take into account HRTF measurements made in an anechoic chamber. In
reality, we listen to sounds in live environments that alter our sense of localisation. Real-time room modelling, with
binaurally spatialised reflections can overcome this. A full real-time room modelling solution can be a CPU intensive
process, but FB360 takes the best of both worlds. The room modelling algorithm in FB360 recreates only the
reflections that are essential for a convincing 3D audio experience. The room modelling algorithm in FB360
generates the first few orders of reflections inside a simple room model. This helps greatly with the externalisation of
sound sources and also improves some common binaural rendering problems such as front/back confusion and
elevation perception.
You can control the level of these reflections as well as the reflection order (i.e. the number of individual reflections
allowed in one reflection path around a room) using the sliders on the Spatialiser plugin. The size of the room being
modelled is controlled globally in the Control plugin. These early reflections can be used effectively with any of your
favourite reverberation plugins without any problems. Adding a small pre-delay to the reverb system (30-60ms)
allows the early reflections to stand out and greatly enhance the spatialisation effect.
2 Getting Started
2.1 Requirements
• Compatible DAW:
◦ Pro Tools HD 12.8.2 and later comes bundled with the current Spatial Workstation AAX plugins
- Older versions of Pro Tools require version 2.2.0 or lower of the Spatial Workstation
◦ 64 bit VST based DAW such as Reaper. 32 bit hosts are not supported.
- The VST based DAW must be able to support 9-channel tracks and buses
• macOS 10.10+ or Windows 7+ 64 bit. 32 bit operating systems are not supported.
• Ensure that the OS, DAW and graphics drivers are up to date.
• A HMD is recommended but not compulsory. The following headsets are supported:
◦ macOS: Oculus Rift DK1, Oculus Rift DK2
◦ Windows: Oculus Rift, HTC Vive
AAX
For Pro Tools HD version 12.8.2 and above the Spatial Workstation AAX installer is automatically run by the Pro
Tools HD installer. The following user files are installed:
1. AAX Plugins in Mac HD/Library/Application Support/Avid/Audio/Plug-Ins/
2. A Pro Tools HD example project in Applications/FB360 Spatial Workstation/Pro Tools HD
VST
AAX
For Pro Tools HD version 12.8.2 and above the Spatial Workstation AAX installer is automatically run by the Pro
Tools HD installer. The following user files are installed:
1. AAX Plugins in C:\Program Files\Common Files\Avid\Audio\Plug-Ins
2. A Pro Tools HD example project in C:\Program Files\FB360 Spatial Workstation\Pro Tools HD
3. Pro Tools HD template project and I/O settings in C:\Program Files\Avid\Pro Tools\Factory Content
4. A copy of this document in C:\Program Files\FB360 Spatial Workstation
Additional components need to be installed in order to use all the features of the Spatial Workstation:
1. Download and run the FB360 Spatial Workstation AAX Addon installer
(SpatialWorkstation-AAXAddon-3.0-Win64.exe)
2. The following user files are installed, depending on your choices during the installation process:
(a) VR Video Player in C:\Program Files\FB360 Spatial Workstation\Video Player
(b) Encoder app in C:\Program Files\FB360 Spatial Workstation\Encoder
VST
It is recommended that you read the information in Workflow before setting up your DAW.
For setting up a project in Pro Tools HD, see Using Pro Tools HD and for Reaper, see Using Reaper.
3 Workflow
The design stage is where you as a sound designer and mixer would spend most of your time. You will be using the
FB360 Spatialiser and Control plugins in conjunction with the VR Player to mix in binaural in real-time. The tools
have been developed to do all the heavy lifting behind the scenes so that you can focus on designing and delivering
great content to a deadline.
3.2 Delivery
This is for the final mastering and delivery of content. The mix from the DAW is encoded into a format that the
FB360 audio engine uses to reconstruct a binaural mix in real-time on the target device. All audio and metadata is
compressed into a single file format that is designed specifically for mobile and desktop devices to ensure low CPU
and memory usage. Alternatively, you can deliver your mix into other formats supported by 360 video and VR
platforms. See Encoding Assets.
3.3 Playback
Depending on the output format, your mix can be deployed to popular 360 video and VR platforms or with a VR app
using the FB360 Audio Engine integrated. The FB360 Audio Engine is cross-platform and works with both native
apps and game engines.
The FB360 Spatialiser plugin replaces the conventional DAW panner to give you full 3D positioning, distance
attenuation and room modelling parameters. It must be the last plugin inserted on the audio channel. All audio
processing (such as compression and equalisation) must happen before it. All channels with the Spatialiser plugin
must be routed to an aux channel which has the FB360 Control plugin instantiated on it.
Parameters
• Input: The channels or format used for processing. In Pro Tools, the available options depend on the number
of channels supported by the track (e.g. a stereo track will let you choose Left, Right, Mixdown or Stereo but
you cannot select other options which require a higher channel count).
◦ Left: The left channel is used for processing
◦ Right: The right channel is used for processing
◦ Mixdown: A mono-mixdown of both channels is used for processing
◦ B-Format (FuMa): For processing pre-recorded 4 channel, 1st order Ambisonics material in the
Furse/Malham B-format. This is the channel configuration output by Soundfield microphones. See
Ambisonics and B-format Audio for more information.
- Source Roll: (visible only with B-Format input) Tilt the B-Format recording (like tilting your head from
side to side).
- Source Pitch: (visible only with B-Format input) Rotate the B-Format recording in the vertical plane or
up-down. A positive value is up, while a negative value is down.
- Source Yaw: (visible only with B-Format input) Rotate the B-Format recording in the horizontal plane
or left-right. A positive value is right, while a negative value is left.
- Envelopment: (visible only with B-Format input) Control the diffuse field of the sound.
The Spatialiser plugin includes an equirect video panner (top-right of the plugin) and a 2D panner (bottom-right of
the plugin). Both panners can be used simultaneously to accurately position sounds in 3D space.
The equirect panner mirrors what is displayed in the FB360 Video Player. When a video is loaded in the FB360
Video Player, it will be automatically shown in the equirect panner.
Typically most 360 videos are stored in an equirectangular projection (similar to how panoramic photos are saved).
This is a “flattened” projection of a 360 video where typically the horizontal axis maps to azimuth and the vertical
axis maps to elevation, with the centre of the scene at the centre of the equirect display.
The 2D panner on the other hand shows a top-down view of the scene. While the equirect panner does not show
distance, the 2D panner can be used to automate distance effects. The centre of the 2D panner is where the
camera is in the scene.
Toolbar And Key Commands
The toolbar to the right of the equirect panner has the following options:
• Toggle Size: The size of the plugin can be toggled to show a larger view. This is useful for more precise
panning. Key Command: S.
• Opacity: The equirect panner draws a darkened overlay of the video to help make the sound objects more
visible. The opacity of this overlay can be controlled with the Opacity slider.
• Grid: The grid overlay can be toggled on and off. Key Command: G.
The toolbar to the right of the 2D panner has the following options:
• Zoom In/Out: The top-down view can be thought of as a map. The zoom buttons can be used to zoom in and
out.
• Grid: The grid overlay can be toggled on and off. Key Command: G.
• Arrange: When working with multichannel material, the Arrange button can be used to arrange the sound
sources as virtual speakers.
When an Ambisonic input format is selected, the FB360 Spatialiser plugin includes sliders to re-orient an Ambisonic
recording. For example, if the default perspective of the 360 degree video (i.e, the perspective with which the video
starts) does not match the recorded sound field (if the microphone was positioned differently on set, for example),
the pitch-yaw-roll sliders can be used to re-orient the sound field. In most cases only the yaw (rotation on the
horizontal plane in the left or right direction) and pitch (rotation on the vertical plane or up-down direction) sliders
would be required to re-orient the recording.
You can use the FB360 Spatialiser to position each channel of a multichannel track independently. This can be used
for playing back a multichannel mix or using a multichannel reverb by inserting the Spatialiser plugin on an aux
channel.
1. Set up a track with the following settings. The routing of multichannel audio behaves differently depending on
your DAW:
• Pro Tools: make sure the number of track channels matches the audio file you wish to use (e.g. 5.0 track
for 5.0 audio file)
• Reaper: set the number channels for the track to 10, regardless of the number of channels in your input
audio
2. Set the Input in the FB360 Spatialiser plugin to the appropriate number of channels for your audio file
3. Import your multichannel recording onto the track
4. You can position the individual channels by dragging the numbered dots in the panner or by using the
parameters within the corresponding tab on the left
Occasions may arise where a spatial mix or sub-mix needs to rotate to follow what is happening in a scene, or
perhaps a 2nd order Ambisonics (ambiX) or 8 channel spatial mix already exists but is incorrectly oriented relative to
the video and needs to be corrected. The Converter plugin is a simple utility which can be inserted between the
FB360 Spatialiser plugin and the FB360 Control plugin to allow yaw rotation of the FB360 Spatialiser output. Input to
the FB360 Converter plugin can either be B-format ambiX 2nd order or Spatial Workstation 8 channel spatial audio.
The output can be set to Binaural, B-Format ambiX (1st order), Spatial Workstation 8 channel (if the input is Spatial
Workstation 8 channel) or kept as B-format ambiX 2nd order. The audio output will be rotated by the specified
number of degrees. You can locate the plugin in various places in the signal chain, or a combination thereof:
• on a single DAW track after the FB360 Spatialiser plugin in order to rotate all sources contained on that track
(e.g. to rotate a full 5.1 mix without having to automate each speaker source separately);
• on a 9 or 10 channel Ambisonics 2nd order bus receiving the output from multiple FB360 Spatialiser plugin
tracks. This would rotate the spatial mix for all of these tracks;
• on the same track as the FB360 Control plugin (must be located before the FB360 Control plugin) to rotate the
entire spatial mix and pass the spatial audio on to the Control plugin.
The FB360 Converter plugin can also be used to convert a Spatial Workstation 8 channel mix to B-Format ambiX
2nd order. This is useful for cases where you might want to include spatial audio stems mixed with an older version
of Spatial Workstation.
Parameters
• Yaw Rotation: Set the number of degrees to rotate the spatial mix input by.
The Yaw Rotation parameter in the FB360 Converter plugin can be automated and controlled via a control surface.
The FB360 Control plugin must be instantiated on an aux channel that receives audio from all the other spatialised
channels in your project. Make sure you have only one instance of the plugin in your project. All audio processing
(such as mastering, compression and equalisation) must be applied to the signal before it reaches the plugin.
Note that whilst the room size is controlled globally here from the control plugin, the room modelling reflections are
mixed into the 2nd order Ambisonics (ambiX) output from the Spatialiser plugin and thus exist in the export mix,
along with any other effects applied before the Spatialiser plugin. The focus and listener orientation controls are
Parameters
• Room
◦ Room Width: A global setting that changes the width of the room in metres. All sounds that have Room
enabled in the FB360 Spatialiser will be affected by this.
◦ Room Length: A global setting that changes the length of the room in metres. All sounds that have Room
enabled in the FB360 Spatialiser will be affected by this.
◦ Room Height: A global setting that changes the height of the room in metres. All sounds that have Room
enabled in the FB360 Spatialiser will be affected by this.
◦ Room Amp: Amplitude of early reflections in the room
◦ Room HF: High frequency absorption within the room. 1 is maximum high frequencies.
• Focus: Focus effects are not baked into the mix. These parameters can be controlled from your app in
real-time using the FB360 Audio Engine or added to an FB360 video as metadata using the Encoder.
◦ Mix Focus: If enabled, an area of the mix will be defined where sounds are played at the normal level.
Sounds outside that region are attenuated.
◦ Follow Head: If enabled, the focus orientation will follow the the listener’s gaze.
◦ Focus Azimuth, Elevation: The orientation of the focus, if Follow Head is disabled. These values are
relative to the listener point of view.
◦ Focus Size: Angle controlling the size of the area included within the focus.
◦ Off-focus Level: Attenuation level of the mix outside of the the focus area.
• Listener
◦ Get From Video: If enabled, the listener’s orientation is automatically queried from the VR Video Player.
◦ Listener Roll, Pitch, Yaw: The orientation of the listener in 3D space. These values are automatable if Get
From Video is disabled.
• Misc
◦ Send Timecode: If enabled, the timecode from the DAW session is sent to the VR Video Player
◦ Frame Delay: Creates a delay for the VR Video Player in relation to the DAW. Delays can be entered
either as a timecode or as a number of frames that will then be converted and displayed as a timecode.
◦ Decode Binaural: If enabled, the mix is decoded to binaural.
The focus effect is not baked into the mix and can be enabled on Facebook 360 videos or used in real-time within
your VR application. The parameters available in the Control plugin are only for preview. To enable the focus effect
on Facebook 360 videos the parameters must be set using the Encoder, see Encoding For Facebook 360 for
instructions.
To get focus control working within your VR app:
1. Use the FB360 audio engine in your app and follow the instructions provided with the engine
2. Specify the value of the Focus Size and Off-focus Level For Engine (displayed in the control plugin) in the
FB360 audio engine API
An important facet of spatial audio is that it is impossible to predict where the listener will be looking, and therefore
the precise loudness of a mix as heard by the listener cannot be determined at the mixing or mastering stage. There
are two loudness plugins in the Spatial Workstation which work together on the 3D master track and the head-locked
stereo track to approximate the overall loudness of your mix. The Loudness plugins provided here give a guideline
for the maximum possible loudness and true peak value in your mix, as if the listener were always looking in the
“loudest” direction. The loudness plugins follow a similar methodology to the EBU-128 technical specification which
details a method for measuring perceived loudness using the units ‘Loudness Units Full Scale’ (LUFS).
The two bars show momentary loudness (LUFS) and true peak (dBFS) approximations for your mix. Along the right
these measurements are repeated with text read-offs in addition to the short term loudness and integrated loudness.
The Video Player is installed in Applications/FB360 Spatial Workstation/Video Player on macOS and C:\Program
Files\FB360 Spatial Workstation\Video Player on Windows. Read Opening A Video and Video Format And Codec
for more information on setting up the player.
The Video Player can be used in either Slave or Standalone mode.
Slave Mode
The Video Player and the Control plugin use Bonjour to easily establish a connection whether they are on the same
host or different hosts on the same network, even hosts using different operating systems. For example, the Video
Player can be run on a Windows host with a VR headset, and the DAW can run on a macOS host.
Each detected host with a Control plugin will be listed in the “Connect to DAW” drop-down. The network interface is
displayed in parentheses; for acceptable video latency ensure that you use a wired Ethernet connection, not a
wireless connection.
If the expected host does not show up in the drop-down, here are some troubleshooting steps:
• Ensure that the DAW is in fact running with the Control plugin loaded.
• Ensure that the hosts are on the same local area network.
• Ensure that the firewall on both hosts is configured to allow network traffic on at least UDP ports 6100, 5125,
and 5353. (If in doubt, temporarily disable the firewalls entirely.)
• On Windows, the Bonjour service is installed by the Spatial Workstation installer. If you opted out, or you or
your administrator has since disabled that service, you will need to reenable or reinstall it. You may reinstall
the Spatial Workstation, or download and install Bonjour Print Services for Windows from Apple.
Standalone Mode
Standalone mode is independent of a DAW and is to preview an encoded .tbe file with a video.
• Load or drop video file: Browse for the video file that needs to be opened
• Load or drop .tbe file: Browse for the .tbe file that needs to be opened
• Video Format
◦ Mono: Non-stereoscopic video. This is usually a video that has a single display
◦ Over-under: Stereoscopic video, where the video for the left eye is displayed in the top-half and the video
for the right eye is displayed in the bottom-half
◦ Side-by-side: Stereoscopic video, where the video for the left eye is displayed in the left-half and the
video for the right eye is displayed in the right-half
• Display Mode
◦ Desktop: The video will be played back in a format that can be viewed on a regular computer display
◦ VR: The video will be displayed in a format that is compatible with Oculus Rift DK1/DK2 on macOS or
Oculus Rift/HTC Vive on Windows
• Open: Opens the video in a new window.
An example Pro Tools HD project and template are automatically installed on your computer. The example project is
located in the installation folder, along with a backup copy of the Pro Tools HD template and I/O settings. Use the
example project to familiarise yourself with the FB360 Spatial Workstation.
To create a new project with the provided template and I/O options with Pro Tools 12. See the Knowledge Base for
creating a new project in Pro Tools 10 and 11 using version 2.2 of the Spatial Workstation.
1. Open Pro Tools HD
2. Create a new project
3. Select Create From Template
4. Choose Post-Production from the Template Group drop-down menu
5. Select FB360 3D Audio from the list of options
6. Set the sample rate and bit depth of your session (see Sample Rate Considerations for information about
target sample rates)
7. Select FB360 3D Audio from the I/O Settings drop-down menu
8. Click Create
The FB360 Spatialiser plugin accepts mono, stereo or multi-channel inputs and outputs a 9 channel 2nd order
Ambisonics (ambiX) signal. These 9 channels of audio must be routed to the FB360 Control plugin for further
processing. Make sure you have only one master channel and instance of the FB360 Control plugin in your project.
You can create as many mono, stereo or quad tracks with the FB360 Spatialiser plugin as your project requires.
There are no limitations. You can also use the separate FB360 Converter plugin to rotate the 9 channel audio output
from the FB360 Spatialiser plugin, or any 2nd order Ambisonics (ambiX) sub-mix before being input to the FB360
Control plugin.
The template project consists of spatialised tracks that have the FB360 Spatialiser plugin inserted and ’normal’
stereo audio tracks. The spatialised tracks are meant for full binaural panning and are routed to a channel called 3D
Master, while the stereo tracks are meant for head-locked stereo panning and are routed to a channel called
Head-locked Master. It is recommended that you stick to this project structure as it makes it easier to export, debug
and deliver mixes. Any audio track in your project must either be routed to 3D Master or Head-locked Master.
Mastering
The template project includes two master channels: 3D Master for all 3D elements in the mix and Head-locked
Master for all non-spatialised elements in the mix. The 3D Master channel is a master auxiliary channel that
receives audio from all FB360 Spatialiser channels. Use it just as you would use a master fader master volume
automation, mastering EQ, etc. The Head-locked Master channel functions in a similar way, but receives audio from
all head-locked stereo tracks. Your mastering chain would need to be applied separately on both masters.
It is quite common that some elements in the mix such as the background score or voice overs might not need to be
spatialised in 3D or react to head-tracking. The two masters, 3D Master and Head-locked Master facilitate this
workflow. Note: some spatial audio formats do not support head-locked stereo/non-spatialised audio.
Mixing
For the spatialised tracks, make sure that the FB360 Spatialiser is the last plugin in the chain (except if you use the
FB360 Converter plugin, which must be located in the signal chain after the FB360 Spatialiser plugin, but before the
FB360 Control plugin). Panning can be controlled and automated through either the sliders or the 2D panner. All
parameters in the FB360 Spatialiser plugin can be automated and controlled via a control surface.
Sub-Mixes
You can create sub-mixes by routing audio from FB360 Spatialiser channels to an Ambisonics (2nd Order) aux
channel. This aux channel would then need to be routed to 3D Master.
The audio from the 3D Master aux is routed to the Control Plugin aux which has the FB360 Control plugin
instantiated on it. The Control plugin is used for setting global parameters (such as room modelling) and for
communicating with the video player. See FB360 Control for more information.
To create a new spatialised or head-locked stereo track, duplicate one of the existing tracks in the project. If you
need to manually create and setup a spatialised track:
1. Create a new mono or multichannel track
2. Instantiate the FB360 Spatialiser by going to multichannel plug-in/Soundfield/FB360 Spatialiser (ambiX) in the
insert plugin drop-down menu
You can create your Pro Tools HD project with any sample rate of your choice, although, 48000Hz is recommended.
5.4 Ambisonics/B-format
The FB360 Spatialiser plugin can also handle and decode 1st order Ambisonics material in either the B-Format
(FuMa) or B-format (ambiX) formats. Here’s how you get it working:
1. Create a a new quad track
2. Insert the FB360 Spatialiser plugin
3. Set the track’s output to the To 3D Master bus
4. In FB360 Spatialiser, set the Input drop-down menu to B-format (FuMa) or B-format (ambiX) depending on
your source material
5. Import your 4 channel B-format recording onto the track
6. The B-format data will automatically be spatialised to binaural by the FB360 Control plugin
For more information about Ambisonics and B-formats see the Ambisonics and B-format Audio section or for
information on rotating the B-format recording, see Rotating the Ambisonic field.
Once you have the video opened and loaded in the VR Video Player, playing back your session in Pro Tools HD
should automatically synchronise playback of the video. Pro Tools HD is always master and the video player is
slave. Make sure your project or your first frame of action starts at 00:00:00:00. See Opening A Video and
Navigating A 360 Video for more information.
6 Using Reaper
Open the example Reaper project SpatialWorkstation.RPP installed in the FB360 Spatial Workstation installation
folder. Go to File → Save Project As.. in the menu bar. Specify a name and location for your project. It is
recommended that you use SpatialWorkstation.RPP as a template for all projects that use the Spatial Workstation
plugins.
The project consists of spatialised tracks that have the FB360 Spatialiser plugin inserted and ’normal’ stereo audio
tracks. The spatialised tracks are meant for full binaural panning and are routed to a channel called 3D MASTER,
while the stereo tracks are meant for head-locked stereo panning and are routed to a channel called HL MASTER. It
is recommended you stick to this project structure as it makes it easier to export, debug and deliver mixes. Any
audio track in your project must either be routed to 3D MASTER or HL MASTER.
To create a new spatialised or head-locked stereo track, duplicate one of the existing tracks in the project. If you
need to manually create and setup a spatialised track:
1. Create a new track
2. In the Mixer view, click on the ’ROUTING’ button
3. Set Track Channels to 10 (the Spatial Workstation will only use the first 9)
4. Click on the Add New Send.. drop down menu and select 3D MASTER
5. Under the options for this newly created send, set Audio to Multichannel source → 10 Channels → 1-10.
6. Uncheck/disable the Master/parent send option at the top-left of the window
6.2 Mastering
The template project includes two master channels: 3D MASTER for all 3D elements in the mix and HL MASTER for
all non-spatialised elements in the mix. The 3D MASTER channel is a master auxiliary channel that receives audio
from all FB360 Spatialiser channels. Use it just as you would use a master fader master volume automation,
mastering EQ, etc. The HL MASTER channel functions in a similar way, but receives audio from all head-locked
stereo. Your mastering chain would need to be applied separately on both masters.
6.3 Mixing
For the spatialised tracks, make sure that the FB360 Spatialiser is the last plugin in the chain (except if you use the
FB360 Converter plugin, which must be located in the signal chain after the FB360 Spatialiser plugin, but before the
FB360 Control plugin). Panning can be controlled and automated through either the sliders or the 2D panner. All
parameters in the FB360 Spatialiser plugin can be automated and controlled via a control surface.
The FB360 Spatialiser plugin can also handle and decode 1st order Ambisonics material in either the B-Format
(FuMa) or B-format (ambiX) formats. Here’s how you get it working:
1. Create a a new track with the settings specified in or duplicate an existing track (ensure the track has 10
channels, even though only four channels will have audio)
2. Insert an instance of the FB360 Spatialiser plugin, if one isn’t present already
3. In FB360 Spatialiser, set the Input drop-down menu to B-format (FuMa) or B-format (ambiX) depending on
your source material
4. Import your 4 channel B-format recording into the track
5. The B-format data will automatically be spatialised to binaural by the FB360 Control plugin
For more information about Ambisonics and B-formats see the Ambisonics and B-format Audio section or for
information on rotating the B-format recording, see Rotating the Ambisonic field.
Once you have the video opened and loaded in the VR Video Player, playing back your session in Reaper should
automatically synchronise playback of the video. Reaper is always master and the video player is slave. Make sure
your project starts at 00:00:00:00. See Opening A Video and Navigating A 360 Video for more information.
7 Video Player
The video player by default works as a slave to the DAW. Once a file is opened and loaded, playback will be
controlled from and synchronised to your DAW.
A list of known issues is maintained in the Knowledge Base and can be found here.
While the video player can load and playback a variety of formats, the following is recommended:
• DNxHR_LB: On both macOS and Windows this results in higher quality playback with quick frame-by-frame
scrubbing and seeking
Frame-by-frame scrubbing and seeking is important when you want the video player to synchronise to the timeline
selection/playhead position in the DAW when you aren’t playing back your session (such as when editing or
synchronising edit points). Refer to this Knowledge Base article for details on the recommended frame rate and
resolution.
We recommend using FFmpeg (http://ffmpegmac.net/) with the settings specified below. FFmpeg is usually used as
a command line utility using the Terminal application on a Mac. For instructions on converting videos to DNxHR
using iFFmpeg see the instructions in the Video Format Guidelines article.
• DNxHR LB:
ffmpeg -i INPUTFILE -map 0:v -an -c:v dnxhd -pix_fmt yuv422p -trellis 0 -profile:v dnxhr_
,→lb -y OUTPUTFILE.mov
Open the Video Player app from the installation folder. Load the video file, specify the playback options and click
Open. For more information about the options, see VR Video Player. If Slave is selected playback will automatically
be controlled from your DAW.
Open the Video Player app from the installation folder. Load the video file and the .tbe file. Select the playback
options and click Open.
If VR is selected as the Display Mode, you will need a VR headset connected to your computer. The video will be
displayed on the device (provided it is setup correctly) and the information from the head-tracker will automatically
be sent to the video player and the FB360 Control plugin. If you have chosen the Desktop display mode, you can
use your keyboard and mouse to navigate the video.
Key Commands
8 Encoder
The Encoder application is installed in Mac HD/Applications/FB360 Spatial Workstation/Encoder on macOS and
Mac HD/Applications/FB360 Spatial Workstation/Encoder on Windows. It can be used to convert your mix to a
variety of formats or create a file that can be uploaded to Facebook 360.
The Encoder requires Mp4Box and Python 2.7 installed on your Windows computer.
1. The Python 2.7 installer can be downloaded from here. Follow the instructions with the installer.
2. Mp4Box can be installed using the GPAC installer from here. The GPAC installer includes Mp4Box and other
components. Installing the additional components is optional
(a) Spatial Workstation 8 Channel: If you have used a version of the Spatial Workstation before 3.0.0 to
design your audio mix, this would be the output of the 3D master from your audio session
(b) B-format ambiX 1st order: First order Ambisonics with ACN ordering and SN3D normalisation, from any
other mix or tool (4 channels)
(c) B-format FuMa: First order Ambisonics with Furse-Malham ordering, typically the B-format audio from
Ambisonic microphones (4 channels)
(d) B-format ambiX 2nd order: Second order Ambisonics with ACN ordering and SN3D normalisation (9
channels), when using version 3.0.0 or later of the Spatial Workstation this would be the output of the 3D
master from your audio session
(e) B-format FuMa 2nd order: Second order Ambisonics with Furse-Malham ordering, typically the B-format
audio from Ambisonic microphones (9 channels)
5. Ensure the From Pro Tools checkbox is ticked if the 2nd order Ambisonics (ambiX) spatial audio file is from
Pro Tools
6. Optionally, you can also drop or load a stereo file for head-locked audio. This is audio that will not rotate when
looking around a 360 video
7. Drop or load the video file. Ensure that the video is encoded as H.264 within an mp4 container
8. Set the layout for the video file:
The Encoder app can also be used to convert an existing mix from the Spatial Workstation to other formats.
The Encoder can be run from the command line, enabling scripting automation. Currently this works on macOS and
Linux only, but we plan to add Windows support as well.
When you run the Encoder binary directly, and pass -h, you will get help output like this:
$ "./FB360 Encoder.app/Contents/MacOS/FB360 Encoder" -h
fb360-encoder \
[--help] [--version] \
--spatial SPATIAL.wav --spatial-format SPATIAL_FORMAT [--from-protools] \
-p,--from-protools the HHOA spatial audio WAV file was exported by Pro Tools
--focus-size-deg ARG size of the focus area (degrees)
--off-focus-level-dB ARG off-focus level (decibels)
-H,--headlocked ARG path to headlocked audio (WAV)
-v,--video ARG input video path
--video-layout ARG one of {mono, top-bottom, left-right} default mono
-o,--output ARG output path
-F,--output-format ARG one of {fb360-hhoa, yt360-ambix-first, rift-oculus-video, fuma-
,→first, ambix-first, fuma-second, ambix-second, mkv}
So for example, to encode a top-bottom stereoscopic video with Spatial Workstation 8-channel audio (exported from
Pro Tools) and headlocked audio, you would run this command:
"./FB360 Encoder.app/Contents/MacOS/FB360 Encoder" \
--spatial spat.wav --spatial-format hhoa --from-protools --headlocked headlocked.wav \
--video video.mp4 --video-layout top-bottom \
--output encoded-video.mp4 --output-format fb360-hhoa
You may need to install ffmpeg, MP4Box, and Python 2.7 and ensure they are in your execution path, or provide the
paths to them with the options --ffmpeg-path, --mp4box-path, and --python-path. e.g. on macOS with
Homebrew:
brew install ffmpeg
brew install mp4box
# python2.7 is already installed in /usr/bin/ by the operating system
export PATH=$PATH:/usr/local/bin
If you have any questions, bugs, or feedback about the CLI interface to the encoder please post in the Spatial
Workstation group!