An example of the role that analysis can play in music editing:
Various editions of Mozart’s piano sonata K. 457, including the New Mozart Edition, comment on this seeming anomaly at X (circled in m. 209) in the last movement:
Is this a slip of the pen? Should the three F#’s at X follow the prevailing neighboring-note pattern seen at the arrows? If so, B would replace A:
But as likely as this correction seems:
1. Mozart rarely mispositions a note head.
2. Two mistakes are required here, the badly placed note head and the omission of a sharp. Mozart does occasionally omit accidentals. But two mistakes at once?
3. If the pattern from the previous measures is to be maintained, why did he write an F as the first note of the measure rather than an E#? Is that also an error? Three errors in one measure?
Based on the following reasoning, I believe that no error occurs here in the manuscript and that the measure is correct as written:
Each of the four similar measures leading to m. 209 contains one principal melody note surrounded by neighboring tones. But measure 209 contains two melody tones, F and F#, and no neighboring tones. The F holds over from the previous measure so that it can fall with the A flat bass tone to complete an F minor chord, which is the iv that will lead eventually to V. It is a chord tone not a decoration and therefore must be written as an F:
The rest of the measure presents an altered form of iv7 created by the passing tone F#.
But why not use the E# to decorate the F# later in the measure? Here Mozart was faced with a difficult choice. If he writes an E# (=F), there is a danger that one will hear this as a repeat of the opening F — F# and iv6 — #iv6/5. We would suddenly have four melody notes and four harmonic changes in the measure, which is out of keeping with the rest.
If he doesn’t use an E#, the only possibility is to repeat the F#—not great from the point of melodic fluency and motivic consistency, but better in terms of voice leading and overall consistency.
Mozart makes his choice, which I think is the best given the situation and one that should be respected in performance.
A more complete analysis follows. The first example shows the symmetrical nature of the passage (bracketed) and Mozart's omission of a measure through ellipsis:
Mozart’s Logic: K. 457
-
- Posts: 2781
- Joined: 05 Oct 2015, 14:25
- Location: Raleigh, NC USA
Mozart’s Logic: K. 457
- Attachments
-
- Mozart K 457.3 E.png (42.82 KiB) Viewed 24888 times
-
- Mozart K 457.3 D.png (94.99 KiB) Viewed 24890 times
M1 Mac mini (OS 12.4), Dorico 6, Finale 25.5, GPO 4, Affinity Publisher 2, SmartScore 64 Pro, JW Plug-ins, TG Tools, Keyboard maestro
-
- Posts: 38
- Joined: 06 Mar 2017, 19:18
Re: Mozart’s Logic: K. 457
Crystal clear, John!
-
- Posts: 2781
- Joined: 05 Oct 2015, 14:25
- Location: Raleigh, NC USA
Re: Mozart’s Logic: K. 457
Thanks so much, Felipe. I am glad you felt that I got my point across.
M1 Mac mini (OS 12.4), Dorico 6, Finale 25.5, GPO 4, Affinity Publisher 2, SmartScore 64 Pro, JW Plug-ins, TG Tools, Keyboard maestro
Re: Mozart’s Logic: K. 457
Yes, that's correct. From the harmonic analysis perspective it is very easy:
F = creates f-minor7, that is subdominant in c-min; then F# = creates Ger+6—leading to D6/4.
https://musictheory.pugetsound.edu/mt21 ... hords.html
F = creates f-minor7, that is subdominant in c-min; then F# = creates Ger+6—leading to D6/4.
https://musictheory.pugetsound.edu/mt21 ... hords.html
- Attachments
-
- hotufql4.png (3.83 KiB) Viewed 24743 times
Finale 27.5 • Sibelius 2024.3• MuseScore 4+ • Logic Pro X+ • Ableton Live 12+ • Digital Performer 11 /// MacOS Monterey (secondary in use systems: Fedora 35, Windows 10)
-
- Posts: 2781
- Joined: 05 Oct 2015, 14:25
- Location: Raleigh, NC USA
Re: Mozart’s Logic: K. 457
Thank you, OCTO.
M1 Mac mini (OS 12.4), Dorico 6, Finale 25.5, GPO 4, Affinity Publisher 2, SmartScore 64 Pro, JW Plug-ins, TG Tools, Keyboard maestro