DMXRouter 1.9.4

Process Engine

• New failsafe mode: Stop Output — when every input to a Process Engine is lost, the engine can now cease transmitting packets entirely instead of holding, blacking out, or playing back a scene. This is the missing piece for touring setups where opening acts route their feeds through DMXRouter on a side VLAN and the main show should regain the rig the instant they disconnect: the engine goes silent on data loss, any other source on the same universe (typically the main show at a lower sACN priority) takes over automatically, and when the opening act's feed returns the engine picks back up without operator intervention. Selectable alongside Hold Last State / Blackout / Full On / Playback Scene in each Process Engine's failsafe configuration. The existing modes are unchanged

Fixture Check

• Walk-the-rig inside a multi-selection — select several fixtures and Next / Previous now step through them with wrap at the ends instead of escaping into the rest of the rig, matching how every lighting console handles a "selected group" walk. Only the active fixture gets the strong selection styling and has its channel sliders shown, so moving a slider during the walk only affects the one head you're looking at. The other group members stay visible in the Patch tree with a subtle tint so you can see the group membership at a glance. When Highlight is active on the selection, the first Next / Previous press anchors the walk at the primary (or last) fixture, releasing the others — so the first press doesn't visibly skip past your starting head. Subsequent presses then step normally through the group
• Auto-Next auto-walk — new ▶ toggle button next to Next in the Fixture Check toolbar, with a spinbox for the interval (0.1–30 seconds, remembered between sessions). Click the toggle and the walk runs automatically on the timer, cycling through the current selection with Highlight propagation like the manual walk. Ideal for hands-free focus checks and for verifying every head in a group without having to tap Next for each one. Stops automatically if you narrow the selection, hit Release All, or change the patch, so it can't keep stepping through a context that no longer exists
• Next / Previous follow the sort order of the Patch tree — when walking with no multi-selection, Next and Previous now step in the same order the fixtures appear in the Patch tree. Sort the tree by FID and the walk goes 1 → 2 → 3…; sort by Address and it goes U1/1 → U1/10 → U2/1…; switch back to MVR order and the walk follows that too. The walk always matches what you see on screen

Fixture Patch

• Sort the patch tree by column — click any column header (FID, Name, Type, Address, Mode) to sort within each layer group. Click the same column again for descending, and once more to return to the original MVR import order. Arrows ▲ / ▼ appear on the active column's header so the current sort is always visible. Sort applies within each layer group rather than across the whole tree, so groups stay organised by their MVR layer. Your preference is saved between sessions. Numeric columns (FID, Address) sort numerically so U2/1 comes before U10/1 as expected

GDTF Share

• Fixture preview panel in Browse GDTF Share — selecting any fixture in the browse dialog now shows an instant preview on the right-hand side: modes with their channel footprint, manufacturer, revision, GDTF version, file size, last-modified date, and the UUID (selectable for copying into a bug report or another tool). No need to download the file first to see whether it fits — if the mode you need is there with the expected channel count, you know before you commit. Fixtures you already have in your library are flagged with a green "In library" badge. The preview panel is collapsible if you prefer the old list-only view, and its width is remembered between sessions

RDM Transaction Log

• Separate PID number and PID name columns — the log now shows the hex PID (0xNNNN) in a dedicated column alongside the PID Name, matching the format used by the Slots and Status Messages tables elsewhere in the RDM panel. Easier to cross-reference with manufacturer documentation, easier to see at a glance what the transaction was. The search box now matches against the hex PID too, so typing "0x0060" or "SET_INFO" both find the same rows
• Export the transaction log — new Export button in the log toolbar with Save as CSV… and Copy to clipboard, mirrored as a right-click menu on the log table itself. Only visible rows are exported, so the active search and Failures-only filter control what ends up in the output — filter down to the problem fixture and export just its transactions for a bug report. The CSV is RFC 4180 with a UTF-8 BOM so Excel on Windows opens it correctly with non-ASCII device names intact; the clipboard copy is tab-separated for direct paste into Excel, Google Sheets, or a Slack code block

RDM Workflow

• Set address from patch — right-click any identified RDM device in the device tree and choose "Set Address From Patch…". A picker opens with every addressable fixture from the loaded MVR, grouped by layer, with the same FID / Name / Type / Address / Mode columns you already know from the Fixture Patch tree. The filter box is pre-filled with the RDM device's manufacturer and model so the likely candidates surface first; typing narrows the list live. Pick a fixture, hit Enter, and its DMX start address is pushed to the RDM device via SET_DMX_START_ADDRESS — no bouncing between the RDM panel and Fixture Check to look up the number. The typical workflow becomes: identify the head on the rig, right-click, pick its MVR entry, done
• Devices reconnect without re-fetching everything — when a device times out (cable pulled, switch reboot, gateway hiccup), DMXRouter now keeps the static info it already collected — manufacturer, model, personality list, slot map, boot software, language, presets, and so on. When the device reappears in a TOD, that info is restored instantly and only the DMX start address and active personality are re-queried (one PID, milliseconds), instead of running the full ~25-PID sweep again. On a rig of 20 heads coming back online after a brief disconnect that's the difference between a 30-second wait and an instant reconnection. The cache holds up to 2000 devices per session and is dropped on Force Discovery so a deliberate refresh is still genuinely fresh
• Quick-select mode — new "RDM quick-select (skip advanced info)" toggle in the View menu. When enabled, selecting an RDM device only fetches what you need to change channel and personality — basic info plus the personality list — instead of also pulling boot software, language, presets, curves, response time descriptions, and the rest. Cuts the wait between selecting a device and being able to act on it from a couple of seconds to nearly nothing. Advanced fields stay empty in the Info tab until you turn the toggle off and re-select, or use Fetch All to populate them. Default is off, so the existing behaviour (everything populated on selection) is unchanged unless you opt in

Mobile / Web

• Walk-the-rig from a tablet — the web Fixture Check tab now mirrors the desktop's walk-the-rig workflow. Tap any fixture to open its detail pane, then tap the new ▶ Walk button between Prev and Next: the rig starts cycling automatically from that fixture in the same order Prev / Next would step through, with Pause and End Walk available on the bar that appears at the top. For a curated subset rather than the whole rig, tap "Pick…" next to Walk — the list switches to checkbox mode, tap the fixtures you want included, hit Start Walk on the bar at the top. Both surfaces stay in sync: a Next from the tablet rotates the walk on the desktop, and vice-versa, so two operators can work the same rig together — one on the booth machine and one walking the truss — without stepping on each other
• Walk follows the desktop's sort — when the booth operator has the patch tree sorted by Address, FID, or Name, the walk on every connected tablet advances in that same order. The two surfaces stay coordinated regardless of what column the operator was sorting by, so the head lighting up next is always the one anyone would predict from looking at the desktop screen
• Sort the fixture list on the tablet — new "Sort: …" chip alongside the existing filters cycles through MVR / Address / FID / Name. Saved per browser so the tablet remembers your preferred view between sessions. Sort applies within each layer group, matching the desktop's sort behaviour
• Auto-Next from a tablet — the same ▶ toggle and interval input the desktop has appear in the walkbar when a walk is active. Tap the toggle and the walk runs on the timer; edit the interval and the change applies live (no stop-and-restart). State is shared, so pausing on the desktop pauses on every connected tablet too
• Set address from patch on a tablet — every RDM device row in the web RDM tab now has a "From Patch…" button next to the existing Set address button. Tap it to open the same fixture picker the desktop has, with the search pre-filled to the device's model so the right candidate surfaces first. Tap the fixture and the address is pushed. Same workflow as the desktop, available on whatever tablet the operator is carrying around the rig

Session Recovery

• Imported MVR survives a restart — closing DMXRouter with an MVR loaded but no Process Engine configured used to silently drop the patch on the next launch: every save path that touched disk (auto-save, the close-time session file, the close-time "save unsaved changes" prompt) had a guard that required at least one engine before writing anything, so MVR-only workflows (commissioning, addressing, fixture review) never persisted. Now the patch is preserved alongside engines, cues, and the rest of the session state across all three save paths. Open the app, import the MVR, work with it, close — next launch it's all still there

• Multi-selection across MVR layers walks in visible order — selecting fixtures across two or three layers (e.g. front truss + side truss + balcony) and pressing Next / Previous used to step through them in a confusing zigzag pattern: all of layer A's selected fixtures, then all of layer B's, then back across, regardless of where they appeared on screen. Qt's selection model groups items by their tree parent rather than by visual position. Now the walk follows the order you see in the Patch tree, top to bottom, including any active column sort. Same fix applied to Select All so an Auto-Walk over the whole rig steps in row order rather than in random hash-bucket order

---

DMXRouter v1.9.4 — Built for the stage.