Deployment - Connecting t Hardware | AVX Architect
In this video, learn how to deploy live devices in AVX Architect. Deployment involves loading and syncing your AVX Architect design file to Soundweb OMNI hardware, ensuring your configuration and parameters are applied correctly.
Transcript
In this video, we’re going to walk you through deployment. Deployment involves the loading and syncing of the AVX Architect design file to the live hardware. In this example, we’re continuing from our last video, where we matched these devices to the design file. Check out that video first if your devices aren’t matched yet.
Once you have matched devices, click the “Deploy and connect” button in the top right of AVX Architect. Click OK for this pop-up to close any open project windows or panels, then the deployment wizard will open. The deployment wizard shows all devices, their information, as well as some status and sync options. Since this is our first time deploying to these devices, we only have the option to load or ignore the configuration. If we choose to ignore, the configuration will not be pushed to the device and it will not be live. In this example, we have two instances of AVX Control. One for the iPad and one for the computer. If we look at the computer’s instance of AVX Control, we’ll see that it’s in the default state of waiting for a control panel. Go ahead and start the deployment process by pressing the “Deploy and connect” button in the bottom right of the deployment wizard. The loading of the devices might take some time depending on how many devices are being deployed to.
Once the devices are successfully deployed, they will be green with check mark indicators in the deployment wizard, and a new option to continue will be in the bottom right corner. Select it, and we will be taken back to the system view. The devices are now green, show connected, and our custom panel will be loaded into the instances of AVX Control. If you’re running a live configuration, these panels will now make active changes to your system.
Let’s take a look at another example where you might be deploying from an existing system with different parameters. I’m going to go ahead and disconnect from this system. Even though we’re disconnected, this AVX Control instance is still active and making changes to the system. Let’s change a few of these parameters, then try to deploy and connect again. This time, notice that the configuration is equal, because nothing has changed in the design, but there is a parameter sync option available. This is because our AVX Control panel made changes to the DSP while we were offline. These sync choices here are the RX, or to receive the parameters from the device, or TX, to transmit the parameters to the device. Let’s choose to receive the configuration, then deploy and connect again. Only doing a parameter sync will usually be much quicker than deploying the whole device configuration.
Here's some quick tips for quickly navigating the deployment wizard. You can use these check boxes on the left side of the devices to select multiple devices and apply the parameter sync RX or TX option simultaneously. If a device does not need a parameter sync, then it will simply ignore this when applied. Remember that the device list can be sorted by clicking these fields in the top of the columns like name, manufacturer, or family. These columns also can be resized, as well as auto-sized and reset to the default sizes using this button on the column headers.