HOST LIVE

Quick manual · version 1.4.1 · hostlive.pro

HOST LIVE hosts Audio Unit and VST3 effects for live use. It has 48 channel strips. Each strip takes one input from your audio interface (mono, or a stereo pair), runs it through a chain of up to four plugins, and sends it to one output. It is built to be set up once, started, and left alone on stage.

The main window while the engine is running (the red frame and the “swipe to stop” button show that it is live).

1. Getting started

  1. Choose your audio device in the Device menu. The circular arrow refreshes the list; the gear opens the device's own driver settings (the manufacturer's control app, or Audio MIDI Setup when there is none).
  2. Set the sample rate and the latency (buffer). A smaller buffer means lower latency but more work for the processor. 64 or 128 samples is a good start.
  3. Give a channel a plugin. Click the plugin box on a strip and pick a plugin from the list. Name the channel in the label field if you like.
  4. Choose the channels. In and Out pick the interface channel the strip uses. The list shows single channels (mono) in columns of 16, followed by stereo pairs (1-2, 3-4…); choose a pair to make the strip stereo. A device with more than 64 channels offers them in banks of 64 instead (1 – 64, 65 – 128…), a submenu each, and Type a number…: write 130, or 130-131 for a pair, and press Return.
  5. Press Start. The button turns into swipe to stop.
Stopping is a swipe. To stop the audio, drag the button to the right. A stray click in front of an audience can't silence the band. ⌘R starts and stops from the keyboard.

2. The window

Header

Header: window buttons, Rehearsal (R), the tempo, the load meters, and Start / Stop.
Start / StopStarts the engine. Stopping needs a swipe.
CPUHow busy the whole computer is, across all its cores – not just HOST LIVE.
DSPThe part of each block's time the processing takes. 100% is where the next block is late, so keep it well below that. The thin mark is the worst block since Start: amber when it was high, never red, since a long block is not yet a broken sound. P/P beside the DSP bar lights up while the channels are processed in parallel, on several threads.
dropoutsBlocks the audio device really missed, as Core Audio reports them to HOST LIVE - counted only while a signal was passing, after the first seconds of a run, and when HOST LIVE itself saw the processing go late at the same time (some devices report misses all the time), so a gap in silence does not add to it. The counter stays red until you reset it with the arrow beside it.
Window buttonsMinimise, back to the default size, and full screen - and R, rehearsal mode (below). Right of the R, Undo (a curved arrow) appears after a change to the plugins and takes it back: a plugin put in, replaced, taken out, moved or pasted, or a channel cleared - one step at a time, the last first. It is there only while there is something to take back, and not while the engine is held still.
BPMThe tempo the plugins are told. A small blue dot to the left of the word BPM blinks on every beat, counted from the last tap (or the last tempo the console gave). Tap it three times or more to set it: the average of up to the last ten taps, as a whole number of beats a minute - it goes on getting steadier while the taps go on; a tap that is off by more than a fifth of the usual interval is left out, and a pause of over two seconds starts again. Right-click it to Enter tempo… (type a number from 30 to 300), to choose where the tempo comes from - ProLink (the console's, the start), Taps only, or a MIDI clock (All inputs or one input) - or to Learn a MIDI note or controller that taps it - the same messages cannot also be a snapshot's or a plugin parameter's. Bright while a clock comes in; taps are ignored then. The panel can be put away - View ▸ Hide Tempo, or Hide Tempo in its right-click menu - and the header buttons take its room; a right-click on the header brings it back (Show Tempo).

Rehearsal mode

The R button beside the window buttons switches rehearsal mode on and off, and works only while the engine is running: with the engine stopped it says so instead, and stopping the engine switches rehearsal mode off. The header and the frame of the window go yellow. In rehearsal the engine keeps running while you add, replace, move and remove plugins, drag them between strips, and change the routing (In, Out, ↓ below); a plugin that is already running stays as it is, with its settings and open window, and only what is new is loaded. A plugin's box still opens its window as it does when running; an empty box, and Choose another plugin… in the box's right-click menu, open the list. Each change is put in a moment after the last one: the sound dips for a fraction of a second, and loading a plugin takes processor time, which can cause dropouts. Rehearsal is for rehearsals, not for a show. Turning it on says so; Don't show this again silences that. Rehearsal is off at every start. The device, sample rate and buffer still need a Stop and Start, as does a channel the device was not opened with. A plugin that does not load leaves the engine running and says so.

Device bar

Device, sample rate, latency, and Load / Save As / Save for sessions.

Under the buffer HOST LIVE shows the estimated round-trip latency of the whole signal path. Load (⌘O) opens a session and Save As (⇧⌘S) stores one under a name you choose. Save (⌘S) overwrites the session file you last opened or saved with the current setup, without asking; if there is none yet, it works like Save As. A session holds every channel's plugins, their settings, the routing and the labels. The session's name is shown under the Load and Save buttons, and the last session you opened or saved comes back the next time you start the app. When you quit with changes that are not in the session's file (a changed arrangement or a plugin setting), HOST LIVE asks whether to Save, Don't Save or Cancel. A setup that has no file yet is kept by the automatic save instead, so it is not asked about.

Channel strip

One channel strip.
Number and labelThe channel's number, and a name of your own (“Vocal”, “Bass”…). The name also appears in the plugin's window title. Right-click the number to copy the channel's plugins, with their settings and Quick Controls, and to paste them into another channel (not the routing, bypass or label; a paste takes effect at the next Start). Exclude from snapshots in the same menu puts a thin red line down both sides of the strip, bending into its rounded corners and fading out there: that channel is then left out of snapshots, which neither store its plugins nor change them. Colour in the same menu gives the number's box one of six muted colours (sand, steel blue, teal, moss, amber, mauve), chosen from a row of squares, or none; two strips in a row share the upper one's. It is only there to tell strips apart.
Plugin boxStopped: click to choose a plugin, or drag a plugin to change the order in a chain. Running: click to open the plugin's own window; Alt on a plugin window's close button puts away every plugin window at once.
+Adds another plugin after the last one, in series. A chain holds up to four.
In / OutThe interface channel the strip listens to and plays to, a single channel or a stereo pair, chosen from the same list. The thin bars below show the level (green; the white mark is the recent peak). Alt-click or right-click to reset this channel's routing (none, mono) or, after a confirmation, every channel's. Custom pair… in the list makes a stereo pair of two channels that are not neighbours (1-5, 12-31…): write them with a dash, and the left one first. Link In/Out, the first entry under the dash in the In list (one switch for every strip, it says on or off), makes an input you choose be chosen as the output too, and the other way round - the same channel or pair, where the device has it. Dragging up or down on the IN or OUT square (plus or minus 12 dB, double-click for 0) sets the strip's gain trim: IN before the first plugin, OUT after the last; the pointer moves three times as far as the trim does. A small blue mark on the level bar shows where a trim other than 0 lies; the meters show the signal after the trim.
ON / OFFOFF bypasses the plugins: the signal still passes, but goes round them. Hold Alt while you click to do it to every channel at once: all go to the state this one is switching to.
⊗Clears the channel (its plugins and its label). It asks first. Hold Alt while you click to clear every channel; that asks first too, and says how many channels it will empty.
Clearing a channel asks first.

Clearing a channel removes its plugins and its label, and nothing else: its inputs and outputs stay as they are. The sheet asks first so that a stray click on the ⊗ button can't empty a channel on stage. Escape, or a click outside the sheet, cancels.

The In and Out lists: single channels (mono) in columns of 16, then stereo pairs.

3. Plugins

Click the plugin box on a stopped strip to open the plugin list. Plugins are grouped by manufacturer; type in the search field to find one by name or manufacturer. The top row, No Plugin, passes the signal straight through.

The plugin list: format switch, search field, and the No Plugin row.

Two strips in a row

The Out list of a strip has ↓ below next to the dash (not on the last strip). Chosen there, the strip below takes what this one puts out instead of an interface input, so two strips can work in a row (up to eight plugins together). The link is made from the upper strip only: the lower strip then has no In picker, the two number squares become one tall rectangle with a bent arrow in its lower half, and a thin blue line goes round both. The upper strip's audio goes to the strip below alone, no longer to the interface; choose an output on the upper strip to separate the two again. The signal between them is as wide as the upper strip's input. The two run one after the other in the same block, so there is no extra delay, but they cannot share the processor's cores as separate strips do, and the pair counts as one in the DSP meter. A strip can be linked to the one below only if neither is already part of a pair, so at most two strips are linked. The choice takes effect at the next Start, like the rest of the routing.

Sidechain

A plugin that has a sidechain input (a compressor, a de-esser) offers it in the menu of its box: right-click ▸ Sidechain input, then a mono input or a stereo pair of the device, or None. The box then shows a small blue arrow in its top left corner (rest the pointer on the box to see which input). Instead of an input you can choose From a plugin: the output of another plugin, in this strip or another (sidechaining a compressor to a vocal, say). A plugin that comes earlier in the same strip is heard at once; any other is heard one buffer late, which the menu says in milliseconds (1.3 ms at 64 samples and 48 kHz), because the strips are processed side by side and none waits for another. A bypassed plugin passes its input on to the sidechain unchanged, and a source that is taken out of its strip is no longer a source. The plugin's sidechain is switched on when the engine starts, so a first choice, or a change between mono and stereo, takes effect at the next Start; once it is on, choosing another input takes effect at once. The menu offers the sidechain as soon as you have chosen the plugin: it is loaded once in the background, which is when it says whether it has one (see Looking at a plugin). The same choice is in the top bar of the plugin's own window (in Touchscreen Friendly mode, in its header beside the window's buttons).

MIDI control

Every plugin can have its parameters moved from MIDI. In the plugin's own window the bar at the top has a MIDI button: MIDI control switches it on, Input chooses which MIDI input it listens to (all of them, or one), and the list below holds what is mapped. With MIDI on, a Learn button appears beside it. Press Learn, take hold of a parameter in the plugin's window (the button says Touch a parameter…), then move a knob or fader, play a key or bend the pitch wheel on your controller (Now move the control…): that message now moves that parameter, and Learn ends. A parameter has one message; learning it again replaces it. Controllers, pitch bend and notes can be learned.

Each mapping has a way of working, chosen in its submenu. For a controller or pitch bend: Jump (the parameter goes where the control is, at once), Pickup (the parameter moves only after the control has reached it, so that a snapshot recall or a change made by hand is not followed by a jump) and Endless encoder (an encoder that sends steps rather than positions moves the parameter up and down from where it is). For a note: Toggle (each press switches the parameter between off and on) and While held (on while the key is down). Remove takes a mapping away, Remove all all of them. The mappings are kept with the plugin in the session, and work while the engine runs.

A message that already recalls or steps a snapshot cannot be learned for a parameter, and the other way round: a notice says so. When you copy a plugin that has MIDI control (Alt-drag, Replace, or Paste plugins) you are asked whether the copy gets the same MIDI control, since it would then move together with the original.

The way back. The MIDI menu also has Send parameter changes back to the controller (available while MIDI control is on): what each mapped parameter is now goes out to the controller, so that its motor faders and LED rings follow the plugin however the parameter was moved - in the plugin's window, by a snapshot, by automation or by the controller itself. Output chooses where it goes: Same as the input (the output of the same name, as a controller shows up as both) or one of the MIDI outputs. The message a controller has just sent is not sent back to it. A controller with a display also gets, for every mapped parameter, its value as the plugin writes it (“-6.0 dB”) and its name, as a SysEx message of HOST LIVE's own (F0 7D 48 4C 01 …) that other devices pass over; HOST LIVE Link shows them on the iCON D4. Off by default; the choice is kept with the plugin in the session.

The other format. Where the same plugin is installed as an Audio Unit and as a VST3, the right-click menu of its box offers Switch to the VST3 version or Switch to the Audio Unit version: the other one takes its place in the chain, with the channel's other settings kept. Only while the engine is stopped (or in rehearsal mode).

Looking at a plugin

When you choose a plugin, HOST LIVE loads it once in the background, while the engine is stopped: its box says loading… for a moment. What it finds out - whether the plugin has a sidechain, its latency and how many channels it takes in and puts out - is in the box's tooltip and is kept in the session. A plugin that will not load (an iLok that is not plugged in, a license that has lapsed) says so right away, with the same Try Again and Remove Plugin as at Start. If the app goes down while a plugin is being loaded, that plugin is taken out of the session the next time, so it cannot do it again. The latency is read again at every Start.

The plugin's top bar

The bar at the top of a plugin's window holds, from the left, a Bypass button (the plugin is passed by untouched; it is the same switch as the channel's, and is lit amber while the plugin is bypassed), the Sidechain and Tempo choices where the plugin has them, and the MIDI and Learn buttons described above. View ▸ Hide Plugin Control Strip takes the whole bar away from every plugin window and Show Plugin Control Strip puts it back; the sidechain can still be chosen from the channel's menu. A right-click on an empty part of the bar offers the same, with a notice of how to bring it back. In Touchscreen Friendly mode the header stays when the bar is hidden, and a right-click on it brings the bar back.

Quick Control

While the engine runs, right-click anywhere on a plugin's box, the slider included, and choose one of its parameters. A slider for it appears on the strip, so you can change it without opening the plugin's window. A channel has room for two Quick Controls, on one plugin or on two. When the channel has several plugins, those that have one get the wider boxes and the others shrink to their names; with two on one plugin, they share its box. Tick a parameter to put it on the strip, tick it again to take it off. With two on the strip already, choosing a third asks which of them it takes the place of.

The list starts with two choices: Default leaves the strip to its own choice, which may put a control of its own for the plugin on the strip (a strength, say); None puts nothing of that plugin on the strip.

Quick Control: each strip shows the parameter chosen for its plugin – its name, a slider and the current value.
Right-click a plugin box and choose Quick Control…: the plugin's parameters, one to be put on the strip.

4. Window and view

The window can be any size. Make it wider and the strips stretch. Make it shorter and the lowest rows scroll, with a scroll bar on the right. Make it taller than all the channels need and the whole interface grows with it, widening the window to match.

A short window: rows scroll.
One page of channels.

Snapshots (View menu): a row under the device bar and a list window store how every plugin's parameters are set and whether it is bypassed (not the plugins or routing). Click the previous or next one to recall it, right-click to Store, or press Overwrite; MIDI can step through them (Learn in the list window), and each snapshot can have a message of its own that recalls it (the MIDI row under its name). They work while the engine runs. In the list window a place, a snapshot or an empty one, is moved by dragging it to where it should go, between two others; the places between shift by one to close the gap. A button in the header, beside the window buttons, shows and hides the list window. A snapshot also keeps the tempo: recalling it brings the song back at its own, unless the tempo is being followed from the console (ProLink) or a MIDI clock, which would only set it again. A snapshot made before the tempo was kept leaves it as it is. Off by default.

The snapshot row: the current snapshot in the middle, its neighbours beside it, Overwrite at the left end and Hide / Show List at the right end.
The list window, with MIDI control of previous / next.

5. Settings menu

Start / Stop⌘R
Start Engine on LaunchWhen ticked, the next time the app opens it loads the last session and starts the engine by itself. Off by default. If the session's audio device isn't connected, the engine is not started: a yellow notice says it is waiting for the device, and you start it yourself once it is back.
CPU CoresHow many processor cores the channels are spread over (the audio thread is one of them). Automatic (the default) uses as many as the machine has, up to 10; 1 core runs everything on the audio thread; any larger number spreads the channels over that many cores. Changing it restarts a running engine. The Performance Test recommends a number, which is marked (recommended) in this menu until you quit.
Performance Test…Runs your channels on the selected device, silently and on noise instead of your inputs, with different numbers of processor cores (about a minute), and recommends the number that gives the safest slowest blocks for this device, buffer size and set of plugins; Use N Cores sets the CPU Cores menu to it. Needs the engine stopped and at least one plugin. The window is closed with its Close button or Escape, not by a click outside it.
Auto RoutingWhen on, choosing a device hands the channels out in order (strip 1 to input 1 and output 1, and so on). Off by default: your routing stays as you set it, whatever the device has. On, a device with the channels your routing uses (about as many as the last one) keeps it as it is; only the strips whose channels the new device lacks are handed new ones. A channel the device does not have (a smaller device, or one whose channels change) shows as (n/a) and is left out; it is kept in the session and works again when the device has it.
Transport PlaysOff by default: the plugins are told that nothing plays. Ticked, they are told from the moment the engine starts that the transport is playing, with a time that counts from then and the beats at the app's tempo - what a plugin that measures over time or follows the host's position needs, an integrated loudness meter for one.
Restart TransportSets the time the plugins are told back to zero, so that a measurement that counts from the start begins again.
Delay CompensationSee below. Off by default.
Autosave Every 10 MinutesOn by default. Besides saving a moment after every change to the setup, the app writes its autosave every ten minutes, so that what you changed inside a plugin's own window is not lost if the app closes unexpectedly.
Tempo fromChooses where the tempo the plugins are told comes from: ProLink (the console's - the start), Taps only, or a MIDI clock (a drum machine, a DAW): All inputs (the first to send a clock is followed) or one input. The tempo in the header is bright while ProLink or the clock gives it. Every plugin's window has its own Tempo button: App tempo, ProLink or the clock of one MIDI input - so one plugin can follow another source than the rest - and its ratio to that tempo (the same, triplets, double, half). The same choice is in the right-click menu of the BPM panel.
ProLink compatibility…Opens a window where a DiGiCo console is let follow and drive HOST LIVE as it does a Waves SuperRack: the switch (Follow the console), the state of the connection, the network adapter the console is on, and SuperRack through HOST LIVE.
LanguageChoose English, Español or 中文. The change takes effect the next time the app starts.
Enter License…Opens the license window.

ProLink compatibility

HOST LIVE can speak ProLink, the protocol a DiGiCo console uses with a Waves rack, so that the console treats it as one. Open ProLink compatibility… in the Settings menu, tick Follow the console and choose the network adapter the console is on (the one the console's or SoundGrid's network is plugged into). HOST LIVE then finds the console and connects to it; the window says what state it is in.

HOST LIVE follows the console it finds first and remembers it; another console that answers is asked about before it is followed. Only a rack on the console's own network link may connect through HOST LIVE, and a rack's list of snapshots renames and adds snapshots here but never deletes them.

Tried with a Quantum and SuperRack 15.15. While ProLink compatibility is on, the wordmark carries the word ProLink.

Delay compensation

A plugin with look-ahead (a limiter, a linear-phase equaliser) reports that it delays the signal. HOST LIVE normally leaves each channel with its own delay. Turn Delay Compensation on and every channel is held back to line up with the one whose plugins add the most latency, so channels that are mixed together stay in time.

Turning it on asks first, because the total latency grows. Tick Don't show this again and it switches on without asking from then on.
While it is on, a yellow notice is shown beside the buffer.

While it is on, the square with each channel's number gets a coloured edge. Yellow means the channel is held back to line up with the rest. Red marks the channel with the most latency, the one the others are lined up with. Click the number to leave a channel out: it is no longer delayed, it no longer sets the pace for the others, and its edge goes. Click it again to put the channel back. The choice is saved with the session. Rest the pointer on the number to see that channel's latency and how much longer it is held back; with Hover Text Help turned off, that is all the hover shows.

It makes everything as late as the slowest channel. A bypassed channel counts as having no latency. Turning it off takes effect at once.

6. License and updates

Without a license HOST LIVE is a trial: playback runs for 30 minutes at a time, and you press Start to carry on. To license it, choose Settings ▸ Enter License…, type the email address and the key you were sent when you bought it, and press Activate. A license can be active on three computers at once, and activating needs the internet once; after that the license works without it. To use it on a fourth, choose Deactivate on one of the others first.

The same window has Deactivate while a license is active. It removes the license from this computer and the app returns to trial mode; you can enter the same email and key again at any time. Buy a license opens hostlive.pro.

HOST LIVE ▸ Check for Updates… asks hostlive.pro whether a newer version can be downloaded and offers the download page if so. At every start it asks Check for a new version?; answer Yes or No, and tick Don't show this again to stop the question.

If you have ticked Don't show this again, the app still looks for a newer version quietly at every start, and says so in the About window (a click on the logo) when there is one to download from hostlive.pro.

A click on the logo opens the About window, which also says whom the license was issued to.

The license window.

7. Tips for live use

8. What's new

The newest version comes first. This manual describes version 1.4.1 in full; later versions add a section here.

Version 1.4.1

Version 1.4.0

Version 1.3.10

Version 1.3.9

Version 1.3.8

Version 1.3.7

Version 1.3.6

Version 1.3.5

Version 1.3.4

Version 1.3.3

Version 1.3.2

Version 1.3.1

Version 1.3.0

Version 1.2.3

Version 1.2.2

Everything since 1.1.0, including the small updates 1.1.1 and 1.1.3.

HOST LIVE · hostlive.pro. VST is a registered trademark of Steinberg Media Technologies GmbH. Built with JUCE.