The desktop application runs natively on Windows 10/11 (64-bit) and macOS (Intel and Apple Silicon). The Android app is a remote control for a running desktop installation — it does not run the audio-analysis or rendering engine itself, so it does not need this hardware. The figures below are engineering sizing guidance, not certified minimums or guaranteed performance: your result depends on the GPU, output resolution, effects, media and connected hardware, so rehearse your actual setup before a show.

Chapter 1: Start Here

If you only remember four things, remember these.

The app also keeps DMX, MIDI, HID and the embedded HTTP/WebSocket/MCP servers on their own threads. A weak CPU will not crash it, but it shows up as analysis jitter and MIDI-to-visual latency creeping above the sub-millisecond target. Related reading: Audio Setup & Beat Sync, MIDI & HID Controllers.

Chapter 2: Computer: Minimum And Recommended

Most Intel/AMD chips from the last six or seven years already support AVX2. The recommended column is not required to run the app — it is the column that keeps multi-layer shows smooth for hours.

Chapter 3: Graphics Card: The Real Bottleneck

Every visual layer — waveforms, spectrum and XY visualizers, the vinyl disc, particles, virtual lighting, GLSL shaders and marquee text — is rendered through Qt's hardware-accelerated engine (OpenGL/Vulkan on Windows, Metal on macOS). Integrated graphics can comfortably handle one background plus one visualizer; the moment you stack several audio-reactive layers, a particle system and a video background at once — a typical live-performance setup — a discrete GPU is what keeps the frame rate smooth.

If you are choosing between upgrading the CPU or the GPU on a tight budget, upgrade the GPU — it is what carries the visual workload on every single set. Do not assume a particular card guarantees a frame rate: start at the output resolution you will actually use, then add layers one at a time while watching for dropped frames. More detail: Visualizers, Layers, Shaders & FX.

Chapter 4: Audio Interface

The audio-analysis engine needs a real, continuous signal to analyze — BPM, key, energy, structure and event detection all depend on it. Your built-in laptop microphone is not a viable source for a live set: you need a proper line-level input carrying the signal from your mixer, controller or media player.

Recommended input paths

1. An external USB audio interface (Focusrite Scarlett, Behringer UMC, PreSonus AudioBox, RME Babyface, or similar) fed by your mixer's booth/master out.
2. A DJ controller/mixer with a built-in class-compliant USB audio output (most Pioneer, Denon, Native Instruments and Numark units qualify).
3. A software loopback device capturing your player's output directly — Windows: a virtual audio cable/WASAPI loopback; macOS: BlackHole or Rogue Amoeba Loopback.

What to look for

• Class-compliant USB audio on Windows (WDM/WASAPI) or Core Audio on macOS — no exotic proprietary drivers.
• Low, stable input latency: the analysis engine reacts within a ~46 ms FFT window, so a jittery driver undermines beat/drop accuracy.
• A dedicated line/aux input separate from your monitoring output, so you are not fighting for the same channel.
• A level that is neither silent nor clipping. A built-in microphone can be used for a quick test, but room noise gives inconsistent results.

Step-by-step device selection and the silence detector: Audio Setup & Beat Sync.

Chapter 5: USB-DMX Controller

DjMirror Pulse auto-detects supported USB-DMX interfaces by port and VID/PID — plug one in and it is ready, with no manual protocol configuration. Every interface exposes one or more universes of 512 channels each, routed to your fixtures by outputPort + universe. Several interfaces can run at once, so your lighting rig can grow with you. Windows sometimes reports an FTDI interface only as "USB Serial Port"; in that case select the controller type by hand or use Detect Protocol.

Two universes: the published requirements page lists the Enttec Pro Mk2 as a two-universe interface. In the current build only port 1 is driven (the secondary port labels require a vendor key), so for two 512-channel universes use a DMXKing ultraDMX2 Pro or two single-universe interfaces on separate USB ports.

Just getting started? A single Enttec Open DMX USB or a DMXKing ultraDMX Micro is plenty to drive a handful of PARs and a moving head for your first live rig — both are auto-detected the moment you plug them in.

Running a full show? Go for a DMXKing ultraDMX2 Pro, or connect two single-universe interfaces on separate USB ports. Keep each USB-DMX interface on a stable, dedicated port — avoid re-enumeration through a cheap hub mid-set, and close QLC+, FreeStyler or vendor utilities, since only one application can hold the serial port at a time. Patching and diagnostics: DMX Rig Configuration.

Chapter 6: Requirements Added By Optional Features

These are additive to the tables above — size only the rows that apply to your setup.

Chapter 7: Size Your Setup To Your Show

For NDI or multi-screen use, run the connection over wired Gigabit Ethernet rather than Wi-Fi: NDI is bandwidth-intensive, and a wired connection on the same LAN segment as your receiver avoids dropped frames. Test the actual venue network and receiver setup — Multi-Screen & Client-Server.

Chapter 8: The Android App

DjMirrorPulse for Android is a remote control for your desktop install (Windows or macOS). It does not run the audio-analysis or rendering engine itself, so it does not need the hardware in this guide. What it does need:

• DjMirror Pulse running on your PC/Mac, with the local server enabled in Settings → Mobile app ("server": true or --server) and an active license.
• Your phone and computer on the same network.
• A free phone slot for your edition: Trial/Standard 1, Professional 2, Enterprise 5.
• No pairing hardware: pair once with the one-use QR code shown in Settings → Mobile app → Pair a phone (valid 180 s), or type the short code on the phone if it has no camera. The desktop listens on its LAN address; default ports are 8080 (HTTP) and 8081 (WebSocket).

From your phone you can switch styles, toggle the visual layers, jump between playlists, and run the full DMX Scene Player — including blackout, fog/haze/strobe bursts and live per-channel sliders. Full workflow: Mobile Remote.

Chapter 9: Faq

Can I run DjMirror Pulse on a laptop with only integrated graphics? Yes, for a simple style with one background and one visualizer — that is the minimum tier. For a full multi-layer live set with particles and a video background, plan on a discrete GPU.

Do I need a dedicated audio interface if I already use a DJ controller? If your controller exposes a class-compliant USB audio output, that is all you need — route its master/booth channel into DjMirror Pulse as the analysis input. A separate interface is only necessary if your setup does not already provide one.

Which USB-DMX controller should I buy first? An Enttec Open DMX USB or a DMXKing ultraDMX Micro covers most first rigs. If you already know you will need two universes, go straight for a DMXKing ultraDMX2 Pro.

Is the Mac App Store version different? Yes. Because of the store's sandbox rules, the Mac App Store build leaves out NDI, local AI inference (llama.cpp), Hugging Face downloads, Ableton Link and Traktor integration. NDI and local AI are the heaviest optional features, so that build needs less hardware for the same show. Everything else follows the guidance above. Your license edition (Standard, Professional or Enterprise) is decided by your activation key, not by the build — see License & Activation.

How do I know if my computer is enough? Rehearse your intended styles, media, resolution and connected hardware together, then check for stutter, dropped frames or audio dropouts before taking it to a venue — see Troubleshooting.

Can I test before buying? Download the free trial (14 days, Standard tier) and measure on your own rig — see License & Activation.