Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

n01op18-1_03: wrong labels due to localkey of i #29

Open
johentsch opened this issue Aug 5, 2022 · 1 comment
Open

n01op18-1_03: wrong labels due to localkey of i #29

johentsch opened this issue Aug 5, 2022 · 1 comment

Comments

@johentsch
Copy link
Member

MC 99 has a change of localkey to i but the labels are written as if appearing in the key of I:

  • 100: V(b64) => V(64)
  • 106: V/bVII => V/VII
  • 110: vii => #vii
  • etc.

The best solution, probably, is to change the localkey to I.

@malcolmsailor
Copy link
Contributor

malcolmsailor commented Aug 9, 2022

There is a similar (only worse, because lasting longer etc.) problem in n16op135_04

Here, the globalkey is F minor throughout, but the annotator has indicated at least some of the localkeys relative to major (which is understandable, since the main key of the movement after the introduction is in fact F major). This is particularly a problem when the music goes to D minor and D major, which are notated as vi and VI respectively. But in F minor, these roman numerals indicate Db minor and Db major!

On the following chart notes that belong to the chord are plotted in yellow and notes that do not are plotted in purple. Note the solid purple regions!
n16op135_04

I think this is relatively easy to fix if you elect to leave the globalkey in F minor: one would just have to go through and change the localkey labels. I don't suppose there is a way to indicate a change of mode of the global key? (So that it goes from f minor to F major after the introduction?) That could be even easier.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants