musescore / musescore/MuseScore

The harp pedal diagram does not change after transposing the score

Open
#23,711 1 comment 0 reactions 1 assignee View on GitHub

@miiizen is already working on this.

Since Jul 23, 2024.

feature request P2 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. Open/create a score
  2. Add a diagram of the harp pedals in the key of C major/A minor
  3. Click on Tools 🠖 Transpose 🠖 in D Major/B minor 🠖 OK.
Expected behaviour

The harp pedal diagram was supposed to be transposed into the key of D major/B minor in the same way, but this did not happen.

Supporting files, videos and screenshots

https://github.com/user-attachments/assets/b70a27cc-1d0a-4e50-89ff-6b5e46c43080

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

MuseScore Studio version (64-bit): 4.3.2-241630831, revision: github-musescore-musescore-22b46f2

Regression

No.

Operating system

Windows 11

Additional context

Even if this is intended "by design", I still think it is wrong, since in the end transposing the score will not affect the sound of the glissando (for example), which is not correct. And if there are about 30 pieces (if not more) of these harp pedal diagrams in the score, then I consider it impractical to manually redo each of them.
The same goes for fretboard diagrams for guitar.

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.