LiveSoundRack Quick Start Guide for Dummies Fast commissioning and first-audio workflow

#LiveSoundRack Quick Start Guide for Dummies

#What this guide helps you do

This guide takes you from an unopened LiveSoundRack folder to a working rack with ASIO input, one or more plugins, and ASIO output. It also shows the minimum steps for playback, recording, saving, and remote control.

LiveSoundRack is a Windows live-audio rack host. The server computer owns the ASIO device, processes audio, loads VST3 or CLAP plugins, plays files, and records channels. A client computer is a control surface. The server and client may be the same Windows computer.

Safety first: turn down the amplifier, powered speakers, and rack Output Gain before starting ASIO or routing a test signal. Build and verify the signal path at a low level.

#1. Know which program to start

#On the server computer

Start:

LiveSoundRack.Server.exe

This is the normal server entry point. It appears in the Windows notification area and starts the audio engine and web gateway for you.

Do not normally start these yourself:

  • LiveSoundRack.Server.Core.exe — the realtime ASIO and rack engine.
  • LiveSoundRack.Server.Web.exe — the control gateway and browser interface.
  • LiveSoundRack.Server.PluginHost.exe — an isolated plugin process started only when required.

#On a Windows control computer

Start:

LiveSoundRack.Client.exe

The client can run on the server computer or on another Windows computer on the same private network. It discovers available LiveSoundRack servers and lets you control them.

#From a browser

Open Google Chrome and enter:

http://SERVER-IP-ADDRESS:21011

Examples:

http://127.0.0.1:21011
http://192.168.1.30:21011

Use 127.0.0.1 only when the browser is on the server computer. On another device, use the server computer's private LAN address. In Chrome, the Web UI provides server-hosted downloads for Client and Plugin Editor Host. The Client app starts directly at the main control tabs.

If the LiveSoundRack Client app cannot find the Server, the current screen is replaced by Server Not Found in Local Network. Check that the LiveSoundRack Server is running and that the Client PC is connected to the same local network. The normal screen returns after the connection is restored.

Keep the server on a trusted private network. Do not forward LiveSoundRack ports directly from the public Internet.

#2. First launch checklist

  1. Connect and power on the audio interface.
  2. Install its Windows ASIO driver.
  3. Install the VST3 or CLAP plugins on the server computer.
  4. Start LiveSoundRack.Server.exe.
  5. Start LiveSoundRack.Client.exe, or open the Web UI in Chrome.
  6. Keep speakers muted or at a very low level.

The main tabs are:

  • RACK — audio routing, racks, plugin chains, gains, meters, mute, bypass, and console files.
  • RECORD — multichannel input/output recording.
  • PLAYBACK — server-side playlists and playback controls.
  • OPTION — Audio Transition Time, Console Change Mode, Plugin Process Isolation, and plugin stability options.
  • SETUP — ASIO, plugin scan folders, Windows startup, scheduled reboot, CPU tools, and process priorities.
  • SERVER — server status and Core restart controls.
  • ABOUT — demo time, license activation, and notices.

Optional performance setting: In SETUP → SYSTEM, you can enable the LiveSound.App Performance Power Plan using the checkbox next to Shutdown. It is off by default. This Windows power plan is designed to help maintain stable, low-latency audio. It may use more power and increase heat, fan noise, and laptop battery drain, so make sure the computer has adequate cooling. LiveSoundRack asks for confirmation before applying the change. Turn it off to return to the previous power plan.

#3. Select and start the ASIO device

Open SETUP, then find the ASIO section.

  1. Click Refresh.
  2. Choose the correct ASIO Device.
  3. Choose a supported Sample Rate.
  4. Choose a supported Buffer Size.
  5. Leave MMCSS (ASIO/engine) enabled for normal use.
  6. Click ASIO Start.

A practical first setting is the device's normal show sample rate with a medium buffer. Very small buffers reduce latency but increase the chance of clicks and dropouts. Large buffers are more stable but add latency.

If ASIO will not start:

  • Close any DAW or other application that may already own the ASIO device.
  • Confirm the interface is connected and powered.
  • Click Refresh and select the device again.
  • Try another sample rate or a larger buffer.
  • Check the SERVER tab for the ASIO state.

Auto-start ASIO can start the remembered device the next time the LiveSoundRack server starts. It works only after a valid device, sample rate, and buffer have been stored.

#4. Scan VST3 and CLAP plugins

Stay in SETUP and find PLUGINS.

  1. Check the folder list on the left.
  2. Click Add folder for any additional server-side plugin folder.
  3. Click Scan.
  4. Let the scan finish before building the rack.

The folder picker shows folders on the server computer, even when you are controlling LiveSoundRack remotely.

LiveSoundRack also creates local drop folders beside the server engine:

VST3\
CLAP\

You may place portable plugin packages there when appropriate, then scan again. Installed plugins may have licensing or installer requirements; copying a package is not always enough.

After scanning:

  • Exclude hides an unwanted plugin from selection lists without removing its catalog entry.
  • Include makes an excluded plugin visible again.
  • Edit changes the displayed vendor or category used to organize the plugin list. It does not alter the plugin itself.

#5. Complete Waves Prewarm when offered

When eligible Waves VST3 plugins are found, LiveSoundRack may ask whether it should initialize them for improved first-use stability.

  1. Choose Yes when you want Waves Prewarm.
  2. Keep ASIO stopped if the prompt tells you Waves Prewarm is pending.
  3. Keep the LiveSoundRack Tray app open.
  4. The LiveSoundRack server restarts automatically once.
  5. Wait until the Server becomes available again before continuing.

Waves Prewarm requires Plugin Process Isolation = Off. It may not run when ASIO is active, no eligible Waves plugin is available, or isolation is enabled.

The corresponding setting is OPTION → Auto-initialize Waves (Server).

#6. Build your first rack

Open RACK.

A rack is a virtual channel strip. Its basic signal path is:

Input source → Input Gain → Automixer → Plugin slots → Output Gain/Mute → Output routing

#Example: stereo input through one plugin to stereo output

  1. Use the first rack, or click Add Rack.
  2. Set the rack to Stereo.
  3. Choose the left and right ASIO inputs in the rack's Input L and Input R routing cells.
  4. Set Input Gain to 0.0 dB unless level correction is needed.
  5. Click an empty plugin slot.
  6. Choose a VST3 or CLAP plugin from the vendor/category list.
  7. Choose the left and right ASIO outputs in Output L and Output R.
  8. Keep Output Gain low while checking the route.
  9. Unmute the rack only after confirming the destination.
  10. Raise the monitoring system gradually.

#Mono racks

A Mono rack uses its left path. The right input and output are unavailable. Use Mono for a single microphone, instrument, or mono bus.

#Important routing rule

A physical ASIO output can be driven by only one rack output at a time. Multiple racks may listen to the same input, but two rack outputs cannot claim the same hardware output destination.

#Add or move plugins

  • Click an empty slot to insert a plugin.
  • Left-click a loaded, healthy slot to open its Original Editor.
  • Right-click a loaded slot for Empty, Bypass, Original Editor, Generic Editor, Copy/Paste, plugin preset, and isolation recovery commands.
  • Drag plugins to reorder them or move them between racks.
  • A rack supports up to 32 plugin slots.

#Protect the layout

Turn on LOCK after the rack is ready. LOCK prevents accidental rack-structure editing while leaving normal operating controls available.

The RACK toolbar also provides these operating indicators and controls:

  • ERROR: n — shows the combined total of ASIO OverLoads, DSP Overruns, and Dropout Signals. Click it to see each counter and RESET them.
  • CPU n% — shows current Server CPU use. Click the CPU meter to open CPU Monitor.
  • RAM n% — shows physical memory use for the whole Server PC. Orange/red decoration is a separate Windows commit-pressure warning. Adding a plugin requires a shared YES/NO confirmation when the latest valid commit reading is 80% or higher; this can occur before the orange marker appears.
  • ▲ / ▼ — collapses or expands the Rack area.
  • Remove Last (n) — removes the last Rack; n identifies the Rack that will be removed.

When supported De-Feedback 1.1.4 is installed, the same toolbar also shows DFB Response with Fastest, Fast, Slow, and Slower. The control works with isolation off or on. Slower choices reduce update frequency but also slow feedback adaptation.

#7. Choose the correct plugin editor

#Generic Editor

Use Open Editor(Generic) when you need simple parameter control.

  • It works in the browser.
  • The client computer does not need the plugin installed.
  • It shows parameter metadata supplied by ServerCore, including isolated PluginHost slots.
  • It does not reproduce the plugin manufacturer's custom graphics, analyzer, or RTA display.

#Original Editor

Use Open Editor(Original) for the manufacturer's own plugin window.

In Chrome, selecting Open Editor (Original) shows this guidance:

The plugin's Original Editor is available in the LiveSoundRack Client app.

Please open LiveSoundRack.Client.exe and try again from the RACK screen.
  • On the server computer, the installed server component can be used by the local editor flow.
  • On a separate Windows client, use the exact same plugin version/build when possible.
  • Prefer the manufacturer's installer. For standalone plugins, place the complete VST3 bundle or CLAP package in the VST3 or CLAP folder beside LiveSoundRack.Client.exe.
  • Windows Client starts LiveSoundRack.Client.EditorHost.exe when needed.

EditorHost searches the same absolute path when available, then its local catalog, then Client drop folders and standard Windows plugin locations by format and stable identity. The local shadow plugin is only a GUI; parameter changes go to the authoritative server slot.

#Remote Live Audio for meters and RTA

The Original Editor top bar can enable Live Audio. This sends a monitor-only preview of the selected server plugin input to the remote editor so compatible plugin meters, RTA, or analyzer displays can react.

  • Allow UDP 21013.
  • Old windows are not queued or replayed. Congestion can make the display skip, while Server production audio remains unaffected.
  • A Mono stream uses about 2 Mbps; Stereo plus sidechain can use up to 8 Mbps.
  • The remote shadow output is discarded and never becomes the show signal.

#8. Save the working setup

The Console File button on the RACK toolbar has two actions:

  • Left-click it to open the recent Console File list, then select a file to change to that Console File.
  • Right-click it to open Load, Save, and Save As.

A console stores the rack, routing, plugin, parameter, and plugin-state configuration required to restore the show setup.

Recommended first save:

  1. Right-click Console File.
  2. Choose Save As.
  3. Enter a simple name such as My First Show.
  4. Leave Autosave enabled while configuring.

Use the X beside a recent item to delete that Console File after confirmation. A changed Console is shown as dirty until it is saved or autosaved.

Use letters, numbers, spaces, _, -, or . in managed names. Do not add .json, .wav, or the Console. prefix yourself.

#9. Quick playback setup

Playback produces virtual stereo sources named Playback L and Playback R. It does not automatically connect to hardware outputs.

#Route playback first

  1. Create or choose a Stereo rack.
  2. Set its inputs to Playback L and Playback R.
  3. Route that rack's outputs to the desired ASIO outputs.
  4. Keep gains conservative until verified.

#Add and play files

  1. Open PLAYBACK.
  2. Click ADD.
  3. Browse files that are accessible to the server computer.
  4. Add supported files.
  5. Select a track and press PLAY.

Supported file extensions are:

.wav  .wave  .mp3  .m4a  .aac  .flac  .wma

Playback also offers playlists, play modes, fades, volume, AutoGain, a Safety Limiter, waveform display, seeking, and cache cleaning.

The Playback Safety Limiter protects the playback source before it enters a rack. Later plugin gain or rack gain can still clip the final output.

#10. Quick recording setup

Recording requires running ASIO and at least one enabled channel.

  1. Open RECORD.
  2. In INPUT CHANNELS, enable the raw ASIO inputs or Playback L/R that you want to record.
  3. In OUTPUT CHANNELS, enable any final ASIO outputs that you want to record.
  4. Give every enabled row a valid Record Name.
  5. Click Start Record.
  6. Click Stop Record before shutting down or restarting the server.

Recordings are written on the server as mono, 32-bit floating-point WAV files at the active ASIO sample rate. Each selected channel has its own file. Large recordings are split into numbered parts before the WAV data reaches 2 GiB.

Recording profiles can be loaded, saved, and saved under a new name. A profile is tied to the committed ASIO device channel layout; a different device or channel count may make the profile incompatible.

#11. Stop and shut down safely

Before restarting or shutting down:

  1. Stop recording and wait for the button to return to Start Record.
  2. Stop playback if it is no longer needed.
  3. Save the current console.
  4. Mute or turn down the system.
  5. Stop ASIO when changing device settings or doing maintenance.
  6. Use the tray application or SETUP controls for shutdown/restart.

The SERVER tab offers normal and forced Core restart. Use normal restart first. Forced restart is for an unresponsive Core and interrupts audio, playback, recording, and editor sessions.

#12. Common first-run problems

Problem What to check
Server is not found Confirm LiveSoundRack.Server.exe is running, server and client are on the same LAN, and firewall/VLAN/Wi-Fi isolation is not blocking discovery. A browser can use http://server-ip:21011 directly.
ASIO does not start Check device power/USB, close other ASIO applications, refresh devices, and try a supported sample rate or larger buffer.
No sound Verify ASIO is running, rack input routes are set, a rack output owns the intended ASIO output, rack/plugin bypass and mute states are correct, and gains are not at minimum.
Playback moves but is silent Route Playback L/R through a stereo rack to ASIO outputs.
Plugin is missing Add the correct server folder, scan again, and make sure the plugin is not excluded.
Original Editor will not open remotely Install a matching plugin on the client, open LiveSoundRack.Client.exe, and retry the Original Editor from the RACK screen. Chrome does not launch the Original Editor directly.
Original Editor meters do not move remotely Turn on Live Audio in the editor top bar. The plugin itself must provide a meter or analyzer.
Waves Prewarm does not run Stop ASIO, set Plugin Process Isolation to Off, enable Auto-initialize Waves, scan eligible Waves VST3 plugins, and follow the prompt.
Clicks or dropouts Increase ASIO buffer size, reduce plugin load, avoid heavy console crossfades, use a wired network for remote editor visuals, and check CPU Monitor.
Record will not start Start ASIO, enable at least one channel, correct Record Names, and verify the record profile matches the current ASIO layout.

#13. Demo and license

LiveSoundRack provides a 30-minute demo period from Server Core start. The remaining time is shown in the tray and ABOUT tab. After demo time ends, audio output may be intermittently muted for 10 seconds. Restarting Server Core begins a new demo period.

Use ABOUT → UI Scale to choose 50%–150% in 10% steps. The default is 100%. The setting applies to the whole Web UI and resets to 100% when the page or Client window is reopened.

Use ABOUT → Activate and enter the license email and access key for uninterrupted operation. Activation and deactivation may require Internet access.

#14. The one-page show checklist

#Before doors open

  • Server, interface, and plugins are installed and licensed.
  • LiveSoundRack.Server.exe is running.
  • Correct ASIO device, sample rate, and buffer are selected.
  • Plugin Scan and Waves Prewarm are complete.
  • Every rack input and output route is verified at low level.
  • Plugin chains and sidechains are tested.
  • PDC, isolation mode, and transition settings are appropriate.
  • Playback L/R is routed if playback is used.
  • Record profile and free disk space are checked if recording is used.
  • Console is saved and Autosave status is understood.
  • Remote client, firewall, and optional Live Audio are tested.
  • Demo time or license status is confirmed.

#During the show

  • Use LOCK to protect rack structure.
  • Watch meters and CPU headroom.
  • Avoid scanning plugins, changing ASIO devices, or making large topology changes.
  • Coordinate multiple operators because all clients control the same server state.

#After the show

  • Stop recording and playback.
  • Save the console.
  • Back up the server's LiveSoundRackData folder while the server is stopped.