O7A View

The O7A View plugin library is similar to the O3A View library, providing tools to help work with video, for VR or film.

This plugin library is intended to work alongside the O7A Core.

CPU Load Warning

The O7A plugins are similar to the O3A plugins, except for the ambisonic "order" in use. The O3A plugins use third order and 16 audio channels to capture a scene, which already gives high spatial precision. The O7A plugins use seventh order and 64 audio channels, which gives much higher spatial precision but is generally only recommended for research applications, or in studios with high-end modern hardware.

These are VST2 or AAX plugins for macOS (10.14 to 13.5) or Windows (10 or 11, 64bit Intel). They can be hosted in some Digital Audio Workstations (DAWs) that can handle tracks with sufficiently high channel counts. Because of the very high channel counts needed for these plugins, this typically means Reaper, Pro Tools Ultimate, or Max/MSP. These plugins use the SN3D higher order ambisonic (HOA) convention, at seventh order, which needs 64 channels. The exact channel counts needed for individual plugins are listed below in the Plugins section. Not all plugins are supported in AAX.

We use some free software, data and artwork in these products. Before purchase, please check the technical requirements and license agreement. Prices include VAT where applicable. EU VAT is normally charged at your local rate using the MOSS VAT system. By beginning the payment process you agree to be bound by our terms and conditions.

The View Applications

Each View application (View or ViewVR) is controlled by an O7A View Sync plugin.

The connection between the plugin and View application is managed over a local network connection, so the application can run on the same machine, or a different one, even one running a different operating system.

O7A View Sync

The plugin can be used to set the video to be shown in the View application and manage synchronization. Stereographic video formats are supported and are rendered stereographically in ViewVR (only).

View and ViewVR support 180 and 360 degree videos, along with traditional video formats, and View supports a number of image projections. Using a camera projection in View, or a headset with ViewVR, head tracking data is sent back to the DAW to allow the audio scene to be rotated.

Once connected, some our O7A plugins acquire an extra "View" button on the top right. This includes the 16 and 32 channel panners in this library and some plugins in other libraries (including the O7A Core). This allows certain spatial controls (typically panning direction) to be controlled from View or ViewVR, using mouse or VR controllers respectively. In addition, the O7A Flare plugin (in the O7A Core) can be used to overlay audio visualisations on top of the video image.

O7A View Button

The VR Monitoring Decoder

The VR Monitoring Decoder is used to decode (or "render") an O7A mix to stereo. It is designed to simulate the final output you will get within a VR experience, providing a number of different decoder styles. The various HRTFs provided by Rapture3D are included, as is YouTube's binaural decoder (as of late 2016).

O7A Decoder - VR Monitoring

If you place this decoder after the O7A View Sync plugin above and enable head tracking, this can provide head tracked binaural rendering - synchronized with 360 video - while you pan sounds around in VR!

Panners

O7A Panner 16

O7A Panner 16

I/O: 16 in, 64 out

This provides 16 channels of panning in one plugin. It comes into its own when controlled from the View applications.

O7A Panner 32

O7A Panner 32

I/O: 32 in, 64 out

AAX: not supported

This provides 32 channels of panning in one plugin. It comes into its own when controlled from the View applications.

Monitoring and Control

O7A View Sync

O7A View Sync

I/O: 64 in, 64 out

This plugin manages the connection to a View application, potentially on another machine. It can modify the DAW audio stream to take head tracking into account.

O7A Decoder - VR Monitoring

O7A Decoder - VR Monitoring

I/O: 64 in, 2 out

This decoder converts O7A mixes to stereo. It has a number of binaural decoder options so you can check how your mix will sound in VR.

Technical Requirements

Please check everything is okay here before purchasing software.

Operating System

Supported versions of Microsoft Windows are 10 or 11, 64bit Intel.

Supported versions of Apple macOS are 10.14 to 13.5, 64bit Intel or Apple Silicon.

VST Host

The VST plugins require a VST 2 host with shell plugin support.

These plugins do not work with all VST 2 hosts. One reason for this is that the O7A plugins need large numbers of channels on their input or output busses. Check the individual plugins for the channel counts they need, but all of the O7A plugins need at least 64 channels on each track. Also, at the time of writing VST 2 shell plugins are not supported in Nuendo or Cubase.

AAX Host

The AAX plugins require Pro Tools Ultimate version 2023.6 or later.

Due to channel and stem restrictions, not all plugins are supported in AAX. Please see the plugin descriptions for details.

PC Hardware

Please check your PC meets the following requirements:

  • Intel Core i7 CPU or better, or Apple Silicon.
  • 400MB of free disk space.

Permissions

You'll need administrator permissions while installing on Windows. The software probably won't install properly using a "restricted" account.

ViewVR Application

For the ViewVR application, Microsoft Windows 10 or 11 64bit is required, along with a supported Virtual Reality headset and a computer meeting its technical requirements. macOS is not currently supported. Note however that it is possible to run the studio plugins on a different computer to the one running the ViewVR application, and to connect the two using a local network.

Currently supported VR headsets are:

  • HTC Vive
  • Valve Index

Other VR headsets that are compatible with SteamVR may work but are not supported.

Internet Connection Required

This software requires an Internet Connection for license activation and verification.

Successful license verification isn't required every time you use the software, but it is needed during installation and needs to succeed once every couple of weeks to keep the license fresh.

The license can be "revoked" to remove it from one machine so it can be moved on to another. You should also do this if you're updating your system in case the machine appears to have changed identity.