musescore / musescore/MuseScore

"Keep the same fingering..." option to be added to transposition feature

Open
#17,820 3 comments 1 reaction 2 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Your idea

In current master of MU4, when I use transposition for the Tab staff (separated or linked) notes on the tab staff are optimises by system and can be moved between strings around the guitar fret neck. This approach is not really common for pop-rock guitarists and sometimes leads to unplayable intervals or chords. We've got a task from UG team to implement a logic which is more common. But, also, this option will be good as a guitar improvement MU4.

Here're main requirements of transposition of notes on Tab staff:
- Transposition on tab staff should NOT change strings, only frets
- If transposed note goes below the fret 0 it should be moved to one string lower (if no lower strings available negative red fret should be rendered, e.g. -2)
- If transposed note goes above the fret 24 it should be moved to one string higher (if no higher strings available red frets should be rendered, e.g. 26)

The option should be reproduced as a checkbox in the Transposition dialog with a text "Keep the same fingering for tabulature staves (where possible)". When checkbox is enabled system should keep the same fingering, when disabled - current transposition logic should be used.

Use the design for implementation
Screenshot 2023-06-01 at 4 16 52 pm

Problem to be solved

Additional, more common transposition approach will be implemented

Prior art

No response

Additional context

No response

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.