Skip to content

Audio Slice Resequencing

A music-production method that cuts one recorded phrase into addressable slices and triggers them by a chosen timing or selection rule to form a new phrase or loop.

Version
v1 · 2026-10-25 · History
Domain-specific #
14361
Origin domain
Music Audio Production
Subdomains
Sampling, Electronic Music Production → Music Audio Production

Core Idea

Audio slice resequencing starts with one recorded musical phrase, divides it into separately addressable segments, and calls those segments at selected times or under a selected ordering rule.[1][2][3] The result is a phrase or loop made from that recording's parts rather than a continuous playback of the unchanged file.[1] Ableton's reference manual describes the core technical relation directly: slicing an audio clip creates a MIDI note and Drum Rack chain for each slice, and the MIDI clip can then trigger those chains in their original order or a newly edited pattern.[1]

The decision rule need not list every future hit in advance. In a worked drum example, Ben Hayes uses a configured arpeggiator to select among fixed, indexed slices at an eighth-note rate; the resulting loop varies.[2] In a worked vocal example, Sam Matla manually keeps four fragments of a sung passage and places their triggers in a piano-roll melody.[3] The shared operation is cut → address → trigger → assemble, while the input and control policy differ.

Structural Signature

Sig role-phrases: recorded source phrase; deliberate slice boundaries; playable addresses; trigger rule; assembled output.

  • Recorded source phrase. A contiguous break, loop, or vocal passage supplies internally related material to recombine. Hayes begins with a Vintage Drum Breaks loop; Matla isolates a two-phrase acapella passage.[2][3]
  • Slice boundaries. Cuts identify the segments. Hayes chooses eighth-note divisions; Matla removes and moves markers until four vocal chops remain.[2][3] Automatic transient detection is possible in other workflows but is not required.[4]
  • Playable addresses. Each segment must be callable separately. Hayes's Slice to New MIDI Track operation creates a Drum Rack and MIDI clip; Matla uses Slicex chops playable from notes in a piano roll.[2][3]
  • Trigger rule. A sequence, performer, or configured generator selects when indexed segments play. Hayes aligns MIDI notes and applies a Random Once arpeggiator; Matla writes the note positions and adjusts velocity.[2][3]
  • Assembled output. Playback realizes the selected calls as a loop or phrase. Hayes presents an automatically varying drum-loop result; Matla describes the evolving vocal phrase and its later processing.[2][3]

Removing the address map leaves only cut audio. Removing the trigger rule leaves a prepared library of fragments. The operation is complete when the fragments are called into an audible arrangement.

What It Is Not

  • Not every chopped waveform. In Hayes's preceding half-time example, he moves audio fragments directly between tracks.[2] That is a valid edit, but the later MIDI-sliced and arpeggiated example supplies the separate address-and-trigger relation used here.[2]
  • Not continuous time stretching. A file can change duration without its constituent sounds becoming independently callable. ReCycle's slice-based tempo procedure instead prepares separate slices and warns that a large slowdown may expose gaps between them.[4]

  • Not the assembly of unrelated one-shot files. Pads can sequence independent samples, but a positive case here cuts its playable units from one recorded phrase.

  • Not random start-point sampling of an unsegmented file. Matla separately demonstrates a Vital method that starts the sample at random positions for each note.[3] It is distinct from his four indexed Slicex chops.[3]

  • Not inherently pitch preserving. ReCycle lets users control tempo and pitch separately, and Matla's vocal fragments can be processed.[5][3] Unchanged pitch is a choice or a specific workflow result, not a defining guarantee.[5][3]

Scope of Application

The method belongs to recorded-audio music production. A drum break may be sliced for rhythmic variation, as in Hayes's worked loop, or a vocal passage may be sliced to construct a melody, as in Matla's tutorial.[2][3] Ableton's manual explicitly describes sliced MIDI data that can retain its original order or be resequenced by editing notes or pad mappings, and says that both drum loops and voices can be used.[1]

Boundary choice depends on the recording and intended result. ReCycle's manual notes that automatic detection can struggle when attacks are weak or sounds are smeared; a user may add markers manually.[4] This is an implementation limit, not a requirement that every slice contain exactly one drum hit. No particular software, file format, genre, or pitch treatment is constitutive.

Clarity

Ask five concrete questions: Which single phrase supplied the material? Where are its boundaries? How is each segment addressed? What decides the trigger timing and selection? What phrase is heard afterward? Those questions separate the operation from the mere appearance of cut marks on a waveform.

The distinction is visible in Hayes's page. Its first worked half-time groove is assembled by moving audio clips directly; its later example turns another break into a MIDI-addressed Drum Rack and routes simultaneous notes through a configured arpeggiator.[2] Both create rhythmic variation, but only the latter demonstrates the bounded address-and-trigger method.

Manages Complexity

Slicing turns a long recording into a set of call sites.[1] In the MIDI-addressed workflows described here, a producer can change the timing or selection rule without recutting the source for each pattern.[1][2][3] In Ableton's described workflow, a MIDI note identifies a slice's Drum Rack chain; editing the notes changes the pattern while the source audio portions remain the playable material.[1]

That separation also makes failure modes visible. A boundary that contains two sounds prevents those sounds from being triggered independently; ReCycle's editing instructions call out that exact limitation.[4] Conversely, forcing a slower output may reveal silence between slices, so audible continuity must be checked at the intended tempo.[4] Neither issue is fixed by simply naming more slices.

Abstract Reasoning

1. Choose the source phrase. Use a passage whose internal fragments are worth retaining together, such as Hayes's drum break or Matla's contrasting vowel and pitch fragments.[2][3] 2. Choose boundaries for the intended control. Hayes uses eighth-note divisions; Matla listens, removes unwanted markers, and adjusts a boundary that cuts awkwardly across words or pitches.[2][3] 3. Verify addressability. Check that each intended fragment has a separate playable address, rather than only a visible cut in a final waveform.[1] 4. Choose a trigger policy. Matla's explicit notes spell out a vocal phrase; Hayes's configured generator selects among the indexed drum slices.[3][2] Describe the rule actually used rather than inventing a fixed order for a random output. 5. Listen to the assembled result. Check rhythmic coherence, unwanted gaps, clipped sounds, and whether the result still serves the production goal.[4][2]

Knowledge Transfer

The same questions transfer within audio production from a percussive break to a sung phrase: source, cut, address, trigger, result. They do not demand the same slicing rule. An eighth-note grid suits Hayes's worked drum variation, while Matla selects four fragments by ear for a melody.[2][3]

The transfer stops when the audio-specific roles disappear. A spreadsheet that segments data and reorders rows shares a loose shape, but it has no recorded phrase, playable slice addresses, or audible recomposition. The relationship would be metaphorical rather than another instance of this domain-specific entry.

Examples

Canonical: algorithmic variation of a drum break

Ben Hayes loads another loop from the Vintage Drum Breaks Vol 1 collection, chooses Ableton's Slice to New MIDI Track command with eighth-note divisions, and obtains a Drum Rack plus MIDI clip that initially calls the slices in order.[2] He aligns the MIDI notes, applies a Random Once arpeggiator at an eighth-note rate, and plays the resulting varying drum loop; the tutorial embeds output audio.[2] The source does not specify the exact random slice order or a changed BPM.

Mapped back: The selected vintage break is the source phrase; eighth-note divisions are the boundaries; the Drum Rack chains are the addresses; simultaneous notes and the configured arpeggiator are the selection and timing rule; playback is the assembled loop.[2] Hayes's earlier directly moved audio fragments are a separate example on the same page, not steps silently imported into this one.

Applied: programmed vocal-chop melody

Sam Matla selects a two-phrase acapella passage, isolates it, and uses FL Studio's Slicex to edit the markers until four contrasting vocal fragments remain.[3] He programs note choices and rhythm in a piano roll, then adds lower-velocity notes and processes the phrase toward a trance-style result.[3] His Ableton Simpler directions describe a parallel path for a reader; his first-person output follows the Slicex path.

Mapped back: The acapella passage is the one source phrase; his edits establish four slice boundaries; Slicex supplies playable addresses; piano-roll note and velocity decisions form the trigger pattern; the heard vocal line is the assembled result.[3] His later Vital random-phase method is a different technique, not a continuation of this case.[3]

Structural Tensions

The consulted sources establish operating limits, including gaps that can appear when a sliced loop is slowed substantially.[4] They do not establish an unavoidable two-sided tradeoff for audio slice resequencing, so no structural tension is asserted on this evidence.

Structural–Framed Character

The five-role pattern is visible in both reviewed cases, but its terms remain tied to musical audio. Vocabulary travels within the domain: a drum hit and a vowel fragment are different sounds yet can each become an indexed slice. Evaluation is goal dependent: a useful drum variation and a useful vocal melody are judged by their audible roles, not by a universal count of cuts. Human practice matters: Hayes chooses a randomizing policy and Matla chooses and adjusts fragments by ear.[2][3] Institutional framing is limited: vendors supply tools and manuals, but no software brand defines the abstraction. Import versus recognition: a nonaudio system may resemble cut-address-reorder in outline; without recorded sound and playback it does not instantiate this domain entry. The portable cut-address-trigger skeleton beyond audio remains a future-prime question; the live Boundary prime supplies only the essential demarcation constituent, not the entire musical procedure. Its character: strongly framed, with a stable five-role comparison within music production but no demonstrated literal transfer of the named method outside recorded-audio practice.

Structural Core vs. Domain Accent

The general skeleton is partitioning a source, assigning addresses to parts, and assembling selected parts by a rule. The live Boundary prime captures the operative delimitation of each separately playable segment as an internal constituent; whether the entire cut-address-trigger skeleton deserves a distinct portable prime is a future-prime question. The domain accent is load-bearing: audio boundaries can split attacks or vowel transitions, slice playback can leave audible gaps, and a musical phrase is the evaluated output.[4][3] These are not optional illustrations. The named method does not clear the prime bar because recorded audio, triggerable samples, and audible musical recomposition are constitutive, whereas apparent data or text analogies do not literally retain those roles. Removing them leaves a broad segmentation-and-sequencing analogy rather than audio slice resequencing.

This entry includes Boundary.

The live Boundary prime names an internal constituent: a slice delimiter determines which samples belong to each independently callable region. Sequencing is related when notes deliberately order slices, but its live identity requires deliberate ordering under precedence constraints, which Hayes’s Random Once selection does not have. Rhythm is related when the output has patterned recurrence; a single sliced phrase need not repeat. These conceptual relations have different structural tests and should not be collapsed into one generic “rearrangement” parent.

Relationships to Other Abstractions

Local relationship map for Audio Slice ResequencingParents appear above the current abstraction, mutual partners to the right, and children below. Node labels state whether each abstraction is prime or domain-specific; colors identify relation types.Audio SliceResequencingDOMAINPrime abstraction: Boundary — includesBoundaryPRIME

Current abstraction Audio Slice Resequencing Domain-specific

Parents (1) — outgoing typed relations

  • Audio Slice Resequencing includes Boundary Prime

    Every audio slice resequencing operation uses boundaries to delimit independently playable regions of one recorded phrase; Boundary is an internal constituent of the method.

    Condition / exception This strict edge applies to the bounded slice-from-one-recording identity. Direct timeline edits, intact time stretching, sequences of unrelated one-shot samples, and random start-point sampling of an unsegmented file are outside this child.

Hierarchy path (1) — routes to 1 parentless root

  • Audio Slice Resequencing → includes Boundary

Neighborhood in Abstraction Space

Audio Slice Resequencing sits in a sparse region of the domain-specific corpus (75th percentile for distinctiveness): few abstractions share its structure, so a faithful description tends to retrieve it precisely.

Family — Musical Form & Rhythmic Devices (15 abstractions)

Nearest neighbors

Computed from structural-signature embeddings · 2026-10-25

Not to Be Confused With

  • Non-Linear Editing: an editor can access and rearrange time-based source clips out of final order, but the broader workflow does not require sample slices mapped to playable trigger addresses.
  • Slice sampling: the live entry with this name is a statistical sampling method, not an audio operation.
  • ReCycle's named Drum Tools Demo: that example shows slice markers, individual audition, a one-bar locator correction, and Preview, but does not execute a changed-order MIDI pattern.[5] It is useful technical context, not one of the two complete positive cases here.
  • Random start-point sampling: Matla's separate Vital example varies the start position within a sample on each note, whereas his worked Slicex melody selects four deliberately indexed pieces.[3]

References

[1] Ableton. Live 11 Reference Manual, §12.1 “Slice to New MIDI Track” and §12.1.1 “Resequencing Slices”. Description of MIDI clip, Drum Rack chains, and pattern editing. registry ↩a ↩b ↩c ↩d ↩e ↩f ↩g ↩h

[2] Ben Hayes. “Sample Mileage: Creating variations in drum loops”. Samplephonics, 5 May 2016. Third worked example, “Slice to New MIDI Track,” steps and linked audio, displayed lines 65–82. registry ↩a ↩b ↩c ↩d ↩e ↩f ↩g ↩h ↩i ↩j ↩k ↩l ↩m ↩n ↩o ↩p ↩q ↩r ↩s ↩t ↩u

[3] Sam Matla. “Vocal Chops: 4 Easy Steps to Create Them in Any DAW”. EDMProd, 9 September 2026. Steps 1–4 and separate Vital section. registry ↩a ↩b ↩c ↩d ↩e ↩f ↩g ↩h ↩i ↩j ↩k ↩l ↩m ↩n ↩o ↩p ↩q ↩r ↩s ↩t ↩u ↩v ↩w ↩x

[4] Reason Studios. ReCycle Operation Manual, “Example Applications”. Source-detection limits, slice-based tempo procedure, and “Slicing for Editing.” registry ↩a ↩b ↩c ↩d ↩e ↩f ↩g ↩h

[5] Reason Studios. ReCycle Operation Manual, “Quick Tour of ReCycle”. Named “Drum Tools Demo.aif” steps and Preview controls. registry ↩a ↩b ↩c