Hardware Controllers

Early Access

CueForge includes dedicated profiles for three hardware controllers. The profiles are implemented — controls are recognised with human-readable names, Learn works in the Control Mapping window, and LED feedback is wired to show state — but physical validation on real hardware is still in progress as part of the beta programme.

Warning: Until a profile is confirmed on physical hardware, test every mapping with your own unit during rehearsal before relying on it in a live show. Report what you find via the support channel — these sessions are exactly how the profiles get accepted.

Status overview

Controller	Implemented	Physical validation
Akai APC Mini MKII	Full profile — pads and all nine faders, Learn, LED feedback, reconnect resync	In progress
Allen & Heath SQ	Profile — GO, Stop, Panic, Pause, Resume, Next/Previous Cue buttons	In progress
SoundSwitch Control One	Profile — Play/Pause, Back, Shift, BPM Tap, encoders	In progress (beta hardware)

Akai APC Mini MKII

The APC Mini MKII is mapped as a set of named controls rather than raw MIDI messages:

• Pads — individual momentary controls. Note On and Note Off are treated as distinct edges, so a pad press and release never double-fire a cue.
• Nine faders — continuous controls, mappable to bus gain, cue gain, opacity, or pan with source and target ranges in the Control Mapping editor.
• LED feedback — pad LEDs follow authoritative show state (for example, a mapped GO pad reflects running state), and LEDs resynchronise when the unit reconnects.

Unplug and replug the unit during rehearsal to verify resync with your setup, and use the health strip in the Control Mapping window to confirm the MIDI listener sees the device.

Allen & Heath SQ

The SQ profile maps the console’s soft keys to show actions: GO, Stop All, Panic, Pause, Resume, and cue navigation. Connect the SQ’s MIDI port (or a USB–MIDI connection from the console), enable MIDI input in Settings → Triggers & Control, and use Learn in the Control Mapping window to bind a soft key to an action.

SoundSwitch Control One

The Control One profile covers transport (Play/Pause, Back), Shift-modified controls, BPM Tap, and the encoders as continuous controls. The unit is beta hardware itself — treat both sides of the connection as under validation.

How to help validate

1. Connect the controller and confirm it appears under Sources in Window → Control Mapping.
2. Map one control with Learn and verify it executes its action exactly once per deliberate press.
3. For faders/encoders, verify the full travel maps smoothly to the target range (check Invert if the direction feels wrong).
4. Unplug and reconnect the unit mid-session; confirm LED state resyncs.
5. Save the project, relaunch CueForge, and confirm the mappings persist.
6. Send your results (what worked, what did not, unit firmware version) to the beta support channel with a diagnostics export (Help → Export Diagnostics…).

Generic MIDI devices without a profile also work through the same Learn workflow — they simply appear as raw note or controller controls.