bug-lilypond
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Hairpin-end/dynamic-mark collision at barlines


From: Thomas Morley
Subject: Re: Hairpin-end/dynamic-mark collision at barlines
Date: Sat, 2 Apr 2016 01:01:04 +0200

Hi Connor,

thanks for well written your report.
Some details:

2016-04-01 23:11 GMT+02:00 Connor Harris <address@hidden>:
> To whom it may concern:
>
> Ordinarily, hairpins that terminate on notes with dynamic markings are
> shortened or vertically displaced so as not to collide with the dynamics
> (see (1) in the included code sample).

This is intended behaviour, at least the shortening. You may want to
improve those cases by overriding minimum-length.
\override Hairpin.minimum-length = #8 %% or what ever value fit your needs.
Tbh, those cases are a steady nuisance and waits for improvement...

The vertically displacement, (3) of your code, is indeed strange.

All other listed case can be done by applying a (correct)
tweak/override for 'to-barline.
\override Hairpin.to-barline = ##f

> When the end of a hairpin coincides
> both with the beginning of a bar and a dynamic mark, however, the width of
> the dynamic mark is ignored, and the hairpin ends on the barline even if
> this causes collisions with the dynamic mark. This happens both for
> decrescendi (2a) and crescendi (2b), and whether or not the hairpin spans
> more than one bar (2c).
>
> Also of note: this problem occurs only at hairpins' ends, not their
> beginnings (3), does not occur when hairpins cross barlines but end at a
> location not a barline (4), is immune to tweaking the to-barline hairpin
> property (5),

Nope.
Your tweak:
\tweak to-barline ##f g1\>
is placed wrongly, so it can't work.
Try:
g1-\tweak to-barline ##f \>

Or use the override as shown above.


> and also occurs with "built-in" dynamics, not just ones user-
> defined with make-dynamic-script (6).
>
> I am assuming, perhaps wrongly, that this is not desired behavior; whether
> or not it is, I would appreciate a workaround.
>
> I tested the included code sample on Windows binary packages, both 2.18.2
> and 2.19.39-1, which gave indistinguishable results.
>
> Best,
> Connor Harris
>
> \version "2.19.39"
>
> \paper {
>   ragged-right = ##t
> }
>
> pocoPMarkup = \markup {\normal-text \italic "un pochissimo" \dynamic "p"}
> pocoP = #(make-dynamic-script pocoPMarkup)
>
> \relative g' {g2_\>^\markup "(1)" g2\pocoP \break
>   g1\>^\markup "(2a)" g2\pocoP g2 \bar "||"
>   g1\<^\markup "(2b)" g2\pocoP g2 \bar "||"
>   g1\>^\markup "(2c)" g g2\pocoP g2 \break
>   g1\pocoP^\markup "(3)" g2\> g2 \break
>   g1\>~^\markup "(4)" g4 g g g\pocoP \break
>   \tweak to-barline ##f g1\>^\markup "(5)" g1\pocoP \break
>   g1\>^\markup "(6)" g4\ppppp g g g
> }
>

Sumary:
Case (3) may be a bug or not, I'm not sure yet.
All other is intended or known or may be worked around quite easily.


Cheers,
  Harm



reply via email to

[Prev in Thread] Current Thread [Next in Thread]