dynamic-positioning.ly
<http://lilypond.1069038.n5.nabble.com/file/n149192/dynamic-positioning.ly> 
The following problem occurs with both 2.16.2 (stable) and 2.17.23
(unstable).

My goal is to produce an orchestral score which both
- uses *\partcombine* (e.g. to combine wind and brass instruments on shared
staves)
- has dynamics separately defined and attached to spacers, so that they can
be duplicated in several staves

Here are my observations:
- If the dynamic is attached directly to the note, it is positioned
correctly.
- If it is attached to a spacer, it is positioned too far to the left,
/unless/ the whole construction is explicitly wrapped in *\new Voice*. This
'solves' the problem in simple cases.
- However, when the music consists of *\partcombine*d material, (which mine
does) the dynamics are positioned wrongly, /even/ if I wrap the whole
construction in a *\new Voice*.

The incorrect positioning may seem small, but it causes great problems in a
real-life score, cutting into barlines and looking very odd especially at
the beginnings of bars.

So my question is, how can I get the dynamics to align themselves
'correctly', i.e. as they would be if they were directly attached to the
notes. Putting the dynamics in a Dynamics context is not really an option,
since that will make them align themselves on one line, and I want the
dynamics and hairpins to be snugly under the notes each time. Any ideas? I
am aware that existing 'issues' exist to do with dynamic positioning, but
many of them claim to be 'fixed' - yet they apparently are not.

I have attached a .ly file containing a series of minimal examples to
illustrate the observations I have made above.

Thanks everyone,

Dominic



--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/Dynamics-spacers-and-partcombine-used-at-once-tp149192.html
Sent from the User mailing list archive at Nabble.com.

_______________________________________________
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Reply via email to