On Sun, Nov 14, 2021 at 4:10 AM Jacques Menu wrote:
>
> Hello folks,
>
> I’m at a loss regarding that : \compressMMRests, compressEmptyMeasures are
> present in LPNR 2.23, but Frescobaldi 3.1.3 knows only \compressFullBarRests.
You can use \compressMMRests in Frescobaldi withou
-visibility = ##(#f #t #t)
R1*2 R1*3 b\longa c'1*3 s1*2
\bar "||"
}
{ \compressMMRests \m \m }
{ \compressEmptyMeasures \m \expandEmptyMeasures \m }
\compressFullBarRests is no longer valid syntax in recent versions.
There's a third variety than expresses more clearly how
2 R1*3 b\longa c'1*3 s1*2
> \bar "||"
> }
>
> { \compressMMRests \m \m }
> { \compressEmptyMeasures \m \expandEmptyMeasures \m }
>
> \compressFullBarRests is no longer valid syntax in recent versions.
>
> Cheers,
> Harm
signature.asc
Description: This is a digitally signed message part.
longer sequential music. It is _limited_ to MMRs.
\compressEmptyMeasures compresses MMRs and other long durations until reverted:
m = {
\override Score.BarNumber.break-visibility = ##(#f #t #t)
R1*2 R1*3 b\longa c'1*3 s1*2
\bar "||"
}
{ \compressMMRests \m \m }
{ \compressEmptyMea
Hello Jacques,
Frescobaldi does not always know the latest Lilypond language. As far as I see
\compressMMRests and \comressEmptyMeasures do the same, but
\compressEmptyMeasures works like a toggle that needs to be unset by
\expandEmptyMeasures (it’s basically just a shorthand for \set Score.ski
Hello folks,
I’m at a loss regarding that : \compressMMRests, compressEmptyMeasures are
present in LPNR 2.23, but Frescobaldi 3.1.3 knows only \compressFullBarRests.
I remember there’s been a name change at some point in time.
Sp which command should one use?
Thanks for your help!
JM
t click on a rest wherever I want
>>> and Frescobaldi takes me right to the line of code (I write one full
>>> measure rest per line) and I just change the corresponding rests with
>>> music. This has the great advantage that I don't have to count anything. I
>>&
sure
>> rest per line) and I just change the corresponding rests with music. This
>> has the great advantage that I don't have to count anything. I just click
>> where I want the music to be and replace silences with music (much like in
>> Sibelius or Musescore). Howeve
Musescore). However, the pending task will be at the end of
> composing to clean all these repeated full bar rests and write the explicit
> multiplications (R1*5, etc.), so that \compressFullBarRests works in the
> parts. This makes me wonder if it's possible to "force" Lilypond to always
ace silences with music (much like in
Sibelius or Musescore). However, the pending task will be at the end of
composing to clean all these repeated full bar rests and write the explicit
multiplications (R1*5, etc.), so that \compressFullBarRests works in the
parts. This makes me wonder if it'
have a look to the picture in annex.
>>>> Left is what is engraved using :
>>>>
>>>> \compressFullBarRests
>>>>
>>>> R1*4
>>>>
>>>> Right is a scan of a part of a score sheet showing the same 4 full rests.
>>&
Nick Alderweireldt writes:
> This is my first day lilypond-frescobaldi. I am really impressed by
> the features.
>
> Please have a look to the picture in annex.
> Left is what is engraved using :
>
> \compressFullBarRests
>
> R1*4
>
> Right is a scan of a part of
At 09:59 on 31 Jul 2014, Nick Alderweireldt wrote:
>This is my first day lilypond-frescobaldi. I am really impressed by
>the features.
>
>Please have a look to the picture in annex.
>Left is what is engraved using :
>
>\compressFullBarRests
>
>R1*4
>
>Right is
Please see http://lsr.di.unimi.it/LSR/Item?id=570
--
Phil Holmes
- Original Message -
From: Nick Alderweireldt
To: lilypond-user@gnu.org
Sent: Thursday, July 31, 2014 8:59 AM
Subject: compressFullBarRests question (see picture in annex)
This is my first day lilypond
This is my first day lilypond-frescobaldi. I am really impressed by the
features.
Please have a look to the picture in annex.
Left is what is engraved using :
\compressFullBarRests
R1*4
Right is a scan of a part of a score sheet showing the same 4 full rests.
The bar with 4 above is longer
Hi Jay,
> Some minor changes would be needed if a break is needed
> mid-measure (something like \lineBreakAt 27 3/4).
Yes. As I understand it, some less minor changes would be needed for that, too:
currently (AFAIK), Lily won’t break mid-measure without an explicit \bar “”.
> I think I'd still
On Fri, Dec 27, 2013 at 4:08 PM, Kieren MacMillan
wrote:
> I think the “perfect” break-engraver would admit coding like the following
> (pseudocode; all numbers in measures):
>
> \lineBreakAt 27
> \lineBreaksAt (12 28 34 48)
> \noLineBreaks (27-30)
> \lineBreaksForbidAt 28
> \
Further to this thread…
> I just think it — or something like it — should be vetted and [the
> improved/approved version] included with the regular distro.
I think the “perfect” break-engraver would admit coding like the following
(pseudocode; all numbers in measures):
\lineBreakAt 27
Hi David,
> A content-independent line- and page-breaking system is easy.
> The content is what makes it complicated…
Ah, the semantics cop is on the beat. ;)
Let me put it another way: Using David’s engraver (which he graciously sent me
off-list), I am happily adding manual breaks EXTERNAL TO
Kieren MacMillan writes:
> Hi all,
>
>> How would it behave if \draftSkip were, instead of being changed,
> tagged, and you ran lilypond with exclude-tag #draft? (I can't
> remember the syntax off the top of my head, but I think that's
> reasonably close.)
>
> It would be fine… but it’s still a b
Hi all,
> How would it behave if \draftSkip were, instead of being changed, tagged, and
> you ran lilypond with exclude-tag #draft? (I can't remember the syntax off
> the top of my head, but I think that's reasonably close.)
It would be fine… but it’s still a band-aid (um, Band-Aid™) solution.
How would it behave if \draftSkip were, instead of being changed, tagged, and
you ran lilypond with exclude-tag #draft? (I can't remember the syntax off the
top of my head, but I think that's reasonably close.)
On Dec 27, 2013, at 1:38 AM, "Keith OHara" wrote:
> On Thu, 26 Dec 2013 18:44:56
On Thu, 26 Dec 2013 18:44:56 -0800, Kieren MacMillan
wrote:
I look forward to stress-testing this in the very near future.
One missing feature is that \mergeSkips doesn't look inside {...} to see if
they are empty. I often set breaks for proofreading and then remove them by
defining them
Hi Keith,
(Sorry for the delay in responding: ice storm + holidays = crazy times.)
YES! This works wonderfully.
I look forward to stress-testing this in the very near future.
Thank you,
Kieren.
On Dec 22, 2013, at 4:35 PM, Keith OHara wrote:
> Let's try it out, then, using music functions.
_
imately you're supporting my argument/request: If one writes R1*48
in a part, one should see a 48-measure MMRs in the output. =)
Ah, I misunderstood the issue. Indeed:
\new Voice <<
{ s1*2 s1*2 }
{ \compressFullBarRests R1*4 }
>>
hjh
music functions. I think that merging
skips after filtering out any irrelevant changes is good to do by default,
but we should only merge { R1*7 R1*8 } if explicitly asked.
music = \context Staff <<
\compressFullBarRests
{s1*10 \tag#'score \break s1*10}
{R1*
Hi David,
> >> I don't understand why, if you want a four measure rest you would
> >> write 2+2. For the vast majority of cases, if there are 48 bars
> >> between two rehearsal marks I'm happy to see |=48=| between them.
> >> So, why write anything but R1*48 in the part in question?
You can write
That could be a useful feature but should not me the default. Perhaps an
override such as
\override MultimeasureRest #'condense-all = ##t
would be helpful. That way the default would still be the intuitive way (2+2
gives two separate groups) whereas the other is still an option for those who
w
> I think one of the things that bothers me about this thread is that
> I don't understand why, if you want a four measure rest you would
> write 2+2. For the vast majority of cases, if there are 48 bars
> between two rehearsal marks I'm happy to see |=48=| between them.
> So, why write anything
- Original Message -
From: "Werner LEMBERG"
To: bobr...@centrum.is
Cc: lilypond-user@gnu.org
Sent: Sunday, December 22, 2013 9:53:36 AM
Subject: Re: [Feature Request] \compressFullBarRests improvement(s)
> I would like to echo Simon's concern as well. Furthermore,
> I would like to echo Simon's concern as well. Furthermore, I don't
> see why:
>
> R1*2 R1*2
>
> ...producing two multimeasure rests of two measures duration is
> troublesome.
It is a fundamental problem of separating contents from layout. In
many cases it is of great importance to structure
- Original Message -
From: "Simon Bailey"
To: "Werner LEMBERG"
Cc: jamshar...@gmail.com, lilypond-user@gnu.org
Sent: Sunday, December 22, 2013 9:07:11 AM
Subject: Re: [Feature Request] \compressFullBarRests improvement(s)
On 22 Dec 2013, at 06:56, Werner LEMBE
>> I also support this request. Another reason is that in many parts
>> of percussion instruments, say, there is `tacet' for a very long
>> time, e.g. from rehearsal number 20 to 76. A potential new
>> implementation of \compressFullBarRests (or a variant as sug
On Sunday, December 22, 2013 5:07:11 PM HKT, Simon Bailey wrote:
I also support this request. Another reason is that in many parts of
percussion instruments, say, there is `tacet' for a very long time,
e.g. from rehearsal number 20 to 76. A potential new implementation
of \compressFullBar
On 22 Dec 2013, at 06:56, Werner LEMBERG wrote:
> I also support this request. Another reason is that in many parts of
> percussion instruments, say, there is `tacet' for a very long time,
> e.g. from rehearsal number 20 to 76. A potential new implementation
> of \compressF
>> Here’s my request: I would love it if \compressFullBarRests actually did
>> what it says it does… ;)
>
> FWIW, I agree with Kieren. If I saw a part with some multimeasure
> rests broken for no obvious reason, e.g.
>
> { \compressFullBarRests \mark \default R1
com> writes:
>
> > FWIW, I agree with Kieren. If I saw a part with some multimeasure rests
> > broken for no obvious reason, e.g.
> >
> > { \compressFullBarRests \mark \default R1*2 R1*2 \mark \default R1*2 }
> >
> > I would think the publisher was insane or
James Harkins gmail.com> writes:
> FWIW, I agree with Kieren. If I saw a part with some multimeasure rests
> broken for no obvious reason, e.g.
>
> { \compressFullBarRests \mark \default R1*2 R1*2 \mark \default R1*2 }
>
> I would think the publisher was insane or incom
Kieren MacMillan sympatico.ca> writes:
> Hello all,
>
> Consider this snippet:
>
> \version "2.17.97"
>
> theMusic = {
> \compressFullBarRests
> R1*2
> R1*2
> }
>
> \score {
> \theMusic
> }
>
> Here’s my request: I wou
e?
i.e., Make \compressFullBarRests work as expected [to me, anyway :)], and have
a command like \splitMMR to force a split where desired.
An implementation like that would allow “surgical” splits (e.g., within a
single part) as well as “global” splits, while the “improved”
\compressFullBarRests would solve [all?]
Kieren MacMillan writes:
> Hi David,
>
>> Well, you would not count. Instead you'd say something like
>>
>> \R-until \atMark 8
>> or
>> \R-until \atmeasure 80
>
> Ah! I could see that being a *very* elegant solution for that problem.
>
> However, if one suddenly added, post-hoc, a “split point”
Hi David,
> Well, you would not count. Instead you'd say something like
>
> \R-until \atMark 8
> or
> \R-until \atmeasure 80
Ah! I could see that being a *very* elegant solution for that problem.
However, if one suddenly added, post-hoc, a “split point” in the [shared]
global music, would it
Kieren MacMillan writes:
> Hi David,
>
>> I have quite a few orchestra parts where multimeasure rest streaks of
>> several lengths are _not_ conflated. Basically, each such rest stands
>> for a recognizable unit.
>
> I’ll look at Gould to see what her recommendations are.
>
> In any case, whethe
a three-measure MMR):
>
> \version "2.17.97"
>
> theGlobal = {
> \compressFullBarRests
> s1
> s1-\tag #'(foo) -\markup "Foo only"
> s1
> }
>
> theMusic = {
> R1*3
> }
>
> \score {
> \new Staff \keepWithTag #'(fo
Hi David,
> I have quite a few orchestra parts where multimeasure rest streaks of
> several lengths are _not_ conflated. Basically, each such rest stands
> for a recognizable unit.
I’ll look at Gould to see what her recommendations are.
In any case, whether or not a best practice is known, the
ident in the following
snippet (where the second score should contain a three-measure MMR):
\version "2.17.97"
theGlobal = {
\compressFullBarRests
s1
s1-\tag #'(foo) -\markup "Foo only"
s1
}
theMusic = {
R1*3
}
\score {
\new Staff \keepWithTag #'(foo)
Kieren MacMillan writes:
> Having just engraved nearly 25 minutes of music resulting in 57
> different individual parts, I can tell you that this issue inspired
> quite a bit of reduced efficiency, increased hackery, and even some
> loud swearing. =)
>
> Thoughts?
I have quite a few orchestra p
Two separate ones. As an orchestral performer those breaks are often used
to signify the beginnings of sections to make counting easier, so if I'm
resting and there are 8 bars of one theme followed by 8 of another, I find
it much easier to keep my place when it's 8 and 8 instead of 16.
Alex
On S
Hi Alex,
> I don't see what's wrong with the output, that's exactly what I would expect
> it to be.
Does your output show a single four-measure MMR (which I would both want and
expect it to be), or two two-measure MMRs (which is undesirable, primarily
because it's distracting to the performer)
I don't see what's wrong with the output, that's exactly what I would
expect it to be.
On Sat, Dec 21, 2013 at 4:09 PM, Kieren MacMillan <
kieren_macmil...@sympatico.ca> wrote:
> Hello all,
>
> Consider this snippet:
>
> \version "2.17.97"
>
Hello all,
Consider this snippet:
\version "2.17.97"
theMusic = {
\compressFullBarRests
R1*2
R1*2
}
\score {
\theMusic
}
Here’s my request: I would love it if \compressFullBarRests actually did what
it says it does… ;)
See <http://lists.gnu.org/archive/html/lilypond
On Mon, Mar 23, 2009 at 01:21:12PM +, Arno Rog wrote:
> Arno Rog gmail.com> writes:
>
> > Fresh install of lilypond-2.10.33-1.mingw.exe on WinXP.
> >
> > \compressFullBarRests generates error: unknown escaped string:
> > `\compressFullBarRests'
>
&
Arno Rog gmail.com> writes:
>
> Fresh install of lilypond-2.10.33-1.mingw.exe on WinXP.
>
> \compressFullBarRests generates error: unknown escaped string:
> `\compressFullBarRests'
Sorry, please disregard!
Downloaded inadvertently the old branch :-( instead of 2
Wasn't this added during 2.11? Please download 2.12.2 and try
again.
Cheers,
- Graham
On Mon, Mar 23, 2009 at 01:16:58PM +, Arno Rog wrote:
> L.S.
>
> Fresh install of lilypond-2.10.33-1.mingw.exe on WinXP.
>
> \compressFullBarRests generates error: un
L.S.
Fresh install of lilypond-2.10.33-1.mingw.exe on WinXP.
\compressFullBarRests generates error: unknown escaped string:
`\compressFullBarRests'
AWRog
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/lis
2009/2/12 Jo Vanattenhoven :
> I started this week with Lilypond and it works great. I'm only having a
> problem
> with grouping rests.
>
> This is the code so far:
> \version "2.11.36"
> \compressFullBarRests
This code works perfectly here on 2.12.2
> C
/4
b'4 (a' d'' b'2.) b'4 (a' e'' b'2.) b'4 (a' e'' b' a' c'' a'2.~a'2) r4 \bar "||"
\compressFullBarRests
R2. *2 |
}
and this is the log # -*-compilation-*-
Changing working directory
57 matches
Mail list logo
