How to make a Korg multisample (KMP/KSF) from your own WAV files

Yes. The Pa series reads Korg's native KMP multisample format (the same one used by Trinity, Triton and Kronos), plus KSF/AIFF/WAV samples in mono or stereo. The catch most people hit: if you load loose KSF or WAV files without their KMP, you lose the key map, tuning and loop data — the samples just sit there with no structure. You want a proper KMP. Xampler exports the complete KMP container, so what you load already has its keys, loops and tuning in place.

Because you loaded the samples without a key map. A raw sample has no idea which key it belongs to, so the Korg spreads one sample across all keys and pitches it as you go — sounding wrong everywhere except the original note. The key map (which lives in the KMP) is what assigns each sample to its correct key range and root pitch. Xampler detects each sample's pitch and writes the key map into the KMP automatically, so every note lands where it should.

Record or gather one WAV per note (or one WAV with several notes), get them tuned and mapped to the right keys, set loop points so held notes sustain, then save it as a Korg multisample (KMP + KSF). On the hardware this means sampling, assigning root/top keys per sample, and looping each one — slow and fiddly. Xampler does the mapping, pitch detection and looping for you and exports the KMP/KSF set ready to load.

It needs to be split into individual notes first, each note detected for pitch and mapped to its key, then looped. Doing that by hand — chopping, tuning, looping each slice — is hours of work. Xampler takes the single multi-note WAV, auto-splits it on the silences between notes, detects each note's pitch, finds a loop, maps it to the keyboard, and exports a Korg KMP (or SFZ/SF2) — automatically.

Yes for the KMP/KSF/KSC structures — Kronos and Pa4X read Triton's KMP, KSF and KSC files directly. What they can't read is the Triton PCG (the program/bank format). So samples and multisamples transfer; programs don't. If you only have loose WAVs and want a fresh multisample for a Kronos or Pa, Xampler builds the KMP/KSF set from scratch.

Both directions come up a lot. KSF is just Korg's sample wrapper around PCM audio, and KMP is the multisample map around the KSF files. Going WAV → KMP is the useful direction for building new sounds: you take ordinary WAVs and produce a Korg-ready multisample. Xampler does WAV → KMP/KSF (full container, with key map and loops). It builds the Korg side; it isn't a KMP-back-to-WAV ripper.

That's the usual desktop route — a paid auto-sampler with a Korg edition records an instrument and outputs a KMP you load on the Kronos. It works, but it's paid desktop software and a separate install. Xampler reaches the same end result — a loadable KMP/KSF multisample with mapping and loops — in the browser, nothing to install. If you already have your WAVs, you don't need a desktop auto-sampler at all.

Korg's KMP format allows only one zone per key, so a true stereo multisample has to be split into two parallel KMP files — a left and a right (-L / -R) — each holding mono KSF samples, played together. A single stereo blob doesn't fit the format. Xampler handles this automatically: a stereo source exports as the correct -L / -R KMP pair with a KSC manifest that loads both.

Korg KMP/KSF stores 16-bit PCM, mono, up to 48 kHz. Higher rates aren't supported by the target hardware, and stereo is handled as two mono files (the -L/-R split). If your source is 24-bit or 96 kHz, it has to be converted down first. Xampler exports within these limits, so the KMP you download is already in a format the keyboard accepts.