> ## 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

> Interpret the main user-facing failure categories in Meiji Sampler and where to recover.

# 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](/troubleshooting/audio-and-playback)         |
| Audio input           | input device unavailable, recording init failure   | [Audio And Playback Problems](/troubleshooting/audio-and-playback)         |
| Project save/load     | failed save, corrupt project, backup recovery      | [File And Project Problems](/troubleshooting/files-and-projects)           |
| Splice                | open/search/download failures                      | [Splice And Network Problems](/troubleshooting/splice-and-network)         |
| MIDI                  | mapping save failure, device/monitor issues        | [MIDI And Sync Problems](/troubleshooting/midi-and-sync)                   |
| PerformFX/config save | config save failures after binding/profile changes | [Performance And System Problems](/troubleshooting/performance-and-system) |

## 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.