[Top][All Lists]

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

[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #3208 Wrong Mu

From: Auto mailings of changes to Lily Issues via Testlilyissues-auto
Subject: [Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #3208 Wrong MultiMeasureRest glyph
Date: Tue, 26 Dec 2017 11:14:41 -0000

issue 3208: MMRs for > 1 m. only count m.

MMRs with measure-count == 1 (single whole measure rests) don’t change
their behaviour (i. e. they respect measure length when choosing the
displayed rest symbol).

MMRs with measure-count > 1 now only respect measure-count and don’t
scale that by closest_duration_log which depends on measure-length.

What do Gould et al. say about the whole issue? I don’t find the discussion on the tracker very clear

[issues:#3208] Wrong MultiMeasureRest glyph

Status: Started
Created: Wed Feb 27, 2013 03:07 AM UTC by Anonymous
Last Updated: Tue Dec 26, 2017 11:14 AM UTC
Owner: nobody

Originally created by: *anonymous

Originally created by: address@hidden

Thomas Morley reported here:

as follows:

With measures longer than two whole notes LilyPond chooses different
glyphs for MultiMeasureRest.

\version "2.17.12"

\new Staff {

  \time 7/4


  \time 9/4

  \time 18/4

Discussion on the user-list:

According to Gould LilyPond's default seems to be correct.
Werner objects.

At least there's need for discussion, I think.

Attached an image showing "LilyPond's default" vs "Correct?"


Sent from because address@hidden is subscribed to

To unsubscribe from further messages, a project admin can change settings at Or, if this is a mailing list, you can unsubscribe from the mailing list.

Check out the vibrant tech community on one of the world's most
engaging tech sites,!
Testlilyissues-auto mailing list

reply via email to

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