musescore / musescore/MuseScore

Identical dynamics duplicated when imploding

Open
#27,604 2 comments 0 reactions 2 assignees View on GitHub

Nobody has claimed this yet.

P3 UX/interaction
Dominant language
C++
Stars
15.1k
Forks
3.3k
Avg merge
2d 2h
Merged PRs (30d)
91

Description

Issue type

UX/Interaction bug (incorrect behaviour)

Description with steps to reproduce
  1. Implode two staves with differing dynamics
  2. Observe the overlapping dynamics.

Scenario 2

  1. Implode two staves with same dynamics.
  2. Change one of the dynamics, and observe overlapping.
Supporting files, videos and screenshots

Scenario 2:

https://github.com/user-attachments/assets/67d4e7b4-102d-4700-99ca-cd74e1b2a3e1

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.5.1-250800846, revision: github-musescore-musescore-603eca8

Regression

I was unable to check

Operating system

Windows 11

Additional context

Perhaps it is not a bug for scenario 1 (though it could certainly be better designed), but when the dynamics are identical they should definitely not be duplicated.
If it is not a bug for scenario 1, then I suggest the dynamics should either appear above or below the staff as applies to their voice, or else all dynamics should be deleted except those of the staff they have been collapsed on to.

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.