DirectWave in FL Studio: Multisamples, Root Offset, VST Sampling

DirectWave is FL Studio's multisample sampler: it maps recordings across key and velocity zones, and its Channel Sampler can record any Channel Rack plugin into a playable instrument. Every edition includes the free DirectWave Player, which only opens .dwp and .dwb programs; building your own instruments takes DirectWave Full, included from the Signature Bundle up or bought separately. Either way, one rule decides whether the result plays in tune: set every sample's Root Key before stretching its zone across the keyboard. I'd treat that order as fixed, because a wrong root makes every zone, layer and loop decision after it wrong too.

For a simple three-note instrument, put low, middle and high recordings on their actual notes, then stretch each zone only until the next recording should take over. Add soft, medium and hard recordings as vertical velocity layers. If a sustained note should keep going while the key is held, set a clean loop and match the amplitude envelope to how the source ought to release.

The root tells DirectWave where a recording plays at its original pitch and speed; the zone tells it which notes and velocities trigger that recording. Below, you'll load presets and third-party libraries, build an instrument from your own files, sample a plugin with the Channel Sampler and its Root offset setting, and save a portable bank. You'll also see the failures that make sampled instruments feel wrong: off pitch, obvious timbre jumps, silent velocity gaps, loop clicks and missing files after a project moves.

Check whether you have DirectWave or DirectWave Player

DirectWave Player can load Image-Line’s own .dwp and .dwb formats, but the official DirectWave manual lists three limits that matter here: external samples cannot be added to patches, new patches cannot be created, and VST sampling is disabled.

If dragging a WAV file into the plugin does nothing, check the version before you troubleshoot the file. Image-Line lists DirectWave Full for the Signature Bundle and the All Plugins Edition and the Player for every edition, so Fruity and Producer owners have the Player unless they buy the full version separately; our FL Studio editions comparison covers the rest of the split. The Player is still handy for opening finished DirectWave programs.

Load presets, libraries and third-party formats

Finished programs load the same way in the Player and the full version. Set the Library path on the FOLDERS tab, to the right of the LIBRARY tab, by clicking the Home icon; DirectWave then scans that folder and all its subfolders for .dwp programs, and a double-click on the list loads one. You can also drag a .dwp file from the FL Studio Browser onto the plugin. The Online Content button opens Image-Line's Content Library, with free selections for most soundbanks so you can test them first.

Third-party libraries go through the importer, which needs the full version: right-click the PROGRAM tab and choose Open program. The manual lists AKAI AKP, Battery, EXS24, Giga, Kontakt and Kontakt 2, Kurzweil and some MPC disk formats, Reason NN-XT, Recycle, SoundFont2 and SFZ. A SoundFont with more than one program bank opens a dialog where you pick the banks to load. Encrypted or protected files won't import at all, so check with the vendor that a library isn't locked to another sampler before you buy it for DirectWave. My rule: no written confirmation that the files import, no purchase.

Prepare and name the source samples

DirectWave can map imperfect files, but clean source prep makes every later decision easier. Trim unwanted silence, keep a natural attack, and use the same recording format across one instrument. For sustained material, record enough stable tone after the attack to build a loop without repeating a section that keeps changing.

Use our Edison sample-editing guide when the files still need trimming, fades or click repair. DirectWave has its own editor, but cleaning up the source and mapping the instrument are two separate jobs. For one long recording of several notes, Edison can slice it and export each region as its own sample with sampler-ready names and metadata: File > Export regions > For sampler use.

Put the sampled note in each filename: Piano_C3.wav, Piano_F3.wav, Piano_C4.wav. Image-Line documents filename suffixes for root note, key range, velocity range and trigger group. One full example is samplename_C4+KA3-F#4+V64-95+TG1+TY3+TF100+TO15.wav. You don’t need that full syntax for a first instrument, since clear root-note names already prevent the most common mapping mistake.

The parser expects the mapping information after an underscore or a properly separated dash. A name like Strings_C4.wav can supply the root note; C4_Strings.wav doesn’t follow the documented pattern.

Read DirectWave as four working areas

Most of the work happens in the Program Window, which reads best as four connected areas:

1. Sample List: every loaded zone with its Root, LKEY, HKEY, LVEL and HVEL values.
2. Zone Mapper: the visual grid where horizontal width represents key range and vertical height represents velocity range.
3. Preview keyboard: audition notes and set a selected zone’s Root Key by right-clicking a key.
4. Lower tabs: Sample controls for start and loop editing, Zone controls for per-zone behavior, and Program controls for the whole instrument.

The horizontal and vertical axes are the key to the whole plugin. A zone that’s too wide pushes one recording too far from its pitch. A zone that’s too tall can cover velocities meant for another layer. When the instrument sounds wrong, look at the rectangle before you reach for filters or envelopes.

Add samples and set every Root Key

Drag WAV files from the FL Studio Browser into the Zone Window, and each drop creates a zone. You can also drop samples into the Sample List and then edit their numeric fields.

Select one zone at a time and set its Root Key to the note that was recorded. The Root field takes a MIDI note number, while the preview keyboard gives you a quicker visual route: right-click the key you want and the root marker turns orange. Play that key and make sure DirectWave isn’t transposing the sample.

If the Root Key is correct but the recording is still slightly sharp or flat, use the Fine tune (FINE) column in the Sample List, which corrects up to 50 cents either way. The DirectWave Zone settings separate pitch adjustment from the root assignment. Keep the root on the recorded note and correct the remaining tuning there.

If a recording is named correctly, Extract root key from filename can save you manual work. Automap Zone/s goes further when the WAV files carry embedded key-range and loop metadata. Automap doesn’t replace checking the result, though, because it can only use the metadata the files carry. When a file has no usable name, Find pitch root in the Zone window's right-click menu estimates its pitch.

Don’t start by stretching one sample across five octaves. Large transposition ranges change duration and timbre along with pitch: a piano note pitched far up gets shorter and brighter, and pitched far down it gets longer and darker. More recorded roots keep that movement small.

Divide the keyboard into useful key ranges

Once the roots are right, set the lowest and highest note for each zone. Drag the zone’s left and right control points or type LKEY and HKEY into the Sample List.

With recordings at C2, C3, C4 and C5, a practical first split puts each handoff roughly halfway between adjacent roots. That keeps the maximum transposition similar on both sides. Then listen to scales across every boundary. Move the split toward the sample that tolerates transposition better.

• If the lower sample becomes dull before the boundary, let the higher sample take over earlier.
• If the higher sample becomes thin below its root, extend the lower sample farther upward.
• If two zones overlap unintentionally, both sound and create a level or phase change.
• If there is a gap, notes inside it will produce silence.

Instrument character matters more than geometric symmetry. A stable synth waveform can cover a wide range. Piano, guitar, voice and acoustic textures usually expose wide transposition more quickly.

Sample any plugin with the Channel Sampler

The Channel Sampler is DirectWave's sampling robot: it records a Channel Rack plugin across the key range you set and builds a DirectWave program from the recordings. It works with native and VST plugins, with or without Mixer effects applied. Right-click the Channel button of the plugin you want to capture and choose Create DirectWave instrument. It needs DirectWave Full, because the Player has VST sampling disabled and can't create patches.

Two jobs make it worth the setup. A heavy synth sampled into DirectWave plays back as samples, so you can remove the plugin and stop paying its live CPU cost; our high CPU guide covers the other fixes. And a sampled patch travels to a producer who doesn't own that plugin. The name is close to FL Studio's Sampler channel, which is a different tool.

What Root offset does

Root offset sets how many notes above the first key of each Key zones range the Channel Sampler takes its recording, and the preview keyboard shows that root in blue. With Key zones at 3 and Root offset at 0, each recording sits on the lowest key of its zone and the two keys above it are pitched up from it. Set Root offset to 1 and the sample comes from the middle key, so no note in the zone is more than one semitone from a real recording.

My default is Key zones 3 with Root offset 1: it records a third as many samples as key-by-key sampling over the same range and keeps every note within a semitone of its source. For any odd zone width, half the width rounded down centers the root, so Key zones 5 takes Root offset 2. Check the blue keys on the preview keyboard before you start sampling.

The other settings decide how big and how playable the program gets:

• Low note and High note: the lowest and highest key to sample.
• Key zones: the width of each sample zone, shown as alternating grey and white sections on the preview keyboard.
• Velocity layers and Max velocity: each velocity step multiplies the patch size; with one layer, every note is sampled at Max velocity.
• Link velocity to gain: turns velocity into volume without changing the recorded samples.
• Cycle layers: repeated recordings with the same settings for round-robin variation, for sources that change on repeated notes; each cycle layer multiplies the patch size again.
• Stop on, Max length and Release after: Release after is how long the key is held, Max length is the total sample duration, and Stop on Silence ends a recording once it fades to -96 dB, never after Max length.
• Trim PDC delay: removes plugin latency from the start of each sample.
• Declick in and Declick out: a 20 ms fade for a start or end that wasn't captured cleanly.
• Normalize: raises the loudest sample to 100%, useful for a single velocity layer with Link velocity to gain on.
• Loop: Enable: automatic looping, which extends held notes while keeping the patch small.
• Stereo mode: Stereo, Mono Left Channel, Mono Right Channel or Mono Merged.

The manual warns that long samples, several velocity layers and small key steps add up to very large programs. I'd start with one velocity layer, Link velocity to gain and Stop on Silence, then add layers or cycles only when the source changes timbre with velocity or on repeated notes.

Build velocity layers without gaps

Velocity lives on the vertical axis. Use LVEL and HVEL, or drag the top and bottom zone points, to decide which playing strength triggers each recording.

For three layers, start with complete coverage:

• Soft: 0–42
• Medium: 43–84
• Hard: 85–127

My default is that even three-way split, adjusted to the performance: if the source changes character sharply between medium and hard, move the boundary, or use a small intentional overlap only when the blend improves the transition.

Test the layer map by repeating one note from quiet to hard. A sudden volume jump comes from the recordings, the velocity boundary or both. Don’t normalize every layer to the same loudness if the natural dynamic change is part of the instrument. You want a believable progression, not identical peak values.

Round robin needs a different control than velocity. Load several takes of the same note into zones over the same key and velocity range, give them one Trigger Group in the Zone tab and pick a Type: Cycle plays each layer in turn, Random picks one at random, and Avoid previous picks at random but never the same layer twice in a row. That last one is my default for repeated drum hits and plucks, since Random can play one layer repeatedly and defeat the purpose.

For velocity-layered drum pads, FPC is usually the clearer tool. DirectWave shines when the samples need pitched keyboard zones, sustained loops or a multi-program bank.

If you build the kit in DirectWave anyway, load the hits and choose Remap Zone/s as Drumkit from the Zone window's right-click menu to spread them across consecutive semitones. Set each hit's Loop Type to One Shot in the Sample tab so it plays to the end regardless of note length, and give closed and open hi-hats the same Mute group above 0 in the Sample List, so a closed hat releases a ringing open one.

Set sample starts and sustain loops

Open the Sample tab for start and loop controls. Keep the sample start ahead of the useful attack. Pushing it too far right can cut off the transient, while leaving noise or silence before the attack makes the instrument feel late.

A sustained loop repeats a stable section for as long as the key stays down. Place Loop A and Loop B inside a stretch of the recording where level and tone change slowly. Image-Line notes that loop clicks usually come from different amplitudes or phases at the two boundaries. Similar waveform height isn’t enough; the waveform should also be moving in the same direction.

Right-click the waveform and use Tools > Tune loop to move the markers between zero crossings. Zoom in before you make the final choice. If the sound still pulses or changes color at the join, move the loop to a steadier section. A Bounce loop can help when forward repetition makes a slow tonal change jump, but some recordings need crossfading or source editing before they’ll loop well.

Match the envelope to the loop

A loop can be technically clean and still feel unnatural if the program envelope cuts it off. For a held instrument, the amplitude sustain has to keep the note alive while the key stays down, and release decides how the note ends after key-up.

Use a short release for tight plucks and rhythmic patches. For a loop that holds and then plays its recorded tail, choose Sustained: the looped region repeats while the key is held, and the audio beyond Loop End plays on key release. Image-Line’s Sustained-loop instructions also require enough ADSR Release in the Zone tab for that tail to sound. Keep usable audio after Loop End and shorten the release if it blurs the next phrase.

Separate three symptoms:

• Click while holding: inspect loop boundaries.
• Click only at note-off: inspect the release transition and the audio after the loop.
• Note dies while held: inspect the loop mode and amplitude sustain.

Shape the sound: filters, LFOs and the Mod Matrix

The Zone tab carries a synth section for each zone. Two variable state filters run in parallel or in series, LFO1 and LFO2 add movement, and the Modulation Matrix assigns one variable to modulate another, such as LFO 1 on filter cutoff. It has 4 banks of 4 pairings: bank 1 holds the basic note controls by default, and banks 2 to 4 start empty. The same tab adds Ringmod, Decimator, Quantizer and Phaser to each sample on its own.

Whole-program behavior sits on the Program tab: Poly, Mono or Legato play mode, Glide for slides between notes, and the settings for Delay, Chorus and Reverb, which each zone feeds through its own send on the Zone tab. Those three are global effects shared by all voices, because they're too CPU hungry to run voice by voice. My order: map and loop first, shape the sound second. A filter can't fix a zone that's stretched too far.

Choose .dwp or a monolithic .dwb

A standard .dwp program usually doesn’t hold the wave data. The manual says its samples are typically stored in a same-name subfolder next to the program. That keeps files easy to edit and replace, but moving only the .dwp breaks the instrument.

Monolithic mode saves the samples inside a .dwb DirectWave Bank. A bank can contain up to 16 Program Channels, so .dwb is useful when one portable file matters more than an exposed sample folder.

Use .dwp while the instrument is still changing and you want direct access to the WAV files. Use a monolithic .dwb for transfer or archiving once every zone checks out. Keep the original lossless recordings separately, because an embedded bank is a delivery format and shouldn’t be your only copy of irreplaceable source audio.

For FL Studio Mobile, choose Save for FL Studio Mobile in the Disk operations menu, which writes a monolithic .dwp; a normal .dwp save also works with the Mobile DirectWave sampler. Our FL Studio Mobile vs desktop comparison covers the other differences between the two apps.

If a project already opens with unresolved paths, use the missing-samples recovery guide before resaving the bank.

Fix DirectWave problems by symptom

A sample plays at the wrong pitch

Play the zone’s Root Key. If the recording already sounds transposed there, the root assignment is wrong or the source filename was read incorrectly. Correct Root before you change LKEY or HKEY.

Some notes are silent

Look for horizontal gaps between zones. Then check the selected note at several velocities, because a complete key range can still go silent if its velocity layers leave a vertical gap.

One note sounds doubled or suddenly louder

Check for overlapping zones at the same key and velocity. Intentional layering is fine, but accidental overlap triggers more than one sample.

The instrument changes character abruptly across the keyboard

Move the key boundary, add another sampled root or replace the weaker recording. Filters can mask a boundary, but they can’t bring back detail lost to excessive transposition.

Velocity produces a hard jump

Compare the source levels and tone first, then adjust LVEL/HVEL. A boundary problem and a recording-level problem often turn up together.

The sustain loop clicks or wobbles

Match the waveform amplitude and direction at Loop A and Loop B, use Tune loop, and move the repeated region into a steadier section. If the source changes continuously, prepare a crossfade in the source editor.

The program works on one computer but not another

The .dwp was moved without its sample folder or with changed relative paths. Restore the folder structure or transfer a checked monolithic .dwb.

DirectWave build checklist

• Confirm you are using the full DirectWave feature set for custom sample mapping.
• Trim and name every source file with its recorded note.
• Set every Root Key before extending key ranges.
• Play scales across each LKEY/HKEY boundary.
• Cover velocities 0–127 without unintended gaps or overlaps.
• Keep loop markers inside a stable sustain at compatible zero crossings.
• Match sustain and release behavior to the loop type.
• Save the companion sample folder with a .dwp, or use monolithic .dwb for a portable bank.
• Reopen the saved instrument and check roots, boundaries, layers and loops before moving it.

My verdict: DirectWave gets predictable once each rectangle has a clear job. Root sets the sample’s true note, horizontal width sets which pitches it covers, vertical height sets which dynamics it covers, and the save format decides where the audio lives. Build in that order and the instrument stays easier to tune, play and move.

Frequently asked questions

What is DirectWave in FL Studio?

DirectWave is FL Studio's multisample sampler. It maps recordings across key and velocity zones, adds filters, envelopes, LFOs and effects to each program, and its Channel Sampler can record any Channel Rack plugin into a sampled instrument. A bank holds up to 16 programs.

What does Root offset do in DirectWave?

In the Channel Sampler, Root offset sets how many notes above the first key of each Key zones range the recording is taken from. With Key zones at 3, Root offset 0 samples the lowest key of each zone and Root offset 1 samples the middle key, so every note stays within a semitone of a real recording. The root shows in blue on the preview keyboard.

Is DirectWave free in FL Studio?

DirectWave Player is free and included in every edition, but it only loads .dwp and .dwb programs. Adding your own samples, creating patches, sampling VST plugins and importing third-party formats need DirectWave Full, which comes with the Signature Bundle and the All Plugins Edition or as a separate purchase.

How do I sample a VST with DirectWave?

Right-click the plugin's Channel button in the Channel Rack and choose Create DirectWave instrument. Set Low note, High note, Key zones, Root offset and the velocity and length options, then let the Channel Sampler record. It works with native and VST plugins, with or without Mixer effects, and needs DirectWave Full.

How do I change the root note in DirectWave?

Select the zone and right-click the key you want on the preview keyboard below the zone mapper; the root key turns orange. You can also type a MIDI note number in the Root column of the Sample List, or let Find pitch root estimate the pitch of the selected sample.

Can DirectWave open Kontakt or SoundFont files?

DirectWave Full imports Kontakt and Kontakt 2, SoundFont2, SFZ, EXS24, Battery, Giga, AKAI AKP, Reason NN-XT and Recycle files: right-click the PROGRAM tab and choose Open program. Encrypted or protected libraries won't import, so check with the vendor before you buy a library for DirectWave. The free Player can't import any third-party format.

Eric Norris Nashville-based FL Studio producer and editor focused on practical workflow, mixer routing, troubleshooting, sampling and native Image-Line tools.