Storage paths and project structure
This page lists the main local paths used by Meiji Sampler.macOS paths
App state and config
- session state:
~/Library/Application Support/Meiji Sampler/state.json - settings:
~/Library/Application Support/Meiji Sampler/config.json - auth state:
~/Library/Application Support/Meiji Sampler/auth.json - analytics anonymous id:
~/Library/Application Support/Meiji Sampler/anonymous_id - update cache:
~/Library/Application Support/Meiji Sampler/update_cache.json - stars/bookmarks:
~/Library/Application Support/Meiji Sampler/stars.json - library database:
~/Library/Application Support/Meiji Sampler/library.db
Projects
- projects directory:
~/Documents/Meiji Sampler/Projects/ - project extension:
.meiji
Bounces
- bounce output directory:
~/Documents/Meiji Sampler/Bounces/ - DJ master recordings:
DJ Set YYYY-MM-DD HH-MM-SS.wavin the same directory, with collision suffixes and numberedPart 2rollover files when needed - interrupted DJ master recordings: retained
.partialfiles in the same directory. These are recovery artifacts, not completed bounces.
Recordings
- recordings directory:
~/Music/Meiji Sampler/recordings/ - Splice licensed downloads:
~/Music/Meiji Sampler/splice/
Packs
- packs directory:
~/Library/Application Support/Meiji Sampler/Packs/
Cache
- cache directory:
~/Library/Caches/Meiji Sampler/
Linux paths
App state and config
- config directory:
$XDG_CONFIG_HOME/meiji-sampler/(default~/.config/meiji-sampler/)
Data
- data directory:
$XDG_DATA_HOME/meiji-sampler/(default~/.local/share/meiji-sampler/)
Cache
- cache directory:
$XDG_CACHE_HOME/meiji-sampler/(default~/.cache/meiji-sampler/)
Recordings
- recordings directory:
~/Meiji Sampler/recordings/when no audio directory is available - Splice licensed downloads:
~/Meiji Sampler/splice/when no audio directory is available
Packs
- packs directory:
$XDG_DATA_HOME/meiji-sampler/Packs/(default~/.local/share/meiji-sampler/Packs/)
.partial file.
Windows paths
App state and config
- config directory:
%APPDATA%\Meiji Sampler\
Data
- data directory:
%LOCALAPPDATA%\Meiji Sampler\(includes thecache\subfolder)
Recordings
- recordings directory:
%USERPROFILE%\Music\Meiji Sampler\recordings\ - Splice licensed downloads:
%USERPROFILE%\Music\Meiji Sampler\splice\
Packs
- packs directory:
%LOCALAPPDATA%\Meiji Sampler\Packs\
Project structure
A.meiji project stores:
- format version
- project name
- created and saved timestamps
- app version
- flattened session state
- pad assignments
- mixer values
- loops
- scenes
- overrides for trim, chop, loop mode, and sample-type metadata
Recovery behavior
Persistence writes use backup files and recovery helpers where possible. If a primary file is corrupt, the app may attempt to restore from a.bak sibling.
Uninstalling
Deleting the application removes Meiji Sampler itself. It does not delete packs, recordings, exports, settings, or preferences in the user paths above. To remove the application and all its data, delete the application and then remove the directories listed above for your platform.- On macOS, delete
~/Library/Application Support/Meiji Sampler/and~/Library/Caches/Meiji Sampler/. - On Linux, delete the config, data, and cache directories.
- On Windows, delete the
%APPDATA%\Meiji Sampler\and%LOCALAPPDATA%\Meiji Sampler\directories.
Related pages
Sample edit assets
Crop/WARP create owned Float32 WAV files insample-edits beside app configuration.
Named-project save bundles live edited pad, original WARP, and undo references into
<project>.assets beside <project>.meiji, using relative references on disk. Keep
both together when copying projects. Unedited external references are not bundled.
The live/background session keeps absolute paths until named-project reload.
MPC Sample stems
The optional offline addon image isMeiji/Runtime/stems.img on the SD card.
A verified standalone session mounts it under /run/meiji-sd-dev/stems-image;
it does not copy the addon to RAM or execute from the noexec SD mount directly.
Completed WAVs and their source.sha256 content binding use
Meiji/State/cache/meiji-sampler/stems. Cache loading does not require the image
or executable. Older unbound native caches are regenerated when the runtime is
available. Desktop cache locations are unchanged.
After a rare failed cache publication and failed rollback, a .keep-stem-*
directory retains the previous complete output in previous; keep it when
collecting diagnostics. See stem recovery.