musescore / musescore/MuseScore
String tuning: Split preset into a all-string detuning part and a part-string scordatura part. Add Nashville variant tunings to presets. Show/indicate correct tuning pitch octave/direction in score. Show preset name in score. Naming of custom tunings.
@bkunda is already working on this.
Since Feb 20, 2024.
- Dominant language
- C++
- Stars
- 15.1k
- Forks
- 3.3k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 91
Description
Your idea
(1) There are string tunings affecting the whole set of strings, like tune down 1/2 step, tune down 1 step, etc., which I would refer to as detuning, and other string tunings affecting only part of the strings, such as drop-D, open, Nashville tunings, traditionally referred to as a scordatura. Presently, whole-string detunings and part-string scordaturae are in one single preset list. However, any scordatura may be combined with any detuning of the whole set of strings. To reflect this, all the combinations would have to be included in one some list which would grow to considerable length and complexity, making it difficult to spot the right one.
I propose that the presets be split into a scordatura part and a detuning part, so one could select a scordatura like an open tuning, and then combine it with a detuning like tune down 1/2 step, as required. It would also be easy to expand the range of detunings up to more than 2 steps down, and also up.
I know that the same result might be obtained by manually adjusting each string, but this is combersome and prone to error.
So, presets could be split into a preset scordatura list box, and a detuning list box including any half step from, say, 2 1/2 steps down to 2 1/2 steps up. Default, of course, should be 0 steps.
(2) A Nashville Tuning normally prescribes E4-B3-G4-D4-A3-E3. I.e. strings 3-6 are an octave higher than standard tuning while stings 1-2 are left as standard. Pat Metheny uses a variant Nashville tuning where only strings 3-4 are an octave higher than while 1-2 and 5-6 are left standard. However, to my knowledge, he uses it on a Baritone guitar on his album "One Quiet Night" while I am not shure whether he would use it on a "normal" guitar as well. Anyway, this tuning style is also higly interesting for normal guitars as it allows for close chords in the upper parts while keeping bass play on the lower 2 strings.
So, I would propose to add the following preset, in addition to Nashville:
- Nashville Variant (Pat Metheny) (E4-B3-G4-D4-A2-E2)
Of course, in case that or as long as my proposal under (1) is not realized, I would ask for including detuned Nashville tunings to the preset list, such as:
- Nashville tune down 1/2 step (Eb4-Bb4-Gb4-Db4-Ab3-Eb3)
- Nashville tune down 1 step (D4-A4-F4-C4-G3-D3)
- Nashville tune doen 1 1/2 step (Db4-Ab4-E4-B4-Gb3-Db3)
- Nashville tune down 2 step (C4-G4-Eb4-Bb4-F3-C3)
- Nashville Variant (Pat Metheny) tune down 1/2 step (Eb4-Bb4-Gb4-Db4-Ab2-Eb2)
- ...
(3) Presently, all tunings are shown in uppercase letters in the score, not indicating the pitch (octave). However, some tunings require rising (such as Nashville) or dropping by an octave. In particular, Nashville tuning shows up on the score like: (1) - E, (2) - B, (3) - G, (4) - D, (5) - A, (6) - E. That would be right the same as in standard tuning so the reader would not know whether standard or Nashville tuning is required.
I think therefore that the correct pitch (octave) of each tuning should be shown in the score. This could be done in different ways which ideally could be selectable from the user dialog:
- including octave number of the tuning (for standard guitar tuning: E4-B3-G3-D3-A2-E2)
- conventional dash/underline/case coding as written (e''-b'-g'-d'-a-e)
- conventional dash/underline/case coding as sounding (e'-b-g-d-A-E)
- relative indicators (e.g. arrows indicating drop or rise tuning, as compared with string data of the instrument from stave properties)
(4) Presently, the name of a selected preset is only seen in the dialog window but is not shown in the score. Therefore, the reader would have to check any string as to whether at all, and if so, to what extent a string is to be altered. In a practical concert or show event, a guitarist would fequently have several guitars at hand for different tunings. It would be very helpful for the reader to see at a glance which tuning is required, to quickly grab the right guitar.
I know that it is possible that a further staff text is generated including the name of the tuning, which text then has to be aligned with the string tuning list. This is quite combersome.
I propose therefore that the selected preset name would also show up on the score. As always, it would be preferable if showing the preset name in the score was a selectable option.
(5) Presently, individually adjusted tunings are indicated as "custom". It would be helpful if an individual tuning could be given a name, which should also reflect in the selected workspace.
Problem to be solved
(1) Quicker finding the right preset. Enhancing flexibility in terms of combining all-string detuning with individual scordaturae.
(2) Additional tuning variants.
(3) Allowing the reader to properly apply the selected tuning.
(4) Allowing the reader to quickly identify a prescribed tuning. Saving time in writing. Saving time in concert or show event.
(5) Enhancing versatility of the feature. Accessing user-specific custom tunings.
Prior art
No response
Additional context
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.