Sync issues can be identified when sync indicators in Spat Revolution (bottom left corner) turns to red. This results in clicks, noises and or loss of sound.
All 'green' indicators mean the sync is correct.
Most of the time, sync issues encountered in Spat Revolution connected to Local Audio Path sources, can be fixed when applying goog routing practices in your DAW, as described just below.
To work properly, the send plugins instances must be processed by the DAW before the return plugin instances. To force the DAW to process this way, each track with send plugin inserted must be routed (directly or indirectly) to the 'return' tracks, using DAW internal routing.
Here are 4 examples, which should cover the main use cases :
- Return on master track
In simple projects, when having a single return plugin on master track, you should not encounter any sync issue as soon as each 'send' track is routed to the master track.
- Single return on an AUX track
Issues may happen when return is inserted on an AUX track. Make sure that each 'send' track is routed to the AUX track ('return' track) using AUX send (see exemple below)
You can also route their output to the AUX track.
- Several returns on AUX tracks
When you need several 'return' tracks (when several rooms in Spat Revolution, and/or several outputs in exemple), you'll have to route each 'send' track to each 'return' track, using the same technique.
But it can quickly become complicated as the project grows. So, in the following exemple, we added a 'dummy' track, that avoid using several AUX sends on the 'send 'tracks. It makes routing more clear and fast to setup on large projects.
The 'dummy' AUX track is routed to all the 'return' tracks (using AUX send)
Then, simply route all your 'send' tracks to this 'dummy' track (using aux send)
- Larger projects that require independant dry and wet signals
In larger projects, when you need to keep both the dry signal and the Spat return signals independant (when the mix requires to switch easily from one to the other), add one AUX (pre-fader may be useful) per audio track to be sent to Spat, and insert the send plugins on these AUX tracks.
This way, you keep the dry signal on the audio track's output.
Here are the cases where the synchronization issues that appear in Spat Revolution (but inaudible) even if you have applied the above recommendations can be ignored:
- when one or more of the tracks with a send plugin inserted don't play audio (between two audio regions, in exemple)
- when some send/return plugins are not connected in Spat.
- when having both 'spat send plugins' objects, and 'hardware' output objects, in the same Spat project. (Mix of software and hardware input is not officially supported at this time although some successful setups exist this way )