If you're reading this you've probably seen the acronym MADRIX plastered on every LED-tutorial YouTube video and wondered what makes it the de-facto industry standard. The short answer: MADRIX is to pixel LEDs what Photoshop is to images — a complete production environment that scales from one strip on your desk to the 100,000-pixel wall at a political rally. This guide walks you through every step of your first MADRIX workflow.

1. What MADRIX actually is

MADRIX is pixel-mapping and show-production software developed by MADRIX GmbH in Germany since 2003. It's Windows-only (there is Mac support via Parallels / Boot Camp, but 95% of installations run on Windows 10/11). The current version at time of writing is MADRIX 6 (and the newer "MADRIX NEBULA" ecosystem for Art-Net).

At its core, MADRIX takes pixel sources — procedural effects, video files, text, images, audio-reactive generators — and renders them onto a pixel matrix, then sends the resulting color data out over Art-Net, sACN or DVI (via a MADRIX-brand or compatible interface). What makes it industry-standard is the MADRIX Patch — a drag-and-drop canvas where you place every physical pixel at its real-world (x,y) coordinates, so animations map onto your actual installation geometry.

2. Installing MADRIX and getting your first license

Download MADRIX from madrix.com/downloads. The installer bundles everything: core software, device drivers for MADRIX-brand USB interfaces, and the activator tool. First-run defaults are fine; just accept the EULA.

Licensing is tiered by pixel output capacity:

  • Start — 32 DMX universes = ~5,440 pixels. ~₹18,000 one-time.
  • Basic — 64 universes = ~10,880 pixels. ~₹36,000.
  • Professional — 256 universes = ~43,500 pixels. ~₹1,30,000.
  • Ultimate — 1024 universes = ~174,000 pixels. ~₹2,80,000.

Licenses are hardware-locked to a MADRIX USB key (dongle). The dongle is physical and must be plugged in whenever MADRIX runs. In 2026, "cloud license" and subscription models are still not supported — this is a dongle-first world.

Tip: buy the smallest license that fits your largest expected project and plan to upgrade later. Upgrades are tier-difference pricing (you don't pay the full new tier again).

3. The MADRIX interface at a glance

MADRIX has four primary panels you'll live inside:

  1. Patch Editor — the pixel-mapping canvas.
  2. Preview — the "LED preview" window that shows exactly what will come out of your controller.
  3. Storage — the deck/cue grid where you store your show looks.
  4. Deck Controls — layer blending, timeline, FX chain.

3.1 Building your first patch

In Preferences → Matrix Generator, specify the X and Y dimensions of your overall pixel canvas — for a 20×10 pixel strip array, that's 20 × 10. Choose the SMD type (usually RGB 24-bit) and MADRIX creates an empty matrix.

Open the Patch Editor. Drag strip after strip onto the canvas, snapping to a grid. Each strip's "data origin" (the pixel that will receive DMX channels 1–3) is marked with a small triangle — orient it correctly or your animation will play right-to-left. Save the patch with the project.

4. Scenes, decks and layers

MADRIX uses a scene metaphor similar to Ableton Live's clip grid. Each "slot" in the Storage panel holds one scene. A scene is a stack of layers; each layer runs an FX. Layers blend top-down using Photoshop-style blend modes (Normal, Add, Multiply, Screen...).

Try this: in Storage slot 1, add Layer 1 → "SCE 2D Color Scroll". Add Layer 2 → "AUD Spectrum", set blend mode to "Multiply". You now have a color-scrolling effect masked by live audio spectrum — a very useful club-floor look that took us 90 seconds to build.

5. Pushing pixels out the door

Three main output paths from MADRIX:

  • Art-Net / sACN over Ethernet. Preferred for anything >10 universes. Device → Network Settings → add a new Art-Net device, specify broadcast or unicast target. Patch MADRIX universes onto your pixel controllers (Advatek, Falcon, SandDevices).
  • DVI output. MADRIX can render straight to a video output and send to Novastar/Linsn LED processors, where your P3/P6 wall accepts video rather than pixel data.
  • MADRIX USB (NEO/USB Pro). Small-scale installations up to ~2 universes per key. Plug-and-play.

6. Building your first full show file

Let's assemble a complete, repeatable 5-scene show for a wedding backdrop:

  1. Open MADRIX, create a 50×20 pixel matrix (1,000 pixels total).
  2. Patch 20 strips of 50 pixels each, serpentine wiring (every other strip reversed).
  3. Scene 1 · Warm welcome. Layer 1 = SCE 2D Clouds, color palette "Golden Hour". Store.
  4. Scene 2 · Entrance. Layer 1 = SCE 2D Spiral, speed 20%, palette "Rose Red". Store.
  5. Scene 3 · First dance. Layer 1 = AUD Spectrum, color "Soft Pink". Layer 2 = SCE Starfield, blend "Add". Store.
  6. Scene 4 · DJ drop. Layer 1 = AUD Equalizer, "Rainbow". Layer 2 = SCE Shape Burst, blend "Add", triggered by bass. Store.
  7. Scene 5 · Grand exit. Layer 1 = SCE Pulse white strobe, 2Hz. Store.
  8. Save project as .mdxs on a USB drive. Test on-site before the show.

7. Common beginner mistakes

  • Patching in the wrong orientation. Always test with "Universe test" (full white per universe) before loading real effects.
  • Running MADRIX on a laptop plugged into shaky venue power. Use a UPS. Always.
  • Forgetting the dongle at home. Our #1 wedding-day panic call. Buy a backup dongle for every working MADRIX programmer.
  • No failover. Have a second laptop pre-loaded with the same show file, ready to patch in via Ethernet switch.
  • Changing the show at the venue. Build and lock all show files 48 hours before the event. Last-minute edits = last-minute bugs.

8. Where to go next

Our two-part MADRIX Basic and MADRIX Advanced courses walk you through every panel at play-pace with real wedding, concert and corporate project files. If you've skimmed this article and want to go deep — those are your next stop.

#madrix #led #pixel-led #koshi-academy