-
Notifications
You must be signed in to change notification settings - Fork 668
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
Comments
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). |
@linhai could you provide an example of how your example would be rendered (ideally) |
Actually, I have no idea. I found nothing in google. Maybe two notes is the best way to show the chord. The example below is from Sibelius.
… On 5 Jan 2017, at 7:06 AM, Cyril Silverman ***@***.***> wrote:
@linhai <https://github.com/linhai> could you provide an example of how your example would be rendered (ideally)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub <#523 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AA8C-YNhwHKYE658lj7yLPV9XxFy7Q7Qks5rPCYCgaJpZM4LaZSn>.
|
@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:
|
Wouldn´t it make sense to represent it like chord(c#/5, dn/5, eb/5)? |
Two errors in a chord(d#/5, dn/5, db/5).
The text was updated successfully, but these errors were encountered: