Re: Multi Measure Rests in Cadenzas

Hallo Calvin, (First time posting here - I hope this works!) I've found the following (based on https://lsr.di.unimi.it/LSR/Snippet?id=836) works well in this sort of situation. The function `cadenzatoMetre` takes two music expressions as arguments. The first denotes the rhythmic "frame"

Re: Multi Measure Rests in Cadenzas

Hello Calvin, MM rests and cadenzas do not play well together. The reason for this is that the MM is placed centered between start and end of measure. But \cadenzaOn is not really made for creating arbitrary length measures. What is does is simply telling Lilypond to stop counting. So when you

Re: Multi-measure rests with alternating time signatures

> On 21 Nov 2020, at 16:14, Kieren MacMillan > wrote: > > I don’t think that solves the OP’s problem, as I understand it to be… I think > the OP wants a compressed visual representation of a whole bunch of 4/4+3/4 > two-measure chunks, without actually seeing them written out. I think the

Re: Multi-measure rests with alternating time signatures

And to make it more challenging, measure numbers should be correct afterwards, too... A tagged measure attached spanner would be a workaround I guess, if there’s an easy way to hide (but count) the remaining but unnecessary measures. Thanks to you all, Max __

Re: Multi-measure rests with alternating time signatures

Precisely! :) > On Nov 21, 2020, at 16:16, Kieren MacMillan > wrote: > > I think the OP wants a compressed visual representation of a whole bunch of > 4/4+3/4 two-measure chunks, without actually seeing them written out.

Re: Multi-measure rests with alternating time signatures

> Compound meter, perhaps? p.s. Gould explicitly notes that compound meter and strictly alternating meter are two distinct things. :) Best, Kieren. Kieren MacMillan, composer (he/him/his) ‣ website: www.kierenmacmillan.info ‣ email: kie...@kierenmacmillan.info

Re: Multi-measure rests with alternating time signatures

Hi Tim, > As far as I can tell from looking at the docs, the only way to do this using > multi-measure rests will be in 7/4. It will count out the same, assuming the > right number of measures is chosen. Yes… That’s why I suggested a measure-attached "x" spanner. (n.b. Gould doesn’t

Re: Multi-measure rests with alternating time signatures

Hi Aaron, > Compound meter, perhaps? I don’t know whether the OP is willing to use compound meter…? Let’s wait to hear OP’s response. Thanks! Kieren. Kieren MacMillan, composer (he/him/his) ‣ website: www.kierenmacmillan.info ‣ email:

Re: Multi-measure rests with alternating time signatures

> On Nov 21, 2020, at 9:14 AM, Kieren MacMillan > wrote: > > I don’t think that solves the OP’s problem, as I understand it to be… I think > the OP wants a compressed visual representation of a whole bunch of 4/4+3/4 > two-measure chunks, without actually seeing them written out. As far

Re: Multi-measure rests with alternating time signatures

On 2020-11-21 7:14 am, Kieren MacMillan wrote: Hi Phil, I don’t think that solves the OP’s problem, as I understand it to be… I think the OP wants a compressed visual representation of a whole bunch of 4/4+3/4 two-measure chunks, without actually seeing them written out. Of course, I might be

Re: Multi-measure rests with alternating time signatures

Hi Phil, I don’t think that solves the OP’s problem, as I understand it to be… I think the OP wants a compressed visual representation of a whole bunch of 4/4+3/4 two-measure chunks, without actually seeing them written out. Of course, I might be wrong! =) Best, Kieren.

Re: Multi-measure rests with alternating time signatures

> On 20 Nov 2020, at 14:01, Maximilian Marcoll wrote: > > I’m wondering wether there is a convenient solution for the following > situation: > > Imagine an ensemble or orchestra piece has alternating time signatures, for > instance repeated 4/4 | 3/4 time signature changes. > Not multiple

Re: Multi-measure rests with alternating time signatures

Here's an alternative semi-automatic way (proof of concept): \new Score { << \new Staff {   \time 3/4 c''2. \time 4/4 c''1 \time 3/4 c''2. } \new Staff {   \new Voice \with {     \remove "Rest_engraver"     \consists "Completion_rest_engraver"   }   {R1*10/4} } >> } On 20/11/2020 15:45,

Re: Multi-measure rests with alternating time signatures

Fantastic! Thank you! __ http://www.marcoll.de subscribe to newsletter > On 20 Nov 2020, at 15:30, Kieren MacMillan > wrote: > > Hi Max, > >> Sure, that would be great. But how would that be possible with the same >> music-content also

Re: Multi-measure rests with alternating time signatures

Hi! Thank you for your response. Sure, that would be great. But how would that be possible with the same music-content also being used for the full score? Cheers, Max __ http://www.marcoll.de http://www.stock11.de > On Nov 20, 2020, at 15:12, Kieren MacMillan

Re: Multi-measure rests with alternating time signatures

Hi Max, > Sure, that would be great. But how would that be possible with the same > music-content also being used for the full score? Tags. =) Hope that helps! Kieren. Kieren MacMillan, composer (he/him/his) ‣ website: www.kierenmacmillan.info ‣ email:

Re: Multi-measure rests with alternating time signatures

Hi Max, > If for some instruments these measures only contain rests, could this somehow > be expressed with multi-measure rests? What about a measure of 4/4 and a measure of 3/4 with a spanner over it saying “12x” (or whatever)? Hope that helps! Kieren.

Re: Multi-measure rests and mark collisions ...

On Tue 26 Apr 2016 at 01:21:00 (+0100), Wols Lists wrote: > On 25/04/16 05:31, David Wright wrote: > > But I see you've now acknowledged (indirectly) that LP can set > > multiple marks at the same point after stating that it can't. > > Are there other things that LP can be persuaded to do itself

Re: Multi-measure rests and mark collisions ...

On Thu 28 Apr 2016 at 13:56:03 (+0100), Anthonys Lists wrote: > On 27/04/2016 01:04, Carl Sorensen wrote: > >On 4/26/16 3:56 PM, "Thomas Morley" wrote: > > > >>2016-04-26 2:21 GMT+02:00 Wols Lists : > >>>On 25/04/16 05:31, David Wright wrote: >

Re: Multi-measure rests and mark collisions ...

On 27/04/2016 01:04, Carl Sorensen wrote: On 4/26/16 3:56 PM, "Thomas Morley" wrote: 2016-04-26 2:21 GMT+02:00 Wols Lists : On 25/04/16 05:31, David Wright wrote: (I still don't know what you're trying to accomplish [...]) The problem

Re: Multi-measure rests and mark collisions ...

On 4/26/16 3:56 PM, "Thomas Morley" wrote: >2016-04-26 2:21 GMT+02:00 Wols Lists : >> On 25/04/16 05:31, David Wright wrote: >>> (I still don't know what you're trying to accomplish >>> [...]) >>> >> Copy "House Style", maybe? >> And the whole

Re: Multi-measure rests and mark collisions ...

2016-04-26 2:21 GMT+02:00 Wols Lists : > On 25/04/16 05:31, David Wright wrote: >> (I still don't know what you're trying to accomplish >> [...]) >> > Copy "House Style", maybe? > And the whole point of this entire thread has been about > SAVING VERTICAL SPACE - it's just

Re: Multi-measure rests and mark collisions ...

On 25/04/16 05:31, David Wright wrote: > On Sun 24 Apr 2016 at 19:18:01 (+0100), Anthonys Lists wrote: >> On 24/04/2016 03:13, David Wright wrote: >> >> Ah - does that mean the rehearsal mark would happily overwrite the >> blank space at the start of the other markup string? > > Typically, yes.

Re: Multi-measure rests and mark collisions ...

On Sun 24 Apr 2016 at 19:18:01 (+0100), Anthonys Lists wrote: > On 24/04/2016 03:13, David Wright wrote: > >On Sat 23 Apr 2016 at 11:25:05 (+0100), Wols Lists wrote: > >>On 22/04/16 19:36, David Wright wrote: > >>>On Fri 22 Apr 2016 at 15:47:59 (+0100), Anthonys Lists wrote: > On 22/04/2016

Re: Multi-measure rests and mark collisions ...

On 24/04/2016 03:13, David Wright wrote: On Sat 23 Apr 2016 at 11:25:05 (+0100), Wols Lists wrote: On 22/04/16 19:36, David Wright wrote: On Fri 22 Apr 2016 at 15:47:59 (+0100), Anthonys Lists wrote: On 22/04/2016 14:31, Kieren MacMillan wrote: David K wrote: Hm? How could you even have a

Re: Multi-measure rests and mark collisions ...

On Sat 23 Apr 2016 at 11:25:05 (+0100), Wols Lists wrote: > On 22/04/16 19:36, David Wright wrote: > > On Fri 22 Apr 2016 at 15:47:59 (+0100), Anthonys Lists wrote: > >> On 22/04/2016 14:31, Kieren MacMillan wrote: > >>> David K wrote: > > Hm? How could you even have a compressed

Re: Multi-measure rests and mark collisions ...

On 23/04/2016 12:23, Kieren MacMillan wrote: Hi Wol, if I use "extra-spacing-width" (which iirc works fine with multi-measure-rests), as soon as I have another part which actually has some notes in the first bar of the MMR, that first bar will be the same width as the markup so that then looks

Re: Multi-measure rests and mark collisions ...

Hi Wol, > if I use "extra-spacing-width" (which iirc works fine with > multi-measure-rests), as soon as I have another part which actually has > some notes in the first bar of the MMR, that first bar will be the same > width as the markup so that then looks awful \textLengthOff ? Hope this

Re: Multi-measure rests and mark collisions

On 23/04/16 01:52, Kieren MacMillan wrote: > Hi David, > >> It strikes me as conceptually problematic to try to put a fermata on a >> multi-measure rest. >> Who does this, and what does it mean, musically? >> In this example, you are actually placing a fermata on a single bar of rest. >> In

Re: Multi-measure rests and mark collisions ...

On 22/04/16 19:36, David Wright wrote: > On Fri 22 Apr 2016 at 15:47:59 (+0100), Anthonys Lists wrote: >> On 22/04/2016 14:31, Kieren MacMillan wrote: >>> David K wrote: > Hm? How could you even have a compressed multi-measure rest when there > is anything like an "8-bar phrase" in

Re: Multi-measure rests and mark collisions

On 23.04.2016 02:06, Flaming Hakama by Elaine wrote: It strikes me as conceptually problematic to try to put a fermata on a multi-measure rest. Who does this, and what does it mean, musically? You must be kidding. While calling R1 a MultiMeasureRest may be slightly confusing in LilyPond

Re: Multi-measure rests and mark collisions

Hi David, > It strikes me as conceptually problematic to try to put a fermata on a > multi-measure rest. > Who does this, and what does it mean, musically? > In this example, you are actually placing a fermata on a single bar of rest. > In which case, this works fine: > { \compressFullBarRests

Re: Multi-measure rests and mark collisions

> Try the following ... > > f1->\fermata R1*3 R1\fermata > > The first fermata prints fine. The second fermata prints > "programming error: Object is not a markup." in the log and doesn't > print. It strikes me as conceptually problematic to try to put a fermata on a multi-measure rest. Who does

Re: Multi-measure rests and mark collisions ...

On Fri 22 Apr 2016 at 15:47:59 (+0100), Anthonys Lists wrote: > On 22/04/2016 14:31, Kieren MacMillan wrote: > >David K wrote: > >>>Hm? How could you even have a compressed multi-measure rest when there > >>>is anything like an "8-bar phrase" in parallel? > >>>That sounds like a problem that

Re: Multi-measure rests and mark collisions ...

On 22/04/2016 16:55, David Kastrup wrote: >The first fermata prints fine. The second fermata prints "programming >error: Object is not a markup." in the log and doesn't print. So >that's another bug tracked down in my piece, That's_explicitly_ what \fermataMarkup is for. If people consulted

Re: Multi-measure rests and mark collisions ...

Hi, > f1->\fermata R1*3 R1\fermata You can use \fermataMarkup { R1\fermataMarkup } I know it looks more like a workaround than something one would expect, but it works. Cheers, Joram ___ lilypond-user mailing list lilypond-user@gnu.org

Re: Multi-measure rests and mark collisions ...

On Fri 22 Apr 2016 at 16:24:06 (+0100), Anthonys Lists wrote: > On 22/04/2016 14:49, Paul Scott wrote: > >>I assume Wol (like me) has the problem where the compressed rest happens > >>>in the part, not in the full score — but one wants not to have to use > >>>multiple \tag constructs just to

Re: Multi-measure rests and mark collisions ...

Anthonys Lists writes: > On 22/04/2016 14:49, Paul Scott wrote: >>> I assume Wol (like me) has the problem where the compressed rest happens >>> >in the part, not in the full score — but one wants not to have to use >>> >multiple \tag constructs just to handle this

Re: Multi-measure rests and mark collisions ...

On 22/04/2016 14:49, Paul Scott wrote: I assume Wol (like me) has the problem where the compressed rest happens >in the part, not in the full score — but one wants not to have to use >multiple \tag constructs just to handle this issue. Me too. I asked a long time ago and got the idea that I

Re: Multi-measure rests and mark collisions ...

On 22/04/2016 14:31, Kieren MacMillan wrote: Wol: Scan through the thread starting at and see if anything there helps. Good luck, Kieren. Just scanned it - unfortunately I'm using \markup on an s, rather than \mark, for

Re: Multi-measure rests and mark collisions ...

On 22/04/2016 14:31, Kieren MacMillan wrote: David K wrote: >Hm? How could you even have a compressed multi-measure rest when there >is anything like an "8-bar phrase" in parallel? >That sounds like a problem that cannot occur. I assume Wol (like me) has the problem where the compressed rest

Re: Multi-measure rests and mark collisions ...

On Fri, Apr 22, 2016 at 09:31:17AM -0400, Kieren MacMillan wrote: > Hi Wol, > > > My usual bugbear ... :-( > > I have a couple of instances where I have a rehearsal mark, a tempo mark, > > […] > > Yeah… this causes me no end of grief, too. > It probably represents a good 10% of my score/part

Re: Multi-measure rests and mark collisions ...

Hi Wol, > My usual bugbear ... :-( > I have a couple of instances where I have a rehearsal mark, a tempo mark, […] Yeah… this causes me no end of grief, too. It probably represents a good 10% of my score/part tweaking time. David K wrote: > Hm? How could you even have a compressed

Re: Multi-measure rests and mark collisions ...

Anthonys Lists writes: > My usual bugbear ... :-( > > I have a couple of instances where I have a rehearsal mark, a tempo > mark, and a tune name all wanting to be over the same barline (this is > an arrangement, where there are several tunes and each is identified >

Re: multi measure rests

- Original Message - From: Sarah k Alawami marri...@gmail.com To: lilly pond discuss discuss lilypond-user@gnu.org Sent: Friday, May 3, 2013 4:13:44 PM Subject: multi measure rests I read the docs on how to do this but is there an easier way to memorize how to do this? the fractions

Re: multi measure rests

Am 03.05.2013 18:13, schrieb Sarah k Alawami: I read the docs on how to do this but is there an easier way to memorize how to do this? the fractions confuse the heck out of me lol! I'm in 12/8 so I'll have 4 doted quarter notes so would the multi measure rest look like this for one

Re: multi measure rests

Ok. I see there a dotted hole note, but a dotted whole note or in this case whole rest is only 8 eithgh notes if I counted correctly which my coffee deprived brain probably did not lol! I get the feeling that i'm making this harder then it really is. lol! Take care all and thanks. On May 3,

Re: multi measure rests

Am 03.05.2013 18:44, schrieb Sarah k Alawami: Ok. I see there a dotted hole note, but a dotted whole note or in this case whole rest is only 8 eithgh notes if I counted correctly which my coffee deprived brain probably did not lol! I get the feeling that i'm making this harder then it

Re: multi measure rests

A MultiMeasureRest for one measure always _looks_ like a whole note rest, no matter how long its real duration is. Maybe it's this what you mix up? Best Urs Sarah k Alawami marri...@gmail.com schrieb: Ok. I see there a dotted hole note, but a dotted whole note or in this case whole rest is

Re: multi measure rests

I remember and use it this way: R length times so many so: R1*3 is three times the length of one whole note. Always calculate the total length you need and that it gets there. I tried simply this: Assume you want 4/4 followed by 3/4 and three full measures rest in each: { \time

Re: multi measure rests

Possibally. Like I said I'm so new to lily pound and I'm trying to read the docs as best I could but sometimes the explanations are just a tad unclear. lol! and I'm trying to do my final assignment from a transcription in braille gone wrong. lol! Take care. On May 3, 2013, at 9:58 AM, Urs

Re: multi measure rests

Hi, I also have a question for you: You seem to use braille music output from LilyPond. Is that builtin in LilyPond? Could you (or anyone) point me to some documentation how to use that? I would like to try it. Cheers, Joram ___ lilypond-user mailing

Re: Re: multi measure rests

On 05/03/2013 03:11 PM, Wim van Dommelen wrote: I remember and use it this way: R length times so many so: R1*3 is three times the length of one whole note. Always calculate the total length you need and that it gets there. FWIW, the general form of what I do is R1*time

Re: multi measure rests

Actually I'm not. The university brailled my piano transcript Im working off of. It would be nice though if maybe a musk student could learn lily pond and output it in to braille so all of my stuff could be done in house. using music vml or some such thing. Take care. On May 3, 2013, at 2:30

Re: Multi measure rests vertical positioning

Hi Werner, I must solve everything for R manually while r works fine. Any ideas to solve that? Can you write a callback function to determine the position of the r and apply it to the R? Just a thought. Kieren. ___ lilypond-user mailing list

Re: Multi-measure rests and counter in piano staff

2012/10/19 David Nalesnik david.nales...@gmail.com to comment #21 at http://code.google.com/p/lilypond/issues/detail?id=2445 . Understand that this version might cause problems if you're running a batch of files (which won't happen with the version that's in the review process.) The

Re: Multi-measure rests and counter in piano staff

Am 21.10.2012 15:51, schrieb Helge Kruse: [...] This measure counter allows a start and a stop. I did not find an option to start at a specific number. Image you start at rehearsel mark H, have a multi-measure rest of 16 bars. In the 17th measure you have some cue notes. It would be nice to

Re: Multi-measure rests and counter in piano staff

Do you have any idea how to combine the two multi-rest bar counts in a piano staff? Helge 2012/10/17 Helge Kruse helge.kr...@gmx.net When playing in an orchestra it's important to count rests. To make this tasks easier you can write numbers into rest measures. Especially for a piano staff

Re: Multi-Measure Rests: Adding to what gets printed?

Alexander, I don't have time to look into this, but wanted you to be aware: I went ahead and used the BarNumberStaff rather than the BarNumberVoice. In trying to adjust the Y-Offset of the BarNumberVoice, it moves the lyrics down as well. The BarNumberStaff does not. \new

Re: Multi-Measure Rests: Adding to what gets printed?

rasAK wrote: I don't have time to look into this, but wanted you to be aware: I went ahead and used the BarNumberStaff rather than the BarNumberVoice. In trying to adjust the Y-Offset of the BarNumberVoice, it moves the lyrics down as well. The BarNumberStaff does not. Ah, I think I see the

Re: Multi-Measure Rests: Adding to what gets printed?

Alexander, Yes, I've got what I need for now, so no rush on the fix. Whenever you do get to it, let me know and I'll be happy to test. Randy Alexander Kobel wrote: rasAK wrote: I don't have time to look into this, but wanted you to be aware: I went ahead and used the BarNumberStaff

Re: Multi-Measure Rests: Adding to what gets printed?

Alexander, One other thing. Your code does solve the additional wrinkle I referred to. In the attached, at letter I, you will see that a 20 MMR is broken up by Rehearsal Letter I and your function calcs the 2 contiguous MMR ranges correctly and attaches them. Randy

Re: Multi-Measure Rests: Adding to what gets printed?

rasAK wrote: Alexander, The only remaining issue is the positioning of the text that results from your function. It is currently being placed above the number (which is above the MMR). I tried to adjust some of the Y-offset and Y-extent numbers, but could only get the text to move up. I

Re: Multi-Measure Rests: Adding to what gets printed?

me - stanford wrote: 2) Also, do you think #'outside-staff-priority = #150 is a reasonable priority setting for the MMR Text? I'm not sure what most objects' settings are for this property. I was just trying to get it to win over the Lyrics setting. Oh, and just a few words about this

Re: Multi-Measure Rests: Adding to what gets printed?

Alexander, I've modified the BarNumberStaff code as you suggested. I also changed one line in your \layout block. I commented out the Mark_engraver as I was getting double boxed rehearsal letters: %\consists Mark_engraver The only remaining issue is the positioning of the text that

Re: Multi-Measure Rests: Adding to what gets printed?

rasAK wrote: In my orchestral parts, I would like Multi-Measure Rests to have both: (1) an integer representing the number of measures in the current MMR, centered above (default behavior) (2) a second text indicating which measures are included in the given MMR, in parentheses and centered

Re: Multi-Measure Rests: Adding to what gets printed?

Alexander, Thanks so much. I'll take a look at your suggestion in detail. Randy rasAK wrote: In my orchestral parts, I would like Multi-Measure Rests to have both: (1) an integer representing the number of measures in the current MMR, centered above (default behavior) (2) a second

Re: Multi-measure rests again again

[EMAIL PROTECTED] writes: Han-Wen Nienhuys wrote: Added this to the doco: If you want to have a text on the left end of a multi-measure rest, attach the text to a zero-length skip note, i.e. @example s1*0^Allegro R1*4 @end example This makes the multimeasure excessively wide

Re: Multi-measure rests again again

Han-Wen Nienhuys wrote: [EMAIL PROTECTED] writes: This makes the multimeasure excessively wide and actually steals space from a following MM rest. Ah, that seems to be a bug. I fixed it partially in 2.0 CVS. For the moment, you might want to put the allegro atop the 72 \mark. Excellent!

Re: Multi-measure rests again again

Ralph Little wrote: Hi Looking through the archives, there seems to be a lot of issues relating to attaching text markup to MultiMeasure rests. One general solutions seems to be along the lines of R1*10 s1^Hello there ...or somesuch. I'm running 1.8.2 now. What's the recommended way of

Re: Multi-measure rests again again

[EMAIL PROTECTED] writes: Ralph Little wrote: Hi Looking through the archives, there seems to be a lot of issues relating to attaching text markup to MultiMeasure rests. One general solutions seems to be along the lines of R1*10 s1^Hello there ...or somesuch. I'm running

RE: Multi-measure rests again again

Hi, This is exactly the issue that I am having! Same goes for: R1*2_\markup{ Allegro } ..I guess. Regards, Ralph -Original Message- From: Paul Scott [mailto:[EMAIL PROTECTED] Sent: 23 September 2003 10:09 To: Ralph Little Cc: [EMAIL PROTECTED] Subject: Re: Multi-measure rests

RE: Multi-measure rests again again

That's funky! Thanks, I'll give it a try! Ralph -Original Message- From: Han-Wen Nienhuys [mailto:[EMAIL PROTECTED] Sent: 23 September 2003 10:28 To: [EMAIL PROTECTED] Cc: Ralph Little; [EMAIL PROTECTED] Subject: Re: Multi-measure rests again again [EMAIL PROTECTED] writes: Ralph

Re: Multi-measure rests again again

Han-Wen Nienhuys wrote: Added this to the doco: If you want to have a text on the left end of a multi-measure rest, attach the text to a zero-length skip note, i.e. @example s1*0^Allegro R1*4 @end example This makes the multimeasure excessively wide and actually steals space from a

Re: Multi-measure rests again again

Paul Scott wrote: (Lily 1.8.1 on Debian unstable) This makes the multimeasure excessively wide and actually steals space from a following MM rest. Paul \score { \property Score.skipBars = ##t \context Staff =

Re: multi-measure rests

The bad news: you have hit a bug, Lilypond doesn't understand that the multi-measure rests need a certain minimal width. The good news: as soon as you add a couple of more bars of music, Lilypond will break the music into several lines and you won't suffer from the problem any more.

Re: multi measure rests

The only problem with your attempt it that you changed the padding of text scripts, but not of the multi-measure rests or rehearsal marks that you wanted to affect. Try \property Staff.MultiMeasureRest \override #'padding = #3 or \property Staff.MultiMeasureRest \override #'padding = #3