thanks, Werner; I'd call that "inconsistently modern practice" in that
multi-measure rests are written so that one bar is represented by a
semibreve rest, while a single measure rest is represented by a breve
rest.
the example is great as it can be compared to the original: Bach wrote
an MMR of 21 2/2 bars, see page 2, line 4 of
http://ks.petruccimusiclibrary.org/files/imglnks/usimg/0/05/IMSLP102259-PMLP04197-Bach_Bm_Mass_parts_278110185_bass.pdf
(note also that Bach shifts full and half bar-lines at the break
between lines 3 and 4)
in the penultimate line of page 3 (Gratias) there's a breve rest with
number 2: it's a single bar rest in modern terms.

2018-01-10 10:31 GMT+01:00 Werner LEMBERG <[email protected]>:
> I had the opportunity to skip through all BWV 232 parts of Bärenreiter – it
> wasn't successful, since Bach seems to avoid an uneven number of full
> bars... Additionally, they re-typeset everything in 2006, with the
> well-known mediocre typesetting quality from that time...
>
> Nevertheless, I had also access to choir parts, definitely older and
> manually typeset, and attached you can find a page that shows MMRs for 4/2
> beat with an odd number of measures.
>
> ________________________________
>
> [issues:#3208] Wrong MultiMeasureRest glyph
>
> Status: Started
> Created: Wed Feb 27, 2013 03:07 AM UTC by Anonymous
> Last Updated: Tue Jan 09, 2018 09:44 PM UTC
> Owner: Malte Meyn
> Attachments:
>
> mmr-02.png (11.9 kB; image/png)
>
> Originally created by: *anonymous
>
> Originally created by: [email protected]
>
> Thomas Morley reported here:
>
> http://lists.gnu.org/archive/html/bug-lilypond/2013-02/msg00180.html
>
> as follows:
>
> With measures longer than two whole notes LilyPond chooses different
> glyphs for MultiMeasureRest.
>
> \version "2.17.12"
>
> \new Staff {
>   \compressFullBarRests
>
>   \time 7/4
>   R1*7/4
>   R1*7/4*2
>
>   \break
>
>   \time 9/4
>   R1*9/4
>   R1*9/4*2
>   \break
>
>   \time 18/4
>   R1*18/4
>   R1*18/4*2
> }
>
> Discussion on the user-list:
> http://lilypond.1069038.n5.nabble.com/Glyph-for-longer-MultiMeasureRest-td141438.html
>
> 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?"
>
> Regards,
>   Harm
>
> ________________________________
>
> Sent from sourceforge.net because you indicated interest in
> https://sourceforge.net/p/testlilyissues/issues/3208/
>
> To unsubscribe from further messages, please visit
> https://sourceforge.net/auth/subscriptions/


---

** [issues:#3208] Wrong MultiMeasureRest glyph**

**Status:** Started
**Created:** Wed Feb 27, 2013 03:07 AM UTC by Anonymous
**Last Updated:** Tue Jan 09, 2018 09:44 PM UTC
**Owner:** Malte Meyn
**Attachments:**

- 
[mmr-02.png](https://sourceforge.net/p/testlilyissues/issues/3208/attachment/mmr-02.png)
 (11.9 kB; image/png)


*Originally created by:* *anonymous

*Originally created by:* 
[[email protected]](http://code.google.com/u/103174888511674413504/)

Thomas Morley reported here:

[http://lists.gnu.org/archive/html/bug-lilypond/2013-02/msg00180.html](http://lists.gnu.org/archive/html/bug-lilypond/2013-02/msg00180.html)

as follows:

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

~~~~
:::TeX
\version "2.17.12"

\new Staff {
  \compressFullBarRests

  \time 7/4
  R1*7/4
  R1*7/4*2

  \break

  \time 9/4
  R1*9/4
  R1*9/4*2
  \break

  \time 18/4
  R1*18/4
  R1*18/4*2
}
~~~~

Discussion on the user-list:
[http://lilypond.1069038.n5.nabble.com/Glyph-for-longer-MultiMeasureRest-td141438.html](http://lilypond.1069038.n5.nabble.com/Glyph-for-longer-MultiMeasureRest-td141438.html)

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?"


Regards,
  Harm


---

Sent from sourceforge.net because [email protected] is 
subscribed to https://sourceforge.net/p/testlilyissues/issues/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/testlilyissues/admin/issues/options.  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, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Testlilyissues-auto mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
  • [Lilypond-... Auto mailings of changes to Lily Issues via Testlilyissues-auto
  • [Lilypond-... Auto mailings of changes to Lily Issues via Testlilyissues-auto
  • [Lilypond-... Auto mailings of changes to Lily Issues via Testlilyissues-auto
  • [Lilypond-... Auto mailings of changes to Lily Issues via Testlilyissues-auto
  • [Lilypond-... Auto mailings of changes to Lily Issues via Testlilyissues-auto
  • [Lilypond-... Auto mailings of changes to Lily Issues via Testlilyissues-auto
  • [Lilypond-... Auto mailings of changes to Lily Issues via Testlilyissues-auto
  • [Lilypond-... Auto mailings of changes to Lily Issues via Testlilyissues-auto
  • [Lilypond-... Auto mailings of changes to Lily Issues via Testlilyissues-auto
  • [Lilypond-... Auto mailings of changes to Lily Issues via Testlilyissues-auto
  • [Lilypond-... Auto mailings of changes to Lily Issues via Testlilyissues-auto
  • [Lilypond-... Auto mailings of changes to Lily Issues via Testlilyissues-auto
  • [Lilypond-... Auto mailings of changes to Lily Issues via Testlilyissues-auto
  • [Lilypond-... Auto mailings of changes to Lily Issues via Testlilyissues-auto
  • [Lilypond-... Auto mailings of changes to Lily Issues via Testlilyissues-auto
  • [Lilypond-... Auto mailings of changes to Lily Issues via Testlilyissues-auto
  • [Lilypond-... Auto mailings of changes to Lily Issues via Testlilyissues-auto
  • [Lilypond-... Auto mailings of changes to Lily Issues via Testlilyissues-auto

Reply via email to