[Feature Request] Control over Merge Mode Switch in Software

[Quphoria]

Currently using Merge Mode Switch allows you to use a DMX channel to control the merge source

It would be nice for an option to control the source in the DMXRouter software itself and over the HTTP API / Web Interface

This would allow some nice flexibility to use scheduler/automation software to select the merge source over the REST API

(It would also be nice to be able to do this on groups of process engines so you could switch multiple universes from one source to another)

[fiverecords]

Thanks for the suggestion — this is a great use case.

Planned for next release.

• Software-controlled Switch: a new option alongside the existing DMX control channel, letting you select the active input directly from the GUI.
• REST API: a runtime endpoint to switch the active input per engine, independent of the engine configuration. Something like POST /api/engines/:index/switch with {"activeInput": 1}.
• Web UI: switch control accessible from the web interface as well.
• Group switching: leverage Engine Groups to switch multiple engines at once via a single API call.

The DMX control channel option will remain available — this adds a software override path on top of it.

No ETA yet but it's on the roadmap. I'll update this issue when it ships.

[fiverecords]

Implemented in v1.7.8.

Software switch is now available from the desktop GUI (right-click → Switch Input), the Web UI (per-engine and per-group buttons), and the REST API:

• POST /api/engines/:index/switch — body: {"activeInput": 0}
• POST /api/groups/:groupName/switch — body: {"activeInput": 0}

The active input is shown in real time in both the routing table and the Web UI. The switch state is runtime-only and not persisted in profiles — it resets to Input 1 on startup.

Thanks for the suggestion.