1
Confirm the venue setup
The agent belongs on the same computer or network segment as the cameras and production software.
Production computerWindows production PC with bundled runtime, or Mac production computer with Node.js 18 or newer. It can run beside vMix, OBS, Livestream Studio, TriCaster control tools, or another show system. Recommended: modern dual-core CPU or better and 8 GB RAM.
Venue agent runtimeThe Windows launcher includes its runtime. The current Mac launcher requires Node.js 18 or newer until the Mac runtime package is finalized.
PTZ camera networkVISCA/IP cameras reachable from the venue computer. MRC is not OBSBOT-only; OBSBOT Tail-series, Minrray-style VISCA/IP, and other compatible PTZ cameras can work when they answer supported commands. A wired gigabit camera LAN is strongly recommended for live shows.
Internet pathStable outbound internet for previews, invites, comms, and the remote camera-op browser. PTZ commands are low bandwidth; preview and audio quality drive bandwidth.
Audio sourceNDI Program, NDI AUX, or another supported confidence feed from the show output.
Remote operatorModern Chrome, Safari, or Edge browser on desktop, iPad/tablet, or recent iPhone/Android phones. The operator page is sized for current standard-phone, Pro Max/Ultra/XL phone, iPad, and tablet layouts. iPads and tablets are a strong remote-op choice on good networks with current browser/OS updates. The on-screen joystick works with touch or mouse. Optional Motion PTZ beta uses device motion/orientation sensors on compatible phones and tablets. Optional USB/Bluetooth gamepad support depends on the browser and operating system.
2
Install and pair the venue agent
The venue agent is the local bridge between remote operators and cameras. It should run before the show starts.
Install packageDownload the MRC venue agent after checkout, extract the ZIP, then double-click Install and Open Maverick Remote Control.cmd on Windows.
Activate from SystemOpen the venue agent console on the production computer, go to System > Activate, and paste the purchase key. BC subscribers can also connect show comms from Broadcast Control.
Keep it localCamera commands are sent from the venue computer to cameras on the local LAN for the lowest practical delay.
Health checksAgent should report camera status, preview age, audio confidence, and active operator lock.
Customer invites use the paired venue computer. Standalone users paste their purchase key into the venue agent from the browser console. BC Producer or Teams users can connect the venue to Broadcast Control so show invites and comms work without asking producers to remember network details.
3
Activate one venue computer
Base Maverick Remote Control licenses pair one venue agent to one production computer.
One active machineThe first venue agent that verifies the purchase key claims the activation for that computer.
Standalone purchase keyUse the MRC-... activation key from the checkout email when the customer only needs remote PTZ, previews, and program audio.
Broadcast Control commsProducer/Teams customers can connect this venue to Broadcast Control so remote camera operators can join show voice comms.
Safe replacementReset the standalone license or revoke the BC venue connection before moving the agent to another Mac or PC.
Copy this one-time BC activation into the venue agent console now: System > License > Activate. It is shown only once.
4
Discover, label, and test cameras
Remote operators need practical labels, not just IP addresses.
Auto scanScan likely VISCA/IP ports and show reachable PTZ cameras with make/model when available. Manual add remains available for cameras that do not advertise themselves or use unusual VISCA ports.
Manual addAllow simple IP entry with smart default ports so non-technical users are not forced to guess.
LabelsUse names like Side Cam, Rear Cam, Host Cam, Crowd Cam, or Arena Cam.
Move testConfirm pan, tilt, zoom, focus, home, stop, and presets before sending the operator link.
5
Choose program audio confidence
The remote operator should monitor the actual show audio path, not remote desktop audio.
NDI ProgramBest first choice when the switcher can publish a Program output with audio.
NDI AUXGood if the director wants a clean confidence feed separate from Program.
Switcher agnosticWorks with vMix, OBS, Livestream Studio, TriCaster, or other tools that can expose an audio confidence source.
Operator controlsThe remote page should provide start/restart, mute, level meter, and source status.
6
Connect MRC show voice comms
MRC is built to connect remote camera operators into Broadcast Control show comms. Voice comms require the Broadcast Control organization to be on Producer or Teams.
Show commsThe remote camera operator joins the same show voice room as the director and crew.
Click-to-muteThe operator clicks Mute or Unmute once, just like crew. They do not hold push-to-talk while moving cameras.
Rundown panelThe simplified show rundown can be minimized while voice stays connected.
Second screenThe operator can open the comms and rundown panel in its own browser window and drag it to another display.
BC handles the secure comms link in the background. The remote operator should only see a simple Join Comms button, not technical URLs or tokens.
7
Send one secure remote operator invite
The invite should contain everything the operator needs, without exposing venue details before verification.
Select showPick the BC show so camera control and comms stay tied to the correct production.
Secure unlockThe verified invite opens the protected venue camera console without exposing the venue password.
One operatorThe venue agent session lock blocks a second browser from taking over the base license.
Revoke/releaseDirectors can revoke invites or release a stuck operator session from BC.
When BC invite management is enabled, the director sends the secure operator link from the show page. Standalone MRC customers can use the venue-agent console to create the operator session link.
8
Try Motion PTZ beta on a phone or tablet
Motion PTZ is a beta control mode for compatible iPad, iPhone, and Android devices. It is fully operational for testing, but should be rehearsed before a show.
Open one camera full screenTap a camera preview, choose FULL, and confirm only the selected camera is under control.
Allow motion permissionTap Motion. If the browser asks for motion or orientation permission, allow it. Some devices require current browser and OS updates.
Set neutralHold the device comfortably, tap Set Neutral, then gently tilt left/right to pan and forward/back to tilt.
Choose Motion speedUse the Motion speed slider for smoother moves. Start slow, especially with fast cameras or close shots.
Motion PTZ is designed as an additional operator option, not the only control path. Keep the touch joystick and Stop All available, and test direction, speed, preview delay, and camera stop behavior before using it on a live production.
9
Run a show preflight
This is the Sunday-morning checklist before a paid operator touches cameras remotely.
Camera motionSelect every camera and test pan, tilt, zoom, focus, stop, home, and presets.
Preview healthConfirm each preview is live and frame age is low enough for operation.
Motion PTZ betaIf the operator will use device motion, set neutral, choose Motion speed, and verify left/right pan plus forward/back tilt on the selected camera.
Audio confidenceConfirm the operator hears Program or AUX audio from the venue feed.
MRC commsDirector and remote op confirm talk/listen plus mute/unmute control inside the selected show before the show starts.