#1089 DynamicTextSpanner not printed

[Anonymous]

Originally created by: *anonymous

Originally created by: pnorcks@gmail.com

Report: http://lists.gnu.org/archive/html/bug-lilypond/2010-05/msg00132.html

% version 2.10.33 is okay
\version "2.13.21"

% In the following example the DynamicTextSpanner is not printed.
%
% The worst is that it does not even give a warning!

\paper { ragged-right = ##t }

\score {
  \relative c' {
    % for 2.10.33, this command is \setTextCresc
    \crescTextCresc
    c'4\p\< c\!  % cresc not printed; no problem without \p
    c c
  }
}

[Google Importer]

Originally posted by: pnorcks@gmail.com

So, apparently I forgot to test 2.12.3, because it works there...

The regression was introduced in 2.13.11, I suspect with this commit:

http://git.savannah.gnu.org/gitweb/?p=lilypond.git;a=commitdiff;h=b0ceb64701c0418fb074b6823cad1c682cefe76a

[Google Importer]

Originally posted by: n.putt...@gmail.com

Yep, that looks like the cause.

The extra padding added to keep the `cresc.' away from the piano dynamic makes the
combined padding from left-right larger than the distance between the spanning points.

From line-spanner.cc:

273   if (gaps[LEFT] + gaps[RIGHT] > dz.length ())
274     {
275       return SCM_EOL;
276     }

Line 275 is where you'd want a warning.

[Google Importer]

Originally posted by: musiccom...@gmail.com

So, it should be a warning, not just work like it did before?

[Google Importer]

Originally posted by: Carl.D.S...@gmail.com

There was a decision to add a bit of space to separate the cresc. from the p.  In so doing, the available space
became too short to fit both.  If there were a warning, the user could make the necessary adjustments.

I actually don't think that 2.10.33 is correct!  The crescendo is supposed to end on the 2nd note in the measure
according to the input code.  But the text spanner goes to at least the 3rd note of the measure, and might be
interpreted as going to the 4th.  So, even though 2.10.33 prints cresc., I don't think the output is consistent with
the input.

[Google Importer]

Originally posted by: percival.music.ca@gmail.com

Good rationale; adjusting priority accordingly.

Labels: -Priority-Critical -Regression Priority-Medium Warning

[Google Importer]

Originally posted by: brownian.box@gmail.com

Some discussion on the topic:
http://lists.gnu.org/archive/html/bug-lilypond/2010-05/msg00277.html

Surely, i would better "summarize" it here, but i am still trying to understand
what's they're talking about ,O)

Hopefully, someone will do this better. If needed.

[Google Importer]

Originally posted by: reinhold...@gmail.com

Concerning Carl's comment: You are correct that the cresc ends on the second note. Hoever, the line spanner of text crescendi cause spacing problems, even if no line is printed at all. In particular, if you print the dynamics above the staff, then the spanner (even if no visible line is printed) will shift e.g. bar number up, which is particularly bad if the staff contains some very high pitches... For this reason, I often have to end a text cresc immediately after creating it.

[Google Importer]

Originally posted by: Carl.D.S...@gmail.com

Responding to Neil --

I was not proposing that this is not a bug.  I agree it is a bug.  I was just proposing that it is not a regression.

[Google Importer]

Originally posted by: n.putt...@gmail.com

> Responding to Neil --

Carl, are you sure you're not replying to somebody else here?