Oh perfect, thank you Michael for the suggestion and to Kieren for passing
it on.
Regards,
Brent.
On Tue, 24 June 2025, 6:51 am Michael Gerdau via LilyPond user discussion, <
lilypond-user@gnu.org> wrote:
> > [n.b. I think you just replied to me, so I included your full response
> below.]
>
> O
[n.b. I think you just replied to me, so I included your full response below.]
Oups, right. Thanks for being so observant :)
Kind regards,
Michael
--
Michael Gerdau email: m...@qata.de
GPG-keys available on request or at public keyserver
factor 2/3.
>
> The reason is that it seems obvious that the time signature change implies a
> tempo change, namely what used to be a bar of 3/2 (or a dotted full note) is
> now a full note.
>
> Or phrased differently:
> The time that used to be taken up by 3 half note is n
Hey Kieren,
Thank you! That looks great. Now I see how simple it is, I feel like I
should have been able to figure that out myself :-/ Now at least I know for
next time :-)
Regards,
Brent.
On Mon, 23 Jun 2025 at 22:13, Kieren MacMillan
wrote:
> Hi Brent,
>
> > I'm trying
Hi Brent,
> I'm trying to reproduce the example in the attached pic, but I'm having
> trouble getting the new common-time signature to align with the barlines
> between the staves. Actually I have no idea how to move time signatures at
> all -- I've nosed around a
Hi all,
I'm trying to reproduce the example in the attached pic, but I'm having
trouble getting the new common-time signature to align with the barlines
between the staves. Actually I have no idea how to move time signatures at
all -- I've nosed around a bit but can't see
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 u
'd be surprised if that is the
> case. But IMO you should test your hypotheses.
>
> OK.
>
> \version "2.24.3"
> \language "english"
>
> minimalExampleVariableOne = \relative c' {
> \time 3/4
> c4 d e
> \time 4/4
> f g a b
>
.
\version "2.24.3"
\language "english"
minimalExampleVariableOne = \relative c' {
\time 3/4
c4 d e
\time 4/4
f g a b
}
minimalExampleVariableTwo = \relative c' {
\time 4/4
c4 d e
\time 3/4
f g a b
}
\score { <<
\new Staff \minimalExampleVariabl
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'
On Sun, 06 Apr 2025 22:04:12 +0800 James Harkins
wrote ---
> \override TimeSignature.stencil = ##f
>
> Does this not work anymore?
Never mind, I found it.
\override Staff.TimeSignature.stencil = ##f
hjh
\override TimeSignature.stencil = ##f
Does this not work anymore?
\score { <<
\new Staff \relative c' {
\override TimeSignature.stencil = ##f
\time 2/4
c4 c4
\time 3/4
c c c
\time 2/4
c c
\bar "|."
}
>> }
...
Hi all,
Right now I am working on a python program for making grids with heterogenous
measure lengths and changing tempos while keeping the spacing proportional to
the time it takes up to help me with some precomposition stuff. I have used
\override Score.SpacingSpanner.spacing-increment to
in a chronometric
transcription I'm working on in which I may need to have Clefs and Time
Signatures in some points (and so I cannot just remove the engravers)
Below is what I am trying (I would like to make the first notes to collide
with the first Clef and Time Signature of each Staff).
T
On Sat, Mar 22, 2025 at 2:05 PM Xavier Scheuer wrote:
> On Sat, 22 Mar 2025 at 21:56, Ralph Palmer
> wrote:
> >
> > Yes, as in that. Here's a minimal non-working example:
>
>>
> Hello Ralf,
>
> The property is called break-visibility, not end-of-line-invisible (which
> is a possible value of thi
On Sat, 22 Mar 2025 at 21:56, Ralph Palmer
wrote:
>
> Yes, as in that. Here's a minimal non-working example:
>
Hello Ralf,
The property is called break-visibility, not end-of-line-invisible (which
is a possible value of this property).
Look also at the section "Special considerations" on the pag
't find it
> there or figure out how to do it.
>
> What I want is to eliminate the end-of-line clef and/or time signature
> when either one changes at the start of the next line.
>
> Could someone please point me in the right direction?
>
>
> As in
>
> http
t;
> What I want is to eliminate the end-of-line clef and/or time signature when
> either one changes at the start of the next line.
>
> Could someone please point me in the right direction?
As in
https://lilypond.org/doc/v2.24/Documentation/notation/visibility-of-objects#using-break_002dvisibility
?
HTH
Hans
Hi -
I've done this before, but I can't figure out where. I've tried searching
the Notation Reference, the User Archive, and the LSR, but I can't find it
there or figure out how to do it.
What I want is to eliminate the end-of-line clef and/or time signature when
either one
On 06/03/2025 20:50, Paul Scott wrote:
I posted before about time signatures and/or key changes repeated at
the end of the previous line and was shown that it works correctly.
I finally saw the problem that occasionally effects my normal code
structure.
Could the \endSpanners music
On Thu, Mar 6, 2025 at 3:52 PM Paul Scott wrote:
> Hi,
>
> I posted before about time signatures and/or key changes repeated at the
> end of the previous line and was shown that it works correctly.
>
> I finally saw the problem that occasionally effects my normal code
> st
On Thu, Mar 6, 2025 at 12:52 PM Paul Scott wrote:
> Hi,
>
> I posted before about time signatures and/or key changes repeated at the
> end of the previous line and was shown that it works correctly.
>
> I finally saw the problem that occasionally effects my normal code
> st
Hi,
I posted before about time signatures and/or key changes repeated at the
end of the previous line and was shown that it works correctly.
I finally saw the problem that occasionally effects my normal code
structure.
I always separate notes and time and dynamics to be able to use all or
> It is the default behavior, lilypond compresses the whole line. You can
> see it in the example below. I'm still confused about what the question
> is, but perhaps a handwritten example or scan from another score would help.
An even more obvious example:
```
{
\repeat unfold 32 { 8 \noBreak
"
\layout {
ragged-right = ##f
}
\score {
\relative g' {
g8 g g g g g g g | g g g g g g g g | \break \time 3/4 g2.
}
}
\score {
\relative g' {
g8 g g g g g g g | g g g g g g g g | \break g2.
}
}
On 1/28/25 02:01, Tim's Bitstream via LilyPond user discussion
Sent from my Galaxy
Original message From: Tim's Bitstream via LilyPond user
discussion Date: 1/28/25 12:03 AM (GMT-07:00) To:
lily Pond Subject: Re: key and/or time signature at end
of line So you want Lilypond to take that space equally from all the measures
in that
:35, Paul Scott
wrote:
When a time signature or key change happens at the
beginning of a line it is repeated at the end of the
previous line. This is good and normal.
The space needed for this is take
I don't want to cancel it. I want it not to compress the music in the
last measure of the line.
I haven't been able to find one of my examples or create a MWE.
Thank you,
Paul
On 1/25/25 11:33 AM, Hans Aikema wrote:
On 25 Jan 2025, at 00:35, Paul Scott wrote:
When a time si
All the examples I sent on the list have the change exactly at the break, not
one measure before the end. You can put as many measures before the \break as
you want, the code addresses the changeover to another key and time-signature
at the measure directly after the break.
So if it's not
ikema wrote:
On 25 Jan 2025, at 00:35, Paul Scott wrote:
When a time signature or key change happens at the beginning of a line it is
repeated at the end of the previous line. This is good and normal.
The space needed for this is taken from the last measure on that previous line
often m
> On 25 Jan 2025, at 19:33, Hans Aikema wrote:
>
>
>
>> On 25 Jan 2025, at 00:35, Paul Scott wrote:
>>
>> When a time signature or key change happens at the beginning of a line it is
>> repeated at the end of the previous line. This is good and normal.
> On 25 Jan 2025, at 00:35, Paul Scott wrote:
>
> When a time signature or key change happens at the beginning of a line it is
> repeated at the end of the previous line. This is good and normal.
>
> The space needed for this is taken from the last measure on that prev
On Fri, Jan 24, 2025 at 6:37 PM Paul Scott wrote:
> When a time signature or key change happens at the beginning of a line
> it is repeated at the end of the previous line. This is good and normal.
>
> The space needed for this is taken from the last measure on that
> previous li
When a time signature or key change happens at the beginning of a line
it is repeated at the end of the previous line. This is good and normal.
The space needed for this is taken from the last measure on that
previous line often making that last measure very cramped . Is there a
way to
On Mon, Oct 14, 2024 at 2:09 PM Sebastian Menge wrote:
> That works well, thank you!
>
> Is there a way to set this for the whole piece? Or at least all
> de/crescendi?
>
> My piece often changes time and also keys - I have many wide gaps for the
> crescs.
>
Try:
\ove
That works well, thank you!
Is there a way to set this for the whole piece? Or at least all
de/crescendi?
My piece often changes time and also keys - I have many wide gaps for the
crescs.
--
Sebastian.
On Mon, Oct 14, 2024 at 8:42 PM David Kastrup wrote:
> Sebastian Menge writes:
>
Sebastian Menge writes:
> Hi folks,
>
> this does not look good to me:
>
> \version "2.24.3"
> {
> c'1\pp\<\time 3/4 g'2.\ff
> }
>
> IMHO the crescendo should span the time signature and reach until the next
> note starts in \ff
>
&
Hi folks,
this does not look good to me:
\version "2.24.3"
{
c'1\pp\<\time 3/4 g'2.\ff
}
IMHO the crescendo should span the time signature and reach until the next
note starts in \ff
Should I get used to it, or should /could this be "tweaked" somehow?
Thanks, Sebastian.
wrote:
> Thanks,
> While it does show what i want, problem is that next measures (g4 in this
> example) also takes 6/8 time. Example
>
> \version "2.24.4"
>
> music = \fixed c' {
> f1
> \repeat segno 2 {
> g1
> \alternative {
> \
Thanks,
While it does show what i want, problem is that next measures (g4 in this
example) also takes 6/8 time. Example
\version "2.24.4"
music = \fixed c' {
f1
\repeat segno 2 {
g1
\alternative {
\volta 1 { \repeat unfold 4 { a2 }
\break
\key f \majo
On Sat, 3 Aug 2024 at 17:17, Vlado Ilić wrote:
>
> So i need something like in the first picture, on coda i have different
time signature than the one before the jump so i need to mark time change
just before the jump. Also related, in the second image i need to mark time
and key change
So i need something like in the first picture, on coda i have different
time signature than the one before the jump so i need to mark time change
just before the jump. Also related, in the second image i need to mark time
and key change before jumping from D.S. to the beginning of the piece. How
> I thought I had this solved before but I can't find it. I need to set the
> time signatures 9/8 and 3/4 side-by-side surrounded by parentheses at the
> beginning of a score.
See https://lsr.di.unimi.it/LSR/Item?id=782
I thought I had this solved before but I can't find it. I need to set the time
signatures 9/8 and 3/4 side-by-side surrounded by parentheses at the beginning
of a score.
-David
the sections into two scores with an indented first line.
\version "2.24.0"
\header {
title = "Shortened Lines"
composer = "John McWilliam"
copyright = "Kopierad av John McWilliam. PMRS 2024"
}
clarinet = \relative c'' {
\key f \major
\nu
From: jsmcwill...@gmail.com
Sent: den 5 maj 2024 09:15
To: lilypond-user@gnu.org
Subject: Cautionary Time Signature
Firstly, I have reregistered since the support forum does not recognise my
credentials!
I enclose a snippet illustrating two problems I am trying to resolve in a
piece
Firstly, I have reregistered since the support forum does not recognise my
credentials!
I enclose a snippet illustrating two problems I am trying to resolve in a
piece containing a melody followed by a Trio section:
1. There is a key signature change before going into the Trio and I
cannot g
iting...
> >
> > Yes there is.
>
> [...]
>
> > The question is only: will it work as well in my score. I still
> > have to try and see, and I will report what will happen...
> >
>
> I think this does what you want:
>
> \version "2.24
t you want:
\version "2.24.3"
rightHand = \relative c' {
\time 3/4
\repeat unfold 6 { c8 }
\set Staff.timeSignatureFraction = 9/8
\scaleDurations 2/3 {
\repeat unfold 9 { c8 }
}
\set Staff.timeSignatureFraction = 3/4
\repeat unfold 6 { c8 }
}
leftHand = \relative c
/4 there was no 3/4 again, although I had written "\time 3/4", and
I could not figure out why.
Am Samstag, dem 20.04.2024 um 16:06 -0700 schrieb Knute Snortum:
> On Sat, Apr 20, 2024 at 3:02 PM Hajo Baess wrote:
>
> > I have messed around with this little lab specime
On Sat, Apr 20, 2024 at 3:02 PM Hajo Baess wrote:
> I have messed around with this little lab specimen here, and I have
> found a solution, but it is weird. You obviously (after having scaled
> some rhythm just once) have to explicitly unscale the rhythm e v e r y
> time you want
I have messed around with this little lab specimen here, and I have
found a solution, but it is weird. You obviously (after having scaled
some rhythm just once) have to explicitly unscale the rhythm e v e r y
time you want it to appear in the staff. I have extended the example
with a short quote
s, I
> get this - see screenshot.
>
> But if I do something really basic like:
>
> \version "2.24.2"
> \language "deutsch"
>
> \relative c'' {
> \time 3/4 c4 c c c2 c4
> \time 3/4 c4 c c c2 c4
> \omit
e:
\version "2.24.2"
\language "deutsch"
\relative c'' {
\time 3/4 c4 c c c2 c4
\time 3/4 c4 c c c2 c4
\omit Score.TimeSignature
\time 3/4 c4 c c c2 c4
\undo \omit Score.TimeSignature
\time 3/4 c4 c c c2 c4
\ba
On Sat, Apr 20, 2024 at 4:17 AM Hajo Baess wrote:
> If I do this, I get other unwanted results - see screenshot. The
> problem is that I am switching back and forth between scaled and non-
> scaled rhythm. And as you will notice, the 6/4 only appears in the
> piano staff and n o t in the top p
should) in the top part like in bars 195
and 197...
Is there no simple way to just toggle "\override
Score.TimeSignature.stencil = ##f " ?
Am Samstag, dem 20.04.2024 um 11:41 +0100 schrieb Mark Knoop:
> This line:
>
> \override Score.TimeSignature.stencil = ##f
>
> mean
This line:
\override Score.TimeSignature.stencil = ##f
means that the time signature will not be displayed (its stencil is set
to false). Either remove it, or if you need it for some other reason,
prefix with \once.
Regards,
Mark
At 10:13 on 20 Apr 2024, Hajo Baess wrote:
> This time w i
This time w i t h screenshot attached - sorry about that... Delete
the previous one ;-)
Unfortunately this does not work - because I have tried exactly this
one, and there is no time signature. I attach a screenshot of the
passage. My piece is in 3/4, and in the top part in bar 185, I have to
Unfortunately this does not work - because I have tried exactly this
one, and there is no time signature. I attach a screenshot of the
passage. My piece is in 3/4, and in the top part in bar 185, I have to
do some rhythmical scaling, whereas the other parts continue in 3/4. I
could as well have
On Fri, Apr 19, 2024 at 4:31 PM Hajo Baess wrote:
> Hello all,
>
> I look for a way to force LilyPond to show the same time signature
> again, although there is no change - just as a reminder. I could not
> find anything in the NR and in the Snippet Repository.
>
>
Unless
Hello all,
I look for a way to force LilyPond to show the same time signature
again, although there is no change - just as a reminder. I could not
find anything in the NR and in the Snippet Repository.
Grateful for any suggestion how to achieve this.
Hi Jean,
> To get 2-digit precision on the number of seconds, you can simply replace
>
> (format #f "~as" (round rest))
>
> with
>
> (format #f "~,2fs" rest)
>
> in the format-time function.
>
> For seconds:frames at 24 frames/second,
edia composers.
To get 2-digit precision on the number of seconds, you can simply replace
(format #f "~as" (round rest))
with
(format #f "~,2fs" rest)
in the format-time function.
For seconds:frames at 24 frames/second, replace format-time with
(define (format-t
Hi Lukas,
I love that we have two custom engravers to compare and learn from!
Thank you so much for this solution — looking forward to analyzing it when I
have a moment.
Best,
Kieren.
> On Mar 14, 2024, at 5:54 PM, Lukas-Fabian Moser wrote:
>> “This sounds like a job for… Custom Engraver!!” :
.
> On Mar 14, 2024, at 5:45 PM, Jean Abou Samra wrote:
>
>> “This sounds like a job for… Custom Engraver!!” :)
>
> \version "2.24.2"
>
> #(define (Custom_engraver!! context)
> (define (format-time seconds)
> (let ((minutes (euclidean-quotient s
On Thu, 14 Mar 2024, Jean Abou Samra wrote:
> > “This sounds like a job for… Custom Engraver!!” :)
>
> #(define (Custom_engraver!! context)
>(define (format-time seconds)
Thanks! I haven't tested this extensively, but so far it looks like it
works well.
-
Hi,
Am 14.03.24 um 17:27 schrieb Kieren MacMillan:
Hi Matthew,
Is there any easy way to find out the time in seconds from the start of a
score to a specified point, corresponding to the timing of the MIDI
output? I can count measures and do math on the tempo, but that's
less than ide
> “This sounds like a job for… Custom Engraver!!” :)
\version "2.24.2"
#(define (Custom_engraver!! context)
(define (format-time seconds)
(let ((minutes (euclidean-quotient seconds 60))
(rest (euclidean-remainder seconds 60)))
(string-append (if (
Hi Matthew,
> Is there any easy way to find out the time in seconds from the start of a
> score to a specified point, corresponding to the timing of the MIDI
> output? I can count measures and do math on the tempo, but that's
> less than ideal in the face of multiple tempo chang
Is there any easy way to find out the time in seconds from the start of a
score to a specified point, corresponding to the timing of the MIDI
output? I can count measures and do math on the tempo, but that's
less than ideal in the face of multiple tempo changes. Another idea would
be to jus
On 03/02/2024 23:45, Valentin Petzel wrote:
Am Freitag, 2. Februar 2024, 16:38:22 CET schrieb Lukas-Fabian Moser:
... and without any new insight, but with a healthy dose of syntactic sugar:
And with a rather simple custom engraver Lilypond will do these kinds of
things for us.
I know, b
#(define-scheme-function (times) (list?)
(make-line-markup
(map
(lambda (x)
(make-compound-meter-markup
(list (ly:music-property x 'numerator)
(ly:music-property x 'denominator))))
times)))
#(define (alternating-time-translator context)
(
Am 02.02.24 um 01:35 schrieb Leo Correia de Verdier:
If you want to avoid some of the jiggery pokery you could do something like:
\version "2.25.12"
#(define ((time-alternate-time upa downa upb downb) grob)
(grob-interpret-m
If you want to avoid some of the jiggery pokery you could do something like:
\version "2.25.12"
#(define ((time-alternate-time upa downa upb downb) grob)
(grob-interpret-markup grob
(markup #:override '(baseline-ski
Thank you, that worked a treat. Though I also had to add a "\time 6/8"
in order to get automatic bar lines inserted. "\time 3/4" produced wrong
beaming in the 6/8 bars, and I can see that I may have to do some
jiggery pokery to the beaming in 3/4 bars if, for example, I hav
On Thu, Feb 1, 2024 at 10:50 AM Raphael Mankin wrote:
> I have music with alternate bars in 3/4 and 6/8. The usual way to
> indicate this is to put both time signatures at the start, but I can
> find no way to do this.
>
> I have tried "\time 3/4 <> \time 6/8&quo
I have music with alternate bars in 3/4 and 6/8. The usual way to
indicate this is to put both time signatures at the start, but I can
find no way to do this.
I have tried "\time 3/4 <> \time 6/8", but I only get the last one.
Note, this is not a compound time of 3/4+6/8,
Hi Stanton,
I’m setting various short organ pieces from an old Peters edition,
mostly to prevent my aging brain from forgetting…
One piece is in 8/4 time -the first measure has a whole note and 2
half notes. However, the time signature as printed is the cut time
symbol. How can I reproduce
David, Thank you. That is exactly what I was looking for. William, thank you
for the helpful explanation of the somewhat archaic use of the cut time sign.
And David, again thank you for your responses.
-Stan
> On Jan 11, 2024, at 9:20 PM, David Wright wrote:
>
> On Thu 11 Jan 2024
r 4/2 (and I
> agree that 4/2 is the most reasonable time signature), I was looking for a
> way of declaring the cut C.
>
> The included photo is from the piece (# 67. Vater Unser in Himmelreich by
> Johann Kyieger, from _80 Choral Preludes_, Edition Peters, No. 4440,
> Copyright
Stanton,
As far as I know (I use Lilypond 2.22.2) cut C is not available for 4/2.
Mark
-Original Message-
From: Stanton Sanderson
Sent: Thursday, January 11, 2024 6:12 PM
To: Mark Stephen Mrotek
Cc: LilyPond Users
Subject: Re: Cut time/half-time/alle breve & 8/4 time
Mark,
T
Mark,
Thank you for the suggestion, but as stated previously, I’m trying to reproduce
the original from the Peters edition. The problem, as you point out, is that
the cut C is used in the original. Whether 8/4 or 4/2 (and I agree that 4/2 is
the most reasonable time signature), I was looking
Stanton,
I think the piece is in 4/2.
Do you want a numeric time signature?
The cut C is used for 2/2.
Mark
From: lilypond-user-bounces+carsonmark=ca.rr@gnu.org
On Behalf Of Stanton
Sanderson
Sent: Thursday, January 11, 2024 3:15 PM
To: LilyPond Users
Cc: Stanton Sanderson
I’m setting various short organ pieces from an old Peters edition, mostly to
prevent my aging brain from forgetting…
One piece is in 8/4 time -the first measure has a whole note and 2 half notes.
However, the time signature as printed is the cut time symbol. How can I
reproduce this? I’m
> does the new proposed spacing mean that the time signatures are not
> aligned across staves any more but were before?
No, they are aligned as before.
Werner
Hi Werner,
does the new proposed spacing mean that the time signatures are not
aligned across staves any more but were before?
Best,
Michael
>>> please have a look at Merge Request 2188 and comment there on how
>>> to proceed with the new distances between clefs and time
>>> signatures, together with the new distances between clefs and key
>>> signatures.
>>>
>>> http
For what it's worth, I think the original suggestion (with the top-left
clef adjusted by -4.4%) is the better of the two.
I do understand that there's an argument to be made against adjusting
clefs that aren't /too/ bad, but the adjusted versions of the treble
clefs /are/ better imo.
With ae
> Thanks, but I would like to know whether you prefer the top
> (alto-based) or bottom (treble-based) image on
>
> https://gitlab.com/lilypond/lilypond/-/merge_requests/2188
Top (alto-based) is 6 days ago and bottom (treble-based) is 4 days ago as of
today?
Of those two I prefer bottom as it
> I’ve just looked at the images and especially w/r to the Alto clef I
> strongly prefer the new spacing. For the others there are spots
> where I’m not sure it is too tight but overall the new spacing
> appears to be more balanced.
>
> I thus think the new spacing is better overall.
Thanks, bu
Mobil gesendet
> Am 09.12.2023 um 08:12 schrieb Werner LEMBERG :
>
>
>>> please have a look at Merge Request 2188 and comment there on how
>>> to proceed with the new distances between clefs and time
>>> signatures, together with the new distances
>> please have a look at Merge Request 2188 and comment there on how
>> to proceed with the new distances between clefs and time
>> signatures, together with the new distances between clefs and key
>> signatures.
>>
>> https://gitlab.com/lilypond/lilyp
>> please have a look at Merge Request 2188 and comment there on how
>> to proceed with the new distances between clefs and time
>> signatures, [...]
>
> FWIW, I think the Petrucci clef distances are a big improvement and
> make incipits closer to what they usually
On Tue, 5 Dec 2023, 07:42 Werner LEMBERG, wrote:
>
> Folks,
>
>
> please have a look at Merge Request 2188 and comment there on how to
> proceed with the new distances between clefs and time signatures,
> together with the new distances between clefs and key signatures.
>
At least for the clef+time signature I prefer the tighter spacing of the first
suggestion. Improvement requires things to change.
> 5 dec. 2023 kl. 07:39 skrev Werner LEMBERG :
>
>
>> please have a look at Merge Request 2188 and comment there on how to
>> proceed w
> please have a look at Merge Request 2188 and comment there on how to
> proceed with the new distances between clefs and time signatures,
> together with the new distances between clefs and key signatures.
>
> https://gitlab.com/lilypond/lilypond/-/merge_requests/2188
>
Folks,
please have a look at Merge Request 2188 and comment there on how to
proceed with the new distances between clefs and time signatures,
together with the new distances between clefs and key signatures.
https://gitlab.com/lilypond/lilypond/-/merge_requests/2188
The question is whether
>> Please check the looong list of bugs related to `\articulate`
>> whether it has already been reported.
>
> Seems to be #3696, reported - by you - in 2013.
D'oh :-)
Werner
On Wed, Nov 22, 2023 at 12:09 PM Werner LEMBERG wrote:
>
> > This fails in 2.24.1 with messages about mid-measure time signature
> > change and failed barcheck:
> >
> > \include "articulate.ly"
> > \articulate
> > {
> > \ti
1 - 100 of 2425 matches
Mail list logo
