musescore / musescore/MuseScore

Sforzando loses all settings on every 2nd opening of the score since they were set

Open
#25,874 0 comments 0 reactions 1 assignee View on GitHub

@RomanPudashkin is already working on this.

Since Dec 18, 2024.

P2 VST
Dominant language
C++
Stars
15.1k
Forks
3.3k
Avg merge
2d 2h
Merged PRs (30d)
91

Description

Issue type

VST bug

Description with steps to reproduce
  1. Load a sound in Sforzando, maybe mess with a few settings
  2. Save score
  3. Close score
  4. Open score
  5. See that the settings are saved (and save the "changes" to the score)
  6. Close score again
  7. Open score again
  8. See that the sound loaded into Sforzando is not anymore, and any settings adjusted are reset to default
Supporting files, videos and screenshots

https://github.com/user-attachments/assets/100ca642-14b5-4b15-9c2c-2081f519ab90

What is the latest version of MuseScore Studio where this issue is present?

OS: Windows 11 Version 2009 or later, Arch.: x86_64, MuseScore Studio version (64-bit): 4.4.4-243461245, revision: github-musescore-musescore-2232670

Regression

I was unable to check

Operating system

Reported on Windows 11

Additional context

This bug is extremely annoying, meaning I have to reset every sfz for every other time I play back the score, which adds up.

Checklist
  • This report follows the guidelines for reporting bugs and issues
  • I have verified that this issue has not been logged before, by searching the issue tracker for similar issues
  • I have attached all requested files and information to this report
  • I have attempted to identify the root problem as concisely as possible, and have used minimal reproducible examples where possible

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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.