Troubleshooting
Resolve audio, MIDI, recording, assets, sync, agent-run, and export problems.
The audio engine is unavailable
Check that Sympose can open the selected system audio device and that another application is not holding it exclusively. Open Settings → Audio and try System Default or another listed output, then restart the audio device or Sympose after changing system settings. Playback, monitoring, recording, mix export, and stem export require the native audio engine to be ready.
Choose Audio engine in the status bar to see the opened sample rate, buffer size, and estimated output latency. If playback glitches, choose the Safe latency preset in Settings → Audio. Sympose always targets 48 kHz; a different rate in those details means the device fell back.
My MIDI controller is missing
Reconnect the device, open Settings → Recording, and refresh or reselect MIDI input (not Audio input, which is the analog microphone). Confirm that operating-system permission is granted. If the typing keyboard is active, single-key workspace shortcuts may be suppressed by design.
Recording does not start
Confirm that the intended track is selected and armed, an input is available, and microphone or MIDI permission is granted. MIDI recording uses MIDI input; audio-track recording uses Audio input in the same Recording settings. Recording always requires your explicit gesture; an agent request cannot start capture by itself.
An instrument or audio clip is missing
Open the dependency or instrument status shown by Sympose. Restore or repair downloaded instrument content, reconnect the original asset, or replace it deliberately. Sympose does not substitute a different sound when identity or integrity checks fail.
A project will not publish or sync
Read the status detail for authentication, connectivity, asset, or conflict guidance. A failed publication leaves the local project usable. Retry after the blocker is resolved. Cloud state does not include local changes until they are acknowledged as synced.
An agent run stopped or disconnected
Open the original project and chat, then inspect the durable run state. Resume or retry when offered. Completed mutations should not repeat after reconnection. If the run is waiting for a question or approval, resolve that checkpoint before expecting progress.
I cannot revert a run
Newer edits may conflict with the original inverse operation. Inspect the affected material and the conflict explanation. Sympose avoids overwriting later work merely to make an old revert succeed.
Export is blocked
Run export readiness again and resolve missing assets, project conflicts, audio-engine failure, or a stale project revision before choosing a destination. See Finish and export your project.
Where is my work saved?
Active projects are saved locally. A project synchronizes to your account only after you explicitly publish it. See Projects, chats, and saving.
Getting help
Use Send feedback in the account menu, or email hi@muse.art.
When reporting a problem, include the visible error, the affected workflow, and whether the project is local-only, publishing, syncing, or synced. Do not send private project assets unless support explicitly asks and you choose to share them.