What’s new
Beta status
Oscivara is in an open Beta period. It is already a working music studio rather than a demonstration mock-up: you can create and save projects, arrange music, edit MIDI, work with audio and export a finished result. The main workflows are generally stable, and the Beta label does not mean that the application constantly crashes or is unsuitable for real creative work.
Beta means something more specific: the application is developing actively and is being tested across real computers, browsers, audio devices, internet connections and music projects. Internal testing alone cannot reproduce every combination.
What already works as part of the application
The core Oscivara workflow includes:
- creating, opening, saving and versioning projects;
- Studio with audio and MIDI tracks, a timeline and transport controls;
- the MIDI editor, patterns, instruments, samples and loops;
- playback, mixing, processing and finished-audio export;
- SteppeMind for creating and reshaping musical material;
- background jobs and a queue for resource-intensive operations;
- Russian and English Wiki instructions and troubleshooting guidance.
We run type checks, builds, automated tests and key user flows before publishing changes. Successful checks are important, but they still cannot represent every hardware combination and real-world project.
Why the Beta status remains
Oscivara combines several technically demanding areas: browser audio, MIDI, large WAV files, background computation, sound banks, local project state and cloud-assisted features. A problem may appear only with a particular project size, browser version, low-memory condition or unstable connection.
The Beta status communicates honestly that compatibility coverage and recovery from unusual situations are still expanding. It lets useful capabilities reach users sooner, provides real feedback and helps rare problems get fixed before they become a normal part of anyone’s workflow.
What depends on the computer and browser
Some music processing runs directly on the user’s device. The same project can therefore behave slightly differently across configurations:
| Factor | What you may notice | What to check |
|---|---|---|
| Processor performance and available memory | Pauses, longer preparation or delayed controls | Close demanding tabs and reduce parallel work |
| Browser version and settings | Differences in playback, file loading or keyboard shortcuts | Update the browser and check audio-playback permission |
| Audio device and its settings | Silence, latency or an unexpected output change | Check the selected system output and volume |
| Project size and complexity | Longer timeline preparation or export | Test a smaller section and wait for preparation to finish |
| Power-saving mode | Reduced speed or a suspended background tab | Connect power and temporarily relax strict performance limits |
See Working on a slower computer for practical steps.
What depends on the internet and background services
MIDI editing, some instruments and many Studio operations work locally, while cloud-assisted features need a connection. Upload speed, task queues, temporary service availability or a computer entering sleep can increase waiting time.
A disconnected view does not always mean that a task was lost. Open its history and check the state again. Do not submit the same request repeatedly: duplicates create unnecessary jobs and make the result harder to understand. If the problem repeats, record the exact visible message and the approximate time it appeared.
How to distinguish a temporary delay from a problem
Save the project and stop playback first. Let visible downloads and background jobs finish, then repeat the action once. For an audio issue, test the same section with one active track. For a cloud-assisted task, open SteppeMind history and check whether its state has changed.
If the same action fails again, sound disappears at the same point or the result consistently differs from what the interface promises, you have a useful reproducible case. Follow When something goes wrong and prepare a short description.
How to help Oscivara improve
Open the application’s three-dot menu → Feedback. Use the form to report a bug, confusing behaviour, an audio problem or slow performance. The same form welcomes wishes, ideas and suggestions.
A useful report includes:
- What you were trying to do.
- The actions immediately before the problem.
- What happened and what you expected instead.
- The exact message shown on screen.
- Your browser, device type and approximate project complexity.
- Whether the problem returns after reloading the page.
Never send passwords, tokens, payment data, private keys or other personal information. If a project or audio file is needed for diagnosis, first make sure you have permission to share that material.
When the Beta label can be removed
Moving to the next status depends on more than the number of features. Core creative workflows need to behave predictably across a broad range of supported computers and browsers; failures need clear messages and safe recovery; queues and background jobs need to remain stable under real load; exports and saved projects must not depend on accidental conditions.
User reports cover combinations of devices, projects and working habits that cannot all be simulated beforehand. Even a short report that a particular workflow works well is useful because it helps distinguish an isolated problem from a general one.
Where to continue
Read the 2.5 update, follow Your first track or continue in Studio. If something goes wrong, check troubleshooting first, then send feedback with a clear description.