#LiveSoundRack Manual for Dummies

#Introduction

LiveSoundRack turns a Windows computer into a live-audio rack. It receives audio from an ASIO interface, sends that audio through virtual racks and VST3/CLAP plugins, and routes the result back to ASIO outputs. It can also play audio files, record separate channels, store complete console setups, isolate plugins in helper processes, and be controlled from another Windows computer or a web browser.

This manual explains the complete end-user feature set in plain language. You do not need to understand the internal software architecture to operate it, but you should already know how to work safely with microphones, mixers, amplifiers, powered speakers, and an audio interface.

Audio safety: start with amplifiers and powered speakers turned down. Keep rack Output Gain low and racks muted until every input and output route has been checked. Test tones can be loud and continuous.

#Part 1 — The basic idea

#1. Server and client

LiveSoundRack has one audio authority: the server computer.

The server computer:

• owns the ASIO device;
• receives and sends the real audio;
• loads VST3 and CLAP plugins;
• performs rack processing;
• runs playback and recording;
• stores console, preset, catalog, and session files.

A client controls the server. It does not become a second audio engine. You can use:

• the Windows desktop client;
• the browser Web UI;
• both at the same time.

The server and client may be the same Windows computer. In a remote setup, the client sends commands and receives status over the network. Closing a client does not normally stop audio processing on the server.

#2. Which executable should I open?

#Start this on the server

LiveSoundRack.Server.exe

This is the server tray application. It starts, monitors, and restarts the internal programs.

#Start this on a Windows control computer

LiveSoundRack.Client.exe

It can run on the server itself or on another Windows computer on the same private network.

#Open this in Chrome for browser control

In Chrome, the Web UI provides Download links for Client and Plugin Editor Host. The Client app starts directly at the main control tabs.

http://SERVER-IP:21011

Examples:

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

#Programs you normally do not open yourself

#3. Main tabs

#Part 2 — First setup

#4. Before starting

Make sure that:

• Windows recognizes the audio interface;
• the correct manufacturer ASIO driver is installed;
• the interface is powered and connected;
• server-side plugins are installed and licensed;
• the server folder is in a location where LiveSoundRack can write files;
• the control network is private and trusted;
• speakers and amplifiers are turned down.

An installation under a heavily protected Windows folder may prevent LiveSoundRack from creating or saving its data. A writable application folder is recommended.

#5. Start the server and connect

1. Run LiveSoundRack.Server.exe.
2. Look for its icon in the Windows notification area.
3. Run LiveSoundRack.Client.exe or open the Web UI in Chrome.
4. Select the discovered server when more than one server is shown.

If discovery does not work, enter the server's LAN address directly in a browser. Discovery can be blocked by Windows Firewall, Wi-Fi client isolation, VLAN boundaries, or routers that do not pass local broadcasts.

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.

#6. Network safety

LiveSoundRack is intended for a trusted local network.

• Do not forward ports 21010, 21011, or 21013 directly from the Internet.
• Do not place the audio server on an open public Wi-Fi network.
• Use a private wired LAN whenever possible.
• The built-in browser connection uses HTTP, not built-in HTTPS.

#Part 3 — SETUP tab

#7. SYSTEM controls

#CPU Monitor

Opens a live view of server CPU activity. Use it to look for high sustained load, short peaks, or a plugin/rack that leaves too little headroom.

A system that looks stable while idle may still fail when every rack, plugin, playback lane, console transition, and recording channel is active. Test the heaviest realistic show condition.

#RAM

The RAM meter shows physical memory use for the whole Server PC, not only one LiveSoundRack process.

LiveSoundRack also checks whether Windows is running out of total usable memory capacity. The orange warning mark appears after two valid readings at 80% or higher. A reading at 95% or higher makes the warning red immediately. The warning may stay visible until memory use has fallen far enough to be safely clear; this prevents rapid flashing near a threshold.

When the latest valid Windows commit reading is 80% or higher, trying to add a plugin sends the same YES / NO confirmation to every connected App/Web client. This can happen on the first high reading, before the orange mark has appeared. Choose NO to cancel the add. Choose YES only after deciding that the Server has enough margin. LiveSoundRack does not automatically change isolation mode or close other programs.

Practical responses are:

• use a shared isolation mode instead of Isolate Each Slot when appropriate;
• turn Plugin Process Isolation off if fault containment is not required and the plugins are trusted;
• close unnecessary applications and plugin editors;
• remove unused plugin instances;
• increase Windows memory capacity before production use.

#CPU Steering

CPU Steering assigns LiveSoundRack work groups to selected logical CPUs. The current window contains six panels:

• Audio + Plugins — the realtime engine and in-process audio workers;
• Plugins (Isolation) — LiveSoundRack.Server.PluginHost.exe work;
• Record;
• Playback;
• Network/UI — plugin scan, network/API, and LiveSoundRack UI work;
• All Processes Except LSR — other currently running Windows processes.

No selected CPU means All CPUs. The Audio + Plugins panel divides its selected CPUs between the main engine and audio workers; with only one CPU selected, both must use that CPU. A Mixed display means the combined internal categories currently have different masks; select a new mask to make them the same.

This is an advanced tuning tool. Leave the default/all-CPU assignment unless you have measured a repeatable scheduling problem and can rehearse the full system after every change.

#Reboot

Restarts Windows on the server computer. This interrupts all audio, playback, recording, editor sessions, and client connections.

#Shutdown

Shuts down the server computer. Stop recording and save the current console first.

#Performance Power Plan

The LiveSound.App Performance Power Plan is an optional Windows setting for stable, low-latency audio. It is off by default. In SETUP → SYSTEM, use the checkbox next to Shutdown to turn it on. LiveSoundRack asks you to confirm before changing Windows.

When enabled, it uses a dedicated power plan for the audio computer. It may use more power and create more heat and fan noise. A laptop battery may drain faster, so connect the charger and provide adequate cooling.

Turn the setting off to return to the power plan that was active before LiveSoundRack enabled it. While the feature is off, LiveSoundRack does not override a power plan that you select directly in Windows.

If System Maximizer Extreme Mode is already active, LiveSoundRack may show System Maximizer Extreme Mode and lock this control. Manage that setting in System Maximizer instead.

#8. HOST controls

#Schedule reboot

Schedules a regular server reboot at the selected local time. Scheduled reboot also requires the related startup/restoration settings so the machine can return to service.

Before relying on it:

• test the complete reboot cycle;
• verify Windows automatically signs in or starts the tray as required by your deployment;
• verify the interface is ready before ASIO auto-start;
• verify plugins and licenses survive reboot;
• make sure no recording will be running at the scheduled time.

#Start with Windows

Creates a Windows Startup shortcut for LiveSoundRack.Server.exe. It is enabled by default unless changed.

#Remember settings

Stores user settings and is enabled by default. Scheduled reboot depends on remembered settings and startup restoration.

#Set Priority

The current priority selectors are:

• Engine;
• Audio;
• Plugin;
• Network/UI.

Choices range from Idle through Realtime. Network/UI may temporarily display Mixed when its internal UI and network categories do not share one value; Mixed is a status, not a priority to select.

Higher is not automatically better. Excessive priority can starve Windows controls, drivers, storage, or network work. Keep normal values unless a measured problem justifies a controlled change.

#9. ASIO controls

#ASIO Device

Selects the hardware driver used by Server Core. Click Refresh after connecting an interface or installing a driver.

#Sample Rate

Choose a rate supported by the driver and the show. Every recorded WAV file uses the active ASIO sample rate. Changing rate may change plugin behavior, latency, CPU use, and device channel availability.

#Buffer Size

The buffer controls the basic processing block size.

• Small buffer: lower latency, less time to complete each block, greater dropout risk.
• Large buffer: more processing margin, higher latency.

Start with a moderate value. Move smaller only after measuring full-load stability.

#MMCSS (ASIO/engine)

Allows Windows multimedia scheduling support for ASIO and engine work. Leave it enabled for normal operation unless a specific driver test proves otherwise.

#Auto-start ASIO

Requests ASIO startup when the LiveSoundRack server starts. It does not immediately start or stop the current session. A valid remembered device, sample rate, and buffer are required.

#ASIO Start / Stop

Starts or stops the audio engine. Stop ASIO before changing hardware configuration, doing maintenance, or cleaning the playback analysis cache.

#Reported latency

The UI shows input/output latency reported for the active configuration. The complete live path may be longer because plugins, PDC, isolation transport, and external hardware add delay.

#10. PLUGINS controls

#Folder list

The left list contains server-side VST3 and CLAP search folders. Add folder uses a server folder browser. A folder on a remote client does not become available to the server.

LiveSoundRack creates these local drop folders beside Server Core:

VST3\
CLAP\

It also includes common installed-plugin locations and configured CLAP paths as scan roots.

#Scan

Scans the selected roots and builds the plugin catalog. Run scans during setup or maintenance, not during a critical live segment.

#Exclude and Include

• Exclude keeps a plugin in the catalog but hides it from plugin selection menus.
• Include returns it to selection menus.

#Edit

Changes the displayed vendor/category information used to organize lists. It does not modify the plugin binary or its license.

#If a plugin does not appear

Check that:

• it is VST3 or CLAP;
• the server can access its folder;
• the correct architecture/build is installed;
• it passed scanning;
• it is not excluded;
• any vendor license service is working.

#11. Waves Prewarm

Waves plugins can require special first-use initialization after boot. When a scan finds an eligible Waves VST3, LiveSoundRack may offer Waves Prewarm.

The normal procedure is:

1. Set OPTION → Plugin Process Isolation to Off.
2. Stop ASIO.
3. Enable Auto-initialize Waves (Server).
4. Scan plugins.
5. Choose Yes in the Waves Prewarm prompt.
6. Keep the LiveSoundRack Tray app open.
7. The LiveSoundRack server restarts automatically once.
8. Wait for the Server to return before continuing.

Waves Prewarm may be skipped when ASIO is active, isolation is enabled, or no eligible Waves plugin is found.

#Part 4 — RACK tab

#12. What a rack is

A rack is a virtual processing strip. It is similar to a channel strip or bus in a digital console.

The normal path is:

Input route
  → Input Gain
  → Automixer
  → plugin slots
  → rack Output Gain and Mute
  → global timing alignment
  → Output route

A rack can be Mono or Stereo. It can receive physical ASIO inputs, Playback L/R, or built-in test signals.

#13. RACK toolbar

#Console File

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

The button shows the current console name. A dirty indicator means the current state differs from the last saved version.

The recent list has an X beside each item. Clicking it deletes that Console File after confirmation.

#Autosave

Saves the current console automatically at 10-, 30-, or 60-second intervals. The normal selected interval is 30 seconds.

Autosave is useful while editing, but it can also preserve an accidental change. For critical work, keep a separate known-good console or backup.

#Add Rack / Remove Last

Adds a new Rack or removes the final Rack. In Remove Last (n), n identifies the Rack that will be removed. At least one Rack remains. A source Rack used by an active sidechain cannot be removed until the sidechain is disabled or reassigned.

#DFB Response

This control appears only when the supported De-Feedback 1.1.4 plugin is present in the server catalog. Other versions do not expose this host-specific control.

Choices are:

• Fastest — quickest adaptation and the most frequent model work;
• Fast;
• Slow;
• Slower — least frequent model work and the slowest adaptation.

DFB Response lets you choose the feedback response speed when supported De-Feedback 1.1.4 is installed.

#ERROR

ERROR: n shows the combined total of ASIO OverLoads, DSP Overruns, and Dropout Signals. Click it to see all three counters, then click RESET when you want to clear them.

• ASIO OverLoads means the ASIO driver itself reported an overload. Some drivers do not provide this report.
• DSP Overruns means the Server used more processing time than the available audio time across an approximately 10 ms group of audio blocks.
• Dropout Signals means the ASIO sample or callback flow showed a missing or seriously late section.

The counters help locate a problem, but they are not an exact audible-click counter. RESET starts the displayed counts again without stopping ASIO.

#CPU and RAM

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. An orange ! or border indicates sustained high Windows memory pressure; red indicates critical pressure. Adding a plugin requires a shared server confirmation whenever the latest valid commit reading is 80% or higher, even if the orange marker has not appeared yet.

#Fold

Use ▲ or ▼ to collapse or expand the Rack area.

#LOCK

Prevents accidental rack-structure changes. Enable it after the system is built and tested.

#14. Rack identification and appearance

A rack can have:

• a descriptive name;
• a background color;
• a foreground/text color;
• a Mono or Stereo width;
• a rack preset name and dirty indicator.

Use short, clear labels such as Lead Vocal, Host Mic, Playback, or Broadcast Mix. Color can help operators identify groups, but do not rely on color alone.

#15. Input routing

Each rack input destination selects one source.

Sources can include:

• physical ASIO input channels;
• Playback L;
• Playback R;
• Pink Noise;
• 300 Hz;
• 500 Hz;
• 1 kHz;
• 2 kHz;
• 4 kHz.

The same source may feed more than one rack. This is useful when one microphone must be processed differently for separate outputs.

#Mono behavior

A Mono rack uses the left path. The right input and right output are not active.

#Stereo behavior

A Stereo rack uses left and right paths. Choose matching left/right inputs and outputs where appropriate.

#Test-signal warning

Built-in test signals are continuous while routed and ASIO is running. Start with the rack muted and Output Gain low. Remove the route when testing is complete.

#16. Input Gain and input meter

Input Gain ranges from -60 dB to +24 dB in 0.5 dB steps.

Use it for normal trim correction, not as a substitute for proper microphone preamp gain. Watch the input meter before adding heavy plugin processing.

#17. Automixer

Automixer is available at the rack input stage. It is intended for workflows where automatic level sharing is useful, such as groups of open microphones.

Do not enable it blindly. Listen to speech transitions, ambience, and gain-sharing behavior under realistic conditions. A music, effects, or playback rack may not benefit from automixing.

#18. Plugin slots

A rack provides up to 32 plugin slots. Audio flows through them in order from top to bottom.

#Insert a plugin

1. Click an empty slot.
2. Select VST3 or CLAP.
3. Choose vendor/category.
4. Choose the plugin.

#Open a plugin

• Left-click a healthy loaded slot to open the Original Editor.
• Right-click and choose Open Editor(Generic) or Open Editor(Original).

#Slot menu

An empty slot also shows the common slot actions and the plugin selection list. Actions that do not make sense for an empty slot are greyed out. Paste Plugin becomes available when you have copied a plugin, and Load Plugin Preset remains available.

A normal loaded slot can offer:

• Empty Slot
• Bypass Plugin
• Open Editor(Original)
• Open Editor(Generic)
• Copy Plugin
• Paste Plugin
• Save Plugin Preset
• Save Plugin Preset As
• Load Plugin Preset
• Reload Isolated Plugin Host, when isolation is active

A crashed isolated slot can offer:

• Empty Slot
• Bypass Plugin
• Reload Plugin
• Acknowledge Crash

#Move plugins

Drag a plugin to another slot or rack. The target graph and state are prepared before becoming the active audio graph. Even so, do large structural changes during safe moments and use an appropriate Audio Transition setting.

#19. Plugin bypass and rack bypass

Plugin Bypass removes one plugin's effect while keeping the slot available.

Rack Bypass bypasses the rack processing path. Confirm how the bypassed signal interacts with the surrounding routing and gain structure before using it live.

Bypass changes can produce discontinuities in some plugins. Audio Transition Time can reduce clicks when process isolation is Off.

#20. Original and Generic Editors

#Generic Editor

The Generic Editor:

• works inside the browser;
• displays editable plugin parameters;
• does not require the plugin on the client computer;
• does not show the plugin manufacturer's custom interface;
• does not provide plugin-owned RTA or analyzer graphics.

It also works for isolated plugins. Parameter names, ranges, units, and flags are obtained from the authoritative server/PluginHost metadata path outside the realtime audio callback. A newly opened isolated editor may briefly wait for that metadata, but it does not need a client-side plugin installation.

Use it for simple remote parameter changes or when a matching client plugin is unavailable.

#Original Editor

The Original Editor displays the manufacturer's own GUI.

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 a remote Windows client:

• install the same plugin build/version as the server whenever possible;
• use the manufacturer's installer first when the plugin has dependencies or licensing services;
• for a standalone plugin, place it in the VST3 or CLAP folder beside LiveSoundRack.Client.exe;
• copy the complete .vst3 bundle/container, not only one internal DLL;
• allow the editor helper through the firewall.

The Client creates its local VST3 and CLAP folders when possible. EditorHost first tries the server-supplied path when that same path exists locally, then its local catalog, then a scan of the Client drop folders and standard Windows VST3/CLAP locations. It selects by plugin format and stable identity rather than by display name alone.

The local copy exists only to show the Original Editor. Parameter changes are sent to the authoritative plugin slot on the Server. The Client copy never replaces the Server's show-audio processing.

#Live Audio in a remote Original Editor

The Original Editor top bar can enable Live Audio. This sends a monitor-only preview of the selected Server slot's post-PDC, pre-plugin main input and optional sidechain input to the remote plugin window so compatible meters, analyzers, and RTA displays can react.

Important points:

• UDP port 21013 must be reachable.
• It does not queue old windows or catch up after a delay. If the editor is busy or packets are lost, stale visual frames are skipped in favor of the newest available signal.
• A Mono plugin uses about 2 Mbps. A Stereo plugin with sidechain audio can use up to 8 Mbps.
• The remote plugin output is discarded.
• Live Audio never replaces the Server's production audio path.
• The plugin must actually provide a meter/analyzer; LiveSoundRack cannot create one inside a plugin that has none.

#21. Sidechain

When a plugin exposes an external sidechain input, its Original Editor top bar shows sidechain controls.

1. Open the Original Editor.
2. Enable Sidechain.
3. Select an available source rack/path.
4. Verify the plugin receives the intended source.
5. Check timing and PDC.

A rack used as a sidechain source cannot be removed while the route is active. Rack preset and paste operations check sidechain validity. A route that cannot exist in the new target may be cleared or require confirmation.

#22. Per-rack PDC and global PDC

Plugins can report processing latency.

• Per-rack PDC helps maintain timing inside the rack and with sidechain paths.
• Global PDC delays lower-latency racks so their outputs align with the most delayed active rack.

PDC improves timing but increases overall delay. Keep it on when phase/time alignment is important. Turn it off only after measuring the result and accepting the timing difference.

#23. Output Gain, meter, mute, and routing

Output Gain ranges from -60 dB to +24 dB in 0.5 dB steps. The output meter shows the rack result.

Each physical ASIO output destination can be owned by only one rack output. If a destination is already used, choose another output or change the existing route.

Mute the rack before changing a critical output route. Confirm destination labels from the ASIO driver; channel names can change after driver or interface configuration changes.

#24. Rack presets and rack clipboard

#Copy Rack / Paste Rack

Copies the rack processing configuration and plugin states to a clipboard, then applies it to another rack. Plugin availability and sidechain dependencies are checked before replacement.

#Reset Rack

Keeps the target rack's input/output routing and width, but clears other rack settings and plugins.

#Rack presets

The Rack Preset menu offers:

• Save Rack Preset
• Save Rack Preset As
• Load Rack Preset

A rack preset stores rack processing settings and plugin state. It loads only into a rack of matching width. The target's physical input/output routing remains in place. Exact plugin availability and compatible versions are required.

#25. Plugin presets

A plugin preset stores one plugin instance's state. It is useful for reusable EQ, compressor, reverb, or other plugin configurations.

Preset operations are in the plugin slot menu:

• Save Plugin Preset
• Save Plugin Preset As
• Load Plugin Preset

A matching plugin must exist on the server when loading. Vendor state compatibility can change between plugin versions, so keep exact production versions backed up.

#Part 5 — Console files

#26. What a console stores

A Console File stores the Rack layout, routing, plugins and their settings, gains, mute and bypass states, sidechains, names, colors, and timing settings.

Console files and plugin-state sidecars are stored under LiveSoundRackData on the server.

#27. Loading and saving

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

Save a baseline before experimenting. Use names that describe the show, room, date purpose, or revision without adding a file extension.

#28. Autosave

Autosave can run every 10, 30, or 60 seconds. It is convenient during setup and protects recent work.

Limitations:

• An unwanted accepted change can also be autosaved.
• Autosave is not a substitute for an offline backup.
• A plugin that cannot provide a valid state may prevent part of the desired state from being saved.

#29. Console change modes

Open OPTION → CONSOLE CHANGE.

#Instant

Loads the target immediately. It uses the least transition processing but may reveal clicks or discontinuities in some graphs.

#Fade

Fades audio out, loads the target, then fades in. Available fade times range from very short values to 10 seconds.

#Crossfade

Runs the old and new console graphs together and crossfades. It uses extra CPU and memory. It is unavailable when Plugin Process Isolation is active.

Test the selected mode with the two heaviest real consoles. A system at 70% CPU on one graph may not have enough headroom to run two graphs during a crossfade.

#Part 6 — OPTION tab

#30. Audio-Safe Plugin State Saving

This reduces the chance that plugin state capture interrupts the audio path. It uses extra CPU and memory because additional state handling is prepared away from the realtime path.

Leave it enabled when reliable live saving is more important than minimum resource use, then test the full configuration.

#31. Auto-initialize Waves (Server)

Enables the Waves startup prewarm workflow. Prewarm requires Plugin Process Isolation Off and stopped audio.

#32. Audio Transition Time

Smooths changes such as:

• plugin insert/replace;
• plugin or rack bypass;
• mute changes;
• routing changes;
• engine start/stop.

Choices include one, five, or ten ASIO blocks and 10 ms, 100 ms, or 1 s.

Long transitions sound smoother but make controls take longer to settle. Audio Transition is disabled whenever Plugin Process Isolation is active.

#33. Plugin Process Isolation

Isolation runs plugin DSP outside Server Core.

#Off

All plugins run in Core. This uses the least process and transport overhead. A faulty plugin has the greatest chance of affecting the whole engine.

#Group by Plugin

Instances of the same plugin share a helper process.

#Group by Rack

Plugins in the same rack share a helper process.

#Isolate Each Slot

Every slot receives its own process. This provides the strongest fault containment but can use much more CPU, RAM, handles, and process-management overhead.

#Transport Latency

Choose 0 to 10 ASIO blocks. The first-run value is 2 blocks. More blocks give the isolated process more scheduling room but add latency. A 0-block setting is the most demanding and can crackle or underrun on some systems.

#Isolation limitations

• Audio Transition Time is unavailable.
• Console Crossfade is unavailable.
• Shared modes can lose several slots when one shared host fails.
• More isolation does not fix an incompatible or unlicensed plugin.
• Isolation adds resource use and transport latency.

#Part 7 — PLAYBACK tab

#34. How playback reaches the speakers

Playback creates two virtual sources:

Playback L
Playback R

They must be routed into a Stereo rack. That rack must then be routed to physical ASIO outputs.

Playback can continue running even when it is not routed to hardware. If the time counter moves but you hear nothing, check the rack route.

#35. Supported files

The playback engine accepts:

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

Windows Media Foundation on the server performs decoding. A file can still fail if the required codec is unavailable or the file is damaged.

The file browser shows the server filesystem. A file on a remote client must first be copied to storage that the server can access.

#36. Transport controls

• STOP — stops and returns according to current behavior/fades.
• PAUSE — pauses with the selected Pause-out fade.
• PLAY — starts or resumes with the selected Play-in fade.
• PREV — selects the previous item according to the playlist.
• NEXT — selects the next item.
• ADD — opens the server-side file/folder browser.

#37. Play modes

• stop after this track
• stop after this list
• repeat this track
• repeat this list
• shuffle this list
• shuffle all lists

Choose the mode before starting unattended playback. Shuffle modes deliberately change item order and should not be used for cue-critical theater or broadcast playback unless that is intended.

#38. Volume and AutoGain

Playback Volume ranges from -60 dB to +24 dB.

AutoGain uses ITU-R BS.1770 / EBU R128-style loudness analysis with a target of -23 LUFS. Analysis happens in the background and may show as pending after a file is added.

AutoGain is a starting point, not an artistic mix decision. Verify every important track by ear and meter. Analysis measures at most the first 300 seconds, so a long track with a very different ending may not be represented fully.

Gain Transition controls how quickly a new gain correction settles.

#39. Safety Limiter

Limiter choices range from none through 0 dBFS to -3.0 dBFS. The default selected ceiling is -1.5 dBFS.

The limiter protects the playback source before it enters a rack. A plugin, rack gain, or later summing can still clip. Keep final output metering and gain structure under control.

#40. Fades

You can set:

• Play in
• Pause out
• Stop out
• Change in
• Change out
• Change cross

Available values are 0, 1, 2, 3, 5, or 10 seconds. The three Change settings control the behavior when moving between tracks.

#41. Waveform and seeking

Enable Waveform to display analyzed waveform data and click/drag to seek.

Waveform limits:

• It uses 1024 min/max display bins.
• It is not generated for files longer than 600 seconds.
• A file without a waveform can still play.

#42. Playlists and tabs

A playlist row shows:

• item number;
• filename;
• length;
• AutoGain status/value.

Use the move controls to place an item at the top, move it up/down, or move it to the bottom. Remove deletes it from the playlist, not from the source disk.

Multiple playlist tabs can be created, named, removed, reordered, and selected. Use clear names such as Walk In, Show, Break, and Emergency.

#43. Analysis cache

Playback stores reusable analysis data under LiveSoundRackData\Playback\AnalysisCache.

Clean Cache removes orphaned cache items. It is available only when ASIO is stopped. Do not delete cache/transaction files manually while Server Core is running.

#Part 8 — RECORD tab

#44. What can be recorded

#Input channels

• raw physical ASIO inputs before rack processing;
• Playback L and Playback R virtual inputs.

#Output channels

• final physical ASIO output channels after rack processing and routing.

Output recording is not a separate arbitrary rack-stem recorder. It captures what is being prepared for the selected ASIO output channel.

#45. Channel table

Every row has:

• an enable checkbox;
• channel number;
• Source Name or ASIO Name;
• Record Name.

Click a Record Name to edit it while not recording. Every enabled channel needs a valid name.

#46. Start and stop

To start recording:

1. Start ASIO.
2. Enable at least one input or output channel.
3. Check every Record Name.
4. Confirm free disk space.
5. Click Start Record.

While recording, channel and profile controls are locked.

To stop:

1. Click Stop Record.
2. Wait for the UI to return to the non-recording state.
3. Then restart, shut down, or remove storage.

#47. Recording file format

Each selected channel is written as its own:

• mono WAV;
• 32-bit IEEE floating point;
• active ASIO sample rate.

Files are split into numbered parts before the WAV data reaches 2 GiB.

Example:

ch_01_Lead_Vocal_001.wav
ch_01_Lead_Vocal_002.wav

#48. Session folders

Sessions are written on the server:

LiveSoundRackData\Record\Sessions\<Profile_YYYYMMDDHHMMSS>\INPUT\
LiveSoundRackData\Record\Sessions\<Profile_YYYYMMDDHHMMSS>\OUTPUT\

Use a fast local disk. The audio callback does not stop to wait for slow storage. If the writer cannot keep up, recorded blocks can be dropped.

#49. Record profiles

The profile toolbar offers:

• Load
• Save
• Save As

A profile stores selected channels and Record Names. It is tied to the committed ASIO device topology.

A profile may be rejected when:

• no ASIO device is committed;
• the device identity is different;
• physical input/output channel counts do not match.

If channel names change but the indexed layout is still compatible, the profile can keep the indexed mapping with a warning. Verify the profile after driver, firmware, or interface changes.

#Part 9 — SERVER tab

#50. Status display

The SERVER tab shows the selected server and status for:

• LiveSoundRack.Server.exe;
• LiveSoundRack.Server.Core.exe;
• LiveSoundRack.Server.Web.exe;
• ASIO Audio;
• Record;
• Playback.

Unknown means the status could not be confirmed, not necessarily that the component has failed.

#51. Restart Server Core

Use Restart LiveSoundRack.Server.Core.exe for a normal restart. It interrupts audio and disconnects editor/client sessions while Core restarts.

Before restarting:

• stop recording;
• stop or account for playback;
• save the console;
• mute the system.

#52. Force Restart Server Core

Use forced restart only when normal restart cannot complete or Core is unresponsive. It is less graceful and can interrupt file finalization or unsaved operations.

#Part 10 — ABOUT, demo, and license

#53. Demo behavior

The demo period is 30 minutes from Server Core start. The remaining time appears 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.

Do not use the demo for an uninterrupted production event longer than the available 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.

#54. Activate and deactivate

Open ABOUT and click Activate. Enter:

• license email;
• access key.

Activation or deactivation may require Internet access. When licensed, the button changes to Deactivate. Protect license credentials and follow the license provider's rules when moving the server to another machine.

#Part 11 — Files, backup, and names

#55. Server data folders

LiveSoundRack creates these beside Server Core:

LiveSoundRackData\
VST3\
CLAP\

Important items inside LiveSoundRackData include:

The local VST3\ and CLAP\ folders are plugin scan roots. Catalog files are stored in LiveSoundRackData, not inside those plugin folders.

#56. Backup

For the safest backup:

1. Stop recording.
2. Save the current console.
3. Stop Server Core or exit the server tray.
4. Copy the complete LiveSoundRackData folder.
5. Copy the local VST3 and CLAP folders if used.
6. Keep installers and exact plugin versions separately.
7. Preserve plugin licenses using each vendor's supported method.
8. Record the ASIO driver/interface version and channel layout.

A data backup does not guarantee that a plugin license or binary state will work on a different machine or plugin version.

#57. Naming rules

Console, rack preset, plugin preset, record profile, playlist, playlist tab, and Record Name fields follow a common policy.

Allowed:

• Unicode letters;
• numbers;
• spaces;
• _;
• -;
• ..

Limits:

• 128 characters maximum;
• no leading or trailing space;
• no final period;
• not . or ..;
• no Windows reserved names such as CON, PRN, AUX, NUL, COM1–COM9, or LPT1–LPT9;
• do not type managed extensions such as .json or .wav;
• do not type the Console. prefix.

#Part 12 — Multi-client and network operation

#58. Shared server state

Every LiveSoundRack Client app and Web UI controls the same Server state. A change accepted from one client appears on the others after synchronization.

Risky or destructive actions use a server-owned shared confirmation. All connected App/Web clients can see the same prompt, the first valid response wins, and the prompt closes everywhere. The command is executed at most once by the client that originated it. This applies to operations such as restart/power actions, isolation changes, destructive console/preset operations, rack/plugin replacement, and the high-memory plugin-add warning.

Local input errors, a local launch failure, or a connection problem that exists only on one computer remain local and do not block every client.

For ordinary scalar controls, the Client may hold the value you just selected while waiting for the matching authoritative revision. If the Server rejects the change or the session changes, the control returns to the accepted Server value. Structural rack changes wait for the authoritative state rather than pretending they are already complete.

When two operators send conflicting commands, Server acceptance order determines the final state. Assign clear control responsibility during a show.

#59. Network interruption

A client network failure does not normally stop Server Core audio. The disconnected client stops receiving current state and should not be trusted until it reconnects and resynchronizes.

A remote Original Editor Live Audio preview can fail or become jumpy without affecting production audio. It is monitor-only.

#60. Firewall checklist

On trusted interfaces, allow the required LiveSoundRack applications and ports:

• TCP 21010 for supervisor control;
• UDP 21010 for discovery;
• TCP 21011 for Web UI/public control;
• Remote Original Editor Live Audio preview.

TCP 21012 is private loopback communication on the server and should not be exposed remotely.

#Part 13 — Performance and limitations

#61. CPU and latency

CPU use rises with:

• more racks;
• more plugin slots;
• expensive oversampling/linear-phase plugins;
• small ASIO buffers;
• plugin isolation;
• console crossfade;
• high channel counts;
• playback decoding and analysis;
• recording many channels;
• remote Original Editor windows and Live Audio on the Client.

Rack latency can include plugin-reported latency, PDC, and isolation transport. Test the actual end-to-end system, not only the ASIO driver's displayed number.

#62. Plugin limitations

• Only VST3 and CLAP are supported.
• A plugin can crash, hang, reject state, or behave differently at another sample rate.
• A remote Original Editor needs a matching local plugin. Use the same version/build whenever possible.
• Standard installer locations and the VST3/CLAP folders beside LiveSoundRack.Client.exe are searched by format and identity.
• Plugin state compatibility is controlled by the plugin vendor.
• Some plugin UIs do not support remote shadow operation perfectly.
• Generic Editor exposes server-published parameters, not every custom feature in a vendor GUI.
• Live Audio animates a compatible remote GUI but does not return its processed output.
• The special DFB Response control is available only for the supported De-Feedback 1.1.4 identity/version; unsupported builds continue as ordinary plugins without that control.

#63. Routing limitations

• One source per rack input destination.
• One rack output owner per physical ASIO output destination.
• Playback needs an explicit rack route.
• Test signals need an explicit rack route.
• Mono uses the left path.
• A sidechain source rack cannot be removed while referenced.

#64. Playback limitations

• Supported extensions are WAV/WAVE, MP3, M4A, AAC, FLAC, and WMA.
• Server codec availability still matters.
• The server must be able to read the file path.
• AutoGain measures at most the first 300 seconds.
• Waveforms are not generated beyond 600 seconds.
• The playback limiter is before rack processing.
• Corrupt or unsupported media can fail to decode.

#65. Recording limitations

• ASIO must be running.
• At least one channel must be enabled.
• Record profiles depend on ASIO topology.
• Files are mono 32-bit float WAV, one per selected channel.
• Files split before 2 GiB data.
• Slow storage can cause dropped recorded blocks.
• Stop recording before restart or shutdown.

#66. Control/security limitations

• The built-in Web UI uses HTTP.
• The server should stay on a trusted LAN.
• Discovery may not cross VLANs or Wi-Fi isolation.
• Direct Internet exposure is unsafe.

#Part 14 — Troubleshooting

#67. Server not found

1. Confirm LiveSoundRack.Server.exe is running.
2. Open the SERVER tab or tray status locally.
3. Check Windows Firewall on server and client.
4. Confirm both devices are on the correct network.
5. Disable Wi-Fi client isolation or use wired Ethernet.
6. Try http://server-ip:21011 directly.

#68. ASIO start fails

1. Confirm interface power and cable.
2. Close DAWs and other ASIO hosts.
3. Refresh the device list.
4. Select a supported rate/buffer.
5. Reopen the manufacturer's control panel.
6. Restart Server Core normally.
7. Reboot the interface/server if the driver remains unavailable.

#69. No audio

Check in order:

1. ASIO running?
2. Correct rack input source?
3. Input meter moving?
4. Input Gain not at minimum?
5. Plugin/rack bypass and plugin crash state?
6. Rack mute off?
7. Output meter moving?
8. Rack output routed to the intended ASIO channel?
9. Another rack already owns that output?
10. Interface mixer and physical output turned up?

#70. Plugin missing or scan failure

• Confirm format and architecture.
• Confirm server-side path.
• Confirm license services.
• Scan again during maintenance.
• Check excluded list.
• Try the plugin in isolation only after confirming it can be scanned/loaded.

#71. Remote Original Editor fails

1. Install the same plugin version/build on the Client computer when possible.
2. Prefer the manufacturer's installer when the plugin needs dependencies or license services.
3. For a standalone build, place the complete VST3 bundle in VST3 or the CLAP file/package in CLAP beside LiveSoundRack.Client.exe.
4. If using Chrome, open LiveSoundRack.Client.exe and retry the Original Editor from the RACK screen. Chrome does not launch the Original Editor directly.
5. Allow EditorHost through Windows Firewall.
6. Confirm the server, Rack, slot, and slot instance still exist.
7. Reopen the editor after a rack/slot replacement; stale stable identity is rejected rather than redirected to another plugin.

#72. Remote analyzer does not move

• Enable Live Audio in the Original Editor top bar.
• Allow UDP 21013.
• Prefer wired Ethernet.
• Check that the selected server slot has main or sidechain signal.
• Confirm that the plugin GUI actually contains a meter/analyzer.
• Remember that the transport is latest-only: old visual frames are deliberately skipped instead of replayed after congestion.
• Close unnecessary remote Original Editors if the Client cannot keep up with the latest visual windows.

#73. Clicks, pops, or dropouts

• Increase the ASIO buffer.
• Reduce heavy plugin settings or oversampling.
• Check CPU Monitor and the global ERROR counters.
• Avoid console Crossfade without measured double-graph headroom.
• Increase isolation Transport Latency when isolated hosts underrun.
• Reduce rack/plugin count or isolation process count.
• If supported De-Feedback 1.1.4 model work is contributing to load, try a slower DFB Response setting and confirm that the slower adaptation is acceptable.
• Check Windows memory-pressure warning before adding more plugins.
• Check interface driver, USB power, DPC behavior, and thermals.
• Avoid scanning or major topology changes during the show.

#74. Recording drops blocks

• Use a faster local disk.
• Increase free space.
• Reduce enabled channels.
• Close other disk-heavy applications.
• Avoid simultaneous large file copies.
• Rehearse the full expected duration and channel count.

#75. Playback has no waveform

• Wait for background analysis.
• Confirm the file is readable and supported.
• Files longer than 600 seconds do not receive waveform data.
• Playback can still work without a waveform.
• Stop ASIO before using Clean Cache.

#76. Console or preset will not load

• Confirm the required plugins are installed.
• Confirm plugin versions match.
• Confirm target rack width matches a rack preset.
• Resolve or accept replacement confirmation.
• Check sidechain-source availability.
• Restore required state files from backup if missing.

#Part 15 — Recommended operating procedure

#77. Before a show

• Boot the server early.
• Confirm license state.
• Confirm interface, ASIO rate, and buffer.
• Load the production console.
• Verify input and output routes at low level.
• Test every critical plugin and sidechain.
• Verify the selected DFB Response wherever supported De-Feedback 1.1.4 is used.
• Check PDC and latency.
• Test playback files and route.
• Load the record profile and check disk space.
• Confirm CPU headroom and that RAM has no warning/critical marker.
• Confirm remote client, shared prompt behavior, and firewall.
• Enable LOCK.
• Save the console.

#78. During a show

• Watch meters and CPU headroom.
• Coordinate all operators.
• Avoid plugin scans and ASIO changes.
• Avoid large graph changes unless rehearsed.
• Do not use Force Restart unless Core is genuinely unresponsive.
• Watch recording status and disk space.
• Treat remote Live Audio as a visual aid, not the production signal.

#79. After a show

• Stop recording and wait for finalization.
• Stop playback.
• Save the final console if required.
• Note any plugin or routing issues.
• Shut down through the application or Windows safely.
• Back up LiveSoundRackData with the server stopped.

#Quick reference

#Essential startup order

1. Power interface
2. Start LiveSoundRack.Server.exe
3. Connect Client or Chrome
4. SETUP: select ASIO/rate/buffer
5. Run Plugin Scan and complete Waves Prewarm
6. RACK: input → plugins → output
7. Save Console
8. Route Playback / configure Record if needed
9. Test, mute safely, then open the system

#Essential shutdown order

1. Stop Record
2. Stop Playback
3. Save Console
4. Mute/turn down output
5. Stop ASIO if doing maintenance
6. Exit or shut down safely