DMXRouter 1.7.6

Engine Groups

Process engines can now be organized into collapsible groups for managing large configurations.

• Create groups — right-click any engine(s) → Move to Group → New Group, or select an existing group name
• Multi-select support — select multiple engines (Ctrl/Shift+click) and move them to a group in one action
• Collapsible headers — double-click the group header to expand/collapse; state is preserved across refreshes
• Group color coding — right-click a group header → Group Color to assign a color from 9 presets (Red, Orange, Yellow, Green, Cyan, Blue, Purple, Pink, White). A vertical color bar appears on the group header and all its member engines for quick visual identification
• Reorder engines — right-click an engine → Move Up / Move Down to reorder within its group
• Reorder groups — right-click a group header → Move Group Up / Move Group Down to change the visual display order. Group order is independent of alphabetical sorting
• Group management — Rename Group, Remove Group (engines are kept, just ungrouped)
• Tristate group checkbox — enable/disable all engines in a group with one click. Partial state shown with a diagonal split indicator when some engines are on and others off
• Bulk operations — selecting a group header includes all its engines for Remove, Reroute, Rename, Uni+/Uni−
• Inheritance — new engines (Add, Templates, Clone) automatically join the group of the currently selected context
• Visual hierarchy — groups appear above ungrouped engines (like folders before files), with a subtle separator line after the last engine in each group
• Full-row hover — mouse hover highlights the entire row across all columns, including group headers (with lightened group background)
• Profile persistence — group assignments, display order, collapsed state, and color assignments are all saved and restored with profiles
• Web API — group field exposed on GET/POST/PUT /api/engines

How it works

The engine list uses a redesigned table with group header rows. Engines without a group appear as standalone items below the groups. Grouped engines appear indented under their collapsible group header, which shows the group name, member count, and an expand/collapse arrow.

Groups are purely organizational — they don't affect routing, merge processing, or output priority. Engine numbering follows the global config order, which can be changed with Move Up/Down.

Engine Reordering

• MergeEngine::moveConfig(from, to) — new method to reorder process engines. Atomically moves a config in the internal vector and re-indexes all state maps (backup, crossfade, switch, master/limit, data loss, failsafe scenes, rate limiter)
• Move Up / Move Down — available in the engine context menu, respects group boundaries (engines can only move within their own group or among ungrouped engines)
• Disabled at boundaries — Move Up is grayed out for the first engine in a group, Move Down for the last

Fixture Database — Scan Mode & Import

New tools for rental companies and large installations that need to link physical fixture serial numbers and asset IDs to RDM devices.

Scan Mode (barcode workflow)

Walk through every fixture in the database that doesn't have a serial number yet. The selected fixture blinks (RDM Identify On), the cursor jumps to the Serial field, and a USB barcode scanner can type the number and press Enter — DMXRouter saves the serial, turns Identify Off, and auto-advances to the next fixture. Click Stop Scan at any time.

Import DB (CSV / Excel)

Import serial numbers and rental/asset IDs from external inventory software (Rentman, custom spreadsheets). Supports CSV files with automatic separator detection (comma, semicolon, tab) and Excel .xlsx files. A column mapping dialog lets you choose which columns in your file correspond to Serial Number and Rental ID, with a preview of the first rows. After import, a report shows how many fixtures were matched and lists unmatched serial numbers.

Manual fixture entries

Right-click the fixture table → Add Entry to create a fixture record that isn't tied to an RDM device. Useful for non-RDM equipment or pre-populating the database before a show. Manual entries use a synthetic UID (0000:xxxxxxxx) and allow editing the Manufacturer and Model columns directly in the table.

VLAN — Cross-Platform Profile Fix

Loading a VLAN profile saved on Windows onto a Mac or Linux machine no longer loses the VLAN 1 (Management) IP address. The physical adapter name is now preserved when the profile originates from a different platform.

---

Platform Availability

Windows

Download and run DMXRouter-Setup.exe. All dependencies included. UAC will prompt for administrator privileges automatically if your account has them — this enables VLAN management without needing to right-click "Run as administrator".

VLAN management requires Windows Pro/Enterprise with Hyper-V enabled.

Linux

Download the binary for your architecture:

• DMXRouter-v1.7.6-linux-x86_64.zip — standard PCs and servers
• DMXRouter-v1.7.6-linux-arm64.zip — Raspberry Pi 4/5, Orange Pi, ARM64 boards

Qt6 runtime required:

# Ubuntu / Debian / Raspberry Pi OS
sudo apt install libqt6core6 libqt6gui6 libqt6widgets6 libqt6network6 libqt6websockets6 libqt6openglwidgets6

# Fedora
sudo dnf install qt6-qtbase qt6-qtwebsockets

# Arch
sudo pacman -S qt6-base qt6-websockets

Then: chmod +x DMXRouter && ./DMXRouter

VLAN management requires NetworkManager (sudo apt install network-manager if not present). No need to run as root — the app prompts for your password when needed. VLANs persist across reboots.

macOS

Download the .app bundle (Qt6 frameworks bundled). Requires macOS 13.0 (Ventura) or later.

First launch: macOS quarantines apps downloaded from the internet. Double-click install.command (shipped alongside the app) to remove the quarantine and sign it locally — you only need to do this once. Alternatively, run manually in Terminal:

xattr -cr DMXRouter.app
codesign --force --deep --sign - DMXRouter.app

Important: Disable the macOS Application Layer Firewall for reliable real-time DMX operation (System Settings → Network → Firewall → OFF). If you need firewall protection, use PF (pfctl) instead — see the v1.5.6 release notes for details and example rules.

No need to run with sudo — the app prompts for your password when needed. VLANs appear in System Settings → Network and persist across reboots.