[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Hairpin-end/dynamic-mark collision at barlines
From: |
Connor Harris |
Subject: |
Hairpin-end/dynamic-mark collision at barlines |
Date: |
Fri, 1 Apr 2016 21:11:02 +0000 (UTC) |
User-agent: |
Loom/3.14 (http://gmane.org/) |
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). 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), 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
}
- Hairpin-end/dynamic-mark collision at barlines,
Connor Harris <=