Menu

#712 alignment of multiple \tempo marks over `church rests'

Accepted
nobody
None
Defect
2020-04-05
2008-12-20
Anonymous
No

Originally created by: *anonymous

Originally created by: lemzw...@googlemail.com

\version "2.11.65"

\header { texidoc = "
The text string of @code{\tempo} over whole bar rests always starts
at the beginning of a bar.

Here is a counterexample.
" }

{
  \tempo "Foo" R1*5 |
  \tempo "Bar" R1*5 |
}

\layout {
  \context {
    \Score
    skipBars = ##t
  }
}

\paper {
  ragged-right = ##f
}
1 Attachments

Related

Issues: #3660

Discussion

  • Google Importer

    Google Importer - 2009-10-10

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

    (No comment was entered for this change.)

    Labels: Priority-Low

     
  • Google Importer

    Google Importer - 2009-12-16

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

    (No comment was entered for this change.)

    Labels: -Priority-Low Priority-Medium

     
  • Google Importer

    Google Importer - 2010-03-02

    Originally posted by: v.villenave

    This seems related to issue 684 (at least, I believe fixing #684 should fix this one
    as well).

    Owner: ---

     

    Related

    Issues: #684

  • Google Importer

    Google Importer - 2011-04-16

    Originally posted by: x.sche...@gmail.com

    Output is different with 2.13.59 since issue 684 is now fixed.
    Now the text string of @code{\tempo} over whole bar rests always starts
    at the beginning of a bar.

    The output is not very pleasant though (IMHO).  It is maybe  better than
    2.12 but I'd prefer it to be aligned over the first (non-existant) note
    (NoteColumn?).

    See attachment.

     

    Related

    Issues: #684

  • Google Importer

    Google Importer - 2012-12-31

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

    Yes, this would be a better optical solution.

     
  • Google Importer

    Google Importer - 2012-12-31

    Originally posted by: x.sche...@gmail.com

    You mean align the tempo indication on the first (non-existing) note?

    Maybe Mike could solve this issue while fixing issue 1263.
    I'll drop a comment there.

    Thank you Werner!

     

    Related

    Issues: #1263

  • Google Importer

    Google Importer - 2012-12-31

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

    Yes, aligning the tempo indication on the first note gives a better result.

     
  • Google Importer

    Google Importer - 2013-02-12

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

    The tempo indication over a full-measure rest was moved back to the bar-line as part of the fix for (bounty) issue 684 citing the request of this issue as the reason:
    https://codereview.appspot.com/1579041/#msg5

    It looks like we can change the settings to
    \override Score.MetronomeMark #'non-break-align-symbols =  #'(paper-column-interface)
    if we want the tempo indication on the first (non-existing) note.

     

    Related

    Issues: #684

  • Google Importer

    Google Importer - 2013-02-12

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

    Neil added a regression test ‘metronome-marking-break-align.ly’ that says pretty much what the initial request said:
    "\tempo marks are aligned with the time signature or first musical element unless the first element is a multi-measure rest: in this case, the tempo mark is aligned with the bar line."

    The result looks strange to me, so I'll use the override in the comment above, but this bug seems to be fixed.

    Labels: fixed_2_17
    Status: Fixed

     
  • Google Importer

    Google Importer - 2013-02-13

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

    Hmm.  For me, `beginning of a bar' is not the same as `aligned with the bar line'.  Especially the `Vivace' in your image is certainly wrong.  Neil's regression test slipped my attention, sorry.

    Note that the alignment mentioned in comment #8 isn't optimal either, especially if the rest takes a large horizontal space: For a plain full-measure rest, I consider the position of the first paper column too much to the right.  Instead, I would like to position the tempo mark as if there were a time signature.

    Below are shown all possible combinations, with and without the paper column setting.  Especially ugly is the case where the tempo mark slips under the rehearsal mark

    Messy, messy.  I've removed the `fixed' label.

    Labels: -fixed_2_17
    Status: Started

     
  • Google Importer

    Google Importer - 2013-02-13

    Originally posted by: x.sche...@gmail.com

    Note that the placement of RehearsalMark at begin of line is wrong,
    it should not be printed above the clef.
    This is tracked as issue 1150.

    (imagine an "invisible" barline after the Clef, after the KeySignature,
    before possible TimeSignature, the RehearsalMark would be just on top
    of this "invisible" barline)
    The placement of this bar line can be clearly seen if you put a begin
    of volta repeat barline at begin of line, actually.

     

    Related

    Issues: #1150

  • Trevor Daniels

    Trevor Daniels - 2015-09-28
    • Description has changed:

    Diff:

    --- old
    +++ new
    @@ -2,29 +2,30 @@
    
     *Originally created by:* [lemzw...@googlemail.com](http://code.google.com/u/102649819178652971408/)
    
    +~~~~
    +:::TeX
     \version "2.11.65"
    
    -\header \{ texidoc = "
    -The text string of @code\{\tempo\} over whole bar rests always starts
    +\header { texidoc = "
    +The text string of @code{\tempo} over whole bar rests always starts
     at the beginning of a bar.
    
     Here is a counterexample.
    -" \}
    +" }
    
    -\{
    -  \tempo "Foo" [r1]\*5 |
    -  \tempo "Bar" [r1]\*5 |
    -\}
    +{
    +  \tempo "Foo" R1*5 |
    +  \tempo "Bar" R1*5 |
    +}
    
    -\layout \{
    -  \context \{
    -    \Score
    -    skipBars = \#\#t
    -  \}
    -\}
    +\layout {
    +  \context {
    +    \Score
    +    skipBars = ##t
    +  }
    +}
    
    -\paper \{
    -  ragged-right = \#\#f
    -\}
    -
    -% EOF
    +\paper {
    +  ragged-right = ##f
    +}
    +~~~~
    
    • Needs: -->
    • Patch: -->
     
  • Trevor Daniels

    Trevor Daniels - 2015-09-28
     
  • Trevor Daniels

    Trevor Daniels - 2015-10-22
    • status: Started --> Accepted
     
  • Trevor Daniels

    Trevor Daniels - 2015-10-22

    Changing Status to Accepted as there is no owner, no patch and there has been no action for several years.

     
  • Valentin Villenave

    Is this issue still relevant? As of 2.20 the following setting is no longer working (or have I overlooked a syntax change?):
    \override Score.MetronomeMark.non-break-align-symbols = #'(paper-column-interface)
    Besides, Xavier’s two examples now look exactly the same.

    Couldn’t/shouldn’t we rather make it simply a matter of documenting the current behavior (which, by the way, doesn’t look so ugly to me)?

     
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.