Slurs
- « Previous
- 1
- 2
- 3
- 4
- Next »
b. 73-74
|
composition: Op. 27 No 1, Nocturne in C# minor
..
In GE, the slur ending in bar 73 points clearly to a continuation but there is not any in bar 74, first in a new system (cf. bars 65-66). This very inaccuracy was most probably a reason for shortening the slur in FE (→EE). category imprint: Differences between sources issues: Inaccuracies in GE |
||||||||
b. 78-83
|
composition: Op. 27 No 1, Nocturne in C# minor
..
In the sources, bars 78-83 are embraced with with two three-bar slurs. In the editors' opinion, the discrepancy caused by the change of key signature could be the reason for inaccurate reading or notation of slurs, as the slur division does not correspond to any division of the phrase resulting from the melody structure or harmonic progression. category imprint: Interpretations within context; Differences between sources; Editorial revisions |
||||||||
b. 84-85
|
composition: Op. 27 No 1, Nocturne in C# minor
..
The slur in EE is certainly an inauthentic addition. category imprint: Differences between sources issues: EE revisions |
||||||||
b. 86-87
|
composition: Op. 27 No 1, Nocturne in C# minor
..
The slur in EE is certainly an inauthentic addition. category imprint: Differences between sources issues: EE revisions |
||||||||
b. 87-88
|
composition: Op. 27 No 1, Nocturne in C# minor
..
GE lacks the ending of the tie sustaining f sharp2 into bar 88 that opens a new line of text in the sources. In FE (→EE1→EE2) the tie from bar 87 was "finished" by beginning the phrasing slur in bar 88 clearly before the 1st note. That version is definitely erroneous (see bars 20-21). In EE3, the ending of the tie sustaining f sharp2was added in bar 88 to the inaccurately started slur, which brought the notation closer to the correct text. category imprint: Graphic ambiguousness; Differences between sources issues: EE revisions , Errors in FE , Inaccuracies in GE |
- « Previous
- 1
- 2
- 3
- 4
- Next »