Manuals

KLANG:app 6.1 Preview: System Setup

KLANG:app & KOS 6.1 let you move settings as files instead of setting every unit up by hand. Export single settings, save a whole KLANG system into one file, or build that system offline before any hardware is on site. Then apply it to the units in one pass. This is for system technicians and rental companies who set up many processors and :kontrollers.

Latest update to this documentation 2026-11-02 for KOS & KLANG:app 6.1.1 (preview). Requires KLANG:app 6.1.1+ for macOS or Windows in ADMIN mode, and KOS 6.1.1+ on the processors and :kontrollers you set up. Back to the overview: What’s new in KLANG:app and KOS 6.1.

System Setup

Two kinds of files

  • A settings file (.ppf) holds the settings of one KLANG:app (KLANGapp.ppf) or of one device (KLANGfabrik.ppf). You choose which entries go in.
  • A system bundle (.KLANGsystem) holds a whole KLANG system: every processor, every :kontroller and every KLANG:app with its mix, its settings, its name and its control IP address. On top it can hold template settings for each device type.

What you can do

TaskWhere
Export settings of this KLANG:appCONFIG > APP > About & Help > Export Settings...
Save a connected device into a system bundleCONFIG > SETTINGS > Device Utilities > Save Device to System Bundle...
Build a system offline, without hardwareCONFIG > APP > About & Help > System Bundle Editor
Import a settings file or apply a system bundleDrop the file onto the KLANG:app window

Identity and licence entries never travel. A file from one unit cannot overwrite the serial number, the licence or the passwords of another unit.

Exporting settings

Settings of this KLANG:app

  1. Go to CONFIG > APP > About & Help and press Export in the row Export Settings....
  2. The table EXPORT SETTINGS lists every entry with its value and a switch. Switch off what should not go into the file.
  3. Press EXPORT <n> SELECTED and choose where to save the file. Keep the name KLANGapp.ppf: the import recognises the file by this name.

Entries that belong to this computer only (window position, skin, MIDI, receive port) and identity entries start switched off and are marked in the Note column. Switch them on if you want a full copy of your own setup.

The Export dialog of KLANG:app listing settings keys with a switch per entry and the buttons Cancel and EXPORT 56 SELECTED.
Choose the entries, then EXPORT <n> SELECTED.

Settings of the connected device

To keep all settings of a processor or :kontroller, save it into a system bundle (see Saving a system from real units). That is the usual way.

Saving a system from real units

Set the system up once on the real units, then collect it into one .KLANGsystem file, one device at a time.

  1. Connect KLANG:app to the first processor or :kontroller.
  2. Go to CONFIG > SETTINGS > Device Utilities and press Save to Bundle.
  3. Type a new file name to start a bundle, or choose an existing .KLANGsystem file to add the device to it.
  4. Connect to the next device and save it into the same file. Repeat for every unit.

Saving the same unit again replaces its entry in the bundle, it is not added twice. The first unit of each type also gives the bundle its template settings for that type; later units of the same type do not change them.

Building a system offline

The System Bundle Editor builds a .KLANGsystem file with no hardware on the network. Prepare the whole show in the office, then apply it on site.

Open it in CONFIG > APP > About & Help > System Bundle Editor with Open. It comes back as you left it, unsaved changes included.

The System Bundle Editor with a KLANG:vokal and a KLANG:konductor, each with its :kontrollers and KLANG:app, listing name, type, serial, processor, mix, user mode and control IP.
The System Bundle Editor: each processor with its :kontrollers and KLANG:apps underneath.

Adding devices

  1. In the row Add processors at the bottom, choose the type and the number of units and press ADD.
  2. Below every processor, + :kontroller and + KLANG:app add a client on the next free mix. Change the processor or the mix of a client in its row.
  3. Click the pencil next to a name to rename the device. This name is the name the unit gets when the bundle is applied (up to 12 characters).
  4. Enter the serial number if you already know which unit goes where. Without it, the unit is found by name or by type when you apply the bundle.

The X at the end of a row removes it. Removing a processor that still has clients asks whether they go too (REMOVE ALL) or stay without a processor (KEEP CLIENTS).

A click on a row selects it. Select several rows like in a file list: the box at the start of a row adds it, shift-click selects a range. The bottom row then shows what you can do with the selection, for example move :kontrollers and apps to another processor or set the user mode of the selected apps. CLEAR ends the selection.

Settings per device

The gear at the end of a row opens the settings of that device, in the same kind of list as CONFIG > SETTINGS. With several rows of one kind selected, a change goes into all of them.

  • :kontroller: mixing permissions with Mix UI Presets, the default bank, display, and Audio & Boost (headphone gain, ambience mic boost, digital mix boost).
  • Processor: Sample Rate and EQ Mode. On KLANG:vokal and KLANG:1 Pro also the Audio Input, Dante or MADI: every channel of that input goes to the KLANG engine, every mix back out, and the clock follows the input. unchanged leaves the unit’s own value alone.
  • KLANG:app: UI settings, screensaver, App User Mode, the recall-safe switches and Lock to Mix.

For everything else on a processor, select exactly one processor and press EDIT OFFLINE.... KLANG:app opens it in the Offline Editor with the settings of the bundle. Change CONFIG > SETTINGS (and on a KLANG:vokal CONFIG > ROUTING) as on a real unit, then press DONE to take the changes into the bundle, or CANCEL to drop them.

Templates from a real unit

LOAD TEMPLATE... takes a KLANGfabrik.ppf or KLANGapp.ppf exported from a real unit (see Exporting settings) and makes it the starting point for every device of one type: routing, clock, sample rate, EQ mode, or the :kontroller permissions. The type is the one of the selected row, otherwise the one chosen in Add processors. Addresses, names and identity of the source unit are never taken over.

Control IP addresses

IP ADDRESSES... opens CONTROL IP ADDRESSES with three choices:

  • Fixed addresses: enter Network, Prefix, an optional Gateway and the first host number for processors (First processor) and for :kontrollers (First kontroller). The preview shows the address of every device.
  • DHCP for every device.
  • Leave every device's address unchanged.

Nothing changes before APPLY. A KLANG:app gets no address from the bundle, and Dante addresses are not part of it.

Saving and opening

  • SAVE and SAVE AS... write the .KLANGsystem file. Before saving, the editor checks for duplicate names, serial numbers and addresses, and for clients on a mix their processor does not have.
  • OPEN... continues an existing bundle, also one saved from real units. CLEAR ALL starts an empty one.
  • UNDO (⌘ CMD + Z on Mac, CTRL + Z on Windows) takes back the last change, up to 50 steps.
  • APPLY... applies the saved bundle to the units on the network, see Applying a system bundle.

Importing and applying

Both kinds of files are imported the same way: switch KLANG:app to ADMIN mode and drop the file onto its window.

Importing a settings file

  • KLANGapp.ppf goes into this KLANG:app.
  • KLANGfabrik.ppf goes into the device KLANG:app is connected to. Connect to the right unit first.

Files with any other name are refused, so keep the name the export gave them. A dialog shows how many entries the file has, how many would change and how many are protected. Then choose:

ButtonWhat happens
MERGEOpens IMPORT SETTINGS, a table with the current and the new value of every entry. Only the entries you switch on are imported. Press IMPORT <n> SELECTED.
REPLACE ALLEvery entry that is not protected takes the value from the file. Entries the file does not contain are removed.

Identity and licence entries are always kept and shown greyed out. When the file comes from another unit, or does not say which unit it comes from, MERGE starts with its addresses, names and VLANs switched off. REPLACE ALL writes them, so the dialog warns you.

After a device import KLANG:app asks to reboot the device: network, clock and audio settings only take effect after a reboot. Press REBOOT (audio is interrupted) or Cancel to reboot later.

Applying a system bundle

Bring all units onto the network, then drop the .KLANGsystem file onto KLANG:app (or press APPLY... in the System Bundle Editor). KLANG:app looks for every KLANG device on the network and opens APPLY SYSTEM BUNDLE.

  1. Check every row. Device is the unit KLANG:app proposes for that entry of the bundle, Found by says how it was found: serial number, name or type only, check.
  2. Rows found by serial number or name start switched on. A row found by type only is a guess and starts switched off. Pick another unit in Device if the proposal is wrong; that switches the row on.
  3. Not sure which physical unit a row means? The identify icon in the Device cell makes that unit blink, like the identify button in CONFIG > CONNECT.
  4. Optional: switch on Also give the template settings to devices of these types that no row takes.
  5. Press APPLY TO <n> DEVICES.
  6. KLANG:app asks Reboot <n> devices?. Press REBOOT ALL.

Each unit first gets the template settings of its type, then its own settings on top. The :kontrollers and KLANG:apps then connect to their processor and mix by themselves.

Units that are not there yet stay switched off or show not found. SAVE REST (<n>)... saves exactly those rows as a bundle of their own. Set up the processors and :kontrollers now and apply the rest bundle to the musicians’ KLANG:apps at the first rehearsal.

Reboot right away. Answer the reboot question with REBOOT ALL, not with Cancel. The routing from a bundle is loaded at the next boot, and changing the routing or the clock on a unit before that writes the old routing back.
Every unit gets the name from the bundle. By default its Dante name follows. Renew Dante subscriptions of third-party devices that still use the old name.

Good to know

  • Show files are not part of it. A settings file and a system bundle carry settings, routing and names, not your shows, snapshots or mix presets.
  • No templates with addresses. Template settings of a type never contain IP addresses or names, so applying them to many units of the same type never gives two units the same address.
  • Cascades: a settings file goes to the connected unit only, never to its backup. To give the backup the same settings, connect to it and import there.
  • Undo an app import: before a KLANGapp.ppf import, KLANG:app keeps a copy of its old settings as KLANGapp_before_import_<date>.ppf. CONFIG > APP > About & Help > Open App Folders shows where.
  • No drop dialog? Switch KLANG:app to ADMIN mode, and check the file name: KLANGapp.ppf, KLANGfabrik.ppf or *.KLANGsystem.
  • A row says no serial? That unit does not report its serial number, so the bundle cannot be applied to it.
Found something odd? Please send us the bundle or settings file, the KOS and KLANG:app version and what you did, ideally with the log package from CONFIG > INFO > Collect Logs.

Still Have Questions?

Contact us here