Troubleshooting
Work more comfortably on a slower computer
Running in a browser does not remove the need for local audio processing. Simultaneous parts, effects and sample loading all affect responsiveness.
Let the sound prepare
The first playback of a new instrument may require recorded sounds to download and audio to be prepared. Later attempts are often faster because prepared data can be reused. The cache is not unlimited, though: browsers manage memory and may release resources.
After opening a large project, wait for visible loading to finish. Avoid switching through many instruments while the previous one is still preparing. Begin with a short section and a few tracks.
Reduce competing work
- Close unnecessary tabs running video, games or other audio applications.
- Avoid playing the same project in several Studio tabs.
- During export, do not start another heavy preview or change many parameters at once.
- Test with fewer active parts, then bring them back gradually to identify the source of load.
- Use a stable power supply and check the device's power-saving mode. The system may limit performance or suspend background tabs.
Muting is useful for comparison, but it does not guarantee that all of an instrument's memory is released immediately. Do not treat M as a cache-clearing control.
Use an audio copy of a finished part
When a part no longer needs note edits, you can render its sound through an appropriate export workflow and use the resulting audio in the arrangement. Save a copy of the MIDI project first. This changes the type of processing required, but may increase audio storage and memory use.
Keep the original notes until you have checked the audio copy and backup. A WAV is not a replacement for editable MIDI if you later need to rewrite the melody.
Diagnose instead of changing settings at random
Open Performance diagnostics in the ⋯ menu. Compare a small project with the problematic composition. Note whether the issue starts after adding an instrument, when seeking, or during a simultaneous export.
A larger buffer of prepared audio can bridge brief delays, but it also uses more memory. It cannot be increased indefinitely with a promise of smooth playback on every device. Oscivara prepares and reuses audio data; the actual load still depends on the project and computer.
Avoid destructive first steps
Do not clear site data or delete banks before backing up your work. Do not restart the same operation many times in quick succession. For a repeatable failure, gather details for Feedback rather than changing every setting at once.