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.

Error messages

Meiji Sampler surfaces many failures as short UI status messages, confirmations, or logged operation errors rather than one centralized error catalog. This page groups the important user-facing error classes so you know where to look next.

Common failure categories

CategoryTypical symptomGo here next
Audio outputno sound, crackles, device init failureAudio And Playback Problems
Audio inputinput device unavailable, recording init failureAudio And Playback Problems
Project save/loadfailed save, corrupt project, backup recoveryFile And Project Problems
Spliceopen/search/download failuresSplice And Network Problems
MIDImapping save failure, device/monitor issuesMIDI And Sync Problems
PerformFX/config saveconfig save failures after binding/profile changesPerformance And System Problems

File recovery behavior

When a state or project file is corrupt, Meiji Sampler may attempt backup recovery from a .bak file. That is usually the first recovery path rather than an immediate hard failure.

Bounce/export errors

Bounce failures usually come from:
  • invalid output path
  • file creation failure
  • video generation cancellation or downstream failure
Check:
  • the target folder exists and is writable
  • export settings are sensible
  • there is enough disk space

Recording/input errors

Input failures typically mean:
  • no usable input device is available
  • the selected device or channel is invalid
  • the device changed after the app opened

Config save failures

Some features save preferences immediately after changes, including:
  • MIDI mappings
  • PerformFX bank/profile changes
  • settings updates
If these saves fail, your change may work temporarily in-session but not persist after restart.

Best recovery approach

Do not treat this page as a final answer. Use it to route yourself to the correct troubleshooting page.