How to Optimize Performance and Reliability?
A Middle Control rig is only as reliable as the network, cabling, and configuration around it. The tips below cover the issues we see most often in support, and apply to any live production setup, not just Middle Control — worth checking before a show.
Network
Use Wired Ethernet wherever possible
For the laptop running Middle Control, prefer wired Ethernet over Wi-Fi and turn Wi-Fi off. Most reliability issues — choppy control, dropouts, intermittent discovery — trace back to Wi-Fi on the control computer.
- Connect your Mac, ATEM, and APC-R units to the same wired network (router or switch with a router upstream).
- Use a USB-C Ethernet adapter or dock and disable Wi-Fi for the show.
- Use Wi-Fi only for secondary control surfaces (for instance a non-critical iPad) or for cameras that can't easily be wired.
Middle Control can be operated in full Wi-Fi mode (laptop and cameras), but that's better suited to studio monitoring and non-critical applications. Wi-Fi performance also depends much more on the quality of your equipment than a wired LAN does.
One network, one control path
If your computer has both Ethernet and Wi-Fi connected, Middle Control may pick the wrong interface and fail to discover devices. It's good practice to disable the unused interface for the duration of the show.
Use quality network gear
Consumer-grade APs and routers are the single biggest source of latency and dropouts. Recommended brands for live production:
- Routers / Wi-Fi APs: Ubiquiti UniFi, Cisco
- Switches: unmanaged gigabit switches are fine; managed switches help with multi-network environments
Avoid mesh systems with aggressive band-steering for camera/APC-R traffic — they introduce unpredictable handoffs.
Wi-Fi: 2.4 GHz vs 5 GHz
- APC-R / APC-R Mini Wi-Fi → 2.4 GHz only. Make sure your AP exposes a 2.4 GHz SSID. 2.4 GHz is the right band here since the APC-R only carries control data (no video).
- Video cameras → 5 GHz preferred, 6 GHz even better for Live View. The FX series performs especially well on 5 GHz.
If your access point only broadcasts a single auto-band SSID, split it into separate 2.4 GHz and 5 GHz SSIDs so the APC-R always lands on 2.4 GHz.
APC-R / Bluetooth control
Keep the APC-R close to the camera
For Bluetooth-paired cameras (Blackmagic), keep the APC-R as close as possible to the camera. Range can extend further, but smoothness degrades quickly.
Mount the antennas before powering on
Always mount the two included antennas on the APC-R before powering it on. Running without antennas can damage the radio over time. The APC-R Mini has built-in antennas — nothing to mount.
Don't double-control the same camera
If you control a Blackmagic camera over both APC-R Bluetooth and ATEM HDMI/SDI at the same time, the camera receives duplicate commands and control becomes laggy and unpredictable. Pick one path per camera and stick with it.
Use data-rated USB cables
For APC-R configuration over USB, use a data-capable USB cable — not a charging-only cable. Phone-charger cables often fail silently here.
Camera & ATEM workflow
Update firmware long before the show
Out-of-date firmware causes most "weird" behavior:
- Middle Control Software (latest)
- APC-R / APC-R Mini (via the Middle Updater)
- Camera (Blackmagic Camera Setup, etc.)
- ATEM Firmware and ATEM Software Control version
Don't update the day-of — do it 24-48 hours before, and re-test the full chain.
Set Camera IDs consistently
The Camera ID must match across:
- The camera itself (in its menu, where supported)
- The APC-R Mini (in its settings)
- The ATEM input number
- The ID selected on the Middle Control camera page
A mismatch on any one of these breaks control silently.
Engage automatic Iris / Focus clutch on lenses
If a lens has an auto-iris switch or a focus clutch, set it to automatic position before the show. Otherwise iris and focus commands will reach the lens but produce no movement.
Test ATEM camera control before connecting Middle Control
For ATEM-bridged setups, get camera control working inside ATEM Software Control first. If it doesn't work there, Middle Control can't fix it — it's an ATEM-side configuration issue.
Latency
Minimize switch hops
Each network switch adds a small amount of latency — usually unnoticeable, but it can add up on complex setups. For the most demanding rigs (live multicam with smooth gimbal control), keep your camera, APC-R, and computer on the same switch when possible.
Avoid running gimbal control over Wi-Fi
Wi-Fi adds ~10-50 ms of jitter. Camera-setting commands (iris, ISO, WB, focus) tolerate this fine. Pan / tilt / zoom on a gimbal does not — use Ethernet to the APC-R for the smoothest feel.
Pre-show checklist
Run through this 30 minutes before doors / cameras hot:
- All firmware up to date
- Camera IDs match across camera, APC-R, ATEM, Middle Control
- APC-R LEDs are correct: solid green (wired) or solid pink (Wi-Fi), with blue if Bluetooth-paired to a camera
- No double-control (APC-R Bluetooth and ATEM HDMI on the same camera)
- Test pan/tilt/zoom on every gimbal
- Test iris, ISO, WB, focus, REC trigger on every camera
- Test ATEM Camera Control panel (if using one)
- Test tally on every camera position
- Save a known-good preset on each camera so you can recall a baseline if something drifts
- Have one spare USB-C / Ethernet cable per camera position