musescore / musescore/MuseScore

Suggestions for amendments to the engraving of guitar tablatures

Open
#23,562 0 comments 0 reactions 2 assignees View on GitHub

Nobody has claimed this yet.

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

Description

My idea

In this issue, I will propose some corrections to the engraving of guitar tablatures. The flaws were revealed by me in the process of writing a recent weighty transcription. This time I will have to deviate from the standard template, otherwise I would have to spam several issues in a row. Therefore, I decided to put the minor flaws together and report it in one issue (I hope the MuseScore Studio team will forgive me for this).

Problem to be solved

Below I have described point by point what each flaw is (in my opinion).

  1. Improved staccato articulation position in guitar tablature.
  2. Alignment of the fret number positions in the tablature according to the position of the grace note.
    • I propose to amend the horizontal alignment of the fret numbers in the tablature in cases where the positions of the numbers from which, for example, the bend begins, should be strictly under a grace note, and not under the "parent" note.
      It would also be nice to reduce the size of those numbers that relate to a grace note.
    • This way the tablature will become visually easier to read. The user will clearly understand that the fret number refers specifically to a grace note.
    • Снимок экрана (428)
      Снимок экрана (430)
      Снимок экрана (431)
    • This applies to pre-bends and unison bends.
  3. The let ring lines should cover the full visibility of the note duration, not just the notehead.
  4. Release back to 1/2, etc.
    • Снимок экрана (435)
    • In my opinion, this is incorrect. The bend digit should not be located within the tablature, only the fret numbers can be in the tablature.
    • Take a look at how this is indicated in other notation software. I think this is the right thing to do:
      Снимок экрана (436)

Checklist

  • ✅ This request follows the guidelines for reporting issues
  • ✅ I have verified that this feature request has not been logged before, by searching the issue tracker for similar requests
  • ✅ I have attempted to identify the root problem as concisely as possible, and have used minimal reproducible examples where possible
  • ✅ I have verified that this issues has not been logged before, by searching the issue tracker for similar issues

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.