Native Instruments
Kontakt
Hosts sample-based instruments and builds custom multisampled instruments with key/velocity mapping, group-level playback, modulation, effects and multitimbral routing.
GUI Screenshot
From My Notebook
The page is ready. Listening notes, favorite settings, and experiments will live here.
The Overview
Sample instruments organized in layers
This entry follows the linked KONTAKT 6 manual. A Sample becomes playable through a Zone, which defines its keyboard and velocity context. Zones belong to Groups that share playback and processing settings; Groups form Instruments, and Instruments combine in a Multi. That hierarchy supports everything from a single triggered recording to a detailed acoustic instrument or a layered production setup.
Play first, edit when necessary
In normal rack use, an Instrument Header handles MIDI input, output, tuning and level. Its Performance View presents library-specific controls, such as articulations or effects, without exposing the underlying construction. Instrument Edit mode reveals mapping, waveform, group, source, modulation and processing panels for deeper work.
A platform, not one sonic character
KONTAKT's sound depends on the samples, programming and library being loaded. Its workflow is therefore to choose the instrument, confirm MIDI and output assignments, then adjust its own performance controls before editing the engine. For custom instruments, organize groups carefully and test the full keyboard/velocity response before adding complex processing. Global master controls and output channels handle the assembled Multi.
Source: Manual, “KONTAKT: The Big Picture,” pp. 22–24; “The Rack Multi Instrument Mode,” pp. 44–49; “The Rack Instrument Edit Mode,” pp. 50–53.
The Controls
Load and perform
Use the Browser to locate libraries, Instruments, Multis or samples, and load the required Instrument into the Rack. Performance View contains that library's own controls; there is no universal KONTAKT articulation, filter or microphone panel shared by every library. PV or the instrument icon shows/hides it, and a minimized header hides the custom panel.
Instrument header
MIDI Channel chooses what triggers the Instrument; Omni accepts all channels. Output Channel selects its audio destination independently of MIDI. Volume, Pan, Tune, Solo and Mute establish the balance. Tune covers ±3 octaves, with Shift for finer adjustment. Voices/Max Voices help diagnose notes being cut off; increasing the limit can preserve tails but also increases processing demands. Memory reports loaded sample usage, and Aux reveals send levels.
Use Purge only after understanding the library's behavior. Reset markers, play the intended part, then update sample pool can retain only used samples. Unplayed notes or velocity layers may no longer sound until reloaded, and round-robin/random sample selection needs special care. Reload all samples restores the full pool.
Instrument Edit mode
The wrench opens deeper editing where the instrument permits it. Check Displayed Group, Edited Groups and Edit All Groups before changing a group-level parameter: an edit intended for one articulation can otherwise affect every group. Quick-Save stores the instrument, and Undo/Redo are available for edit-mode operations when enabled.
Group Editor organizes groups. Mapping Editor creates Zones and maps samples to keys and velocity ranges. Wave Editor edits loops, slices and sample-level details. Source Module chooses sample playback behavior, while the source's Modulation Router animates its parameters. Group Insert Effects process individual voices; the Amplifier shapes group level, pan and phase. Instrument-level buses, inserts and sends combine and process the resulting sound. Script Editor hosts logic and custom control panels rather than serving as a necessary step for ordinary playback.
Global control and output
The Master Editor exposes Master Vol, Master Tune and Master Tempo. In plug-in use, Ext normally follows the host tempo; disabling it permits an independent tempo. Metronome and reference-tone controls assist setup. The Outputs section handles configured audio channels and auxiliary returns. Save an Instrument for its construction and a Multi for the collection and routing, keeping sample files available alongside the project.
Source: Manual, “Instrument Header,” pp. 45–46; “Purge Menu,” pp. 47–48; “Performance View,” pp. 48–49; “The Rack Instrument Edit Mode,” pp. 50–53; “The Master Editor,” pp. 72–73; “The Browser,” p. 74.