Am 21.12.2014 um 18:00 schrieb Br. Samuel Springuel:
On 2014-12-21 12:20 AM, pe...@chubb.wattle.id.au wrote:
As both cases have the same stem direction one has to be shifted.
Usually if you want two voices you either give them separate staves,
or give one the \voiceOne and the other the \voiceTwo appellations.
Ah! I didn't notice this because I'm reproducing a chant without any
note stems.
Hi,
I've now had the chance to compile your example and have a look.
I think the first thing for you to do is to get clear about what you
actually want to achieve.
I'm not really sure why you chose to try out separate voices.
From the looks of it your original chorder version seems to be right
what you need.
You need voices when you *do* have voices, that is either different
"instruments" or "voices" or virtual instruments like in polyphonic
keyboard writing, where you really want to show that there are layers of
notes that belong together.
But if you use independent voices it's natural that each voice has its
own set of articulations and dynamics.
I'd say:
If you want to have distinct voices (for whatever reason) but want them
to be printed with only one (upper) articulation, then either write the
articulations to the upper voice only or (if you need them for MIDI)
hide them in the lower voice.
If that doesn't help you it'd be good to know still more about the
instrumental context.
Urs
However, even after adding \voiceOne and \voiceTwo I'm still seeing
the double articulation. It's harder to see (because the articulation
on the lower note tends to collide with the higher note) but it's
still there (see first articulated note below in voiced staff).
Changes are to use the `natural' articulation direction (- instead of
^)
I forced the up direction on the articulations because when I used the
natural articulation direction in chord construction the articulations
appeared below the chord (see third articulated note below in chorded
staff). In the piece I'm reproducing, however, the articulations were
above the notes. Further, this switch still results in double
articulations: one above and one below (see second and third
articulated note below in voiced staff).
To reproduce the articulations I've got, I need it to always appear
over the top note (the piece doesn't have any notes higher than bflat').
As an aside, dutch note names and \relative make data entry MUCH
faster.
I tried both of these before and found the resulting code much harder
to read. I don't speak Dutch and so the Dutch note names don't seem
natural to me ("is" and "es" are too similar to stay distinct). Also,
in relative mode I had lots of trouble telling just exactly which note
I was entering (I'd often have to go back and reset the score because
I'd made a mistake and entered the note in the wrong octave). As a
result I've made a deliberate choice for clarity over speed. It's
purely a personal preference, but this is what makes my life easier.
And I prefer to have bars present in a
longer piece, to allow line breaking and to allow bar checks to be
added in the source, so as to not lose myself when making amendments.
I don't disagree, but I'm working on a non-metrical piece with
arbitrary bar lines. As a result I can't depend on the normal bar
checking mechanisms and have to introduce them manually. Stripping
down to a tiny example hides this (as I've only included a single
"measure" in the example).
%%%%%%%%%%
\version "2.18.2"
\language "english"
mel = {bflat'2 bflat'4^- a'-- a'--}
harm = {g'2 g'4^- c'-- f'--}
chorded = {<g' bflat'>2 <g' bflat'>4-- <c' a'>-- <f' a'>^-}
global = { \key f \major
\set Score.timing = ##f
\omit Stem }
\new Staff \with {
\remove "Time_signature_engraver"
}
<<
\global
\new Voice = "melody" {\voiceOne \global \mel}
\new Voice = "harmony" {\voiceTwo \global \harm}
>>
\new Staff \with {
\remove "Time_signature_engraver"
}
{
\global
\chorded
}
✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝
Br. Samuel, OSB
(R. Padraic Springuel)
PAX ☧ ΧΡΙΣΤΟΣ
_______________________________________________
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
_______________________________________________
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user