Skip to article
OscivaraWiki
EN
Open Studio (opens in a new tab)

Troubleshooting

When audio or a task does not work

Begin with a few safe checks. Initial troubleshooting should not require deleting a project, clearing browser data or repeatedly starting a paid task.

No sound

  1. Check device volume and the selected output: headphones, speakers or an audio interface.
  2. Make sure the browser tab is not muted. Press play yourself; the browser may need a user action before enabling audio.
  3. Check track M and S controls. Soloing another part can exclude the track you want to hear.
  4. Check that there is a clip at the playhead position, then return to the beginning.
  5. Wait for instrument or cloud-audio preparation, then try one part.

If a pattern-card preview plays but the arrangement does not, your output device is working. Continue with the assigned instrument and project state, rather than only checking system volume.

Audio changes could not be applied

This means a new version of the sound could not be prepared or applied. The message alone does not identify the cause. An unavailable audio file, bank download, connection problem or limited resources may be involved.

Save your work, stop playback and let current downloads finish. Try again with one track. If it keeps happening, open performance diagnostics from and note which project and action trigger it. Do not rebuild the whole project just to test the issue.

MIDI playback stops unexpectedly

Check that you have not reached the clip end and that looping is not causing the movement you see. If the playhead or sound truly stalls, stop playback, allow preparation to finish and replay the same section. Reduce competing work and follow the slower-computer guide.

If the problem repeats at one position, report the approximate time, instrument and track count. If it happens at different positions, also include your browser, device and other heavy operations running at the time. This helps distinguish a material-specific problem from general load.

An AI task takes a long time

Check its SteppeMind status. Queued means it has not yet received processing capacity. Do not submit duplicate requests. If the connection drops, restore it and reopen task history.

For a failed task, read the detailed notification. Check the account, feature availability and balance. After cancellation, wait for the cancelled status before treating the work as stopped.

Audio does not save or reopen

Check the account, connection and available storage. Make sure the project was not left only on another device. If an unused separation result expired, look for the stems in the saved project: task history is not a permanent archive.

Send a useful bug report

Open Feedback in the menu. Describe the action, expected result, actual message, browser and device. A screenshot of the problem is more useful than “it does not work”. Hide personal data and never attach passwords, access keys, payment details or someone else's private project.