That did it! Thank you. I did have to delete my wayward \ChoirStaff layout,
but once I did that, it's exactly what I wanted.
On Wed, Jul 2, 2025 at 6:30 PM Kieren MacMillan
wrote:
> Hi there,
>
> > I want lyrics to respect bar lines, but I don't want to print bar
Hi there,
> I want lyrics to respect bar lines, but I don't want to print bar lines in
> the lyrics themselves.
Maybe something like this?
%%% SNIPPET BEGINS
\version "2.22.1"
musicOne = \relative c'' { a1 a2 a2 a1 }
musicTwo = \relative c { a1 a2 a2 a1 }
I want lyrics to respect bar lines, but I don't want to print bar lines in
the lyrics themselves.
Minimal example:
\version "2.22.1"
musicOne = \relative c'' { a1 a2 a2 a1 }
musicTwo = \relative c { a1 a2 a2 a1 }
verseOne = \lyricmode {
\once \override LyricTe
Hi Valentin,
> alternatively consist Span_bar_engraver to ChoirStaff, default
> Staff.BarLine.allow-span-bar = ##f and override Staff.BarLine.allow-span-bar
> =
> ##t before the barline you want the span (this needs to be done in all staves
> where a span should descend from
Hi Helge, hi Kieren,
> 1. \consists Span_bar_engraver to the ChoirStaff (not the Staff!)
> 2. \omit it right off the top
> 3. \undo the \omit just before the final barline
alternatively consist Span_bar_engraver to ChoirStaff, default
Staff.BarLine.allow-span-bar = ##f and
objects#using-break_002dvisibility>
for more details.
--
This solution draws a connected bar line at each line end. This might be
good. In the current notes to write I want only the final bar line at
the end of the piece.
With Kierens approach I can control where to write the connected bar
lines. The
Am 19.05.2025 um 19:05 schrieb Kieren MacMillan:
There may be a more elegant way…?
Hope that helps!
Kieren.
This does the requested job nearly to perfectly. I have control where
exactly the connected bar appear. The notes are move a little bit, but
that's okay for me.
Thanks
Helge
Hi Helge,
On Mon, May 19, 2025 at 12:57 PM Helge Kruse wrote:
%%
> That's the desired for the whole song. Except at the end. How can I get
> this closing connected bar line?
>
I do something similar with a StaffGroup - I also prefer the closing span
bar be there. Leaving the two
omit ChoirStaff.SpanBar c4 d e f c, d e f \undo \omit
ChoirStaff.SpanBar \bar "|." } }
\new Staff
{ \relative c' { g4 a b c c, d e f \bar "|." } }
>>
\layout {
\context {
\ChoirStaff
\consists Span_bar_engraver
}
}
%%% SNIPPET ENDS
There may be a more elegant way…?
Hope that helps!
Kieren.
I am writing notes for a choir. That's why I use the ChoirStaff.
Everything looks nice. But the original like many other printed notes
have a closing bar line connected after the final measure. I tried to
this with BarLine.allow-span-bar. This doesn't give neither a warning
nor a err
Hello, Valentin and Kieren
I have tried Valentin's method on my side. It works beautifully.
Thank you guys very much.
On Wed, May 7, 2025 at 2:16 PM Kieren MacMillan
wrote:
> Hi Peter,
>
> Valentin’s suggestion should help you make it work in v2.24.
>
> That being said…
>
> > Before I go ahead
Hi Peter,
Valentin’s suggestion should help you make it work in v2.24.
That being said…
> Before I go ahead and install v2.25.24, I just wanted to ask a quick question
> about compatibility. Since 2.25.x is still considered unstable, do you know
> if it’s fully backward-compatible with scores
Hi Kieren, hi Peter,
> Here’s the output on my end (v2.25.24, which may be the difference?):
The issue here is that `proportionalNotationDuration` is expected to be a
moment on 2.24, so this should be
proportionalNotationDuration = #(ly:make-moment 1/16)
Cheers,
Tina
signature.asc
Description
Hi Kieren,
Thanks again for your detailed response! I agree — your results look
exactly like what I’m aiming for, and it makes sense that version
differences might explain the discrepancy.
Before I go ahead and install v2.25.24, I just wanted to ask a quick
question about compatibility. Since 2.2
Hi Peter,
> I gave it a try — it definitely helps organize things more cleanly — but I’m
> still not quite getting the effect I’m hoping for. I’ve attached a screenshot
> of the current output.
>
> What I’m aiming for is this:
>
> On each system, every measure should have exactly the same widt
ter,
>
> > I'm trying to produce a clean and aligned layout in LilyPond where each
> line contains exactly two measures, and the measure widths on each line are
> exactly equal. Additionally, I want the final (fifth) bar — which is a
> short bar containing 16 sixteenth notes —
Hi Peter,
> I'm trying to produce a clean and aligned layout in LilyPond where each line
> contains exactly two measures, and the measure widths on each line are
> exactly equal. Additionally, I want the final (fifth) bar — which is a short
> bar containing 16 sixteenth no
Hi everyone,
I'm trying to produce a clean and aligned layout in LilyPond where each
line contains exactly two measures, and the measure widths on each line are
exactly equal. Additionally, I want the final (fifth) bar — which is a
short bar containing 16 sixteenth notes — to have the same
Thank you guys! Splendid!
Now I learnt SpanBar.glyph-name and systemStartDelimiter from you.
Kind regards,
Nike
On Wed, Apr 23, 2025 at 8:47 AM Kieren MacMillan <
kie...@kierenmacmillan.info> wrote:
> Hi Yoshi,
>
> > I would add the following near beginning of the code:
> > \unset systemStartDel
Hi Yoshi,
> I would add the following near beginning of the code:
> \unset systemStartDelimiter
Oh, yes, for sure!
> I didn’t know you can name a StaffGrouper like that (“GrandStaffDashed”) …
> Learning new things every day.
Welcome to the beautiful world of custom Lilypond contexts. :)
Best
That’s enlightening; thanks Kieren!
I would add the following near beginning of the code:
\unset systemStartDelimiter
So it looks like:
\defineBarLine "|-dashedSpan" #'(#t #f "!!")
\layout {
\context {
\GrandStaff
\name GrandStaffDashed
\override SpanBar.glyph-name = #"|-dashedSpan"
Hi all,
>> I'm trying to put dashed bar lines between PianoStaff like in this
>> screenshot.
>> I believe it's the same with StaffGroup.
> Maybe there’s a more elegant solution
How about something like this?
SNIPPET STARTS HERE
\version "2.24.4&q
> Hi,
>
> I'm trying to put dashed bar lines between PianoStaff like in this screenshot.
>
> I believe it's the same with StaffGroup.
>
> However I haven't been able to find a solution.
> Writing several with \with measureBarType or \defineBarLine wa
On Sun, 13 Apr 2025 08:50:09 +0800 Knute Snortum
wrote ---
> I don't think \enablePolymeter is supposed to allow measures that don't have
> the correct number of beats in them. It's supposed to allow different time
> signatures in different staves to line up in a score. You still ne
On Sat, Apr 12, 2025 at 4:54 PM James Harkins wrote:
> On Sun, 13 Apr 2025 03:13:41 +0800 Carl Sorensen <
> carl.d.soren...@gmail.com> wrote ---
> > I'd suggest that you make a minimal example that uses variables, and see
> if the use of variables is the issue. I'd be surprised if that is
On Sun, 13 Apr 2025 03:13:41 +0800 Carl Sorensen
wrote ---
> I'd suggest that you make a minimal example that uses variables, and see if
> the use of variables is the issue. I'd be surprised if that is the case.
> But IMO you should test your hypotheses.
OK.
\version "2.24.3"
\langua
On Sat, Apr 12, 2025 at 8:06 AM James Harkins wrote:
> I have \enablePolymeter in my layout block.
>
> In a minimal example, this prevents warnings about time signatures in the
> middle of a bar.
>
> In my actual score, I get:
>
> warning: mid-measure time signature with
I have \enablePolymeter in my layout block.
In a minimal example, this prevents warnings about time signatures in the
middle of a bar.
In my actual score, I get:
warning: mid-measure time signature without \partial
\time 2/4
The main difference is that the minimal example doesn'
ripletFeel 8 {
> >
> > \partial 8 e8 | a2. \tuplet 3/2 { e8 e8 e8 } |
> >
> > }
> >
> > \midi{}
> > }
> >
> > produces
> >
> > xx.ly:5:19: warning: bar check failed at: 1/24
>
> Sounds like a case for \applySwingWithOffset .
>
>
>
> --
> David Kastrup
>
Eric Benson writes:
> Here's a minimal example:
>
> \include "swing.ly"
>
>
> \score {
>
> \tripletFeel 8 {
>
> \partial 8 e8 | a2. \tuplet 3/2 { e8 e8 e8 } |
>
> }
>
> \midi{}
> }
>
> produces
>
>
On 15/03/2025 04:40, Eric Benson wrote:
Yes, this does solve my problem. I can use "s8" instead of "r8"
because I don't need a visible rest there. The written music can start
with the leading eighth note, but the midi needs the extra eighth rest
to align with the beat. The only drawback to this
de "swing.ly"
>
>
> \score {
>
> \tripletFeel 8 {
>
> \partial 8 e8 | a2. \tuplet 3/2 { e8 e8 e8 } |
>
> }
>
> \midi{}
> }
>
> produces
>
> xx.ly:5:19: warning: bar check failed at: 1/24
>
>
>
Hi William and thanks for your help.
Le jeu. 6 mars 2025, à 21 h 12, William Rehwinkel
a écrit :
> You can hide the staff barline like this:
> \once \hide Staff.BarLine
But then, with the
\once \hide Staff.BarLine
solution, it hides the bar line in other situations.
The problem is, I do
x27;
}
>>
Thanks,
-William
On 3/6/25 20:43, Pierre-Luc Gauthier wrote:
Hi everyone,
Is there a way to remove the "spurious" barline at the end of bar 1 of
the second Staff ? Please see the attached image. MWE :
\version "2.25.24"
<<
{ c''4 4 4 4
Hi everyone,
Is there a way to remove the "spurious" barline at the end of bar 1 of
the second Staff ? Please see the attached image. MWE :
\version "2.25.24"
<<
{ c''4 4 4 4 | 4 }
{
\stopStaff
s1 |
\break
\startStaff
c'4
}
>>
--
Pierre-Luc Gauthier
son >:
> >
> > Here's a minimal example:
> >
> > \include "swing.ly"
> >
> >
> > \score {
> >
> > \tripletFeel 8 {
> >
> > \partial 8 e8 | a2. \tuplet 3/2 { e8 e8 e8 } |
> >
> > }
> >
> >
Am Mi., 5. März 2025 um 02:32 Uhr schrieb Eric Benson :
>
> Here's a minimal example:
>
> \include "swing.ly"
>
>
> \score {
>
> \tripletFeel 8 {
>
> \partial 8 e8 | a2. \tuplet 3/2 { e8 e8 e8 } |
>
> }
>
> \midi{}
>
>
score {
\tripletFeel 8 {
\partial 8 e8 | a2. \tuplet 3/2 { e8 e8 e8 } |
}
\midi{}
}
produces
xx.ly:5:19: warning: bar check failed at: 1/24
Here's a minimal example:
\include "swing.ly"
\score {
\tripletFeel 8 {
\partial 8 e8 | a2. \tuplet 3/2 { e8 e8 e8 } |
}
\midi{}
}
produces
xx.ly:5:19: warning: bar check failed at: 1/24
On Mon 24 Feb 2025 at 10:02:27 (-0500), Aleksa Jakovljevic wrote:
> I assume you want a repeat barline? The syntax in 2.22 and later would be
> \bar".|:" .
>
> {
> c1 \bar".|:" c1
> }
>
No, the behaviour of that barline is quite different, as
I assume you want a repeat barline? The syntax in 2.22 and later would be
\bar".|:" .
{
c1 \bar".|:" c1
}
If you don't mind having one at the end as well (the usual format), you
could just use \repeat, i.e.:
{
c1 \repeat volta 2 { c1 }
}
Cheers,
Al
Someone using LilyPond 2.22 emailed me to say that the repeat start
barline was not showing.
I only have 2.20 and 2.24 but I see the change:
With this code:
8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8>
Orm Finnendahl wrote:
Attached now...
>
> AFAICS the only thing stated about Bar Numbers in the score is:
>
> \context Score {
>\set barNumberVisibility = #(every-nth-bar-number-visible 1)
> }
>
>
> lilypond version is 2.23.11.
>
&g
Am Freitag, den 21. Februar 2025 um 16:18:29 Uhr (+0100) schrieb Mats Bengtsson:
> Did you by chance forget the attachment?
yes, sorry!
Attached now...
>
> /Mats
>
> On 2025-02-21 13:15, Orm Finnendahl wrote:
> > Hi,
> >
> > in a chamber ensemble sc
Did you by chance forget the attachment?
/Mats
On 2025-02-21 13:15, Orm Finnendahl wrote:
Hi,
in a chamber ensemble score with bar numbers on every bar above the
score, the vertical position of the bar number of the first bar is too
low on some some pages (see attached png). This doesn&#
Hi,
in a chamber ensemble score with bar numbers on every bar above the
score, the vertical position of the bar number of the first bar is too
low on some some pages (see attached png). This doesn't happen on all
pages.
The topmost staff system is an empty "conductor" staff
currentBarNumber to the desired number.
\once \set Score.currentBarNumber = #target-measure
% 2) Override the bar-number stencil once
\once \override Score.BarNumber.stencil =
#(lambda (grob)
(let* ((text (ly:grob-property grob 'text))
(m-num (ly:grob-pro
Number = #48
c4 d e f
\set Score.currentBarNumber = #48
c4 d e f
\revert Score.BarNumber.stencil
c4 d e f
c1 \bar "|."
}
{ \music }
%%% SNIPPET ENDS
Obviously you’ll want to figure out how to get the letters to increment while
the numbers aren’t incrementing, and wrap it all in a music functio
Hi Steph,
> I'm looking for how to set some bar numbers in my score to have letters.
> For example:
> 46, 47, 48, 48A, 48B, 48C, 49, etc...
> I've been looking at the documentation and I see how to achieve this for
> \repeat'ed bars, but this is just sequential m
Hey All!
I'm looking for how to set some bar numbers in my score to have letters.
For example:
46, 47, 48, 48A, 48B, 48C, 49, etc...
I've been looking at the documentation and I see how to achieve this for
\repeat'ed bars, but this is just sequential music and so the
Hi Matthew,
> * List a human-made selection of inherited and grob-defined properties,
> with commentary on when they are or are not likely to affect the grob
> in cases where it's not obvious. This cannot be infallibly correct in
> every case, and cannot be done automatically
Why, exactly?
If t
On Sun, 15 Dec 2024, Trevor Bača wrote:
> Is what's being communicated here that (for technical reasons) users won't
> *ever* be able to visit a single page of documentation somewhere and see all
> the properties that affect a grob?
Three ways to go:
* List only properties that are defined on th
On Fri, Dec 13, 2024 at 11:00 PM Werner LEMBERG wrote:
>
> Folks,
>
>
> please calm down. Nobody here is insinuating anything! As far as I
> can see, we have a clash of concepts that is probably not resolvable
> in *any* satisfying way. Consequently, the only way forward is to
> minimize the f
p.s.
From a still-unanswered email sent a few weeks ago
(https://lists.gnu.org/archive/html/lilypond-user/2024-11/msg00211.html):
> Using something like "\override BreathingSign.X-offset = #1" simply doesn't
> work. Specifying the context in the override doesn't help. I don't
> understand wh
> In addition to that, the IR is a static document that *cannot*
> reflect the state of LilyPond at an arbitrary point of time while
> processing an input document. Instead, it presents LilyPond in a
> pristine state, before any `*.ly` files has been loaded, more or
> less (including LilyPond's
Folks,
please calm down. Nobody here is insinuating anything! As far as I
can see, we have a clash of concepts that is probably not resolvable
in *any* satisfying way. Consequently, the only way forward is to
minimize the fallout, namely by providing explanations what a musical
term 'foo' mea
Hi Matthew,
> It would really be nice if the documentation could give the reader as much
> information about these kinds of cases as possible
+1
> because trying to use a property and not knowing whether
> it will work or not, is frustrating and a common occurrence.
I’m glad I’m not the only on
On Fri, Dec 13, 2024 at 4:30 PM David Kastrup wrote:
> Trevor Bača writes:
>
> > On Fri, Dec 13, 2024 at 3:46 PM David Kastrup wrote:
> >>
> >> Why would you want to list a property that has no effect on a grob?
> >>
> >
> > David, please go look at the IR 3.1 entry for TupletBracket ...
> >
>
On Fri, 13 Dec 2024, Thomas Morley wrote:
> > Otoh, NoteColumn has grob-interface as well (ofcourse), overriding
> > NoteColumn.color takes no effect.
> And here NoteColumn.color works:
> it's far from trivial to say which property may work or not.
> _If_ something reacts on a property, then it
On Fri, 13 Dec 2024, David Kastrup wrote:
> Creative quoting games. I am out.
I wrote this:
But one might well also ask, if there are useless properties with no
effect, then why are there useless properties with no effect, and isn't
the fact that such properties exist a much bigger pro
Am Fr., 13. Dez. 2024 um 23:26 Uhr schrieb Thomas Morley
:
>
> Am Fr., 13. Dez. 2024 um 22:59 Uhr schrieb Trevor Bača :
> >
> >
> >
> > On Fri, Dec 13, 2024 at 3:46 PM David Kastrup wrote:
> >>
> >> Trevor Bača writes:
> >>
> >> > On Fri, Dec 13, 2024 at 1:11 PM David Kastrup wrote:
> >> >
> >>
Kieren MacMillan writes:
> Hi David,
>
>>> I, for one, would love to see a list of all properties that are
>>> implied to have an effect on a grob [by interface inclusion] but don’t
>>> actually [due to lack of implementation].
>>
>> The proposal would not distinguish between properties having a
Hi David,
> This is the last answer I will provide to this thread since I am sick of
> the insinuation that the documentation of LilyPond is intended to annoy
> people.
That’s not insinuated, as far as I’ve seen — that’s your inference.
> The way to achieve this is to volunteer, not to complain.
> TupletBracket has grob-interface (ofcourse).
> https://lilypond.org/doc/v2.24/Documentation/internals/grob_002dinterface
> lists 'color.
>
> Otoh, NoteColumn has grob-interface as well (ofcourse), overriding
> NoteColumn.color takes no effect.
THIS IS LITERALLY WHAT I’M TALKING ABOUT.
Thanks f
msk...@ansuz.sooke.bc.ca writes:
> On Fri, 13 Dec 2024, David Kastrup wrote:
>
>> > But one might well also ask, if there are useless properties with no
>> > effect,
>>
>> Straw man. There are no such properties.
>
> Then why are you so concerned about whether they'd be listed?
Creative quoting
Trevor Bača writes:
> On Fri, Dec 13, 2024 at 3:46 PM David Kastrup wrote:
>>
>> Why would you want to list a property that has no effect on a grob?
>>
>
> David, please go look at the IR 3.1 entry for TupletBracket ...
>
> https://lilypond.org/doc/v2.24/Documentation/internals/tupletbracket
>
>
Hi David,
>> I, for one, would love to see a list of all properties that are
>> implied to have an effect on a grob [by interface inclusion] but don’t
>> actually [due to lack of implementation].
>
> The proposal would not distinguish between properties having an effect
> and properties not havin
Am Fr., 13. Dez. 2024 um 22:59 Uhr schrieb Trevor Bača :
>
>
>
> On Fri, Dec 13, 2024 at 3:46 PM David Kastrup wrote:
>>
>> Trevor Bača writes:
>>
>> > On Fri, Dec 13, 2024 at 1:11 PM David Kastrup wrote:
>> >
>> >> Trevor Bača writes:
>> >>
>> >> > Most helpful of all was the suggestion that t
On Fri, 13 Dec 2024, David Kastrup wrote:
> > But one might well also ask, if there are useless properties with no
> > effect,
>
> Straw man. There are no such properties.
Then why are you so concerned about whether they'd be listed?
--
Matthew Skala
msk...@ansuz.sooke.bc.ca Pe
msk...@ansuz.sooke.bc.ca writes:
> On Fri, 13 Dec 2024, David Kastrup wrote:
>> >> I don't see how it is a great idea to list properties that may not
>> >> affect a grob at all in the documentation of a grob.
>> >
>> > Excuse me?
>> >
>> > Can you please elaborate just a little bit more on what yo
Kieren MacMillan writes:
> Hi David,
>
>>> Can you please elaborate just a little bit more on what you're
>>> thinking?
>>
>> Why would you want to list a property that has no effect on a grob?
>
> I, for one, would love to see a list of all properties that are
> implied to have an effect on a g
Hi Trevor,
> please go look at the IR 3.1 entry for TupletBracket ...
> https://lilypond.org/doc/v2.24/Documentation/internals/tupletbracket
> ... and tell me where on that page users learn that they have the ability to
> override the color of a tuplet bracket to red.
> Go ahead. Where is that in
Hi Matthew,
> The point isn't to list properties with no effect, but to list *all* of
> the properties that *do* have an effect - not only those that happen to be
> overridden at the most specific level of the hierarchy.
That was the first level of my requests dating back to 2016 (or maybe earlie
On Fri, Dec 13, 2024 at 3:46 PM David Kastrup wrote:
> Trevor Bača writes:
>
> > On Fri, Dec 13, 2024 at 1:11 PM David Kastrup wrote:
> >
> >> Trevor Bača writes:
> >>
> >> > Most helpful of all was the suggestion that the grob descriptions
> given
> >> as
> >> > IR 3.1 ...
> >> >
> >> >
> >>
On Fri, 13 Dec 2024, David Kastrup wrote:
> >> I don't see how it is a great idea to list properties that may not
> >> affect a grob at all in the documentation of a grob.
> >
> > Excuse me?
> >
> > Can you please elaborate just a little bit more on what you're
> > thinking?
>
> Why would you want
Hi David,
>> Can you please elaborate just a little bit more on what you're
>> thinking?
>
> Why would you want to list a property that has no effect on a grob?
I, for one, would love to see a list of all properties that are implied to have
an effect on a grob [by interface inclusion] but don’t
Trevor Bača writes:
> On Fri, Dec 13, 2024 at 1:11 PM David Kastrup wrote:
>
>> Trevor Bača writes:
>>
>> > Most helpful of all was the suggestion that the grob descriptions given
>> as
>> > IR 3.1 ...
>> >
>> >
>> https://lilypond.org/doc/v2.24/Documentation/internals/all-layout-objects
>> >
>
On Fri, Dec 13, 2024 at 1:11 PM David Kastrup wrote:
> Trevor Bača writes:
>
> > Most helpful of all was the suggestion that the grob descriptions given
> as
> > IR 3.1 ...
> >
> >
> https://lilypond.org/doc/v2.24/Documentation/internals/all-layout-objects
> >
> > ... be expanded to list *all* p
Hi all,
> Back in 2021 this question lead to an extensive discussion about how the
> information architecture of the IR might be optimized.
> Most helpful of all was the suggestion that the grob descriptions given as IR
> 3.1 ...
> https://lilypond.org/doc/v2.24/Documentation/internals/all-layou
Carl Sorensen writes:
> I was under the impression that if a grob had a particular interface,
> all of the properties of the interface could be applied to the grob.
But that doesn't mean that they will have an effect.
--
David Kastrup
On Fri, Dec 13, 2024 at 2:13 PM David Kastrup wrote:
> Trevor Bača writes:
>
> > Most helpful of all was the suggestion that the grob descriptions given
> as
> > IR 3.1 ...
> >
> >
> https://lilypond.org/doc/v2.24/Documentation/internals/all-layout-objects
> >
> > ... be expanded to list *all* p
Trevor Bača writes:
> Most helpful of all was the suggestion that the grob descriptions given as
> IR 3.1 ...
>
> https://lilypond.org/doc/v2.24/Documentation/internals/all-layout-objects
>
> ... be expanded to list *all* properties for a given grob, rather than only
> the properties that a grob
On Tue, Nov 9, 2021 at 5:59 PM Paolo Prete wrote:
> Hello,
>
> How can I increase the distance between the last note of a measure and the
> following bar line?
>
Hi,
Back in 2021 this question lead to an extensive discussion about how the
information architecture of the IR mig
Hi everybody,
I'm trying to find the right option to make sure that the bar spacing
follows the length of a text markup.
See this example: if it's one bar long it works, if 2 or more it doesn't.
\version "2.25.19"
\score {
<<
\new StaffGroup <<
#x27;re right that I need an acciaccatura. Thank you for
looking into it.
Hmm... the code still issues a bar check warning with an acciaccatura
or grace. It also doesn't help if I tinker with the durations:
%%%
\oneVoice \grace { c'16*1/8 d e } d8 c |
%%%
I think I unders
. How is that
supposed
to work? You probably want \acciaccatura or \grace instead.
I think you're right that I need an acciaccatura. Thank you for
looking into it.
Hmm... the code still issues a bar check warning with an acciaccatura
or grace. It also doesn't
;> to work? You probably want \acciaccatura or \grace instead.
>
>
> I think you're right that I need an acciaccatura. Thank you for looking
> into it.
>
Hmm... the code still issues a bar check warning with an acciaccatura or
grace. It also doesn't help if I tinker wit
On Mon, Sep 16, 2024 at 12:15 PM David Kastrup wrote:
>
> In my book, an appoggiatura is executed at least with the written
> duration, and here you take 3/16 of time from 1/8. How is that supposed
> to work? You probably want \acciaccatura or \grace instead.
I think you're right that I need
Dear Michael,
I have v. 2.24.4 so I had to replace \musicLength 16 to #(ly:make-moment 1/16).
But it appears that the proportionalNotationDuration computes as expected if a
measure is complete. Combining concatenated scores in complete measure(s)
against those in incomplete measures will cause
Knute Snortum writes:
> I have discovered that LilyPond 2.25.19 produces a bad bar check warning
> under certain circumstances. The three parts are 1) using two voices, 2)
> an appoggiatura, 3) using articulate.ly. Below is my example code:
>
> %%%
> \version "
I have discovered that LilyPond 2.25.19 produces a bad bar check warning
under certain circumstances. The three parts are 1) using two voices, 2)
an appoggiatura, 3) using articulate.ly. Below is my example code:
%%%
\version "2.25.19"
rightHand = \relative {
\time 3/4
<<
Hi all,
I want to align several small scores in a grid for processing with a
laser cutter, while maintaining proportional spacing.
This works well for whole notes and half notes, for quarter notes,
however, the staff symbols seem to be a bit longer
(while occupying the same duration).
Please s
Lucas,
You can add the Bar_number_engraver to one of the staves, like so: (this
will make the second example have two measure numbers)
%
\version "2.25.18"
song = { \new TabStaff \with { \consists Bar_number_engraver}{
\tabFullNotation
\time 4/4 \relative c'' {
\
Hello! I was writing a piece and realized the bar numbers are omitted when
using the "\enablePolymeter" feature.
[image: image.png]
Is there any way to have both of them working together?
Best regards,
Lucas
\version "2.24.4"
song = { \new TabStaff { \tabFullNotation
\
> >> It's in the "expressive marks" snippets, though I admit I
> >> couldn't have found it myself without searching the docs source
> >> code.
> >
> > Could you suggest index entries that I can add to the NR?
>
> Thank you for following up on this.
Paul, the question is addressed to you, too :-
Thank you for following up on this.PaulSent from my Galaxy
Original message From: Werner LEMBERG Date:
6/11/24 8:51 PM (GMT-07:00) To: j...@abou-samra.fr Cc:
waterhorsemu...@aol.com, lilypond-user@gnu.org Subject: Re: hairpin over bar
line and over end of line >> How w
>> How would I have found that in the documentation?
>
> It's in the "expressive marks" snippets, though I admit I couldn't
> have found it myself without searching the docs source code.
Could you suggest index entries that I can add to the NR?
Werner
> How would I have found that in the documentation?
It's in the "expressive marks" snippets, though I admit I couldn't
have found it myself without searching the docs source code.
https://lilypond.org/doc/v2.24/Documentation/snippets/expressive-marks.html#expressive-marks-controlling-spanner-vis
On 6/11/24 11:50 AM, Jean Abou Samra wrote:
\override Hairpin.after-line-breaking = ##f
Thank you, Jean
How would I have found that in the documentation?
Paul
> Probably a simple answer but how do I get a crescendo in this example to
> continue to the next line?
\override Hairpin.after-line-breaking = ##f
signature.asc
Description: This is a digitally signed message part
1 - 100 of 3102 matches
Mail list logo
