Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.sampler.meiji.industries/llms.txt

Use this file to discover all available pages before exploring further.

​
Audio and playback problems

​
No audio output

Check these in order:
  1. the correct output device is selected in Settings
  2. the system output device itself works outside Meiji Sampler
  3. the relevant channel is not muted
  4. another channel is not soloed
  5. preview playback works from the browser with Space
If browser preview works but pad playback does not, the issue is usually session state, assignment, or mixer state rather than audio initialization. If a pad plays a different section than expected, check whether a per-channel override is active — see Per-Channel Playback.

​
Crackling or dropouts

Usually caused by buffer underruns. Try:
  • increase buffer size
  • reduce other audio-app load
  • wait for background processing such as stems to finish
  • simplify the active session

​
High latency

Try:
  • smaller buffer size
  • 44100 Hz sample rate
  • system default output device
  • the native macOS app or a better-supported terminal

​
Input works poorly

If recording or sampling from input is unstable:
  • re-check input device selection
  • verify the input channel
  • confirm another app is not already monopolizing the device

​
Time-stretch sounds wrong or takes too long

If a stretched loop sounds distorted or artifacts are audible:
  • Extreme ratios (below 0.5x or above 2.0x) can produce artifacts on any material. Try a ratio closer to 1.0x if possible.
  • Percussive material may lose transient sharpness when stretched significantly. Consider layering an unprocessed copy for attack.
If time-stretch is unexpectedly slow:
  • The first stretch after an update regenerates the cache (the old cache is purged automatically when the engine version changes). Subsequent plays are instant.
  • Very long samples take proportionally longer to process. The stretch runs in a background thread and does not block the UI.
If stretched audio sounds stale or mismatched:
  • The cache validates against the expected length, channel count, and sample rate. Mismatched entries are regenerated automatically. If you still hear stale audio, clearing the stretch cache directory manually will force a full rebuild on next play.

​
Pad stops unexpectedly when another pad plays

This is usually a choke group. Channels in the same choke group cut each other off — triggering one stops the others. Check:
  1. open Channel Detail (Enter on the affected pad)
  2. look at the Choke control
  3. if it shows a group number, other channels in that group will stop this pad when they trigger
To fix, change or remove the choke group assignment with Left and Right.

​
Linked pad does not fire

If a channel has a linked pad configured but the secondary trigger does not sound:
  1. confirm the target channel has an assigned sample
  2. confirm the link target is not the same channel as the source
  3. open Channel Detail and verify the Link control shows the expected target
The linked pad will not fire if the target channel is empty or if the source pad itself has no sound to play.

​
Linux-specific host issues

On Linux, if Auto is unstable, explicitly try:
  • ALSA
  • JACK if your system is already set up for it