[Vlog] Demoing the Waves SoundGrid BR1 With the Avid S3L

TL;DR Demonstration of bridging Avid S3L AVB and Waves SoundGrid using the Waves SoundGrid BR1.

In the video I demonstrate a fifth way of using Waves plug-ins with the Avid S3L. (See my previous vlog for the first four ways.) This solution is quite simple and powerful. I also evaluate the configuration based on complexity, portability, latency, and cost.

The five methods are:

  • Hardware Inserts
  • Analog Fx Returns
  • AVB Fx Returns
  • SoundGrid Fx Returns (MOTU M64 + DiGiGrid MGO)
  • SoundGrid Fx Returns (Waves SoundGrid BR1)

Please watch the video, and let me know in the video comments what you think, and what other kinds of videos you’d like to see.

P.S. You’re welcome to read the script I used in planning the video.

[Vlog] HOWTO Use Waves Plug-ins With the Avid S3L

TL;DR I’ve you’ve ever wanted to use Waves plug-ins with the Avid S3L, then I’ve got the video for you.

In the video I demonstrate four different ways of using Waves plug-ins with the Avid S3L. While running plug-ins directly on the console is not supported, these alternatives should be attractive alternatives to most sound engineers. I evaluate each configuration based on complexity, portability, latency, and cost.

The four methods are:

  • Hardware Inserts
  • Analog Fx Returns
  • AVB Fx Returns
  • SoundGrid Fx Returns

Please watch the video, and let me know in the video comments what you think, and what other kinds of videos you’d like to see.

P.S. You’re welcome to read the script I used in planning the video.

[Vlog] HOWTO Connect a MOTU AVB Device to the Avid S3L

TL;DR I’ve you’ve ever wanted to connect a MOTU AVB device to your Avid S3L, then I’ve got the video for you.

In the video I demonstrate connecting a MOTU Stage-B16 to expand both the input and output signal count, as well as how to record from the MOTU in addition to other stage boxes.

The process requires changing an internal configuration of the Avid S3L, but this is a simple one-time process that is reversible if needed. Once the change is made, it should be possible to connect practically any AVB device to the S3L. The process required some trial and error, and some help from the Avid forums, but it works consistently and I’ve used it for a while now.

Please watch the video, and let me know in the video comments what you think, and what other kinds of videos you’d like to see.

[Vlog] Redundant Recording With the Avid S3L

TL;DR I’ve you’ve ever wanted to make a redundant recording of an Avid S3L (i.e., record on two computers simultaneously), then I’ve got the video for you.

I’ve played around quite a bit with the S3L and found that it has capabilities beyond those mentioned by Avid. Specifically, the AVB protocol allows for much more, but for simplicity sake, the S3L does not expose anything other than that which is needed to meet common customer needs.

One common need that isn’t addressed though is making a redundant recording, like when one is recording a live performance and wants to insure against a computer crashing or something. As this requires extra hardware, it isn’t something supported “by default”, but with the purchase of an AVB Switch (e.g., the PreSonus SW5E, or the Netgear GS724Tv4 with additional AVB license), this becomes easily possible.

Please watch the video, and let me know in the comments what you think, and what other kinds of videos like this you might like to see.

Testing the Avid S3L with the MOTU M64

TL;DR The MOTU M64 works great with the Avid VENUE S3L. The tested setup was sending 32ch of audio from an Avid VENUE S3L via AVB to a MOTU M64, converting the signal to optical MADI, and sending it over fiber into an Avid VENUE Profile.

Background

A couple of weeks ago, I had the privilege of working with Patrick Müller and Luca Bruegger of Tonkultur.ch GmbH / Remote Recording Services to connect their Avid S3L system to their Avid Profile system via optical MADI using the the MOTU M64 as a converter.

Patrick and Luca were looking to use a spare Avid S3L console as additional inputs for an Avid Venue Profile console. They normally get a MADI feed from the FoH for their recording, but sometimes have the need for their own on-stage preamps. They wanted the ability to place two Avid Stage 16 stage boxes on the stage, acting as as mic preamps, and send the signals into their existing setup via optical MADI. Unfortunately the S3L doesn’t support MADI.

In their search for a solution, they were pointed at my Avid S3L and 3rd-party AVB Devices article. Seeing that I’ve connected MOTU devices already, they purchased the MOTU M64, and reached out for some help getting it going. Luckily Luca and I have known each other for several years now which made it easy to connect.

Getting it going

Working through the documentation I’ve written, we were able to get the setup working in a couple of hours. This was my first chance to test the documentation on a second S3L system, and I was able to fix some minor mistakes along the way, which should make future configurations go much faster.

A future desire they have is to leave the E3 Engine out of the mix completely, using only the Stage 16 and M64 devices. I’ve started digging into the Stage 16 to see whether that might be possible, and both Luca and I are reading more into the AVB standard, as well as Milan, which is the follow-up standard to AVB. Stay tuned!

[Update 2020-01-14] I’m now able to announce the Stage 16 via AVB so that I can record directly from it with macOS, and I can also manually control the signal settings (gain, pad, and phantom) as well as the LEDs on the front. See what all I have working on my Projects page.

Stop Avid Link from starting at boot

TL;DR Avid Link starts at boot, and there is no setting in the app to prevent launching at boot. I hate software that doesn’t allow me to control whether it starts automatically!

To stop Avid Link from launching on macOS at boot, run the following command from a Terminal. It is a long line, so make sure to copy the whole thing. You will be asked for your password.

sudo defaults write /Library/LaunchAgents/com.avid.avidlink.plist RunAtLoad -boolean false

To again allow Avid Link to start at boot, run the same command again, changing the “false” to “true”.

Background

I’m not a fan of software makers taking action on my computers without my awareness. One of the most annoying things companies do is that they install something that starts at every boot – without asking – because they mistakenly believe that their software always needs to be running, and that I as a user am not smart enough to make that decision on my own. Even worse than not asking is not even giving the permission to stop the software from starting at boot.

As you can see, Avid Link gives me no option to disable the launch at boot, only that it is hidden after launch.

Looking in the standard location for controlling such things (System Preferences > Users & Groups > Login Items), Avid Link isn’t listed.

As you can see, I’m not against things starting at boot, only things that I cannot control!

Avid S3L and 3rd-party AVB Devices

This article describes how to connect and use MOTU AVB audio interfaces with the Avid S3L-X console.

[Update: 2021-03-22] I recently released a video on YouTube that demonstrates this. See my [Vlog] HOWTO Connect a MOTU AVB Device to the Avid S3L blog entry for more information.

For years, I have wanted to connect my MOTU AVB audio interfaces to my Avid S3L console, but have had no luck. After recently finding some information on the internets, I’ve found a way to reconfigure the S3L to talk using 8-channel AVB streams, which my MOTU devices require, and with some effort I now have bi-directional audio working!!

I’ve written up a document, and shared it as a public Google doc. I’ll eventually write it up here, but don’t feel like messing with WordPress right now.

Avid S3L-X and 3rd Party AVB (a Google Doc)

I’ve also started collecting data as I discover it in a wiki (https://wiki.forestent.com/Avid_S3L).

I look forward to any feedback!!

Avid S3L Remote Power On

The ICF recording studio where I do mixing for live video and internet broadcasts for is, shall we say, small. Due to its small size and the presence of multiple large screens, it can become quite warm, despite fans to help cool it.

ICF Recording Booth

To remove a source of heat generation, I moved the Avid E3 Engine outside and on top of the booth, a change that both made it quieter and much cooler. (Note, we use a separate console for recording our bands in the studio, so the E3 fan noise doesn’t cause any problems as it is normally powered off.)

Placing the device outside though means I cannot as easily flip the power switch to power it on. To get around this limitation, I did some research and found that I can power the device on using the Ethernet Wake-on-LAN protocol.

Avid E3 Engine

To remotely wake the E3 engine, you need three things:

  1. A computer that is connected to the same Ethernet network as the E3 engine. If VLANs are in use, they must be on the same VLAN.
  2. The MAC address for the engine. The MAC address is available under the Options > Devices tab and right-clicking on the E3 engine image.
  3. The IP subnet address of the network. (Optional,  depending on the software used.)

Software for remotely waking the E3 engine.

There are several software packages available to send the special Wake-on-LAN Magic Packet.

Mac

  • Wake On Lan by Depicus (Mac App Store, $1.99)
  • Remote Desktop  (Apple, $79.99) – Also useful for controlling the S3L-X remotely.

Windows

Command-line

For those comfortable with the command-line, a short Python script will also do the job. Save this script somewhere as wakeonlan.py and make it executable with chmod +x. Myself, I keep a copy of the script in my ~/usr/bin directory.

#!/usr/bin/env python
# https://apple.stackexchange.com/questions/95246/wake-other-computers-from-mac-osx

import socket
import sys

if len(sys.argv) < 3:
    print "Usage: wakeonlan.py <ADR> <MAC>     (example: 192.168.1.255 00:11:22:33:44:55)"
    sys.exit(1)

mac = sys.argv[2]
data = ''.join(['FF' * 6, mac.replace(':', '') * 16])
sock = socket.socket(socket.AF_INET, socket.SOCK_DGRAM)
sock.setsockopt(socket.SOL_SOCKET, socket.SO_BROADCAST, 1)
sock.sendto(data.decode("hex"), (sys.argv[1], 9))

To wake my system, I call the  script like below, where 172.16.0.255 is the subnet of my network, and 00:90:fb:4a:13:9e the MAC address of my E3 engine.

~/usr/bin/wakeonlan.py 172.16.0.255 00:90:fb:4a:13:9e

Avid Stage 16

Unfortunately, the Stage 16 Box cannot be remotely power cycled without additional equipment. I haven’t set this up yet, but my plan would be to use one of the devices below to enable remote power on/off of the device.

My quest to get MIDI working on the Avid S3L

During large productions, my team uses QLab to play various sound effects, and to trigger snapshots changes on our Avid D-Show mixing console. I’d like to make use of the same triggers on the Avid S3L we use for our video mix, but unlike the D-Show it doesn’t have built-in MIDI.

According to the Avid Knowledge Base, the Roland UM-One MK 2 is officially supported, but that other class-compliant USB MIDI interfaces should also work. I don’t have the Roland, so over time I’ll try out various interfaces that I come across to see what I can get working.

If you know of a MIDI interface that works with the S3L-X, leave a comment and I’ll add it to the list.

Device Works? Tested Notes
MOTU 828mk3 No 2018-11-18
MOTU Stage-B16 No 2018-11-18
MOTU UltraLite-mk3 Hybrid No 2018-11-18 USB mode requires external power.

McDSP VENUE 6.4.0.15+ plug-ins don’t work on Avid S3L-X

I tried installing the latest versions of the McDSP VENUE plug-ins on my Avid S3L-X today, but they don’t work. The announcement says they are for the S6L, but all past versions have also worked on the S3L, so I’d hoped they would continue working. Alas, they don’t. Stick with the older 6.3.0.11 release.

The specific behaviour I see is that the plug-ins install successfully, as I’d expect, but when I open a show file using one of the plug-ins, they appear with the yellow/red triangle and are listed as “not available”. Plug-ins that I don’t have loaded in the current show file don’t even appear in the tree of available plug-ins, although they are listed on the plug-ins install page.

To get back to working plugins, I downgraded all plug-ins to the previously working versions in the VENUE 6.3.0.11 bundle installer.


[Update: 2020-12-19] I updated the VENUE link with one provided to me by McDSP when I upgraded individual plug-ins to the Everything Pack v6.4 HD.

[Update: 2019-03-03] McDSP released a new VENUE S6L Installer v6.5.0.12. I tried it, and it doesn’t work. They continue not listing support for the S3L, so I’m saddened, but not surprised.

[Update: 2018-10-16] I fixed the link to the VENUE 6.3.0.11 bundle installer. I had incorrectly pointed to a nonexistent 6.4.0.11 version.

[Update: 2018-09-06] McDSP released a new 6.5.0.3 plug-in version for Windows that supports iLok Cloud. I tried this version (via manual install), and it also does not work.

[Update: 2018-09-04] I noticed today that the term “S3L” was removed from the VENUE installer on the McDSP Downloads page, and only the S6L is listed as supported for the 6.4.0.15 release. I’m guessing they have unofficially dropped support for the S3L, although I can’t find any other confirmation to that effect.

[Update: 2018-09-01] I tried manually downloading and installing the 6.4.0.14 version of the EC300 and NR800 plug-ins on a separate Windows machine, copied the installed plug-ins to a USB stick, and installed them on my S3L-X. This also did not work. (I’ve successfully used this method in the past to install the SA-2 Dialog Processor before it was included in the VENUE bundle installer, so I know it works.)