Skip to content

File Locations and Data Management

Justagwas edited this page Jul 15, 2026 · 1 revision

File Locations and Data Management

Main locations

Data Default location
Configuration %LOCALAPPDATA%\A2M\a2m_config.json
Model bundle %LOCALAPPDATA%\A2M\models\piano-engine
CUDA runtime pack %LOCALAPPDATA%\A2M\runtime_packs\cuda
DirectML runtime pack %LOCALAPPDATA%\A2M\runtime_packs\dml
A2M-managed cuDNN %LOCALAPPDATA%\A2M\dependencies\cudnn
MIDI output %USERPROFILE%\Downloads\A2M by default; configurable

A source checkout can also supply a model bundle beside the application as a fallback. The per-user LocalAppData model is preferred.

Output naming

A2M starts with the input stem, removes invalid Windows filename characters and reserved names, truncates long names, and writes .mid. Existing output is never intentionally overwritten: subsequent files receive _2, _3, and so on.

The output file is reserved before transcription. If conversion or MIDI writing fails, A2M removes that incomplete reserved file.

Configuration migration

If the current config is absent, A2M can read older configurations from the application directory, %APPDATA%\A2M, or %USERPROFILE%\.a2m_config.json, normalize them into the current schema, and save the current LocalAppData file.

These paths are version-sensitive implementation details. See paths.py, model_service.py, runtime_pack_service.py, and conversion_service.py.

Clone this wiki locally