Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

hidden staves ignore hairpins and incorrectly use volume dynamics on playback, only when a score is launched with the staves already hidden. #25924

Open
4 tasks done
UncleRed0899 opened this issue Dec 26, 2024 · 0 comments
Assignees
Labels
playback General playback issue

Comments

@UncleRed0899
Copy link

Issue type

General playback bug

Description with steps to reproduce

I use both MuseSound playback and Spitfire LABS VST3 playback. This happens with both sound options.

Create a score, utilizing hidden staves for the improvement of playback sound for certain instruments at certain parts (i.e. Spitfire articulation isn't as good as musesound articulation for a specific set of notes, and you want playback to sound accurate to what's written)

Save the score, then close MuseScore Studio 4.4.4.

Open MuseScore Studio 4.4.4, and launch the saved score. Initiate playback and observe the malfunction of the playback ignoring hairpins and playing markings such as "f", "mf", "p" etc... at an incorrect volume level.

Opening the Instruments pane, setting the hidden staves to "visible", starting then immediately stopping playback, then hiding the staves again fixes the problem. However, for larger scores, this is a tedious process, as MS4 freezes for a few seconds, up to 20s at the longest, whenever a staff is hidden or made visible. (Freezing not a part of this issue, however, is an issue nonetheless)

Supporting files, videos and screenshots

Hairpin.bug.mp4

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

Windows 11 Home

Additional context

Regarding the video, the Violin playback sound is coming from the staff labeled "Violin". The Staff "Violins 1 & 2" is used for the dominant violins playback sound throughout the score, using VST3 playback, and for the notation seen, the "play" property is disabled. "Violin" is just for the section marked "solo".

This issue happens with all playback instruments that I've used for this purpose, including both Musesounds (Known to happen with Horn in F, Trumpet & Trumpet(s), (solo) Violin 1 & 2 / Violins 1 & 2, Viola & Violas and Cello & Cellos) and Spitfire VST3 (specific sounds irrelevant). To take it further, if the video were longer, as in, I showed the proof that when the staff is hidden again after being unhidden, the playback will reflect what was last heard in the video, and not what was first heard.

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
@muse-bot muse-bot added the playback General playback issue label Dec 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
playback General playback issue
Projects
None yet
Development

No branches or pull requests

3 participants