Top 10 Best Etc Software of 2026

GITNUXSOFTWARE ADVICE

General Knowledge

Top 10 Best Etc Software of 2026

Ranked top 10 etc software picks for teams, including Notion, monday.com, and Trello, with workflow notes and tradeoffs.

31 min readUpdated AI-verified · Expert reviewed
How we ranked these tools
01Feature Verification

Core product claims cross-referenced against official documentation, changelogs, and independent technical reviews.

02Multimedia Review Aggregation

Analyzed video reviews and hundreds of written evaluations to capture real-world user experiences with each tool.

03Synthetic User Modeling

AI persona simulations modeled how different user types would experience each tool across common use cases and workflows.

04Human Editorial Review

Final rankings reviewed and approved by our editorial team with authority to override AI-generated scores based on domain expertise.

Read our full methodology →

Score: Features 40% · Ease 30% · Value 30%

Gitnux may earn a commission through links on this page — this does not influence rankings. Editorial policy

This roundup compares ETC-centric software used for stage lighting control, programming, and electrical commissioning and test reporting, with emphasis on configuration accuracy, automation paths, and auditability. The ranking favors tools that fit specific team workflows, from operator console environments to field capture and device monitoring, so evaluators can compare execution, not marketing claims.

If you’re a touring or install lighting team sharing one programming workflow between Windows stations and NX consoles, ONYX is the best fit, whereas Avolites Titan suits teams that need deeper console programming plus integrated media-server playback, and Martin M-PC is the budget-friendly entry if you want portable offline Martin show work before venue access.

Editor’s top 3 picks

Three quick recommendations before you dive into the full comparison below — each one leads on a different dimension.

Editor pick
1

ONYX

DYLOS pixel-control engine creates layered effects within the same ONYX programming environment.

Built for fits when touring lighting teams need one workflow across Windows programming stations and NX control consoles..

2

Avolites Titan

Editor pick

Synergy triggers Avolites Ai media-server content alongside Titan lighting playbacks from one show control workflow.

Built for fits when touring and production teams need deep console programming with integrated media-server playback..

3

Martin M-PC

Editor pick

Windows-based access to the Martin M-Series programming and playback environment.

Built for fits when lighting teams need portable Martin show programming before venue access..

Comparison Table

1
ONYXBest overall
SMB
9.4/10
Overall
2
enterprise
9.0/10
Overall
3
8.7/10
Overall
4
vertical specialist
8.4/10
Overall
5
API-first
8.0/10
Overall
6
7.7/10
Overall
7
7.3/10
Overall
8
vertical specialist
7.0/10
Overall
9
vertical specialist
6.6/10
Overall
10
enterprise
6.3/10
Overall
#1

ONYX

SMB

Lighting control software for live entertainment, installation, and event applications.

9.4/10
Overall
Features9.1/10
Ease of Use9.6/10
Value9.5/10
Standout feature

DYLOS pixel-control engine creates layered effects within the same ONYX programming environment.

ONYX provides fixture creation tools, configurable playback pages, macros, effects, and show-file transfer between compatible Windows and NX systems. DYLOS adds layered pixel effects without requiring a separate programming environment for standard lighting looks. The software also supports Art-Net and sACN for network-based distribution across larger systems.

The broad control surface requires practice with playback organization, effect parameters, and console-specific hardware workflows. PC-based operation also requires compatible output hardware for physical DMX512 transmission. ONYX fits touring teams that build shows on a laptop and later operate them from an NX console.

Pros
  • +DYLOS creates layered pixel effects inside the main programming environment
  • +Shared show files transfer between Windows PCs and NX consoles
  • +Fixture Builder supports custom fixtures and unavailable library entries
  • +OSC and MIDI inputs support external triggering
Cons
  • Advanced programming requires familiarity with playback pages and effect controls
  • Physical DMX512 output requires compatible external hardware
  • Capture visualization introduces a separate application workflow
  • Non-lighting production teams gain little from the feature set
Use scenarios
  • Touring lighting crews

    Build shows on laptops, operate on consoles

    Consistent touring show workflow

  • Concert lighting programmers

    Create layered pixel looks

    More complex pixel effects

Show 1 more scenario
  • Small venue operators

    Control networked lighting rigs

    Repeatable venue operation

    ONYX routes lighting data through network protocols and organizes playback controls for recurring events.

Best for: Fits when touring lighting teams need one workflow across Windows programming stations and NX control consoles.

#2

Avolites Titan

enterprise

Lighting console software for entertainment and stage lighting control.

9.0/10
Overall
Features9.3/10
Ease of Use8.8/10
Value8.8/10
Standout feature

Synergy triggers Avolites Ai media-server content alongside Titan lighting playbacks from one show control workflow.

Large productions can build reusable showfiles with playback pages, palettes, macros, and customized workspace layouts. Titan supports DMX512 output, Art-Net networking, MIDI, OSC, and remote operation through Titan Remote. Its personality system provides detailed fixture control for conventional fixtures, moving lights, LED products, and media-oriented devices.

Programming requires familiarity with Avolites terminology, page-based playback, and console navigation. The workflow suits festivals, concerts, and theatrical productions that need fast live edits, but it is less appropriate for teams needing browser-based collaboration or shared project documentation.

Pros
  • +Synergy connects Titan playbacks with Ai media-server cues
  • +Key Frame Shapes generates layered effects across fixture parameters
  • +TitanNet supports multi-console show control and backup workflows
  • +OSC, MIDI, and macro controls support external automation
Cons
  • Console-oriented terminology creates a steeper learning curve for software-only operators
  • Browser-based multi-user editing is not Titan's primary workflow
  • Complex showfiles require disciplined page, playback, and macro organization
  • Media-server integration depends on the Avolites Ai ecosystem
Use scenarios
  • touring lighting crews

    festival cue playback

    Faster artist changeovers

  • concert production teams

    lighting and video synchronization

    Synchronized lighting and video

Show 2 more scenarios
  • lighting programmers

    complex fixture effects

    Reusable dynamic effects

    Key Frame Shapes applies timed parameter movements without building every step as a separate cue.

  • production system operators

    redundant console control

    Continuity during console failure

    TitanNet links consoles for shared show data and backup control during live operation.

Best for: Fits when touring and production teams need deep console programming with integrated media-server playback.

#3

Martin M-PC

SMB

Free offline lighting control and programming software supporting DMX512, Art-Net, sACN, and RDM.

8.7/10
Overall
Features8.8/10
Ease of Use8.8/10
Value8.4/10
Standout feature

Windows-based access to the Martin M-Series programming and playback environment.

Martin M-PC mirrors the M-Series operating model on a Windows computer, including programming views, playback controls, fixture handling, and show-file operations. Programmers can prepare lighting states away from the venue and later transfer the work to compatible Martin control hardware. Martin fixture profile libraries reduce manual parameter setup for supported fixtures.

The main tradeoff is that dependable live output depends on compatible Martin interfaces or control hardware rather than software alone. M-PC fits touring programmers and small production teams that need to edit Martin shows on a laptop before arriving at the venue.

Pros
  • +M-Series programming runs on a Windows PC without requiring a dedicated console surface.
  • +Portable editing supports show preparation away from venue hardware.
  • +Martin fixture profile libraries reduce manual parameter mapping.
  • +Console-style playback provides familiar control for existing Martin operators.
Cons
  • Live output depends on compatible Martin interfaces or control hardware.
  • The interface favors console programming knowledge over simplified task workflows.
  • Integration centers on lighting hardware rather than general business-system connectors.
  • Third-party fixture support may require more manual verification than Martin fixtures.
Use scenarios
  • Touring lighting programmers

    Prepare Martin shows during travel

    Faster venue setup

  • Small production venues

    Run Martin-controlled lighting systems

    Lower console dependence

Show 1 more scenario
  • Lighting production teams

    Review show programming offsite

    More preproduction time

    Teams can inspect playback behavior and revise lighting states without occupying the performance system.

Best for: Fits when lighting teams need portable Martin show programming before venue access.

#4

ETC Eos

vertical specialist

Lighting control software for ETC Eos-family consoles and show-control workflows.

8.4/10
Overall
Features8.3/10
Ease of Use8.2/10
Value8.6/10
Standout feature

Eos showfile programming ties cues, patch, and fixture behavior into one continuous production artifact.

ETC Eos is electrical test and commissioning software tuned for lighting control commissioning workflows, especially console showfile management and cue building. It manages fixture profiles, patching, and channel behavior as part of show data, with configuration workflows that track changes across a production.

The tool supports integration points used in real shows, including DMX512-oriented networked control and import or export paths for show artifacts. Its strengths concentrate on showfile continuity and operational automation rather than generic work management for unrelated systems.

Pros
  • +Showfile workflows keep cue lists, timing, and changes tightly coupled
  • +Fixture profile and patch management reduces errors during dimmer configuration
  • +Lighting-specific programming tools map directly to commissioning deliverables
  • +Extensive console operations for rehearsals and offline show rehearsing
Cons
  • Commissioning documentation exports are not as structured as document-first tools
  • Network discovery and universe management depend on external venue practices
  • External automation requires more setup than general project tooling
  • Admin governance features are less granular than IT RBAC-focused systems

Best for: Fits when crews need showfile-first commissioning and repeatable console programming workflows across venues.

#5

QLC+

API-first

Open-source DMX and lighting control software for computers and compatible interfaces.

8.0/10
Overall
Features7.9/10
Ease of Use8.2/10
Value8.0/10
Standout feature

Timeline and cue sequencing inside QLC+ showfiles, designed for fast rehearsal loop playback and portability across desktops.

QLC+ performs fixture and show control from a single desktop workspace, with DMX output that can drive lighting scenes and cue sequences. It supports patching fixtures to DMX addresses and building playback via timelines and cue lists.

For ETC project management workflows, QLC+ can serve as the commissioning and visualization endpoint when those workflows need repeatable console-style playback. Its strengths concentrate on practical DMX showfile management rather than deep electrical commissioning documentation.

Pros
  • +DMX fixture patching with addressable channel mapping per project
  • +Cue list and timeline playback for repeatable scene sequences
  • +Showfile management that keeps console-style layouts portable
  • +Offline-friendly desktop execution for rehearsal and commissioning previews
Cons
  • Limited commissioning reporting compared with ETC documentation tools
  • Network discovery and topology monitoring are not the focus
  • Channel schedule and universe management stay basic for large estates
  • Extensibility depends on external tools rather than native APIs

Best for: Fits when small teams need local DMX show playback and fixture patch iteration without deep commissioning paperwork.

#6

Lightkey

SMB

Mac lighting control software for DMX fixtures, live shows, and installations.

7.7/10
Overall
Features7.7/10
Ease of Use7.7/10
Value7.6/10
Standout feature

Workflow-driven linkage between commissioning configuration records and generated documentation packages.

Lightkey is an ETC-focused workflow tool for managing lighting commissioning outputs rather than general project boards. It centers on organizing fixtures, channel mapping, and commissioning deliverables into one place so teams can align patch decisions with produced reports.

Lightkey also supports importing and exporting structured data formats for moving elements between design, patching, and handoff steps. For commissioning groups, the main differentiator is how its workflow ties configuration records to documentation artifacts used during turnover.

Pros
  • +Commissioning deliverables stay linked to configuration records
  • +Structured import and export reduce manual re-entry between stages
  • +Fixture and channel organization supports traceable handoff workflows
  • +Documentation generation supports consistent turnover packages
Cons
  • Offline or field-first commissioning support is not its strongest area
  • Automation depth is limited compared with tools that expose full extensibility via API

Best for: Fits when commissioning teams need consistent fixture mapping to produce turnover-ready documentation.

#7

EcoStruxure Power Commission

enterprise

Schneider Electric tool for configuration, testing, and commissioning of LV circuit breakers and digital switchboards.

7.3/10
Overall
Features7.1/10
Ease of Use7.4/10
Value7.5/10
Standout feature

Project-driven power documentation and reporting ties commissioning evidence to the electrical network asset context.

EcoStruxure Power Commission pairs commissioning project tracking with electrical power-centric documentation workflows, so test results and asset context stay tied to the network. It supports equipment and power distribution information management for MV and LV commissioning deliverables, including report output built around project activities. The tool also integrates with Schneider Electric ecosystems for data alignment across power systems and commissioning steps, which reduces rework when topology and equipment data change.

Pros
  • +Power distribution documentation workflows keep electrical context attached to commissioning activities
  • +Project activity tracking matches how commissioning teams produce and revise deliverables
  • +Schneider-electric ecosystem alignment reduces duplicate equipment and topology handling
  • +Report generation supports repeatable commissioning outputs from the project record
Cons
  • Best results depend on importing accurate equipment and topology inputs early
  • Commissioning tasks for non-power lighting workflows need extra coordination outside the core model
  • Advanced automation requires deeper configuration and governance than generic task tools
  • Network discovery and signal monitoring coverage is narrower than lighting-first ETC tools

Best for: Fits when electrical MV and LV commissioning needs tracked deliverables tied to asset and distribution documentation.

#8

FieldTestPRO

vertical specialist

Electrical test reporting platform for NETA-accredited inspection companies with offline field capture and client portal.

7.0/10
Overall
Features7.1/10
Ease of Use7.0/10
Value6.9/10
Standout feature

Evidence-to-report traceability ties field test outcomes directly into commissioning deliverables.

FieldTestPRO is a project and commissioning workflow tool focused on organizing field testing evidence for electrical and lighting systems. It centers on structured equipment and test record capture, then packages commissioning outputs into shareable reports.

The workflow connects test findings back to deliverables such as as-built documentation and fault logs so teams can trace issues through the project lifecycle. Admin control and automation options are aimed at repeatable reporting and consistent capture across multiple sites.

Pros
  • +Structured test record capture keeps evidence consistent across sites
  • +Traceability from findings to reporting reduces rework during commissioning closeout
  • +Report generation supports repeatable commissioning documentation outputs
  • +Equipment inventory tracking fits mixed asset sets across projects
Cons
  • Commissioning data reuse across tools is limited without export-based handoffs
  • Advanced automation needs careful configuration to match site-specific workflows
  • Offline commissioning workflows may require extra operational planning in the field
  • Complex network topology documentation workflows can be manual-heavy

Best for: Fits when teams need consistent field testing evidence capture and traceable commissioning reports.

#9

MADRIX RADAR

vertical specialist

RDM device monitoring and automatic fixture patching software with 24/7 supervision and email notifications.

6.6/10
Overall
Features6.6/10
Ease of Use6.5/10
Value6.8/10
Standout feature

RADAR’s live network monitoring ties Art-Net and sACN behavior to MADRIX-driven fixture presence to pinpoint signal failures.

MADRIX RADAR performs offline analysis and monitoring for MADRIX-based lighting control networks to surface device health and signal issues before events run. It works around RADAR’s view of the Art-Net and sACN ecosystem and can correlate controller output to fixture and receiver behavior.

The tool focuses on operational visibility for patch and showfile-driven workflows rather than authoring cue lists. MADRIX RADAR also supports configuration for network scope so technicians can narrow troubleshooting to the relevant topology and subnets.

Pros
  • +Fast fault localization for Art-Net and sACN lighting networks
  • +Operational health views map signal behavior to MADRIX lighting workflows
  • +Network scope controls reduce noise during troubleshooting sessions
  • +Designed for technical operations tied to showfile and patch changes
Cons
  • Best results depend on consistent universe and patch conventions
  • Less useful for DMX512 console-only operations without MADRIX integration
  • Does not replace full commissioning documentation exports
  • Troubleshooting workflows require network familiarity and scanning setup

Best for: Fits when lighting teams need network-level visibility to diagnose MADRIX show failures quickly.

#10

Ekip Connect

enterprise

ABB commissioning and programming software for low-voltage devices with monitoring, testing, and diagnostic functions.

6.3/10
Overall
Features6.3/10
Ease of Use6.2/10
Value6.5/10
Standout feature

ABB ecosystem alignment that keeps commissioning evidence tied to configured equipment records across install and closeout.

Ekip Connect targets electrical testing and commissioning workflows with project-centric organization and equipment documentation support. It coordinates test results, asset records, and commissioning outputs so teams can keep evidence aligned with the field activities.

The core differentiator is how ABB’s ecosystem connectivity and configuration assets reduce friction between design intent, installation, and commissioning closeout. Ekip Connect also fits teams that need repeatable reporting artifacts and structured handover packs instead of freeform note tracking.

Pros
  • +Commissioning evidence stays linked to the project and equipment records.
  • +Document outputs support consistent handover formatting across teams.
  • +ABB integration reduces translation effort between configuration artifacts and site work.
  • +Structured test capture supports faster reviews during commissioning sign-off.
Cons
  • Workflow coverage is strongest when teams align to ABB-centric project structures.
  • Deep customization requires stronger admin governance than general-purpose tools.
  • Limited fit for non-ABB ecosystems with mixed vendor fixture and device types.
  • Offline field usage depends on the deployment model and device access pattern.

Best for: Fits when electrical commissioning teams need structured test evidence and ABB-linked project documentation.

Conclusion

After evaluating 10 general knowledge, ONYX stands out as our overall top pick — it scored highest across our combined criteria of features, ease of use, and value, which is why it sits at #1 in the rankings above.

Our Top Pick
ONYX

Use the comparison table and detailed reviews above to validate the fit against your own requirements before committing to a tool.

How to Choose the Right etc software

This buyer’s guide covers electrical test and commissioning software workflows across lighting and power delivery needs, using 10 named tools as reference points. The coverage includes ONYX, ETC Eos, Avolites Titan, Martin M-PC, QLC+, Lightkey, EcoStruxure Power Commission, FieldTestPRO, MADRIX RADAR, and Ekip Connect.

The ranking emphasizes integration depth, showfile and documentation coupling, automation and API surface where present in the workflow, and admin control patterns tied to commissioning evidence. Notion, monday.com, and Trello are included because teams often use them as ETC project management backbones for cue lists, approvals, and handover tracking.

etc software for commissioning evidence, patching workflows, and operational network control

etc software coordinates commissioning outputs by tying together fixture patching, cue sequencing, and evidence capture into artifacts teams can reuse across venues and install phases. ETC Eos anchors this workflow by coupling cue lists, timing changes, patch, and fixture behavior into one Eos showfile so revisions stay tied to the same production object.

Some tools focus on network visibility and fault localization by linking live Art-Net and sACN behavior to fixture presence, which MADRIX RADAR does for MADRIX-driven show failures. Other tools lean into document production and traceability, where Lightkey links commissioning configuration records to generated documentation packages and EcoStruxure Power Commission keeps power distribution evidence tied to electrical asset context.

ETC commissioning criteria across showfiles, patching, evidence, and network control

Commissioning outcomes hinge on whether software couples patch, cue timing, and operational behavior into a single repeatable production artifact rather than splitting them across separate steps. ONYX and ETC Eos anchor this by keeping cue and configuration changes inside the same showfile workflow so updates stay traceable across revisions.

For projects that include DMX networking and real-time troubleshooting, the deciding factor is whether the tool adds a monitoring surface that maps live signal behavior to the show or fixture presence. MADRIX RADAR does this for Art-Net and sACN behavior tied to MADRIX fixture presence, while other tools focus more on document and evidence outputs.

  • Showfile coupling for cues, patch, and fixture behavior

    ETC Eos ties cue lists, timing changes, patch, and fixture behavior into one continuous showfile artifact. ONYX also supports fast iteration inside its programming environment with DYLOS pixel-control effects stored alongside the rest of the show logic.

  • Cross-platform show preparation and portable programming

    Martin M-PC provides Windows-based access to the M-Series programming and playback environment for pre-venue show preparation. ONYX supports touring workflows by moving shared show files between Windows programming stations and NX control consoles.

  • Layered effects and parameter-level trigger automation

    ONYX uses the DYLOS pixel-control engine to create layered effects within the main ONYX programming environment. Avolites Titan provides Synergy triggers that play Avolites Ai media-server content alongside Titan lighting playbacks from one show control workflow.

  • Commissioning evidence linkage to configuration and documents

    Lightkey links commissioning configuration records to generated documentation packages so deliverables stay tied to the underlying mapping decisions. EcoStruxure Power Commission ties project activity and power distribution documentation to electrical asset context for commissioning reporting workflows.

  • Field test record traceability into commissioning closeout

    FieldTestPRO captures structured test records so findings stay consistent across sites and traceability reduces rework during commissioning closeout. Ekip Connect keeps commissioning evidence linked to configured equipment records across install and closeout within an ABB-aligned project structure.

  • Network visibility and fault localization for DMX transport families

    MADRIX RADAR provides live network monitoring that ties Art-Net and sACN behavior to MADRIX fixture presence to pinpoint signal failures. QLC+ centers on DMX show playback and cue sequencing inside local showfiles rather than network monitoring depth.

Pick the ETC workflow shape: showfile-first, evidence-first, or network-debugging

The key fork is whether the workflow must revolve around a showfile-first loop where patch and cue logic remain coupled as teams iterate. ETC Eos and ONYX fit this shape by keeping cue lists, timing, patch, and related behaviors inside the same production object.

A second fork is whether the project depends on commissioning documentation linkage and audit-ready traceability rather than real-time console programming. Lightkey, EcoStruxure Power Commission, FieldTestPRO, and Ekip Connect prioritize configuration-to-deliverable linkage and evidence capture, while MADRIX RADAR targets live signal fault localization for Art-Net and sACN networks.

  • Choose the governing artifact: one showfile or split evidence objects

    If cue timing changes, patch edits, and fixture behavior updates must remain coupled inside one artifact, ETC Eos and ONYX match this by using showfile-first workflows. If the organization must attach commissioning evidence to configuration records and generated deliverables, Lightkey and EcoStruxure Power Commission better match document-linked execution.

  • Match automation needs to the available programming trigger surface

    If layered effects and parameter-level control need to live inside the same programming environment, ONYX supports DYLOS pixel-control engine effects. If media-server synchronization must originate from lighting show control, Avolites Titan pairs Titan playbacks with Ai media-server content via Synergy triggers.

  • Decide whether Windows staging is mandatory before hardware access

    If show preparation must occur on Windows without needing a dedicated console surface, Martin M-PC is built for portable access to the Martin M-Series programming and playback environment. If touring teams must move shared show files between Windows PCs and NX consoles, ONYX supports that shared showfile transfer.

  • Select network troubleshooting depth based on DMX transport and system pairing

    If troubleshooting requires live network monitoring that maps Art-Net and sACN behavior to fixture presence, MADRIX RADAR provides operational health views for MADRIX-driven workflows. If the team only needs local DMX fixture patching and cue sequencing in a portable showfile, QLC+ focuses on timeline and cue playback rather than network monitoring.

  • Plan evidence capture flow around test records or configuration record linkage

    If field teams capture evidence and later need traceability into commissioning reports, FieldTestPRO keeps structured test record capture consistent across sites. If the organization needs turnover-ready documentation packages linked to commissioning configuration decisions, Lightkey generates documentation packages directly tied to configuration records.

  • Confirm documentation exports and structured handover format needs

    If exported commissioning documentation structure must be highly formal and document-first, tools like Lightkey emphasize structured import and export linked to deliverables. If export structure needs are secondary to coupling inside a console showfile, ETC Eos emphasizes showfile coupling with cue lists, timing, and patch.

Teams that fit these ETC workflows best

Different ETC software picks align to distinct workflow priorities, such as showfile-first commissioning loops, evidence-linked documentation production, or live network fault diagnosis. The right match depends on whether the commissioning process is anchored by programming artifacts or by deliverable evidence packages.

For touring and pre-venue planning, portability and cross-station show reuse matter. For electrical commissioning documentation workflows, the ability to tie commissioning evidence to power distribution context and configured equipment records matters more than console programming depth.

  • Lighting crews preparing shows across Windows stations before venue access

    Martin M-PC supports Windows-based access to the M-Series programming and playback environment without requiring a dedicated console surface for early planning.

  • Touring productions that need one repeatable programming environment across controllers

    ONYX uses shared show files transferred between Windows PCs and NX consoles so touring teams can keep one programming workflow end-to-end.

  • Commissioning teams that must generate turnover-ready documentation from configuration mapping

    Lightkey keeps commissioning deliverables linked to configuration records and generates documentation packages from those linked inputs to reduce manual re-entry between stages.

  • Electrical commissioning teams tying deliverables to distribution assets and tracked projects

    EcoStruxure Power Commission provides power distribution documentation workflows that keep electrical context attached to commissioning activities and revisions.

  • Teams operating MADRIX-driven fixtures who need fast fault localization on DMX networks

    MADRIX RADAR provides live network monitoring that ties Art-Net and sACN behavior to MADRIX-driven fixture presence to pinpoint signal failures.

Common ETC software pitfalls during commissioning and handover

Mistakes usually come from choosing a tool that matches a single phase while failing to support the governing artifact across the full workflow. Another failure pattern is underestimating how much local venue networking practices shape discovery and topology behavior.

These pitfalls show up differently across showfile-first tools and documentation-first tools, so the fix depends on whether the workflow is anchored in cue programming or commissioning evidence linkage.

  • Assuming console-oriented showfile tools provide structured commissioning export output that matches document-first workflows

    ETC Eos couples cue lists, timing, patch, and fixture behavior inside a showfile, but commissioning documentation exports are not as structured as document-first tools, so planners should align deliverable format expectations to the showfile workflow.

  • Choosing a commissioning evidence tool without verifying early equipment and topology inputs

    EcoStruxure Power Commission depends on importing accurate equipment and topology inputs early, so teams that start with incomplete distribution data can end up with downstream reporting that needs rework.

  • Relying on network discovery and universe management without checking how much depends on external venue practices

    ETC Eos notes that network discovery and universe management depend on external venue practices, so commissioning plans should account for site-specific network conventions before scheduling signal validation.

  • Expecting offline or field-first commissioning coverage to match evidence-linked documentation depth

    Lightkey links commissioning configuration records to generated documentation packages, but offline or field-first commissioning support is not its strongest area, so field capture workflows may require a complementary process.

How We Selected and Ranked These Tools

We evaluated ONYX, ETC Eos, Avolites Titan, Martin M-PC, QLC+, Lightkey, EcoStruxure Power Commission, FieldTestPRO, MADRIX RADAR, and Ekip Connect using features at 40% weight because commissioning outcomes depend on how cue timing, patching, evidence, and network behavior stay connected. We weighted ease and value at 30% each because operators still need practical setup, especially when touring teams move show files between systems.

We prioritized integration depth by comparing how each tool binds showfile workflow to configuration changes, and we prioritized admin and governance controls only where the workflow centers on evidence linkage and documented deliverables. ONYX separated itself by pairing DYLOS pixel-control effects inside the main programming environment with shared show file transfer between Windows PCs and NX control consoles, which creates a single workflow for effect creation and touring reuse.

Frequently Asked Questions About etc software

How do ONYX and ETC Eos handle showfile continuity during commissioning changes?
ONYX ties fixture patching, playback control, and show-file management into one programming environment so programming edits stay consistent across the same workspace. ETC Eos is built around showfile-first commissioning workflows where cues, patch, and channel behavior remain linked as configuration changes are tracked inside the show artifact.
Which tool is better for console programming workflows, Avolites Titan or ONYX?
Avolites Titan fits touring workflows that require console-focused show control with integrated media-server cue triggering through Synergy. ONYX fits teams that move the same production between Windows programming stations and Obsidian NX consoles using one shared environment.
How does Art-Net and sACN output support differ between ONYX and MADRIX RADAR?
ONYX includes Art-Net and sACN output support for networked lighting control so fixtures and receivers can be driven from the same environment. MADRIX RADAR targets monitoring and troubleshooting for MADRIX-based networks by viewing Art-Net and sACN behavior and correlating controller output to device presence.
When is Martin M-PC the right choice versus using QLC+ for preproduction or rehearsal?
Martin M-PC fits Martin-based workflows that need portable, console-style programming and cue playback from a Windows PC with DMX512 output through compatible Martin hardware. QLC+ fits small teams that need local DMX patching and fast rehearsal loop playback using timeline and cue sequencing inside QLC+ showfiles.
What tradeoff appears when Lightkey is used instead of ETC Eos for cue building and showfile-first operations?
Lightkey focuses on organizing commissioning outputs and aligning fixture mapping to generated documentation packages, so it emphasizes handoff records over console-style cue construction. ETC Eos is structured for showfile-first commissioning where cue building and fixture profile patching are maintained inside a continuous production artifact.
How do FieldTestPRO and EcoStruxure Power Commission differ in traceability from evidence to deliverables?
FieldTestPRO is built for structured field testing evidence capture that links test findings into commissioning deliverables such as as-built documentation and fault logs. EcoStruxure Power Commission pairs commissioning project tracking with electrical power-centric documentation workflows so evidence and reports stay tied to electrical equipment and distribution documentation.
How does Ekip Connect support structured handover packs compared with general equipment-note tracking?
Ekip Connect coordinates test results, asset records, and commissioning outputs so commissioning evidence aligns with configured equipment records across install and closeout. FieldTestPRO also supports evidence-to-report traceability, but Ekip Connect is specifically positioned around ABB ecosystem connectivity and configuration assets that reduce friction between design intent and closeout documentation.
Which tool provides multi-console operation and pixel mapping features, Avolites Titan or QLC+?
Avolites Titan supports TitanNet multi-console operation and includes pixel mapping plus macros and palettes for complex live production workflows. QLC+ provides timeline-based cue sequencing and DMX patching for local show control, and it does not target the same console-networked operating model.
What breaks if a team needs offline analysis rather than cue-list authoring, using MADRIX RADAR and QLC+?
MADRIX RADAR focuses on offline network monitoring and analysis for MADRIX-driven Art-Net and sACN behavior, so it does not serve as a cue authoring tool for building DMX show timelines. QLC+ is designed for fixture patching and playback sequencing with cue lists and timelines, so network-level device health visibility is not its primary workflow.

Tools reviewed

Primary sources checked during evaluation.

Referenced in the comparison table and product reviews above.

Logos provided by Logo.dev

Keep exploring

FOR SOFTWARE VENDORS

Not on this list? Let’s fix that.

Our best-of pages are how many teams discover and compare tools in this space. If you think your product belongs in this lineup, we’d like to hear from you—we’ll walk you through fit and what an editorial entry looks like.

Apply for a Listing

WHAT THIS INCLUDES

  • Where buyers compare

    Readers come to these pages to shortlist software—your product shows up in that moment, not in a random sidebar.

  • Editorial write-up

    We describe your product in our own words and check the facts before anything goes live.

  • On-page brand presence

    You appear in the roundup the same way as other tools we cover: name, positioning, and a clear next step for readers who want to learn more.

  • Kept up to date

    We refresh lists on a regular rhythm so the category page stays useful as products and pricing change.