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

Chord with accidentals looks wrong #523

Open
linhai opened this issue Jan 4, 2017 · 6 comments
Open

Chord with accidentals looks wrong #523

linhai opened this issue Jan 4, 2017 · 6 comments

Comments

@linhai
Copy link

linhai commented Jan 4, 2017

Two errors in a chord(d#/5, dn/5, db/5).

  1. Only shows two note keys;
  2. First note key overlaps the last accidental.

image

@mscuthbert
Copy link
Collaborator

Point 2 seems to be the one worth fixing as a medium-term project, while point 1 is not handled correctly by any software package automatically (requires automatic stem forking).

@Silverwolf90
Copy link
Contributor

@linhai could you provide an example of how your example would be rendered (ideally)

@linhai
Copy link
Author

linhai commented Jan 5, 2017 via email

@gristow
Copy link
Collaborator

gristow commented Jan 5, 2017

The ideal rendering would be splitting the stem, showing multiple noteheads, each accidental appearing before the notehead it modifies. (For whole notes, generally a square bracket is used above the notes -- sort of like a big down-bow mark -- to show they're played at the same moment.) Stem splits of two are fairly common, three is rarer but happens.

The example from standard rep that comes to mind is Chopin's Ballade No. 2. Here's a measure with this issue -- from three different publishers, each of which takes a different approach. (The first would be my preference, it's what most modern houses have landed on.)

Peters Edition: Split stem (preferred in most modern music), when there's not a stem, use a square bracket above the whole notes to indicate they are to be played at the same time.
screen shot 2017-01-04 at 10 03 13 pm

Paderewski Edition (Breitkopf also follows suit): Write as two separate voices, arrange as accidental-note accidental-note
screen shot 2017-01-04 at 10 06 54 pm

Chopin Complete Works Edition (Bote & Bock): Strangest solution -- one of the notes is just off to the left of the stem, with no stem of its own.
screen shot 2017-01-04 at 10 10 29 pm

@Silverwolf90
Copy link
Contributor

Silverwolf90 commented Jan 5, 2017

@gristow That's a great comparison! Agreed that the split stem is the ideal way for two noteheads each with a different accidental. Behind Bars has a section on Altered Unisons (page 50). But the original case @linhai presented in fact has 3 notes -- a D sharp, D natural, and D flat. This specific case is not discussed in Behind Bars, but there is an example of a triple split stem in the context of a note cluster. So I guess I would do the following:

  • notehead+flat is displaced to the left
  • notehead+natural remains in default position
  • notehead+sharp is displaced to the right
  • Split the stem in 3, centered over the notehead w/ natural
  • Forever hold a grudge against the original composer :)

@rvilarl
Copy link
Collaborator

rvilarl commented Oct 24, 2021

Two errors in a chord(d#/5, dn/5, db/5).

  1. Only shows two note keys;
  2. First note key overlaps the last accidental.

Wouldn´t it make sense to represent it like chord(c#/5, dn/5, eb/5)?
@mscuthbert what is your oppinion?

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

No branches or pull requests

5 participants