lilypond-auto
[Top][All Lists]
Advanced

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

Re: [Lilypond-auto] Issue 3687 in lilypond: only full-measure-rests shou


From: lilypond
Subject: Re: [Lilypond-auto] Issue 3687 in lilypond: only full-measure-rests should be able to compress
Date: Fri, 01 May 2015 22:00:37 +0000

Updates:
        Status: Started
        Owner: tdanielsmusic
        Labels: Patch-new

Comment #4 on issue 3687 by tdanielsmusic: only full-measure-rests should be able to compress
https://code.google.com/p/lilypond/issues/detail?id=3687#c4

Issue 3687 (part 4): Update regression tests to use \compressMMRests


Issue 3687 (part 3) Update snippets to use \compressMMRests


Issue 3687 (part 2): Amend docs to use \compressMMRests

  Amend the examples in the LM and NR to use the \compressMMRests
  music function rather than the predefs \compressFullBarRests and
  \expandFullBarRests to avoid advocating the use of techniques
  which may have undesirable side effects.

Issue 3687 (part 1): Provide a compress MM function for MM rests only

  Multi-measure rests were previously compressed (i.e. all bars
  following the first were removed) by using the \compressFullBarRests
  predef.  This simply turned on 'skipBars, which causes bar lines at
  the ends of bars which contain either no rhythmic event or contain
  a rhythmic event with a duration extending beyond the bar to be removed.
  Such bars are generated by notes with durations longer than a bar,
  like a1*3, or by shorter notes which extend beyond the bar.

  This patch provides a function which also uses 'skipBars, but with
  a filter so that 'skipBars is activated only when an actual MM rest
  is encountered and deactivated by the first following rhythmic event.

Issue 3687 (part 0): run convert-ly

  Run convert-ly on the doc files to be changed to bring them
  up to date.

http://codereview.appspot.com/232130043

--
You received this message because this project is configured to send all issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings



reply via email to

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