Manual — channel templates

A known-good channel, carried from one gig to the next.

A channel config is one channel’s processing, saved under a name and applied to any other channel. The console ships a set of factory instrument templates alongside the ones you save, and both go on through the same door — but they say different things, and the difference is the whole chapter. Before any apply lands, the desk shows you exactly which fields it would move.

01

Saving one.

In the library, pick the channel to capture, give it a name, and save. You can file it under a family — Vocals, Drums, Guitars — which groups it beside the factory templates for the same family in the picker. Naming no family is a choice rather than a missing field: it lands as an ungrouped entry.

The library is sorted by name, never by date. A config library is something you browse for the chain you want, not something you replay in the order you made it.

What a save captures:

  • The EQ, the gate and the compressor.
  • The insert rack and the order the processing runs in.
  • Digital gain, trim and pan.
  • Phantom, pad and head-amp gain.
  • Polarity, and the alignment delay with what it is aligned against.

And what it deliberately does not:

  • The fader, the mute, the solo and solo-safe.
  • The channel’s name, its colour and its instrument.
  • Recall safe, and whether the channel is armed to record.
  • Every send to every bus.
  • What is patched into the channel, and what the channel is linked to.

A config says what this channel’s processing is. It says nothing about where the channel is patched, how loud it sits in the mix, or what it is called — those belong to the show, and they are what a session saves.

02

A factory template states the chain, and only the chain.

The instrument templates that come with the console — Kick In, Lead Vocal, and the rest — are a statement about the instrument: the EQ, the gate, the compressor, the insert rack and the order they run in. Applying one leaves the strip’s own facts exactly where you put them. Your gain, trim, pan, polarity and alignment do not move.

A kick drum’s compressor is much the same in every room. Its trim never is. Those two sentences are why the split exists: a template describes an instrument, and the head stage describes this strip and the source plugged into it.

A config you saved yourself is the other kind of statement — a whole one. It was captured from a real channel with a real head stage, so applying it moves the head stage too, including back to fresh if that is where you captured it. That is not an inconsistency between the two: a factory template never mentions the head stage, and something that is not mentioned is not changed.

Factory templates are read-only. They cannot be deleted, and a save cannot take one of their names out from under them.

03

The preview of moves.

Applying a config is not additive, so before it lands the console asks the desk what would actually change and shows you the answer:

Apply “FOH Vocal Capture”?

A config is a whole statement about a channel, so applying it will move what CH3 holds now:

  • Gain −6.0 dB → 0.0 dB
  • Trim −8.0 dB → 0.0 dB
  • Pan 0.60 → 0.00
  • EQ replaced
  • Insert chain replaced

The list is one line per field that would move, computed by the console against what the channel holds at that moment — never by the surface, so what you are shown and what the door will do cannot disagree. A fact that rides several fields is listed field by field: you are warned about the 48 V, not about “the head amp”.

Three things read differently on purpose. A structured fact — an EQ curve, a gate, an insert rack — says replaced rather than printing a before and an after, because “from 8 bands to 8 bands” is not a readable sentence. A dash means the desk does not know what is there now, which happens on a head-amp fact from a preamp that has never reported; unknown is not zero. And a config applied to a channel that already matches it moves nothing, so it applies on one tap with no dialog at all — applying the same config twice must not ask twice.

The warning can be turned off with Don’t warn me again, which is a console-wide setting of its own. It is deliberately not the same switch as the one that arms destructive actions: an apply removes nothing, and an operator who turned off delete-arming did not ask to lose this.

Every way into an apply obeys it — the instrument picker on the processing view and the Apply button in the library both ask the same question. Cancelling leaves both doors shut, so a channel is never labelled with a template it did not get.

The question is asked by the console, not by the screen you happen to be using. An apply that would move something is refused at the door and comes back carrying the same list of moves, and nothing is written until the apply is sent again saying, in so many words, go ahead. That is why the dialog you see is not a screen the browser invented: the button fires, the console refuses, and the refusal is what the dialog is drawn from.

applying this would move 5 of what the channel holds (gain, trim, pan, eq, inserts) — confirm to go ahead

An OSC surface and an MCP client meet exactly the same refusal, with the same list, and answer it the same way. There is no client that quietly applies without asking, and no client that has to be taught the rule: the desk holds it, in one place, and every surface renders what the desk said.

Both the sign-off setting and the list of moves are read afresh on every attempt. Turning the warning off takes effect on the next apply rather than on the next reload, and a console that cannot read its own setting asks rather than assumes.

04

An apply clears the history.

Applying a config restates a whole channel in one action, so it empties the journal rather than appearing in it — the same rule that covers loading a session or recalling a scene. Saving or deleting a config empties it too. See undo and the history for what that means and what the way back is.

The library is /channelConfigs, the apply is /channelConfigs/{id}/apply/{kind}/{index} and the preview is the read-only sibling at …/applyMoves/{kind}/{index}, whose state is what a refused apply hands back. The console lists every row that asks before it fires in its own index, so a client knows to expect the question rather than guessing — both rows are in the REST reference.

openmixer

A software mixing console for Linux. The desk is the software; the browser is the surface.

Pages

Licence

OpenMixer is free software under the GPL-3.0-or-later. Every package in the workspace carries the same licence.

Roland, Midas, Behringer, RME and the product names used here belong to their respective owners. OpenMixer is an independent project and is not affiliated with any of them.