-
Notifications
You must be signed in to change notification settings - Fork 0
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
Enharmonies #25
Comments
This is not mentioned in the guidelines but I think the way annotators go at it so far is to care less about enharmonic spelling than about the function that the chord conveys in its context. In this particular case, I have trouble considering the chord over Eb as a B major chord because I cannot hear it as anything else than a chord over |
Look at the following bar: the e minor harmony is the In any case, if function is what matters over enharmonic spelling - I'd naturally agree - perhaps a comment and an example could be added to the guidelines in order to guide annotators outside your lab. |
Maybe I am blind but I don't see an E minor chord; otherwise I would totally agree. |
You're right, I'm the blind/imaginative one: I was extending the natural from the previous bar (which one has to do very frequently in these sources, but certainly not here). In that case, I'd enharmonise the Eb-Gb-B as Eb-Gb-Cb ( |
Are annotators encouraged to consider enharmonies when a chord seems out of context in the way it is written?
See the example below (in Bb major): b. 50 is, as written, a minor 4th degree with augmented fifth yet it functions as the dominant of the following chord (Eb=D# and Gb=F#). It's a 1733 piece, so no augmented 5ths in general (or in other pieces by the same composer, Caldara). What would you tell annotators?
The text was updated successfully, but these errors were encountered: