The Avid S3L console (including the updated Avid:S3L-X version) is an amazing digital console. Anyone who has used an older Avid console (e.g., the Avid:D-Show or Avid:Profile) will be right at home with the Avid:VENUE software interface, meaning they can jump straight to crafting their mix.
This site focuses on non-standard solutions to problems that many S3L users are curious about. Information abounds on the internets for how to use the console for normal situations. Google is your friend for finding it.
None of the information on this site is endorsed or supported by Avid. Do not contact Avid about anything you have read here!
Information and solutions provided:
- Avid:S3L:3P_AVB – Configuring the S3L to work with third-party (3P) AVB devices (e.g., the MOTU:Stage-B16).
- Avid:S3L:AVB_Switches – Tested AVB capable Ethernet switches.
Avid E3 Engine
- Avid:E3 Engine
- Avid:E3 Engine:Internals -- Information about the internals of the E3 Engine (e.g., the multiple embedded Linux devices).
Avid Stage 16
- Avid:Stage 16
- Avid:Stage 16:Internals – Information about the internals of the stage box (e.g., the embedded Linux AVB server).
- Avid:Stage 16:Standalone – Configuring the Stage 16 stage box to work as a stand-alone device (e.g., directly accessible from macOS, or attached via AVB to a MOTU:Stage-B16 without the Avid:E3 Engine)
The security model of the Avid S3L console was never designed for it to be attached directly to an open, unprotected internet connection. If you decide to connect the device to a network that connects to internet, please ensure that connection is secured with a firewall!!
The embedded Windows 8.1 installation has few open ports, but the multiple embedded Linux devices in the Avid:E3 Engine, Avid:Stage 16 stage box, as well as the Avid:S3 Console all have some open ports with practically zero protections in place.
Ideally, the Avid S3L would only be connected to an isolated network with devices dedicated only to the task at hand, with no other devices.