SysDVR-Client on macOS needs no installer and no drivers: download the build for your chip, extract it, and launch. The one hurdle most Mac users hit is Gatekeeper — SysDVR is an unsigned app, so macOS may refuse to open it until you allow an exception, and on some machines you may also need to self-sign its library files. Both fixes take a minute and are covered below.
Step 1 — Pick the build for your chip
There are two separate macOS builds, and they are not interchangeable:
| Your Mac | Download | Size |
|---|---|---|
| Apple Silicon (M1, M2, M3, M4…) | SysDVRClient-MacOs-arm64.zip | About 48 MB |
| Intel processor | SysDVRClient-MacOs-x64.zip | About 49 MB |
Not sure which you have? Open the Apple menu → About This Mac: if the chip line says “Apple M…” you want the arm64 build; if it names an Intel processor, take the x64 build. Both are on the download page, which links the official GitHub release.
Step 2 — Extract and launch
- Double-click the downloaded zip to extract it.
- Open the extracted folder and launch the SysDVR-Client file.
- With SysDVR running on the console, pick your connection mode in the client — Network for TCP Bridge, or USB for a cable connection.
That is the whole setup on most machines. Receiving a USB stream on macOS needs no driver installation (unlike Windows), and network modes need nothing beyond both devices being on the same network.
If macOS blocks the app: add a signature exception
Because the app is not signed with an Apple developer certificate, Gatekeeper may say it cannot be opened or cannot be verified. The official wiki points to Apple’s own documented remedy: open System Settings → Privacy & Security, scroll to the message about the blocked app, and click Open Anyway, then confirm. You only need to do this once. Avoid blog advice telling you to disable Gatekeeper system-wide — the per-app exception is enough and much safer.
If it still won’t run: self-sign the dylib files
On some machines the app is allowed but its bundled libraries are rejected. The official fix is to self-sign the dylib files. Open Terminal inside the runtimes/osx-…/native folder of the extracted client (the folder name starts with osx- and matches your chip — there is only one, so you can’t pick wrong), then run:
codesign --remove-signature -v *.dylib
codesign -s - -v *.dylibThe first command strips the existing signatures, the second applies an ad-hoc signature your own Mac trusts. Relaunch the client afterwards. This is a local signature for your machine only — it doesn’t modify what the app does.
Version matching still applies
As on every platform, the client version must match the sysmodule version on the console — v6.3 with v6.3. If you update the console side, download the matching Mac build too, and reboot the console after updating it. If you haven’t installed the console side yet, start with the SysDVR install guide.
One more reassurance if you’re coming from Windows guides: there is no macOS equivalent of the MSVC redistributables step, and no .NET to install either. The zip you download is the whole application. If it runs, you’re done with installation — everything after that is connection choices, covered in the mode guides linked below.
Connecting once the client runs
With the client open and SysDVR running on the console, choose your mode. Network connects to a console set to TCP Bridge mode and finds it automatically on your local network. USB connects over a cable — and on macOS there is no driver step at all, unlike Windows. If the console list is empty, work through the boring causes first: both devices on the same Wi-Fi, the console booted more than 20 seconds ago (the sysmodule starts slowly), and matching versions on both sides.
macOS firewall prompts
macOS may ask whether SysDVR-Client may accept incoming network connections. Allow it — the client needs to hear the console’s discovery broadcast and receive the stream. If you dismissed the prompt and discovery never works, you can allow the app later under System Settings → Privacy & Security → Firewall. This is separate from the Gatekeeper “unsigned app” prompt in the steps above; a Mac can show you both, once each.
Quick troubleshooting list
- “Cannot be opened because the developer cannot be verified” → the Privacy & Security → Open Anyway exception above.
- App opens, then closes or errors on libraries → self-sign the dylib files with the two codesign commands above.
- Client opens but no console appears → same network, wait past the ~20-second sysmodule start, check version match, allow the firewall prompt.
- Stream connects but stutters → that’s connection quality, not the Mac build; get closer to the router or use 5 GHz, see the lag and desync fixes.
Keeping the Mac client updated
There is no auto-updater and no installer to re-run: updating means downloading the new zip for your chip and replacing the old extracted folder. If Gatekeeper treats the fresh copy as a new unsigned app, it may ask for the Open Anyway exception once more — annoying, but the same one-minute fix. Always update the console sysmodule in the same sitting so the pair stays on the same version.
Next steps
- TCP Bridge mode — the recommended, lowest-hassle network mode.
- USB streaming setup — lowest latency over a cable; remember USB doesn’t work while the console is docked.
- Simple Network (RTSP) mode — stream to a player like mpv with no client at all.
- Using a Linux machine instead? See the Linux client setup.