Back to home

LoopSeek walkthrough

Not a classic tutorial — a walkthrough with real screens and numbered pins.

Download PDF

LoopSeek Walkthrough

Jump to Easy or Expert, then to any step. The left column is repeated on every PDF page (PDF cannot keep a live sticky sidebar like the HTML guide).

Easy walkthrough Expert walkthrough

Easy steps

  1. 1. Start screen
  2. 2. Theme & Easy / Expert
  3. 3. Easy Autosample layout
  4. 4. Scan plugins
  5. 5. Load your instrument
  6. 6. Settings & Start
  7. 7. Editor
  8. 8. Virtual keyboard
  9. 9. Export

Expert steps

  1. 1. Start screen
  2. 2. Expert overview
  3. 3. Load plugins
  4. 4. Loop algorithms
  5. 5. Split
  6. 6. Velocity & Round Robin
  7. 7. FX Chain
  8. 8. Editor — Loop Detection
  9. 9. Split in the Editor
  10. 10. Apply Helix to all
  11. 11. Batch cut & lock
  12. 12. Live Play
  13. 13. Export
Easy · beginner

Your first multisample

One simple path: record a plugin in Easy mode, check the loops, play a bit, then export. Numbers on each screenshot match the list underneath. Prefer a hardware synth or custom note picks? Those sit in the indented nice to know blocks — not required for the main path.

Tip: in the LoopSeek app, hover the mouse briefly over a button or control — most show a short tooltip with extra info (this does not apply to the PDF or this online guide).

1 Start screen

Open LoopSeek. For this guide you will create samples from a plugin.

Start screen with numbered pins
  1. 1New upload — import existing WAV/folders (not used in this guide).
  2. 2New autosample — click this to record from a plugin or hardware.
  3. 3Drop zone — optional: drag files here instead of using New upload.

2 Light / dark theme & Easy / Expert

After you open Autosample, the top bar always has the appearance toggle and the Easy / Expert switch. You can change both anytime.

Easy dark mode with theme and mode pins
  1. 1Easy / Expert — switch whenever you like. This guide stays on Easy.
  2. 2Sun / moon — light or dark appearance. Pick what is easiest on your eyes.

This capture is a darker, lower-resolution frame that may already show a plugin from a later session — ignore the rest of the screen; only pins 1–2 (mode + theme) matter here. A clean empty Autosample follows in step 3.

Switching Easy ↔ Expert keeps most Expert toggles in memory (velocity layers, Round Robin mapping, dual layer), but Easy capture always records a simple note grid: one velocity, no Round Robin, no second layer. Switching to Easy also forces the loop algorithm to Helix (100% assist, crossfade 0) for the Easy path — going back to Expert does not auto-restore Flux/X-ray; pick the algorithm again if you need it.

3 Easy Autosample — what you see

Stay on Easy (blue). The screen is three parts from top to bottom.

Easy Autosample empty with pins
  1. 1Easy / Expert — keep Easy selected in the app (see also step 2).
  2. 2VST/AU/CLAP — choose plugin (not Hardware) for this guide.
  3. 3Choose Plugin — pick an instrument from the list.
  4. 4Load Plugin — load it into LoopSeek.
  5. 5Plugin scan… — if the list is empty, open this (detailed in the next step).
  6. 6Name your sample — type a name later (step 6).
  7. 7Every N semitones — how dense the note grid is.
  8. 8Loop vs One Shot — pads/strings usually Loop.
  9. 9Start Autosampling — the orange button (use after setup).
  10. 10Keyboard + blue keys — which notes will be recorded.

Pin 5 marks Plugin scan… at the top right of Source — use it once if nothing appears under Choose Plugin.

4 Scan plugins (first time)

If the list is empty, open Plugin scan… once so LoopSeek finds your instruments.

Plugin Scan with pins
  1. 1Click Scan for Plugins and wait.
  2. 2Leave Instruments on (toggle).
  3. 3Enable VST3 / AU (and CLAP if you use it).
  4. 4Add Folder… only if plugins live elsewhere — defaults are usually fine. Close the panel when done.

5 Load your instrument

Pick a synth, load it, then open its UI and set a simple sound. On this screenshot the plugin window covers Load Plugin and Show UI — those were on step 3 / appear again on step 6.

Plugin UI open with pins
  1. 1Plugin selected (e.g. Zebralette3). The “Loaded” status sits behind the plugin window — close the UI (or check again in step 6) to confirm it.
  2. 2Plugin UI window — choose a simple sound you like.

6 Name, spacing, range — then Start

Only a few settings matter for the first run. Plugin UI closed so every control is visible.

Settings ready with pins
  1. 1Show UI — reopen the plugin window anytime (was covered in step 5).
  2. 2Name your sample — e.g. Softpad.
  3. 3Every N semitones — good starting density (not too many files).
  4. 4Loop for pads/strings (use One Shot later for drums/plucks).
  5. 5Summary line — e.g. 11 notes × 1 vel = 11 samples.
  6. 6Drag the blue range on the keyboard (example: c1–c6). Blue key marks = notes that will record. (Prefer hand-picked keys? See nice to know — Custom Notes below.)
  7. 7Click Start Autosampling and wait until it finishes.

Don’t use the computer while it records. When done, the Editor opens with your samples.

nice to know

Custom Notes

The even grid from Every N semitones is enough for most sounds. If bass needs a few extra pitches (or the highs do), turn on Custom Notes and pick keys by hand — still Easy, just more control. In Custom Notes mode the blue range bar is not a drag handle; Shift+click keys instead.

Custom Notes on Easy keyboard with pins
  1. 1Click Custom Notes (button turns blue when active).
  2. 2Shift + click keys on the keyboard to add or remove individual notes. Blue marks = notes that will record.

When you are happy with the selection, click Start Autosampling as in step 6, then continue with the Editor below.

7 Editor — check the loops

Each note is one card. LoopSeek already placed loop markers. Steps 7–9 share one capture with the virtual keyboard open — pins mark the Editor chrome still visible above the overlay. Tap the small piano icon at the bottom anytime to hide the keyboard and see full cards.

Editor with pins
  1. 1Still in Easy in the app.
  2. 2NAME + Apply To All — rename the whole set if needed.
  3. 3TARGET — e.g. Tonverk (device + format).
  4. 4Zip / Folder — export later (after you listened). Not “New Autosample”.
  5. 5Sample card — filename + Root note (mapping key).
  6. 6Waveform — green S / red E are loop start/end. Use Find loop / Play on the card when the keyboard is closed.

8 Play with the virtual keyboard

Same Editor frame as step 7 — focus on the keyboard overlay to audition before exporting.

Virtual keyboard with pins
  1. 1Play keys on this keyboard (or use a real MIDI keyboard if connected).
  2. 2Arp / Seq / CHORD LOOP — leave them alone for now and just play notes. (This screenshot may show Seq lit — turn it off if you only want single notes.)

9 Export

Same capture as steps 7–8 — pins highlight the top export strip:

Export strip with Zip and Folder pins
  1. 1Confirm NAME (e.g. Softpad).
  2. 2Choose TARGET (Tonverk, SFZ, …) and format.
  3. 3PEAK (~ −6 to −1 dB) and MONO — for stereo files turn MONO off (this screenshot shows Mono on — flip it if you want stereo WAVs).
  4. 4Zip — one archive with the device folder layout inside.
  5. 5Folder — same files, written directly into a folder (no zip).
nice to know

Hardware Autosample

Same Easy path as with a plugin — only the Source I/O strip changes: pick the MIDI port and audio input for your hardware synth.

Hardware Autosample Easy with pins
  1. 1Hardware Synth — switch Source away from VST/AU/CLAP.
  2. 2MIDI — the port that sends notes to your synth.
  3. 3AUDIO — the interface / virtual device that records the synth’s output.
  4. 4INPUT — which channels to capture; gear opens Audio & MIDI settings.
  5. 5CH — must match the synth’s MIDI channel. Wrong channel → silence or noise only.
  6. 6Noise floor — for older analog synths that hiss while idle. Measure once with silence at the input; without a profile LoopSeek waits for near-silence and caps the release tail at about 18 s per note.
  7. 7Start Autosampling — then continue with Editor steps 7–9 as after a plugin run.

Use Test MIDI + Audio / Input Check before a long run. A capture that is only noise usually means wrong Audio + MIDI routing — fix that first, then retry.

Done

You autosampled from a plugin (or hardware), checked loops in the Editor, played the instrument, and exported as Zip or Folder.