Thanks for your reply - it solves the problem of bar-line/dynamic collisions (or rather, it side-steps the problem). Actually it also begins to answer what might well have been my next question, because generally I prefer the left edge of dynamics to be related to the note position. But I should like it to be a little further to the left than the value of -1 gives. That is a bit of a problem, because the value required for a dynamic such as 'f' will be different from that needed by a wider marking such as 'ffff'.
Is there perhaps a way of specifying where the left edge of the dynamic should be in relation to the note? For instance, I might like all dynamics to appear about half a note-head's width before the left edge of the note-head itself. It is going to get very tedious having continually to specify different self-alignment-X values when there are, say, alternating 'p' and 'mf' markings. Also, considering that LilyPond is generally so good at avoiding collisions, I have been surprised to find that it seems to have no objection to printing dynamics and bar-lines on top of one another. Is there no way to tell it to avoid these collisions? I would have expected avoidance to be the default, with an override to allow collisions if that is what is wanted in a particular case. But the default appears to be that bar-lines and dynamics pay no regard for each other. Am I missing something here? David On Mon, 2014-02-03 at 03:04 -0500, Hwaen Ch'uqi wrote: > Greetings David, > > > Following the problem I was having with dynamics in a flute part and a > > piano part not lining up, on the advice of the list I upgraded my > > LilyPond from v2.14.2 to 2.18.0. > > > > Problem of non-alignment solved. > > > > But I still find that dynamics often contact or even cross a bar-line. > > In the flute part of this piece it does not matter, of course, because > > the bar-line does not extend beyond the stave. But in the piano part it > > does matter. The problem is the same whether the dynamic marks are > > added in a Staff context or in a separate Dynamics context. > > > > How do I tell LilyPond not to superimpose dynamics and bar-lines? > > > > David > > Now that you have successfully upgraded to LilyPond 2.18.0, the > command which I earlier gave you should work - namely, > > \override Staff.DynamicText.self-alignment-X = #-1 > > If your dynamics are in a Dynamics context rather than a Staff > context, then change Staff in the above command to Dynamics. The > default horizontal position for DynamicText is #0, or centered. #1 > right-aligns the dynamics; #-1 left-aligns them. Other numbers, > whether between or outside of these bounds, will work as well. > I hope this helps. > Please take care. _______________________________________________ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
