musescore / musescore/MuseScore
VST Plugin sandboxing
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 15.1k
- Forks
- 3.3k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 91
Description
Your idea
Running VST plugins in a separate process, to prevent VST crashing from bringing down the whole MuseScore.
I do hope VST support come stable before anything else, but this may worth considering in the long run.
Problem to be solved
Some crashes are caused by VST, and MuseScore suffers from that. This kind of processing, tho may reduce stability and compatibility in some cases, could defend MuseScore from this kind of crash.
Prior art
BitWig has a good reputation for its plugin sandboxing, and some options are provided to reduce compatibility or performance problems:
https://www.bitwig.com/learnings/plug-in-hosting-crash-protection-in-bitwig-studio-20/
and REAPER do have similar options, tho, from my experience, could be problematic sometime.
Additional context
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing MuseScore's existing VST support and the Bitwig and REAPER crash-protection examples linked in the issue. Define how separate-process hosting should preserve MuseScore when a VST crashes, while accounting for the compatibility and performance concerns described.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- audio-video-rtc, desktop
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100