How do I connect my remote grading panel (Advanced, Mini, or Micro Panel)?

Your physical grading panel sits at your desk while DaVinci Resolve runs in the cloud. A small script on your local computer listens on port 20323 and waits for the cloud workstation to connect in to it. Because our cloud machines share a network gateway and don't have individual public addresses, the cloud connects out to *your* public IP, so your firewall has to allow that connection in.

Before you start, confirm:

• Your panel is plugged into your local computer (USB or Ethernet).
• DaVinci Resolve is installed on your local computer, at the same version as the cloud workstation.
• You can connect to the cloud workstation via HP Anyware (PCoIP).
• Port 20323 (TCP) is open inbound on your firewall and forwarded to your local workstation. Share the firewall details at the end of this section with your IT team.

Setup steps:

1. Confirm the panel works locally first. Open DaVinci Control Panels Setup on your local computer and check your panel appears. Then open DaVinci Resolve on your local computer, go to Preferences > Control Panels, select your panel model, save, and restart Resolve. Move a trackball or press a button to confirm it responds. If it doesn't respond, unplug the panel and plug it back in. Once confirmed, quit DaVinci Resolve on your local computer.
2. Run the remote panel script on your local computer. This starts the listener on port 20323. A terminal window will appear, keep it open for the whole session. The script must be running *before* you launch DaVinci Resolve on the cloud. Wait until you see the message Resolve communication is open and waiting.... The script for your operating system is:

• Mac (any panel): /Library/Application Support/Blackmagic Design/DaVinci Resolve/DaVinciRemotePanel.app
• Windows (Advanced Panel): %ProgramFiles%\Blackmagic Design\DaVinci Resolve\DaVinciRemoteAdvPanel.bat
• Windows (Micro/Mini Panel): %ProgramFiles%\Blackmagic Design\DaVinci Resolve\DaVinciRemotePanel.bat
• Linux (Advanced Panel): /opt/resolve/bin/DaVinciRemoteAdvPanel.sh
• Linux (Micro/Mini Panel): /opt/resolve/bin/DaVinciRemotePanel.sh

1. Find your public IP address. On your local computer, go to portchecker.co, your public IP is shown at the top of the page (it looks something like 77.168.12.196). Write it down.
2. Configure DaVinci Resolve on the cloud. Connect via HP Anyware, open DaVinci Resolve, and go to Preferences > Control Panels. Select your panel model, then open Advanced and add this line exactly, replacing the placeholder with your public IP from step 3: Local.Panel.Remote.Address = YOUR.IP.ADDRESS.HERE:20323. Save, then quit and relaunch DaVinci Resolve on the cloud.
3. On the cloud workstation, go to Preferences > Control Panels and set the Color Grading Panel to your panel type. The remote panel script on your local computer should report Accepted new client and USB Session started successfully, and your panel should now control Resolve in the cloud.

*The remote panel script running and waiting for the cloud to connect:*

*Add your public IP in Preferences ▸ Advanced:*

*Select your panel under Preferences ▸ Control Panels:*

Once the script is running on your local computer, you can restart DaVinci Resolve on the cloud as many times as you need, you don't have to restart the script each time.

If the panel won't connect:

1. Confirm no other session is already holding the panel. If you have another remote desktop or workstation session open, log out of it fully.
2. If portchecker.co shows port 20323 as closed, the inbound firewall rule or port forwarding isn't in place yet, share the firewall details below with your IT team.
3. If the terminal shows no activity, the script isn't running or the wrong script was used, re-run the correct script for your operating system.
4. If the panel is unresponsive after setup, double-check the public IP you entered and confirm the firewall rule with your IT team.
5. If a USB panel keeps dropping, run the script first, then unplug and replug the cable. Use Ethernet if possible.
6. If your facility's public IP address changes, notify post-support@amazonstudios.com so the connection can be re-established, and update the address in the Advanced settings.

Firewall details for your IT team: The remote panel script listens for inbound connections on port 20323 (TCP), and the cloud DaVinci Resolve instance initiates the connection outward to your public IP. Your firewall needs to allow inbound TCP traffic on port 20323 and forward it to the local workstation's internal IP address (standard port forwarding). Also confirm the rule points to the correct internal IP, that Deep Packet Inspection (DPI) isn't blocking traffic on port 20323, that no IPS rule is dropping the traffic, and that the rule applies to the correct network zone. To verify, run the script (so it shows Resolve communication is open and waiting...) and test port 20323 at portchecker.co, it should show as open.

When to contact support

If the self-service steps above don't resolve your issue, reach out to the team that handles your type of request:

ProdTech: post-support@amazonstudios.com

ProdTech manages Studio in the Cloud, including initial user onboarding, new account creation, and provisioning access to storage, workspaces, cloud workstations, applications, and tools, plus the setup, performance, and technical issues covered in this guide.

TechOps (TOPS): support@amazonstudios.com

TechOps manages your Originals Access account, and will assist you with issues around Okta sign-in/SSO problems, password resets, MFA/2FA resets (including a new phone), and account lockouts.

TechOps also handles requests for access to specific applications (such as Box, Flow Capture, or Aspera on Cloud).

When contacting us, help us resolve your issue quickly by always including:

• Your full name and account email (@originalsaccess.com).
• A clear description of the problem and the exact error message you see (a screenshot helps).
• Your show code and show name
• The show/workspace, workstation, or application involved.
• When the problem started and what you've already tried.

Please open a new request for each separate issue rather than replying to an older, resolved one, so it reaches the right team.