DjMirror Pulse system requirements
What are the DjMirrorPulse system requirements? This guide covers exactly what computer, graphics card, audio interface and USB-DMX controller you actually need to run it smoothly, from a bedroom setup to a full club rig.
DjMirrorPulse is not a lightweight slideshow app. Even before you switch on a single feature, it is already running a real-time audio FFT analysis thread and rendering GPU-accelerated shader layers — every second, on every set. That baseline workload is what makes hardware choice matter more here than on a typical desktop app. This guide breaks down the full DjMirrorPulse system requirements — the computer, the graphics card, the audio interface, and the USB-DMX controller — at two levels: the minimum to get it running, and the recommended setup for a professional live performance.
⚡ The Quick Answer
If you only remember four things, remember these.
🎮 GPU first
The graphics card is the real bottleneck, not the CPU. Every layer, shader and particle renders through it.
🎧 Real audio input
A laptop microphone won’t cut it. You need a line/loopback input carrying your mixer or player signal.
🔌 Stable USB
Keep every USB-DMX interface and controller on dedicated, stable ports — never behind a flaky hub during a live set.
💾 16 GB RAM
Comfortable for a full live rig with video backgrounds, DMX, MIDI and NDI running together.
💻 DjMirrorPulse System Requirements: Minimum vs. Recommended Computer
DjMirrorPulse runs natively on Windows 10/11 (64-bit) and macOS (Intel & Apple Silicon). The audio engine runs a dedicated real-time thread performing continuous 2048-point FFT plus BPM, key, energy and structure analysis, while DMX, MIDI, HID and the embedded HTTP/WebSocket/MCP servers each run on their own threads. A weak CPU won’t crash the app, but it will show up as analysis jitter and MIDI-to-visual latency creeping above the target of under 1 ms.
| Minimum | Recommended (live performance) | |
|---|---|---|
| Operating system | Windows 10 64-bit / macOS 11 | Windows 11 64-bit / macOS 13+ (Apple Silicon) |
| CPU | Quad-core, 2.5 GHz (Intel i5 8th gen+ / Ryzen 3 / Apple M1) | 6+ cores, 3.2 GHz+ (Intel i7 10th gen+ / Ryzen 5-7 / Apple M2-M3 Pro) |
| RAM | 8 GB | 16 GB (32 GB with local AI models or large media libraries) |
| Storage | 2 GB free, HDD acceptable | 5 GB+ free on SSD/NVMe (video backgrounds and screen recordings add up fast) |
| Display | 1280×720 @ 60 Hz | 1920×1080 @ 60 Hz or higher, dual monitor (control panel + full-screen output) |
Note on instruction sets: if you plan to use the optional local AI features (offline image generation via llama.cpp, Full edition only), your CPU needs AVX2 support — most Intel/AMD chips from the last 6-7 years qualify.
🎮 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 for hours.
| Minimum | Recommended | |
|---|---|---|
| Windows | DirectX 11 / OpenGL 3.3, 2 GB VRAM (e.g. Intel UHD 620/630 integrated) | DirectX 12 / Vulkan discrete GPU, 4-8 GB VRAM — NVIDIA GTX 1660 / RTX 3050+ or AMD RX 6600+ |
| macOS | Metal-capable integrated GPU (Apple M1 or Intel Iris Plus, 2018+) | Apple Silicon Pro/Max-tier GPU, or discrete AMD Radeon Pro on eligible Intel Macs |
| 4K video backgrounds | Not guaranteed smooth | 6 GB+ VRAM with hardware HEVC/H.264 decode |
If you’re 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, minimum or advanced.
🎧 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
- An external USB audio interface (Focusrite Scarlett, Behringer UMC, PreSonus AudioBox, RME Babyface, or similar) fed by your mixer’s booth/master out.
- A DJ controller/mixer with a built-in USB audio class-compliant output (most Pioneer, Denon, Native Instruments and Numark units qualify).
- 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’re not fighting for the same channel.
🎛️ USB-DMX Controller
DjMirrorPulse auto-detects supported USB-DMX interfaces by port and VID/PID — plug one in and it’s ready, no manual protocol configuration. Every interface exposes one or more universes of 512 channels each, routed to your fixtures by outputPort + universe. You can run several interfaces at once, so your lighting rig can grow with you.
| Interface | Universes | Best for |
|---|---|---|
| Enttec Open DMX USB | 1 | Entry-level rig, budget-friendly first controller |
| Enttec Pro DMX USB | 1 | Reliable single-universe professional interface |
| Enttec Pro DMX USB Mk2 | 2 (on one cable) | Two-universe rigs without doubling your USB ports — our top recommendation for most live setups |
| DMXKing ultraDMX Micro / Pro / 2 Pro | 1-2 | Compact, auto-detected multi-output setups |
| Eurolite DMX Pro v2 | 1 | Widely available in the EU lighting market |
| SoundSwitch Micro DMX Interface | 1 | Musicians/producers already in the SoundSwitch ecosystem |
| FreeStyler USB DMX / generic FTDI | 1 | Budget and DIY-friendly interfaces |
| DMXIS | 1 | Combined controller + interface hardware |
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 — and both are auto-detected the moment you plug them in.
Running a full show?
Go for an Enttec Pro DMX USB Mk2, 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.
⚙️ Size Your Setup to Your Show
Not every gig needs the same rig. Use this checklist to match the DjMirrorPulse system requirements to what you’re actually going to do on stage.
| Tier | Typical usage | What it drives |
|---|---|---|
| Basic | Single visual layer (images + waveform), no external hardware | Minimum spec is enough |
| Standard live | Multiple layers, particles/shaders, a MIDI controller, one USB-DMX interface | Recommended spec |
| Advanced production | 1080p/4K video backgrounds, several DMX universes across multiple interfaces, NDI output, screen recording, and/or local AI running together | High-end recommended spec + wired Gigabit network + SSD/NVMe storage |
One more thing worth planning for if you’re pushing NDI output: run it 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 during the stream.
❓ DjMirrorPulse System Requirements: Frequently Asked Questions
Can I run DjMirrorPulse on a laptop with only integrated graphics?
Yes, for a simple style with one background and one visualizer — that’s 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’s all you need — route its master/booth channel into DjMirrorPulse as the analysis input. A separate interface is only necessary if your setup doesn’t 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’ll need two universes, go straight for an Enttec Pro DMX USB Mk2.
Does the Lite (Mac App Store) edition need less hardware?
Slightly — Lite disables NDI and local AI inference at compile time, which are the two heaviest optional features. In practice, the Lite edition matches the Basic/Standard tiers above without the Advanced-tier additions.
Got the hardware? Time to try it.
Now you know the DjMirrorPulse system requirements — download the free trial and see how it performs on your own rig, no credit card required.
Windows 10/11 x64 – MacOS Arm64 (M2, M3, M4 compatible)
Hardware figures on this page are engineering sizing guidance based on DjMirrorPulse’s real-time workload (continuous audio analysis, GPU-shader rendering, optional DMX/MIDI/HID/NDI and local-AI features) and should be treated as a starting point rather than a certified benchmark for every possible combination of styles and add-ons.
