Skip to main content

DMX Input and Media Servers

Use Blackout's DMX Input feature to visualize other consoles or media server input

Ian Peterson avatar
Written by Ian Peterson
Updated this week

DMX Input Setup in Blackout

DMX Input allows Blackout to receive and visualize DMX data from external consoles or media servers.

This feature is perfect for giving visualization to DPs, Gaffers, DITs, or whoever can't remember those pesky fixture numbers ;). Or, If you're working with a programmer using another console, this is a great way to see what their doing and keep up effective communication but visualizing your set in real time using a tool you already know and love.


We will also go into detail about how to use a media server like MadMapper with Blackout to make Pixel Mapping (or "Image Based Lighting" as the kids call it) a breeze. You can visualize your media server on your fixtures in Liveplot and even setup control channels to control your media server remotely with Blackout.


Basic DMX Input Setup

Prerequisites

  • Blackout

  • DMX input from a console (MA, EOS, HOG, Chamsys, ONYX) or media server

  • Network connection (Ethernet recommended)

Step 1: Import Your Patch

  1. Export from your console: Export your patch from your lighting console

    • Supported consoles: MA(2&3), EOS, HOG, Chamsys, ONYX

    • Also supports MVR export from Capture

  2. Import to Blackout:

    • Navigate to your patch in Blackout

    • Tap the "Import Patch" button at the top left

    • Select your exported patch file

    • If using custom fixture profiles, you may need to create them in the fixture database

  3. Complete the import: The patch will populate with the same addresses and fixture numbers from your console

Step 2: Network Configuration

  • Ensure all devices are on the same network

  • Use static IP addresses when possible

  • For SACN: Verify your network hardware supports multicast

  • Close any other applications reading DMX/SACN to avoid conflicts

  1. Go to Live Plot and enter edit mode

  2. Create visual representations of your fixtures using rectangles or other shapes

  3. Assign fixture numbers to match your patch

  4. Exit edit mode when complete

Step 4: DMX Input configuration

  1. Disable DMX Output (if using for visualization only):

    • Go to Link Status

    • Disable DMX output to avoid conflicts on the network

    • For 1:1 patches, no additional configuration is needed

  2. If you need universe routing -- Enable DMX Input:

    • If you need to route universes you can find these options in the DMX Input menu in link status.

  3. Change View State:

    • The view-state drop down menu is found at the top of fixtures view and Live Plot

    • Change the view state from "Output Value" to "INPUT Value" or "INPUT DMX"

    • This displays what your console is sending rather than what Blackout is outputting



Media Server Integration (Example with MadMapper)

For more advanced workflows, you can use Blackout to merge media server content with traditional lighting control. This example uses MadMapper but works with any media server.

Hardware Setup

  • Router or network switch with multicast support (for SACN)

  • Computer running MadMapper connected via Ethernet

  • Blackout iPad connected via Ethernet

  • DMX node/transmitter connected to the same network

Creating Custom Fixture Profiles

  1. In MadMapper: Create a new file with DMX output

  2. Navigate to Fixture Editor and create a new fixture

  3. Configure for media server integration:

    • Set pixel size to match your fixture's DMX Footprint

    • Mark non-RGB channels as "unused" so MadMapper only controls the color channels

    • Let Blackout control intensity, effects, and other parameters

TIP: Search for the fixture profile you want to use in Blackout, and tap the profile to see how the channels are divided. This makes setting up your profile in MadMapper a breeze as Blackout will accurately tell you what the parameter is for each DMX channel


Universe Configuration

  1. Configure Blackout:

    • Set up DMX input to receive from MadMapper's universe

      • You can either do this 1:1 or setup DMX routing.

        • 1:1 Example - In Blackout your fixtures are patched in Universe 1. Madmapper outputs to universe 1.

        • Routing Example - In Blackout your Fixtures are patched to Universe 1. Madmapper outputs to universe 21. In Blackout, you route universe 21 to universe 1 and use HTP merge.

    MADMAPPER INPUT

    • If you want to control MadMapper parameters via Blackout, Patch in the Madmapper fixture from the Blackout database or dimmers to whatever universe you set as MadMapper's INPUT universe.

  2. Set MadMapper Input Universe: I like to use a high universe number (like 100) to avoid conflicts

Advanced Control Options

DMX Masters: Set up master controls in MadMapper's DMX preferences:

Patch Dimmers to the input universe:

  • Master Level (Channel 1)

  • Hue Control (Channel 2)

  • Saturation Control (Channel 3)

Scene Control: Use MadMapper's cue system with DMX control:

  • Set up next/previous scene triggers

  • Target specific scenes with dedicated channels

You can also build a single fixture profile for MadMapper rather than using separate dimmers OR you can use the one we made in the database. Just be sure your profile channels match the control DMX Input channels in MadMapper


Best Practices

  • Use separate universes for MadMapper and traditional lighting to avoid conflicts

  • Create fixture groups in Blackout for easier control

  • Set up favorites for common color combinations

  • Use static IP addresses for stable connections

  • Test your setup thoroughly before going live

Troubleshooting

  • If SACN isn't working, verify multicast support on your network hardware

  • For Art-Net setups, pay attention to universe offset settings

  • Ensure only one application is reading SACN/DMX on the network

  • Check that all devices are on the same network segment

Web Browser Access

Once configured, you can share your live plot with others:

  1. In Live Plot, tap the QR code button

  2. Anyone on the same network can scan the QR code or use the provided URL

  3. They'll see the same live visualization in their web browser

Did this answer your question?