xtc/docs/MIDI_WORKFLOWS.md

15 lines
993 B
Markdown

# Application configuration and MIDI workflows
`~/.xtc.conf` is the application's base configuration. It is read before creating
its first project and backend. Missing keys use compiled defaults. Preferences
Apply writes every tab atomically with owner-only permissions; clean exit also
collects workspace, snap/zoom, loop, piano filters and note defaults. A missing
file is created on Apply or clean exit. Invalid files produce a visible startup
error and are preserved until an explicit successful Apply replaces them. A save
failure keeps the window open for retry. Project contents, plugin states and
session clipboards are project/session data, not application preferences.
All persistent preference fields are listed by the shared C schema and available
in Preferences. Existing project tempo/controller maps remain project data;
Preferences project defaults apply to New. No configuration I/O runs in an audio
callback. Tests and screenshot captures use isolated configuration paths.