"Use german note names" in 1.3 score is honored only after editing a chord symbol

• Jun 24, 2014 - 07:04
Type
Functional
Severity
3
Status
closed
Project
MuseScore

MuseScore a818188986

  1. Open attached score, created with 1.3, it contains one chord symbol and the style has been changed to use german note names. Note that on 1.3 it doesn't make any difference in the display... and the chord symbol is displayed as F#m
  2. In MuseScore a818188986 the chord symbol is also displayed as F#m
  3. Double click it the chord symbol
  4. Now the chord symbol is displayed as Fis

Discussion: I'm not really sure what the expected behavior is here since in 1.3 I believe "use german note names" had no impact on the accidental. I guess it would be nicer if the behavior is consistent, so or we ignore the "use german name" option when importing 1.3 files, or we make sure that the chord symbols are displayed correctly (Fis) and do not change when edited.

Comments

• Jun 25, 2014 - 00:49
Severity ⇒

The change upon edit was a bug on reading 1.3 scores; that was an easy fix.

I've read over some previous discussions of expected behavior for German chords overall:

http://musescore.org/en/node/21540
http://musescore.org/en/node/20731
http://musescore.org/en/node/7017

Plus I've looked at the various options provided by LilyPond, Sibelius, and Finale.

We seem to decided some time ago to use "H" and "Bb" for German chords (typed as "H" and "B" respectively). Not understanding this, I had changed the rendering for TPC_B_B to "B"; I am now changing it back to "Bb" (still typed as "B" as in 1.3).

Up through 1.3, we rendered sharp and flat as "#" and "b" even with the German option. The consensus seems to be that it would be better to change to "is" and "es" going forward, so I had made this change as well, and I'd like to keep it this way unless the consensus shifts again. However, I can and will make it so that German 1.3 scores continue to render with "#" and "b" - *if* they are using one of the pre-defined chord description files that we ship (I am tweaking the 2.0 versions of the legacy files to force "is" and "es" to render as "#" and "b"). 1.3 scores using custom chord description files will render sharp and flat as "is" and "es" unless users further customize their chord description files to override this.

I've thought about the different variations that could possibly make sense to support, and most if not all can be accomplished by chord description file customization, starting either from an existing custom file, a legacy file, or the new default files for standard and jazz styles.

With German option turned on:

- default rendering of TPC_B is "H"; you can change to "B" or "B♮" by customizing sym declaration for "H"
- default rendering of TPC_B_B is "Bb"; you can change to "B" or "Bes" by customizing sym declaration for "b"
- default rendering of sharp is "is"; you can change to "#" by customizing sym declaration for "is" (I am already doing this for the 2.0 versions of the legacy files)
- default rendering of flat is "b"; you can change to "b" by customizing sym declaration for "es" (I am already doing this for the 2.0 versions of the legacy files)
- default rendering of bass notes is lower case; you can render as capitals by customizing sym declarations for "a" - "h" (with class="note" to avoid also overriding rendering of "b" as flat sign in TPC_B_B)

Not that I expect any of this to be obvious. I just wanted to make sure the defaults make sense.

Reply

• Jun 25, 2014 - 02:35
Severity ⇒
Status (old) active ⇒ patch (ready to commit)

https://github.com/musescore/MuseScore/pull/1008

Implements what I propose above:

- fix bug preventing German spelling mode from being recognized initially on load of 1.3 score
- change default rendering of TPC_B_B from B to Bb (reverting to 1.3 behavior even for new scores)
- edit legacy chord description files to override default spelling of flat and sharp, so scores created in 1.3 using German spelling will keep 1.3 rendering of "b" and "#" while new scores will get "es" and "is"

Reply