• The SPAT Send and Return plugins use LAP automation when the « Enable » of the plugin is activated, i.e. when the audio is sent to SPAT Revolution via the plugin.
• When the LAP is deactivated, i.e. the “Enable” button is off, OSC is used to control the objects.
• OSC is used always used for the SPAT Room plugins.

Automation reading with Local Audio Path

• Ensure your DAW and the wanted track automation status are set to “Read” or “Touch”.
• On the « Item» page on SPAT Revolution, check if the “Automation” field of the wanted source is enabled. This parameter allows disabling the incoming automation input.
• If the automation does not work, on the SPAT plugin, please check if the field « Publish changes in main thread » is set according to the following wanted status for your DAW:
  • ON: Ableton Live, ProTools, Steinberg products (Cubase, Nuendo, Wavelab), StudioOne
  • OFF: all others
• Finally, check if the source index in SPAT Revolution and the plugin source index are the same. It can sometimes, according to the DAW, causes issues.

If it doesn’t work, please contact us.

Automation reading with OSC

• Make sure the OSC is configured on both SPAT Revolution and SPAT plugin sides, i.e. the address IP and the port number are set. Use 127.0.0.1 if DAW and SPAT Revolution are on the same machine. 
• On SPAT Revolution, make sure OSC Enable is checked.
• To check if SPAT Revolution receives the OSC data sent by the plugin, enable the “Command log” on the OSC preferences panel, then open the terminal (menu Help, or F7). The OSC input message will be shown in it. If no OSC input message is displayed, there has been an error configuring the address and port.
• Make sure the plugin source index and the source remote index in SPAT are the same. On SPAT Revolution side, the remote index is located on the Item page.
• On the « Item» page of SPAT Revolution, make sure « Remote » is on for the wanted sources.

The post Troubleshooting SPAT Revolution with DAW automation reading appeared first on FLUX:: Immersive.

To prevent some playbacks errors and glitches, Nuendo introduces the “ASIO-Guard” (more details about it in this dedicated article). This will allow to use the block size given to Nuendo for the “time-critical” operation (like track with monitoring option activated), but a larger one for the other. This buffer depends on the ASIO-guard level (typically, 256 for “low”, 512 for “normal” and 1024 for high in 48kHz).

Be sure to deactivate this ASIO-guard to use the same block size for all tracks, and for the block size to match the driver one.

The post Why does the block size indicated in SPAT not correspond to the Nuendo ones when using LAP? appeared first on FLUX:: Immersive.

https://www.ilok.com/#!license-manager

If not, please contact support at support.flux.audio.

The post Windows – libxml2.dll not found error appeared first on FLUX:: Immersive.

If so, ensure to use the intel version of Reaper with ReaVolution instead of the M1 native one, as SPAT Revolution plugins that are loaded in ReaVolution are still compiled for intel machines.

We are currently working on an update to fix this issue.

The post Error messages in ReaVolution on M1 macs appeared first on FLUX:: Immersive.

In order to ensure this synchronization, SPAT Revolution will send all parameter data to the different devices based on the OSC output configured in the application preference. This action automatically happens at the session opening. Something we may refer to as an OSC dump.

If you ever experience an out-of-sync device, for example by enabling an OSC device after session opening, some actions located in the “Setup/OSC” menu could help you send the current parameters to all OSC devices configured on output:

• Send all sources properties (Option/Alt + Command/Ctrl + S)
• Send all sources position (Option/Alt + Command/Ctrl + P)
• Send all rooms properties  (Option/Alt + Command/Ctrl + R)
• Send all master properties (Option/Alt + Command/Ctrl + M)

These actions will send dedicated data on all the configured and available OSC output sockets.

To note, some issues currently exist with these OSC dump functionalities:

• Sources’ positions aren’t sent on session opening. You may have to use the “Send all sources position” action to resolve it.
• Shortcuts and actions only work on the setup page.

Note: To ensure that you are actually sending the data, you can simply enable the command log in the OSC Main section page of the preferences and then open a terminal window from the Help menu.

The post Troubleshooting with OSC appeared first on FLUX:: Immersive.

Please ensure that you have an active SPAT Revolution license (SPAT Revolution Essential, SPAT Revolution Ultimate bundle) assigned to your iLok key or to the actual computer.

This can be validated with the iLok manager application.

Please note that as of April 15th, 2021, a new SPAT Revolution license called SPAT Revolution Ultimate bundle was deposited to all perpetual owners or subscribers in order to support the SPAT Revolution software version 21.4.0.xxxxx and the release of the new SPAT Revolution Essential license.
See this article for more information: SPAT Revolution April 2021 – New Essential and Ultimate license (bundle)

New licenses are needed to support the SPAT Revolution version 22.09.xxxx and up. More information about this subject in this article: SPAT Revolution 22.09 license upgrade required.

The post Error message: “SPAT Revolution initialization problem found! Please check your license authorization” appeared first on FLUX:: Immersive.

If you encounter such an issue, please follow the guidelines described in this section of the SPAT Revolution user manual:

Troubleshooting – Sync issues with LAP

The post Local Audio Path – Solve sync issues appeared first on FLUX:: Immersive.

After the installation is ready, reboot Windows and then start Spat Revolution again, and everything should work as intended.

The post Windows – “import DLL netcdf.dll cannot be loaded” error on Spat Revolution startup (Windows only) appeared first on FLUX:: Immersive.