Am 22.02.2013 11:18, schrieb Jim Long:
On Fri, Feb 22, 2013 at 09:41:01AM +0100, David Kastrup wrote:
Jim Long <[email protected]> writes:
I will say that the merging of noteheads onto stems is probably
the weak spot in my knowledge.
[...]
The piece also generates several warnings about clashing note
columns.
Small wonder:
\new Voice { \voiceOne \hornA }
\new Voice { \voiceOne \hornB }
Both with \voiceOne but in separate voices?
I didn't mean to imply that it shouldn't generate those warnings,
just acknowledging that the warning serve to indicate that this
probably isn't "snippet-quality" code.
I was trying to reproduce the example .png given in the blog,
accessible at http://felixrosch.com/example.png.
That example shows two grouped staves, each with two horn parts
written on the same stem, as though they were a chord.
Ah, that makes it clearer.
If you want to achieve that result but want (obviously) to have separate
voices you can write both as you did but write
\override NoteColumn #'ignore-collision = ##t
to suppress the warnings (which would make it more elegant).
But please read
http://www.lilypond.org/doc/v2.17/Documentation/notation/multiple-voices#automatic-part-combining,
which will probably lead you to the 'right' solution (especially in the
given context as a show-case example).
HTH
Urs
I didn't
know how else to merge the noteheads from two different voices
onto a single stem. See opening disclosure. I'll try chasing
down some of Xavier's clues.
_______________________________________________
lilypond-user mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/lilypond-user
_______________________________________________
lilypond-user mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/lilypond-user
