What a sample is: one-shots, loops, multisamples and construction kits.

A sample is an audio fragment saved as a file, intended to sound again within something else: a track, a set or a demo. The definition is almost too broad, so the word alone tells you little. Five details decide whether a file is useful: length, pitch, tempo, format and number of layers.

The most common beginner’s mistake is downloading hundreds of files and treating them as equivalent. They are not: a one-second kick and a four-bar loop are used differently, edited differently and fail differently. Here is the taxonomy you need to avoid collecting useless material.

What a sample is and what makes it useful

A sample is audio already fixed: someone recorded, synthesised or cut it, leaving it written in a file. From then on, usefulness depends on data rather than impressions:

• Length. A hit ending in milliseconds, or a fragment with complete bars? This determines whether you trigger or loop it.
• Pitch. Is it tuned, and to which note? For a kick one-shot it does not matter; a piano fragment determines the key in which you can use it.
• Tempo. If it has rhythmic structure, what is its BPM? A 124 BPM loop in a 128 BPM track needs stretching.
• Format. Uncompressed WAV or AIFF at 24 bits and 44.1 kHz is the delivery norm for professional packs; a 128 kbps MP3 introduces loss before you do anything.
• Layers. One file, or a collection of recordings of the same sound at different notes and velocities?

The final two points connect with DAW documentation. Ableton’s manual distinguishes clips without rhythmic structure—percussion hits, atmospheres, effects and speech—from those with it. Warp treats audio as elastic for time-stretching and tempo synchronisation. Software itself identifies two file families: answering “is this sample useful?” starts with knowing which one you have.

The five sample types you will encounter

In practice, there are four named families, plus standalone recordings cut from records or your own takes.

• One-shots: one hit played once. Kick, snare, hi-hat, synth stab, isolated voice or door noise.
• Loops: fixed-length fragments repeating seamlessly, with tempo and arrangement already decided.
• Multisamples: a whole instrument sampled across the keyboard at several dynamics.
• Construction kits: one track broken into layers for recombination.

Four names, four different jobs. The table summarises the important difference: contents, triggering and where each fits.

One-shots and loops: the distinction determining workflow

A one-shot is raw material: trigger it and it ends. Its benefit is full control—you decide the pattern, velocity and placement—and its cost is building the rhythm hit by hit. Native Instruments defines it as a single sound playable rhythmically and chromatically: at different pitches, like a note.

A loop is the opposite: decisions are already built in. Four bars of swinging drums, a bass line with phrasing or an evolving pad. Its benefit is speed: drag, synchronise and you have a foundation. Its cost is using someone else’s decisions, often without separating the parts you like from those you do not.

The modern exception is that loops are no longer usually tied to their BPM. Ableton documents warping as stretching audio without changing pitch while keeping it synchronised to project tempo: precisely what lets a 124 loop play in a 128 track. One-shots, conversely, almost never need warp: trigger them at their original speed.

In the booth, this becomes two uses. Loops add rhythmic layers locked to the playing track’s tempo. One-shots provide fills, accents and endings that do not depend on a grid.

Multisamples: an instrument sampled in layers

A multisample is not one file but an organised collection: the same sound recorded at many notes and intensities, distributed across keyboard zones. Ableton’s Sampler Multisampling section describes each zone covering a note range with its own velocity layer, and supports third-party multisample imports.

The reason: stretching one file across the keyboard sounds artificial because transposition carries formants and background noise with it. Note and dynamic layers preserve the original instrument’s character, at the cost of far more disk and memory.

You find multisamples in pianos, strings, winds, ethnic instruments and drum kits storing three or four variants per hit to avoid a mechanical sound. Identification is simple: a folder with named notes (C1, C2, C3…) or velocities (soft, medium, loud) indicates a multisample.

Construction kits: a song taken apart

A construction kit delivers one song broken into pieces: drum loops, bass, melodies, vocals, one-shots and sometimes MIDI files and presets. Everything shares key and tempo because it came from the same project.

Its benefit is coherence: you need not match tuning between elements bought in different packs. Its risk is the opposite: releasing the whole kit makes your track sound like the kit. Value comes from taking two or three layers, modifying them and building around them.

One non-technical issue should not wait: a construction kit from a pack you bought comes with a licence; the same kit downloaded from an unlicensed site does not, and you bear the risk. The distinction is developed in sample licences.

When to use each type in production and the booth

There is no best type; each fits a decision:

• For speed, start with a construction kit or two or three well-chosen loops. Within hours, you have a foundation with key and tempo resolved.
• For identity, build the pattern with one-shots: your own groove resembles nobody else’s.
• For instrumentation, load multisamples: they sustain melodies and chords without sounding like a stretched file.
• For performing live, bring one-shots and short loops to the controller; multisamples are heavy and add little to a set governed by shared tempo.

A useful filter: before loading a file, ask what you want to control. Groove? One-shots. Arrangement? Loops. Timbre? Multisample. A complete foundation? Construction kit.

What to check before loading a sample

A sixty-second checklist, in order:

1. Structure: do loops contain complete bars and start on beat one? An extra hit creates a problem that only appears when mixing.
2. Declared tempo and pitch: serious packs put these in filenames. If missing, measure and note them before losing context.
3. Format: WAV or AIFF at 24 bits. For MP3, know its origin rather than using a recompression of a recompression.
4. Layers: check for velocity variants and use them if present; they keep patterns from sounding robotic.
5. Licence: record where the file came from. Consistent folders and naming solve this, as proposed in organising a DJ library.

A warning about quantity: collecting is enormously tempting, but a huge uncatalogued library is useless material. Packs use category folders for this reason; organising turns a folder of files into a usable library.

Next step

You know what a sample is and which file type you have. Next comes the question deciding whether you can release a work using it: what each licence really means. Continue to Sample licences: royalty-free, public domain and Creative Commons.