Menu

#1547 Too many colliding rests

Verified
nobody
Defect
2011-07-04
2011-03-02
Anonymous
No

Originally created by: *anonymous

Originally created by: RalphBug...@gmail.com

Phil Holmes :

Fitting music on 1 page...
Drawing systems...
warning: too many colliding rests
warning: too many colliding rests

The warnings aren't there unless I have the 3rd voice.  Seems like a bug to me, and I can't find a report on the tracker?

\relative c'{
\new Staff
<<
\new Voice { \voiceOne f'8 f f r f r \oneVoice }
\new Voice { \voiceTwo d,8 d d r d r \oneVoice }
\new Voice { \voiceFour \tieUp a'2~ a \oneVoice }

}

Keith OHara :
The warning is not always a false alarm, sometimes LilyPond fails to place the
two rests "correctly".  I suspect that her rules for placement require keeping
rests away from the line of the third voice, so the warning tells us she cannot
not satisfy all her rules.

\version "2.12"
\new Staff <<
\new Voice { \voiceOne s4 }  % just a skip
\new Voice { \voiceTwo d'8 r }
% warning before failure if voiceFour, not so bad if voiceThree.
\new Voice { \voiceFour a'8 r }
%{%} >>

Phil Holmes :
My preference is for all my lily source to compile cleanly, so a warning when there's actually no problem is annoying.  Given the other collisions that can occur and don't produce a warning, I'd view this warning when there's no collision as a bug.  Low priority, but still a bug.

Related

Issues: #1618

Discussion

  • Google Importer

    Google Importer - 2011-04-22

    Originally posted by: k-ohara5...@oco.net

    Pitched rests {\voiceFour a'8 b'\rest} can produce good output but still issue the warning.

    Better behavior would be to suppress the warning if the "too many colliding" rests are explicitly pitched.

     
  • Google Importer

    Google Importer - 2011-04-24

    Originally posted by: v.villenave

    Fixing typo in the issue's title.

    Summary: Too many colliding rests
    Labels: Warning

     
  • Google Importer

    Google Importer - 2011-05-01

    Originally posted by: k-ohara5...@oco.net

    With the patch pushed in 1edd0, the original example generates no warning,
    but my counterexample (above after "not always a false alarm") does produce a warning (because the rests are overlaid, which some, but not all users will want).

    Labels: fixed_2_15_0
    Status: Fixed

     
  • Google Importer

    Google Importer - 2011-05-03

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

    Verified 2.15.0

    Status: Verified

     
  • Google Importer

    Google Importer - 2011-05-04

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

    Unverified in 2.13.61

    Status: Fixed

     
  • Google Importer

    Google Importer - 2011-06-21

    Originally posted by: PhilEHol...@googlemail.com

    (No comment was entered for this change.)

    Status: Verified

     
  • Google Importer

    Google Importer - 2011-07-04

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

    Backported

    Labels: fixed_2_14_2