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
| Category | Typical symptom | Go here next |
|---|---|---|
| Audio output | no sound, crackles, device init failure | Audio And Playback Problems |
| Audio input | input device unavailable, recording init failure | Audio And Playback Problems |
| Project save/load | failed save, corrupt project, backup recovery | File And Project Problems |
| Splice | open/search/download failures | Splice And Network Problems |
| MIDI | mapping save failure, device/monitor issues | MIDI And Sync Problems |
| PerformFX/config save | config save failures after binding/profile changes | Performance 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
- 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