musescore / musescore/MuseScore

Easy, intellegentTAB fret number entry method that references Fretboard Diagrams

Open
#34,537 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Your idea

Presently a click-entered tablature number always defaults to 0.

I’d like to see the following option when a measure has one or more Fretboard diagrams:

When click-entering notes on the strings of a linked tablature staff—IF the linked treble staff has one or more Fretboard diagrams—it would be helpful to have the option (on click) so the fret number DOES NOT always default to 0, but instead enters the fret relevant to the string indicated in the Fretboard diagram.

See attached MS7.4 score:

Tablature entry default fret number on clicked string.mscz.zip

Image
Problem to be solved

This would dramatically increase the speed of tablature fret entry, particularly when complex chords are involved.

Prior art

No response

Additional context

No response

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

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.

Research direction

Open the attached “Tablature entry default fret number on clicked string.mscz.zip” score and reproduce click-entry on a linked tablature staff with fretboard diagrams. Trace the tablature click-entry and fretboard-diagram handling entry points, then define the option’s behavior and verify that clicked strings receive the corresponding diagram fret without breaking the existing default.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
desktop
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.