musescore / musescore/MuseScore

Warning if sounds/samples are not available

Open
#30,130 2 comments 3 reactions 0 assignees View on GitHub

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

When MuseSounds are not available when opening a score, MuseScore falls back to MS Basic without any notice. If you are not aware of this and you save the score, you have to manually revert everything once the sounds are available again. I think there should be a warning along the lines of "Samples not available, loaded MS basic instead".
Taking it further, there could also be an option to choose which alternative you want to load (which I guess would be magnitudes more complicated to implement than a simple warning).

Problem to be solved

Having to change possibly dozens of instruments back to another sound.

Prior art

No response

Additional context

I have to deal with this regularly because I have the Muse Sounds on an external drive that isn't alway connected.

Checklist
  • This request follows the guidelines for reporting issues
  • I have verified that this feature request has not been logged before, by searching the issue tracker for similar requests

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing what happens when a score is opened with MuseSounds unavailable and MS Basic is loaded instead. Confirm where the fallback is selected and how a warning could be shown without changing the requested sound behavior. Done means users are clearly warned when samples are unavailable, with the fallback identified as MS Basic.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
desktop
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.