mothy Lanfear:
On 18/05/2025 12:54, Stephan Schöll wrot
How can I avoid the collision warning and the omission of one of the
marks in a way that both the \codaMark and the \sectionLabel are
printed side by side (ideally the codaMark above the barline and the
sectionLabel with a minimal offset t
Hi Mark
Am 18.05.2025 um 19:00 schrieb Mark Knoop:
\once \override Score.SectionLabel.X-offset = #0
\sectionLabel \markup { \coda "Chorus" }
That's a viable workaround for my case. Thanks a lot.
S.
Hi Stephan,
At 13:54 on 18 May 2025, Stephan Schöll wrote:
> Hi all
> How can I avoid the collision warning and the omission of
> one of the marks in a way that both the \codaMark and the
> \sectionLabel are printed side by side (ideally the
> codaMark above the barline and the se
On 18/05/2025 12:54, Stephan Schöll wrot
How can I avoid the collision warning and the omission of one of the
marks in a way that both the \codaMark and the \sectionLabel are
printed side by side (ideally the codaMark above the barline and the
sectionLabel with a minimal offset to the right
Weitergeleitete Nachricht
Betreff:How to avoid codaMark / sectionLabel collision?
Datum: Mon, 5 May 2025 21:37:03 +0200
Von:Stephan Schöll
An: lilypond-user
Hi all
How can I avoid the collision warning and the omission of one of the
marks in a way that both the \codaMark
Hi all
How can I avoid the collision warning and the omission of one of the
marks in a way that both the \codaMark and the \sectionLabel are printed
side by side (ideally the codaMark above the barline and the
sectionLabel with a minimal offset to the right).
TIA
Stephan
%%% MWE
\version
This is perfect, thanks so much for your responses everybody.
-William
On 5/19/24 10:56, Kieren MacMillan wrote:
Hi Knute,
There are ways to "disable the padding" (a.k.a. have the spacing engine
ignore the TextScript). However, it might be just as easy — or maybe
even easier? — to simply twea
Hi Knute,
>> There are ways to "disable the padding" (a.k.a. have the spacing engine
>> ignore the TextScript). However, it might be just as easy — or maybe
>> even easier? — to simply tweak the X-offset and Y-offset rather than
>> using extra-offset:
> The extra-offset happens late in the rend
On Sun, May 19, 2024 at 4:22 AM wrote:
> Hi William,
>
> > In the following example, I use a section label and a TextScript on a
> > note. I offset the markup text so that it appears inside the staff, but
> > it still makes the section text higher up. I would like to know if it
> > is possible to
Hi William,
In the following example, I use a section label and a TextScript on a
note. I offset the markup text so that it appears inside the staff, but
it still makes the section text higher up. I would like to know if it
is possible to disable this padding around the TextScript, so that the
Dear list,
In the following example, I use a section label and a TextScript on a
note. I offset the markup text so that it appears inside the staff, but
it still makes the section text higher up. I would like to know if it is
possible to disable this padding around the TextScript, so that the
Am Mon, Jan 01, 2024 at 06:55:39PM + schrieb Werner LEMBERG:
>
> > while typing down the score from an old scan, I discovered a
> > collision between an accidental and a tuplet spanner, or rather the
> > number in it:
> > […]
> > Perhaps this is worthy of an is
I see that it can be corrected with
\override TupletBracket.padding = 2.5
See this page
<https://lilypond.org/doc/v2.24/Documentation/internals/tupletbracket>
\version "2.24"
\language "deutsch"
\relative c' {
\tupletUp
% corrects the collision be
> while typing down the score from an old scan, I discovered a
> collision between an accidental and a tuplet spanner, or rather the
> number in it:
>
>
> \version "2.24"
> \language "deutsch"
>
> \relative c' {
> \tupletUp
> \times
Hello list,
while typing down the score from an old scan, I discovered a collision
between an accidental and a tuplet spanner, or rather the number in it:
\version "2.24"
\language "deutsch"
\relative c' {
\tupletUp
\times 2/3 { g'=''8 b4 } des8 h
On Jul 31, 2023, at 10:36 PM, Abraham Lee >> <mailto:tisimst.lilyp...@gmail.com>> wrote:
>>>
>>> Hi, Carolyn!
>>>
>>> On Mon, Jul 31, 2023 at 8:22 AM Carolyn Beeton >> <mailto:carolyn.bee...@icloud.com>> wrote:
>>>> Th
et is positioned where the second beat of the measure would be,
and 2) the lilypond placement on the left of the dotted minim is the
"right" or at least standard way of typesetting this type of collision.
Best wishes,
Jakob
On 01.08.2023 16.11, Carolyn Beeton wrote:
Thanks Abraham
I
;
>
> \layout { }
>
> }
>
> Thanks,
> Carolyn
>
> On Jul 31, 2023, at 10:36 PM, Abraham Lee
> wrote:
>
> Hi, Carolyn!
>
> On Mon, Jul 31, 2023 at 8:22 AM Carolyn Beeton
> wrote:
>
>> The default when there are two voices with colliding notes i
Hallo Carolyn,
I have read that section again and I am still a bit confused at what I
am seeing in this attempt at a MWE. In bar 2 the voiceTwo notes are
shifted right, but in bar 5 the voiceOne note, a dotted note, is being
shifted to the right. I have tried using the
Staff.NoteCollision.
Carolyn Beeton writes:
> I have read that section again and I am still a bit confused at what I
> am seeing in this attempt at a MWE. In bar 2 the voiceTwo notes are
> shifted right, but in bar 5 the voiceOne note, a dotted note, is being
> shifted to the right. I have tried using the
> Staff.N
oiceOne, with
>> stems up, shifted left. Is this possible? (not as a single override, but
>> throughout the entire piece)
>
> I trust you've seen this section in the NR on collision resolution, but if
> not, here it is:
>
> https://lilypond.org/doc/v2.24/Doc
One, with
> stems up, shifted left. Is this possible? (not as a single override, but
> throughout the entire piece)
>
I trust you've seen this section in the NR on collision resolution, but if
not, here it is:
https://lilypond.org/doc/v2.24/Documentation/notation/multiple-voices#collis
The default when there are two voices with colliding notes is to shift the
voice with upstems (odd-numbered voices) to the right and voices with downstems
to the left. I would like the opposite - i.e. voiceOne, with stems up, shifted
left. Is this possible? (not as a single override, but thro
roperty is used to control the spacing between the second part of a
> broken slur's left control point and the preceding key signature? I'd like
> to increase this spacing a bit as the current collision is quite
> bothersome. Here's what I mean:
>
> [image: image.
Le mercredi 05 juillet 2023 à 18:45 -0600, Abraham Lee a écrit :
> All,
>
> What property is used to control the spacing between the second part of a
> broken slur's left control point and the preceding key signature? I'd like to
> increase this spacing a bit as the c
All,
What property is used to control the spacing between the second part of a
broken slur's left control point and the preceding key signature? I'd like
to increase this spacing a bit as the current collision is quite
bothersome. Here's what I mean:
[image: image.png]
Thanks,
Abraham
Thank you, Jean, for these very detailed explanations about how the
voices are to be used -- and the alternate way to achieve the same
result. I hugely appreciate your input.
Archer
On 14/03/2023 19:09, Jean Abou Samra wrote:
Le mardi 14 mars 2023 à 14:36 +, Archer Endrich a écrit :
Th
Le mardi 14 mars 2023 à 14:36 +, Archer Endrich a écrit :
> Thank you Xavier and Jean. The warnings have disappeared and the
> MMrest with #-6 is perfectly placed on the E line of the staff.
> The revised version looks like this:
> \score {
>
> \new Staff {
>
Thank you Xavier and Jean. The warnings have disappeared and the MMrest
with #-6 is perfectly placed on the E line of the staff.
The revised version looks like this:
\score {
\new Staff {
\time 4/4
\clef treble
g'1^\markup{Fl 1} |
<<
{ \voiceTwo
\once
Le mardi 14 mars 2023 à 13:13 +0100, Xavier Scheuer a écrit :
> On Tue, 14 Mar 2023 at 12:55, Archer Endrich
> <[archer...@gmail.com](mailto:archer...@gmail.com)> wrote:
> >
> > The reason I used c'1\rest was so that the rest would be placed on the
> > bottom line of the Staff. I would real
On Tue, 14 Mar 2023 at 12:55, Archer Endrich wrote:
>
> The reason I used c'1\rest was so that the rest would be placed on the
> bottom line of the Staff. I would really like a centered rest (R1) but
> this automatically places it on the 2nd line from the top, which does
> conflict with the music
the
definition outside \book made it all work perfectly.
I have another problem with a very simple use of cues, using code as in
the Notation Manual. This is my example:
%CuesandRestCollisions.ly
\version "2.22.1"
\header {
title = "Cues and Rest Collision Warning"
}
Le vendredi 10 mars 2023 à 02:46 -0500, 4w6xr...@duck.com a écrit :
> I'm attempting to position a text mark just above the staff as I have with a
> text script, ignoring collision with the note.
>
> \version "2.24.1"
>
> % Is there a text mark an
I'm attempting to position a text mark just above the staff as I have with a
text script, ignoring collision with the note.
\version "2.24.1"
% Is there a text mark analog to the following text script?
{
\override TextScript.outside-staff-priority = ##f
c''2^&quo
Thanks,
Paul
From: Jean Abou Samra
To: Paul Hodges , lilypond-user Mailinglist
Sent: 04/01/2023 16:27
Subject: Re: Allowing a collision
Le 04/01/2023 à 17:24, Paul Hodges a écrit :
> I have a score which has two staves, for unrelated instruments. To
> reproduce the c
the collision from happening.
Is there a way to turn off the collision avoidance for this specific
item in isolation?
The real question is: why is \crossStaff inapplicable for you?
OpenPGP_signature
Description: OpenPGP digital signature
cable; so I am trying either to lengthen the stems on
one staff or to draw a line joining them, using \markup.
However, whichever method I try, LilyPond prevents the extended stem/line from
reaching note on the other staff, because it prevents the collision from
happening.
Is there a way to
wrote:
Hi all
First of all, wish a happy New Year to all of you!
I'm struggling with a collision of fingerings and a tuplet number when a
slur is around:
\version "2.24.0"
\relative c' {
\time 2/4
\tuplet 3/2 { e8^1 g^2 c^5}
\tuplet 3/2 { g_5 c_2 e_1}
}
\relative c'
Hi all
First of all, wish a happy New Year to all of you!
I'm struggling with a collision of fingerings and a tuplet number when a
slur is around:
\version "2.24.0"
\relative c' {
\time 2/4
\tuplet 3/2 { e8^1 g^2 c^5}
\tuplet 3/2 { g_5 c_2 e_1}
}
\relative c'
On Tue, Nov 22, 2022 at 3:37 PM Leo Correia de Verdier <
leo.correia.de.verd...@gmail.com> wrote:
> That is not another bug, that is because I only redefined the regular
> barline
>
D'Oh. Of course. Thanks...
> Another curious thing is that bar six prints right for me, even without
> barlines
That is not another bug, that is because I only redefined the regular barline
(not the double) to print on the beginning of staves. Add:
\defineBarLine "||" #'("||" "|" "||”)
to the layout block and you’re back. That needs to be done for every kind of
barline you use.
Another curious thing
Ha.
So it works. but also reveals another bug
Note small change in bar 5: now the bar 6 line is gone again, and so it's
the correctly accounted accidental spacing...
L
\version "2.22.1"
\layout {
\override Score.Clef.break-visibility = #'#(#f #f #f) % make only the
first clef visible
}
\d
Noice, thanks Leo, this is enough of a workaround for my current state,
thanks for figuring that out
Cheers,
Luca
On Tue, 22 Nov 2022, 14:04 Leo Correia de Verdier, <
leo.correia.de.verd...@gmail.com> wrote:
> Hi Luca!
>
> This could well be a bug. In the context you have shown you can work
> ar
Hi Luca!
This could well be a bug. In the context you have shown you can work around it
by printing the barlines at the beginning of staves too, by adding
\defineBarLine "|" #'("|" "|" "|”)
to the layout block.
HTH
/Leo
> 22 nov. 2022 kl. 13:30 skrev Luca Fascione :
>
> Ok, so, small source at
Ok, so, small source at the bottom
[image: image.png]
See how the stems of the first columns in bars 2, 6, 10 all line up,
whereas on bars 3, 7, 11 they don't...
L
\version "2.22.1"
\layout {
\override Score.Clef.break-visibility = #'#(#f #f #f) % make only the
first clef visible
}
m =
It seems to have something to do with this:
\override Clef.break-visibility = #'#(#f #f #f)
I'm working on shortening the source
L
On Tue, Nov 22, 2022 at 12:25 PM Luca Fascione wrote:
> Ha. Ok, I'll whittle it down to something small that repros it then.
> Thanks Leo!
> L
>
> On Tue, 22 Nov
Ha. Ok, I'll whittle it down to something small that repros it then.
Thanks Leo!
L
On Tue, 22 Nov 2022, 12:00 Leo Correia de Verdier, <
leo.correia.de.verd...@gmail.com> wrote:
> Hi Luca!
>
> This works quite well when I try to replicate it, so the code producing
> the error is probably needed to
Hi Luca!
This works quite well when I try to replicate it, so the code producing the
error is probably needed to solve this. Try to make a minimal example. That
said, one could guess that it could have something to do with break-alignments.
Best
/Leo
> 22 nov. 2022 kl. 11:27 skrev Luca Fascion
Hi all,
In a sheet I'm working on I'm observing that the accidentals on the first
bar of a line aren't handling collisions with the start-of-line bracket and
bar, while inbetween bars this works just fine (see attached image).
Where do I look for hints on how to fix this?
Many thanks,
Luca
[imag
zo de 2022 0:05
Para: Robert Mengual ; lilypond-user@gnu.org
Asunto: Re: Stem.note-collision-threshold
Hi Robert,
Le 11/03/2022 à 18:05, Robert Mengual a écrit :
> Hello everyone,
>
> I am developing a custom music notation in which distance between
> notes is different from the stan
causes notes in the same chord that are 1 tone away to
overlap. I wanted to fix this by overriding
Stem.note-collision-threshold to 1.5 (which would solve it). However,
it won't allow to pass float numbers. My question is, shouldn't it
allow them? Why not?
Comparing floats is haz
.
I wanted to fix this by overriding Stem.note-collision-threshold to 1.5 (which
would solve it). However, it won't allow to pass float numbers. My question is,
shouldn't it allow them? Why not?
In any case, does anyone know how might I approach this challenge in a
different way? I tri
A quick workaround:
\version "2.23.5"
global = {
\time 6/8
\tempo "Allegro"
}
goUp = { \change Staff = "right"
\stemDown
}
goDown = { \change Staff = "left"
\stemUp
}
right = \relative c'' {
\global
\once\override Fingering.cross-staff = ##f
8-2-4 \goDown \goUp
Le 05/01/2022 à 20:59, Michael Rivers a écrit :
The fingering here collides with the tempo. If the cross-staff beams
are commented out (all notes on the upper staff), the fingering
displays fine.
Is there a workaround? Am I doing something wrong?
\version "2.23.5"
global = {
\time 6/8
\t
The fingering here collides with the tempo. If the cross-staff beams are
commented out (all notes on the upper staff), the fingering displays fine.
Is there a workaround? Am I doing something wrong?
\version "2.23.5"
global = {
\time 6/8
\tempo "Allegro"
}
goUp = { \change Staff = "right"
Hi Xavier;
I have implemented as you have suggested and it seems to work just fine.
Thanks,
Ken
On Mon, Sep 20, 2021 at 11:49 PM Xavier Scheuer wrote:
>
> On Tue, 21 Sept 2021 at 05:01, Kenneth Wolcott
> wrote:
> >
> > Thanks, Carl.
> >
> > Here's the erroi stream with the reduced Lilypond
On Tue, 21 Sept 2021 at 05:01, Kenneth Wolcott
wrote:
>
> Thanks, Carl.
>
> Here's the erroi stream with the reduced Lilypond code.
Hello Kenneth,
You do not use Full Measure Rests (these appear centered horizontally in
the middle of the measure).
But I would use them with \voiceTwo or \overrid
gt; Drawing systems...
> Hungarian_March_from_La_Damnation_de_Faust_MWE.ly:22:17: warning:
> cannot resolve rest collision: rest direction not set
> { \stemDown
> d,1\rest d,1\rest d,1\rest d,1\rest b1\rest b1\rest }
> Hungarian_March_from_La_Damnatio
output to `Hungarian_March_from_La_Damnation_de_Faust_MWE.midi'...
Finding the ideal number of pages...
Fitting music on 1 page...
Drawing systems...
Hungarian_March_from_La_Damnation_de_Faust_MWE.ly:22:17: warning:
cannot resolve rest collision: rest direction not set
{ \stemDown
d,1\rest d,
have a direction that will cause a
collision?
>
> I tried using \stemDown, but that had no effect.
>
> warning:
>
> blah.ly:34:7: warning: cannot resolve rest collision: rest direction not
set
> {
> d,1\rest d,
see attachment of what looks fine (to me) even though I received the warnings...
On Mon, Sep 20, 2021 at 6:06 PM Kenneth Wolcott
wrote:
>
> why must a full measure rest (2/2) have a direction that will cause a
> collision?
>
> I tried using \stemDown, but that had no effe
why must a full measure rest (2/2) have a direction that will cause a collision?
I tried using \stemDown, but that had no effect.
warning:
blah.ly:34:7: warning: cannot resolve rest collision: rest direction not set
{
d,1\rest d,1\rest d,1\rest d,1\rest b1\rest b1\rest
Le 31/05/2021 à 22:38, Valentin Petzel a écrit :
Hello Stéphane,
If you want manual control you can try to move New_fingering_engraver from
Voice to Staff. The Y-position has to be tweaked manually (which would kind of
not work if the side-axis-interface is used).
It is somewhat of a hack, to g
Hello Stéphane,
If you want manual control you can try to move New_fingering_engraver from
Voice to Staff. The Y-position has to be tweaked manually (which would kind of
not work if the side-axis-interface is used).
It is somewhat of a hack, to get this done propery we’d need to create an
engr
Bonjour Stéphane,
The example you want shows three voices while your file has only two...
So I'd do something like:
\version "2.20.0"
\new Staff \relative c' <<
\new Voice {
\voiceOne
\set fingeringOrientations = #'(left)
2
}
\new Voice {
\voiceTwo
\set fingeringOrienta
Hello,
I'm trying to put fingering information in a lilypond file and the result I
get is not correct.
I extracted a simple case in the file attached.
With lilypond, I get that :
[image: image.png]
The for is displayed in the same place that the note...
I try to have something li
> On 6 Dec, 2020, at 3:55 PM, Matthew Fong wrote:
>
> Hello Fr Samuel,
>
> It sounds like we are solving almost the same issue with note entry, and
> Aaron Hill created a function which basically scales note values so that they
> group together nicely. And the clutter from manual scaling is re
Hello Fr Samuel,
It sounds like we are solving almost the same issue with note entry, and
Aaron Hill created a function which basically scales note values so that
they group together nicely. And the clutter from manual scaling is removed
entirely.
However, I am using fixed time (1/4). And to 'for
Hi there,
> It tightens the spacing between notes which are inside a slur so that the
> musical sense is clear without the usual bow (though, it’s a separate setting
> to actually omit the bow). Attached are two versions of the same antiphon:
> the first uses the usual bow for slurs, the secon
> On 6 Dec, 2020, at 12:00 PM, Kieren MacMillan
> wrote:
>
> I’m hoping to avoid the Slur_spacing_engraver entirely. ;)
> What does it do exactly?
>
It tightens the spacing between notes which are inside a slur so that the
musical sense is clear without the usual bow (though, it’s a separate
Hi,
> Closer to just left of the first choir word. There can be some “springiness”
> in its placement for spacing reasons, so long as it doesn’t collide with the
> words on either side and there is some clear whitespace around it (i.e. I’d
> like to avoid a “word*word” look).
Thanks.
> In th
> On 6 Dec, 2020, at 10:37 AM, Kieren MacMillan
> wrote:
>
> Where is the asterisk supposed to sit?
>
> Horizontal: Just to the right of the last cantor-only word? Just to the left
> of the first choir word? Centred between those words?
Closer to just left of the first choir word. There can
Hi,
> This is working fine for my hymns, but when I tried using it with the
> antiphons, which have an asterisk in them to indicate when the choir joins
> the cantor, the spacing around said asterisk is too tight in some cases.
Where is the asterisk supposed to sit?
Horizontal: Just to the rig
> On 5 Dec, 2020, at 1:46 PM, Kieren MacMillan
> wrote:
>
> Hi there,
>
>> I’m still working on getting my modified slur spacing issues worked out and
>> have yet to come up with a solution for the collision between \set stanza =
>> "*"
>
>
Hi there,
> I’m still working on getting my modified slur spacing issues worked out and
> have yet to come up with a solution for the collision between \set stanza =
> "*"
I honestly can’t understand what you’re trying to achieve… =\
Having done a lot of work with Sche
I’m still working on getting my modified slur spacing issues worked out and
have yet to come up with a solution for the collision between \set stanza = "*"
and the words when a slur occurs on either side of the asterisk. (You’ll note
that the first asterisk in the MWE doesn’t have an
Dear community,
is there a way to avoid the collision between ledger lines and beams in the
following example:
\version "2.20.0"
Music = {
\time 6/8 \clef "treble_8"
r8 g''-> gis fis' r ais
}
\new Staff \Music
Could this be done automatically if there are
On Sat, 17 Oct 2020 at 18:29, Marc Shepherd wrote:
>
> Kieren's example does indeed work with LP 2.21.2. However, the
distribution for 2.21.2 seems to "break" a number of other functions; for
instance, \fermataMarkup no longer works.
>
> Anyhow, I am still in the market for a better way to do this
Le 17/10/2020 à 18:28, Marc Shepherd a écrit :
Kieren's example does indeed work with LP 2.21.2. However, the
distribution for 2.21.2 seems to "break" a number of other functions;
for instance, \fermataMarkup no longer works.
Use \fermata.
http://lilypond.org/doc/v2.21/Documentation/changes
Kieren's example does indeed work with LP 2.21.2. However, the distribution
for 2.21.2 seems to "break" a number of other functions; for instance,
\fermataMarkup no longer works.
Anyhow, I am still in the market for a better way to do this, but for the
time being will just turn off bar numbers sel
Hi Marc,
> In your example, the rehearsal letters printed twice at the top of the winds
> group. I don't know if it matters that I am on version 2.20
It may.
> Also, if I am reading the code correctly, in a passage where only the brass
> and strings play, no marks would print on that system. T
If you want to try 2.21.2 (as opposed to 2.21.7) see
https://lilypond.org/download/binaries/mingw/ for which Windows releases (for
example) are available for download.
On 17/10/2020 15:46, Marc Shepherd wrote:
Hi Kieren,
In your example, the rehearsal letters printed twice at the top of the w
Hi Kieren,
In your example, the rehearsal letters printed twice at the top of the
winds group. I don't know if it matters that I am on version 2.20, whereas
you specified 2.21.2, which is not publicly available from the LP website.
Also, if I am reading the code correctly, in a passage where only
Hi Marc,
> What I want is to print the MarkLine twice, once above Violin I, and once at
> the top of each system.
In recent versions, you can just add the engravers to the appropriate
StaffGroup contexts (see below). Does that solve your problem?
Cheers,
Kieren.
\version "2.21.2"
\layou
; \repeat unfold 56 { c4 }
>> }
>> }
>> >>
>> }
>> >>
>> }
>>
>> [image: Collision.PNG]
>>
>>
> The BarNumber is not spaced relative to the StaffGroup any more. It is
> spaced relative to th
Bracket.collapse-height = #4
>> \new Staff {
>> \key f \major \relative c' {
>> \repeat unfold 56 { c4 }
>> }
>> }
>> >>
>> }
>> >>
>> }
>>
>> [image: Collision.PNG]
>>
>
PNG]
>
>
The BarNumber is not spaced relative to the StaffGroup any more. It is
spaced relative to the MarkLine context (you can see this by commenting out
your VerticalAxisGroup.staff-staff-spacing override).
The MarkLine context is spaced relative to the Staff (as can be seen by the
overrid
; }
>
> [image: Collision.PNG]
>
> On Fri, Oct 16, 2020 at 3:58 PM Xavier Scheuer
> wrote:
>
>> On Fri, 16 Oct 2020 at 20:55, Marc Shepherd wrote:
>> >
>> > In the example shown below, lilypond is shifting the measure number
>> (85) down, becaus
e: Collision.PNG]
On Fri, Oct 16, 2020 at 3:58 PM Xavier Scheuer wrote:
> On Fri, 16 Oct 2020 at 20:55, Marc Shepherd wrote:
> >
> > In the example shown below, lilypond is shifting the measure number (85)
> down, because it thinks there is a collision with the rehearsal le
On Fri, 16 Oct 2020 at 20:55, Marc Shepherd wrote:
>
> In the example shown below, lilypond is shifting the measure number (85)
down, because it thinks there is a collision with the rehearsal letter "C".
But in fact there is no collision: the 85 would be just fine in its norma
In the example shown below, lilypond is shifting the measure number (85)
down, because it thinks there is a collision with the rehearsal letter "C".
But in fact there is no collision: the 85 would be just fine in its normal
position. This occurs only where a rehearsal letter coincide
Am Do., 11. Juni 2020 um 08:50 Uhr schrieb Pierre Perol-Schneider
:
>
> Hi Paolo,
>
> Le mer. 10 juin 2020 à 22:29, Paolo Prete a écrit :
>>
>> Hello,
>>
>> as you can see in Lilybin's output, the below expression produces a
>> collision:
>>
Hi Paolo,
Le mer. 10 juin 2020 à 22:29, Paolo Prete a écrit :
> Hello,
>
> as you can see in Lilybin's output, the below expression produces a
> collision:
>
> { \repeat tremolo 8 { aes'16 bes' } }
>
> http://lilybin.com/tmdugu/1
>
> What
Hello,
as you can see in Lilybin's output, the below expression produces a
collision:
{ \repeat tremolo 8 { aes'16 bes' } }
http://lilybin.com/tmdugu/1
What's wrong and how can I fix it?
Thanks!
Maybe another solution could be to reduce the clef size, e.g.:
\version "2.20.0"
\paper {
line-width = 50
}
\layout {
indent = 0
system-count = 1
}
<<
\new Staff { R2.*3 c''8 8 8 8 8 8 8 8 8 8 8 8 }
\new Staff { R2. c''4 r r c'' r r r e'' r r d'' r }
\new Staff {
\clef F \time 3/
Le lun. 1 juin 2020 à 08:10, Josiah Boothby a écrit :
> Well, now at least I know of a way to move it around, but I have no
> idea what the pair of numbers for x-extent mean (and #'(-5 . 5) puts
> the clef in an even stranger place).
...
Maybe playing with other settings wil help for a better p
Basically, X-extent will define the X space dimension used by the clef.
1 is the height between two lines in a staff.
Here, #'(-5 . 5) stays for 5 spaces on the left side of the clef and 5
spaces on the right side.
Too much, of course; you'll have to find the right figures according to
your score.
Well, now at least I know of a way to move it around, but I have no
idea what the pair of numbers for x-extent mean (and #'(-5 . 5) puts
the clef in an even stranger place). Looking through the documentation
only tells me that X-extent takes two numbers, but doesn't actually
inform me of what those
Hi Josiah,
Maybe try:
\version "2.20.0"
{
\clef F \time 3/4
R2.*3
\clef G
g4 r r g r r
\once\override Staff.Clef.X-extent = #'(-5 . 5)
\clef F
}
and properly set the extent.
HTH.
Cheers,
Pierre
Le lun. 1 juin 2020 à 07:32, Josiah Boothby a écrit :
> I'm struggling to increase the
I'm struggling to increase the padding for a cautionary clef in a
slightly crowded line, since it's colliding with rests when there are
notes on other lines. Attached is an image of the score I'm working
with as I'm struggling to come up with a concise test snippet that
doesn't have other problems.
1 - 100 of 727 matches
Mail list logo
