WATCHOUT 7 and Pixelhue P20

Task+

Task+ talks to WATCHOUT 7 and to the Pixelhue P20 switcher, and puts in front of the operator what is actually needed in the room: the buttons with their cue lists, the timelines with their colours, the show variables, the P20 mixer and the time left. It is not a generic remote: it is a desk built around the show, programmed the way you think about the gallery.

Task+ — GRAND FINAL
Task+ — GRAND FINAL
The desk
Buttons that run cue lists

Every button is a task: an ordered sequence of commands towards the show, with its progress visible while it runs.

Rundowns and categories

One page for each moment of the show, coloured bands to group the buttons. Emergency categories can be pinned to every page.

Free, stable layout

Every button stays where you put it: drag, align, duplicate, and free labels on the grid.

Automatic name and colour

A button can take its name and colour from its first timeline, its first cue or the value of a variable.

Exclusive groups

Starting a task in a group stops the others in the same group.

Programming cues
Every show command

PLAY, STOP, PAUSE, jump to cue or time, inputs, variables, cue sets, waits, BREAK, other tasks, PLAY takes.

On-the-fly fixes

The quick panel next to the button changes verb, timeline, cue and timing without opening the editor.

Re-target in one move

Change a row's timeline or cue while holding Ctrl and every row that referenced it follows.

The next row, ready

The row menu creates the following PLAY, STOP or CUE on the same timeline; BREAK is always one click away.

Row test

The ▶ runs a single cue immediately, to check it while you write it.

Pixelhue P20, direct
No middleman

Task+ drives the switcher through its own network interface, without going through Companion: no added delay between the press and the cut.

A real mixer

The MIXER tab brings TAKE, CUT and MATCH PGM, fade to black (FTB) and FREEZE with their tally lights, screen by screen.

Presets and layers

Presets recalled to preview, to program or globally; layer presets and source changes on a chosen layer or on the one selected on the P20.

In the same list as WATCHOUT

P20 commands are cue rows like any other: one button runs the timeline and cuts the switcher, with optional fire-and-forget.

Configuration read from the device

Screens, presets, layers and inputs come from the P20; presets are tracked by number, so they stay linked even when the switcher renames them.

Show logic
Triggers on press

A switch/case decides what the button does based on the state of the show: the first true case wins.

Conditions

Variables, timeline state, time and cues, inputs, cue sets, other tasks and groups, also on a single row. An incomplete condition never counts as false.

Templates

A saved cue list can be reapplied to other timelines and cues: jumps are found again by name on the new timeline.

Reminders

The STILL MISSING checklist flags the buttons to finish before going live.

Show state
Live state

Stopped, running or paused, read straight from WATCHOUT, with time and countdown for every timeline.

Variables in view

The variables that matter sit above the grid, always in sight; show inputs have their own fader mixer.

An honest connection light

A stopped show sends no events: the light stays green, because silence is not a failure.

Memories

Items copied from WATCHOUT are kept in the project and copied back to the clipboard when needed.

Several workstations, integrations
One master, many workstations

A single workstation runs the tasks and talks to WATCHOUT and the P20; the others see the same state and forward their presses.

Working together

Changes are synchronised across workstations, tasks being edited are protected with the editor's name, undo and redo per workstation.

Companion

Tasks reach the Stream Deck with ready-made presets, and button states come back to the surface without waiting.

PLAY and MIDI

A PLAY take can press a Task+ button and vice versa; buttons can also be bound to MIDI notes and controls.

Same home as PLAY

Same projects, same backups, same multi-user locking, yet genuinely separate projects: the ban lives in the server.

Want to try Task+?

We will set up a demo on your own material: it is the quickest way to tell whether it is the right tool.