Re: Spontini line break slurs

This has already been reported some time ago: https://github.com/paopre/Spontini/issues/18 You can bypass it by simply using two shapes: % \version "2.24.0" \include "../lib/ly/jssvg.ly" \score { \relative c' { c d e << {s8\jsShape "1" "

Spontini line break slurs

I think I may have run across a bug/limitation of Spontini. I was adjusting slurs. When I adjusted one that occurred over a line break I got unexpected results. I eventually figured out that only the part before the line break was changing even if I only moved the control points of the slur

Re: Empty chord construct and \break.

> > >>> > I am trying to typeset a stack of spoken lines above a multimeasure rest. >>> > This works fine when preceded by notes in the same system. However, when >>> > it follows a forced break, the output is not so desirable. Can anyone >>> > ex

Re: Empty chord construct and \break.

gt; wrote: > >> Am So., 28. Apr. 2024 um 06:25 Uhr schrieb Hwaen Ch'uqi < >> hwaench...@gmail.com>: >> > >> > Greetings, >> > >> > I am trying to typeset a stack of spoken lines above a multimeasure >> rest. This works fine when preceded

Re: Empty chord construct and \break.

ypeset a stack of spoken lines above a multimeasure > rest. This works fine when preceded by notes in the same system. However, > when it follows a forced break, the output is not so desirable. Can anyone > explain what I am missing? MWE below. > > > > \version "2.24.3" &

Re: Empty chord construct and \break.

Am So., 28. Apr. 2024 um 06:25 Uhr schrieb Hwaen Ch'uqi : > > Greetings, > > I am trying to typeset a stack of spoken lines above a multimeasure rest. > This works fine when preceded by notes in the same system. However, when it > follows a forced break, the output is not

Empty chord construct and \break.

Greetings, I am trying to typeset a stack of spoken lines above a multimeasure rest. This works fine when preceded by notes in the same system. However, when it follows a forced break, the output is not so desirable. Can anyone explain what I am missing? MWE below. \version "2.24.3&quo

Re: Snippet: Adding indicators to staves which split after a break

>> The easy question. The fourth line of the snippet reads: >>(PI_OVER_180 (/ (atan2 1 1) 34)) >> Surely that “34” should be “45”. > > Did you try changing it? ;) Yes. It breaks things slightly. I need to dive further down the rabbit-hole to work out why. >> The more difficult question.

Re: Snippet: Adding indicators to staves which split after a break

Hi Kevin, > I have two questions about this snippet: You forgot to include the snippet or a link! :) But I assume you mean https://lilypond.org/doc/v2.25/Documentation/snippets/vocal-music_003a-adding-indicators-to-staves-which-get-split-after-a-break > The easy question. The fourt

Snippet: Adding indicators to staves which split after a break

I have two questions about this snippet: The easy question. The fourth line of the snippet reads: (PI_OVER_180 (/ (atan2 1 1) 34)) Surely that “34” should be “45”. The more difficult question. This snippet adds two arrows to the bar line at the end of the staff. I have a case where there is

Re: tied sharps after line break

Ah I see. Yes that's the one. Op zondag 3 maart 2024 om 18:21:59 +00:00:00 schreef Werner LEMBERG : 2. LilyPond's default behaviour in this situation is (in my opinion) sub-optimal. It's a bug known since 15 years... Werner

Re: tied sharps after line break

> 2. LilyPond's default behaviour in this situation is (in my opinion) > sub-optimal. It's a bug known since 15 years... https://gitlab.com/lilypond/lilypond/-/issues/649 Werner

Re: tied sharps after line break

Op zondag 3 maart 2024 om 18:58:45 +01:00:00 schreef Hans Aikema : Does not yet cover the case Martin was looking for - omitting the second accidental in a situation of a line-break on a tied accidental. Can be done however by an explicit \omit, which should be only \once, because otherwise

Re: tied sharps after line break

Does not yet cover the case Martin was looking for - omitting the second accidental in a situation of a line-break on a tied accidental. Can be done however by an explicit \omit, which should be only \once, because otherwise it would omit accidentals from that point onwards. The correct

Re: tied sharps after line break

bumped into a situation similar to this tiny example (In the real score the linebreak happened at such a situation without a forced \break but the result was the same):\relative c' {c4 c c cis ~ |\breakcis cis cis d |}the sharp sign in the 2nd bar is printed twice. I am not sure

Re: tied sharps after line break

Op zondag 3 maart 2024 om 18:33:26 +01:00:00 schreef Hans Aikema : On 3 Mar 2024, at 17:26, Martin Tarenskeen wrote:  Hi LilyPonders, I bumped into a situation similar to this tiny example (In the real score the linebreak happened at such a situation without a forced \break

Re: tied sharps after line break

> On 3 Mar 2024, at 17:26, Martin Tarenskeen wrote: > >  > Hi LilyPonders, > > I bumped into a situation similar to this tiny example (In the real score the > linebreak happened at such a situation without a forced \break but the result > was the same): > &g

tied sharps after line break

Hi LilyPonders, I bumped into a situation similar to this tiny example (In the real score the linebreak happened at such a situation without a forced \break but the result was the same): \relative c' { c4 c c *cis* *~* | \break *cis* *cis* cis d | } the sharp sign in the 2nd bar

strange `break-align-symbols` behaviour

ture } { \override Score.MetronomeMark.break-align-symbols = #'(time-signature key-signature) \music } \paper { ragged-right = ##f } ``` I don't understand why the addition of `key-signature` to the `break-align-symbols` list makes 'T-note' left-align to the bar line — there is no key signature at this

Re: Extra space before line break before ossia staff

> Is this a bug? Yes , see https://gitlab.com/lilypond/lilypond/-/issues/4263 signature.asc Description: This is a digitally signed message part

Re: Extra space before line break before ossia staff

Solved with \set Staff.explicitKeySignatureVisibility = #end-of-line-invisible \version "2.24.3" \layout { ragged-right = ##t } mainKey = { \key es \major } \new StaffGroup { \new Staff = main \relative { \mainKey g'1 | \break << { g1 }

Extra space before line break before ossia staff

It seems to me that when an ossia staff (or similar supplementary staff) happens to begin at a line break, Lilypond meaninglessly sets space apart for a key signature before the line break even though there is no key signature printed there. Is this a bug? Is there a workaround? The output

Re: Score layout - ragged bottom and page break?

gt; \bookpart { > :: and the next score, and so forth :: > } > } > > One note - using \bookpart inserts a page break between parts, so no need > for any explicit \pageBreak commands. For some more details have a look at: > > http://lilypond.org/doc/v2.24/Documentation/notation/multiple-scores-in-a-book > -- > Michael > >

Re: Score layout - ragged bottom and page break?

so forth :: } } One note - using \bookpart inserts a page break between parts, so no need for any explicit \pageBreak commands. For some more details have a look at: http://lilypond.org/doc/v2.24/Documentation/notation/multiple-scores-in-a-book -- Michael

Score layout - ragged bottom and page break?

Hello, (Note: Lilypond v. 2.24.2, in Linux.) I am setting a group of pieces; each piece is in its own score block. I want each score to start on a new page, and the final page in each score to have a ragged-last-bottom, so that the systems are evenly spaced - these are duets, and I like no more

Re: Y-offset of dynamic text after break

Le dimanche 22 octobre 2023 à 13:48 -0700, Knute Snortum a écrit : > Is it true then that using extra-offset in these situations are the only way > to move the dynamic text? No, because there are still limits on how close vertical axis groups can get even without considering their outlines. Try

Re: Y-offset of dynamic text after break

baseline, > which is the VerticalAxisGroup of the Dynamics context. Without \break, > the VerticalAxisGroup contains two dynamics, "f" and "p", with "p" offset > compared to "f", which forces them to be at different positions. With > \break, the

Re: Y-offset of dynamic text after break

Hi, The DynamicText's Y-offset controls its position relative to its baseline, which is the VerticalAxisGroup of the Dynamics context. Without `\break`, the VerticalAxisGroup contains two dynamics, "f" and "p", with "p" offset compared to "f", which

Y-offset of dynamic text after break

Hi, everyone. I have a question for you, more than a need for a solution. It involves tweaking the Y-offset of a dynamic text after a break. Here is some code to illustrate what I mean: %%% \version "2.24.2" rh = \relative { c'4 4 4 4 | f,4 4 4 4 | f'4 4 4 4 | } lh = \relative

Re: Beam slope across break

Thank you! -- Knute Snortum On Sat, Aug 26, 2023 at 1:23 AM Jean Abou Samra wrote: > > In short, is there a way to control the slope of the beam after the > break, or > > some other way to deal with the situation? > > \alterBroken positions #'((-6.5 . -3.5) (-3.5 . -1)) Beam > > >

Re: Beam slope across break

> In short, is there a way to control the slope of the beam after the break, or > some other way to deal with the situation?   \alterBroken positions #'((-6.5 . -3.5) (-3.5 . -1)) Beam signature.asc Description: This is a digitally signed message part

Beam slope across break

on the second part of the beam. I have attached a PNG displaying the behavior with the code that produced it below. The first score shows how the default beam positions after the break don't look good, and the second shows my attempt to fix the situation. In short, is there a way to control

Re: Staff switch over page break spoils vertical spacing

On Sun, 9 Jul 2023 at 13:10, Jean Abou Samra wrote: > Le samedi 08 juillet 2023 à 17:44 +1000, Vaughan McAlley a écrit : > > When a staff-switch line goes over a page break, the first system in the > next page is stretched and may cover the next system. In the example here, > it

Re: Staff switch over page break spoils vertical spacing

n a staff-switch line goes over a page break, the first system in the > next page is stretched and may cover the next system. In the example here, > it nearly touches, but in a full score the top system is stretched beyond > the bottom of the page. > > In the wild, a system may stretch ov

Re: Staff switch over page break spoils vertical spacing

Le samedi 08 juillet 2023 à 17:44 +1000, Vaughan McAlley a écrit : > When a staff-switch line goes over a page break, the first system in the next > page is stretched and may cover the next system. In the example here, it > nearly touches, but in a full score the top system is stretch

Staff switch over page break spoils vertical spacing

Hi, When a staff-switch line goes over a page break, the first system in the next page is stretched and may cover the next system. In the example here, it nearly touches, but in a full score the top system is stretched beyond the bottom of the page. In the wild, a system may stretch over

Re: Non-local page-break oddities

to determine what exactly is causing the bad page-breaking results, maybe you are using the optimal-page-turn algorithm for example. Thanks for reminding me about the various page break algorithms.   I’d found that when I last had a chance to work on this project

Re: Non-local page-break oddities

Le lundi 24 avril 2023 à 23:33 -0400, Joel C. Salomon a écrit : > I’m getting close to finished with my first Lilypond project, a book of some > 30 scores.  I tried building the `\book` section piecemeal, including a > handful of scores and tweaking the page breaks, and then another batch, and

Re: Non-local page-break oddities

Dear Joel, I think that using multiple bookparts is a perfect strategy for this document based on this example, in which each score should nicely start on a new page. Without any minimal examples, it is hard to determine what exactly is causing the bad page-breaking results, maybe you are

Non-local page-break oddities

I’m getting close to finished with my first Lilypond project, a book of some 30 scores. I tried building the `\book` section piecemeal, including a handful of scores and tweaking the page breaks, and then another batch, and so on. \book { \scoreI \pageBreak \scoreII \pageBreak \scoreIII

Re: Coda without line break

Hi John, On Sat, Apr 15, 2023 at 7:03 AM John McWilliam wrote: > Hi, > > The enclosed attachment illustrates a Coda including a > line break, however: > > Well, actually it's illustrating two entirely separate scores that happen to be on the same page. The two

Coda without line break

Hi,    The enclosed attachment illustrates a Coda including a line break, however:  I want to remove the line break and have the Coda on line 1 keeping the jump text between the Main  and the Coda. Also, there should some space between the jump text and the start of the coda.I would

Re: Lilypond-book-preamble introducing page break after custom header

Le mercredi 15 mars 2023 à 22:49 +0100, Jean Abou Samra a écrit : > - > use `-dseparate-page-formats=pdf` if you want to get one output file per page > (or per system if also using lilypond-book-preamble.ly), > > > - > use `-dtall-page-formats=pdf` if you want to get squashed pages. P.S. Can

Re: Lilypond-book-preamble introducing page break after custom header

Le mercredi 15 mars 2023 à 17:32 -0400, Fr. Samuel Springuel a écrit : > The attached file compiles differently under 2.22 and 2.24: 2.24 introduces a > page break that isn’t present in 2.22.  This is causing some havoc in my > lyluatex tool chain.  Any idea what’s causing the proble

Lilypond-book-preamble introducing page break after custom header

The attached file compiles differently under 2.22 and 2.24: 2.24 introduces a page break that isn’t present in 2.22. This is causing some havoc in my lyluatex tool chain. Any idea what’s causing the problem and how to fix it? convert-ly doesn’t change anything in the file when upgrading

Re: changing ottavation text after line break

On Fri, 17 Feb 2023 at 19:26, Immanuel Asmus wrote: > > Hello, > > I’d like to have an OttavaBracket with ottavation "8", but after a line > break, the ottavation should read "(8)". I cannot figure out whether > this can be achieved with \alterBroke

changing ottavation text after line break

Hello, I’d like to have an OttavaBracket with ottavation "8", but after a line break, the ottavation should read "(8)". I cannot figure out whether this can be achieved with \alterBroken, since ottavation is not a feature of OttavaBracket. I r

Re: Clef change after end-repeat before break -- how?

>> Under 2.22 I do not get extra space. > > That’s still more curious. On 2.22.2 I get a warning > that the break is overwritten by another event, so we > don’t get the line break that I had specified and wanted. It's expected. 2.22 doesn't accept mid-measure breaks without a

Re: Clef change after end-repeat before break -- how?

On 28/01/2023 06:52, Ole V. Villumsen wrote: > Thanks, everyone, for your contributions. > > First of all Jean. Your code gives me exactly what I wanted. I haven’t > learned to use the internals, but see here that it’s useful. > >> Not sure, but my guess is that LilyPond might be trying to make

Re: Clef change after end-repeat before break -- how?

On 28/01/2023 16:51, David Kastrup wrote: > Jean Abou Samra writes: > >>> Le 28 janv. 2023 à 08:01, Darren Ng a écrit : >>> >>> [subject] How to define a macro that expands to a percussion "pitch"? >> >> >> It may be worth noting that LilyPond does not have macros, only >> variables and

Re: Clef change after end-repeat before break -- how?

Furthermore, for the record, the same trick also works in the case where there is no break after the end-repeat sign. In this case the second of the three inner lists in Score.BreakAlignment.break-align-orders governs the order. So I want to modify both the 1st and the 2nd list. From

Re: Clef change after end-repeat before break -- how?

o not get extra space. That’s still more curious. On 2.22.2 I get a warning that the break is overwritten by another event, so we don’t get the line break that I had specified and wanted. @Ralph Palmer, you may have forgot to put content into your message? At least none arrived here. Best,

RE: Clef change after end-repeat before break -- how?

: Clef change after end-repeat before break -- how? Hi, I am typesetting a movement with a repeat and a clef change right after the repeat. I have a suitable line break where the repeat ends and the clef change happens. Default Lilypond sets the new clef within the repeat, before the end-repeat

RE: Clef change after end-repeat before break -- how?

Subject: Clef change after end-repeat before break -- how? Hi, I am typesetting a movement with a repeat and a clef change right after the repeat. I have a suitable line break where the repeat ends and the clef change happens. Default Lilypond sets the new clef within the repeat, before the end-repeat

Re: Clef change after end-repeat before break -- how?

On 27/01/2023 22:35, Ole V. Villumsen wrote: > Hi, I am typesetting a movement with a repeat and a clef change right after > the repeat. I have a suitable line break where the repeat ends and the clef > change happens. Default Lilypond sets the new clef within the repeat, before

Re: Clef change after end-repeat before break -- how?

On Fri, Jan 27, 2023 at 1:36 PM Ole V. Villumsen < ole.villum...@protonmail.ch> wrote: > Hi, I am typesetting a movement with a repeat and a clef change right > after the repeat. I have a suitable line break where the repeat ends and > the clef change happens. Default Lilypond se

Clef change after end-repeat before break -- how?

Hi, I am typesetting a movement with a repeat and a clef change right after the repeat. I have a suitable line break where the repeat ends and the clef change happens. Default Lilypond sets the new clef within the repeat, before the end-repeat sign, which I don’t want and find meaningless in my

Re: Repost: LP 2.24.0 segno repeat where coda break is in the middle of a repeat volta block

Thank you, Kenneth, for posting this, you beat me to it. I'm editing lead sheets for a couple of ensembles and have run into the same issue. I have used the segno structure for the repeat and inserted \coda manually. I couldn't work out how to automate it with the \alternatives { { } { } }

Re: LP 2.24.0 segno repeat where coda break is in the middle of a repeat volta block

Hi David; Thank you so much for reminding me that there are ways to reduce the size of the pdf, decreasing the size to reduce the pain of downloading a huge attachment. Ken On Sun, Jan 22, 2023 at 8:35 AM David Wright wrote: > > On Sat 21 Jan 2023 at 15:51:16 (-0800), Kenneth Wolcott wrote:

Re: LP 2.24.0 segno repeat where coda break is in the middle of a repeat volta block

On Sat 21 Jan 2023 at 15:51:16 (-0800), Kenneth Wolcott wrote: > Using Lilypond 2.24.0, I engraved "Memory" (from "Cats") using the > example published in the Hal Leonard Easy Piano Songs book (the pdf > file generated from photos from this book are huge). I displayed your PDF at 60% size, and

Re: MetronomeMark and break-visibility

gt; > > { > >b1 > >\override Score.RehearsalMark.break-visibility = ##(#t #f #f) > >\mark \default > >\break > >b > > } > > > > Alas, the same for _Metronome_Mark fails, the MetronomeMark is not > > printed at all: > > > > { &

Re: MetronomeMark and break-visibility

Le 01/11/2022 à 12:55, Thomas Morley a écrit : Hi, the following code for _Rehearsal_Mark works as expected, i.e. the RehearsalMark is printed at end of line: { b1 \override Score.RehearsalMark.break-visibility = ##(#t #f #f) \mark \default \break b } Alas, the same

MetronomeMark and break-visibility

Hi, the following code for _Rehearsal_Mark works as expected, i.e. the RehearsalMark is printed at end of line: { b1 \override Score.RehearsalMark.break-visibility = ##(#t #f #f) \mark \default \break b } Alas, the same for _Metronome_Mark fails, the MetronomeMark is not printed

Re: Tie almost invisible before line break

> https://gitlab.com/lilypond/lilypond/-/issues/298 > > The workaround is increasing minimum-length. > > > \version "2.23.12" > > \paper { >ragged-right = ##t >indent = 0 > } > > \relative { >\voiceOne >d''8( c4 b a e'8\tw

Re: Tie almost invisible before line break

Le 17/09/2022 à 20:24, Knute Snortum a écrit : I have run into a situation that may be a bug or it may be I'm not doing something correctly. I have a \voiceOne note at a line break where the tie becomes nearly invisible. %%% \version "2.23.12" \paper { ragged-right = ##t

Tie almost invisible before line break

I have run into a situation that may be a bug or it may be I'm not doing something correctly. I have a \voiceOne note at a line break where the tie becomes nearly invisible. %%% \version "2.23.12" \paper { ragged-right = ##t indent = 0 } \relative { \voiceOne d''8( c4 b a e'8

Re: warning: forced break was overridden by some other event, should you be using bar checks?

a number of reasons why a break > > is disabled, and the information will come from different > > sources depending on the cause. It might be possible, > > though. My own take, however, would be to make \break > > override all kinds of restrictions altogether and > > ju

Re: warning: forced break was overridden by some other event, should you be using bar checks?

Le 13/01/2022 à 00:00, Jean Abou Samra a écrit : There is no position information in the diagnostic just because it is a bit inconvenient to do internally, as there can be a number of reasons why a break is disabled, and the information will come from different sources depending on the cause

Re: text spanner around a line break restates the text, this is not wanted

Hi Xavier; Thank you. Why is it so obvious when somebody points out what you do not see? :-( \facepalm :-( It seems (mostly) correct now. How do you get the text spanner to display all the way to the end of the bar? I'll look at the manual again to try to find out how I missed that

Re: text spanner around a line break restates the text, this is not wanted

On Wed, 23 Mar 2022 at 20:39, Kenneth Wolcott wrote: > > I missed some pertinent code: bars 37-42; enclosed below. > > (snip) > Hello, You have \stopTextSpan in measure 38, so it ends in measure 38. Furthermore you have Moderato in measure 39, do you really want the TextSpanner to continue

Re: text spanner around a line break restates the text, this is not wanted

I missed some pertinent code: bars 37-42; enclosed below. %\break % \tempo 2.=42 4(g' q | % m37 % \set Score.tempoHideNote = ##f 2.)\stopTextSpan| % m38 \tempo \markup { \bold \fontsize #3 "Moderato" } 2.=44 4(4. 8 |

Re: text spanner around a line break restates the text, this is not wanted

On Tue, Mar 22, 2022 at 11:57 PM Kenneth Wolcott wrote: > Thank you for your assistance, Leo. > > With your example I was able to remove the duplicate text in the text > spanner, but I was not able to get the text spanner to continue beyond bar > #38. > > So, I will spend more time studying what

Re: No line break after score

ine to swamp unknown first_staff_min_translation \override Staff.BarLine.Y-extent = #(cons -2 even-taller) \overrideProperty Score.NonMusicalPaperColumn.line-break-system-details .Y-offset #(- Y-pos even-taller) % wonky if even-taller isn't taller #}))) % cf lilypond-user/2

Re: Grace after break spacing

Le 18/03/2022 à 19:16, Knute Snortum a écrit : On Fri, Mar 18, 2022 at 10:47 AM Kieren MacMillan wrote: Hi Knute, I've run into -- maybe not a defect, but an "ugly" engraving problem Yeah… non-optimal for sure. In the meantime, does anyone know of a work-around? c''4 c c \tweak

Re: Grace after break spacing

On Fri, Mar 18, 2022 at 10:47 AM Kieren MacMillan wrote: > > Hi Knute, > > > I've run into -- maybe not a defect, but an "ugly" engraving problem > > Yeah… non-optimal for sure. > > > In the meantime, does anyone know of a work-around? > > c''4 c c \tweak extra-spacing-width #'(0 . 1.5) c > >

Re: Grace after break spacing

Hi Knute, > I've run into -- maybe not a defect, but an "ugly" engraving problem Yeah… non-optimal for sure. > In the meantime, does anyone know of a work-around? c''4 c c \tweak extra-spacing-width #'(0 . 1.5) c Hope that helps! Kieren.

Grace after break spacing

Hi all, I've run into -- maybe not a defect, but an "ugly" engraving problem in LilyPond. If there is a grace note after a break, the last measure before the break does not leave enough room for the last note. Here's a MWE: %%% \version "2.23.6" \relative { c''4 c c c

Re: No line break after score

Patrick Martin wrote: For example, in this picture, 22 follows directly on from the end of 21, and 23 from 22, etc. Or would this need to be implemented some other way? Are you a Tetris fan? Pseudoindent could help with the horizontal aspect. https://lsr.di.unimi.it/LSR/Item?id=1098 You

Re: No line break after score

Hello Patrick, hello Kieren (how is your musical going?), Considering how this probably does not make a lot of sense with variable instrumentation I guess the thing we actually want there is being able to break a system without skipping to the next line. This is something that is occasionally

Re: No line break after score

o duo, etc.) "automagically". Looking forward to seeing the solution! Kieren. > On Mar 11, 2022, at 11:44 AM, Patrick Martin wrote: > > Hello, > > Can anyone help with a layout query, please? Is there some way to allow a > score within a book to follow t

Re: bar count not displayed after partial measure followed by forced line break

Hi Brian; Thank you for your patience with me. I found the 2.23.6-1 doc tarball, downloaded it and made a web browser bookmark to it just like I did for 2.22.1 docs. I then carefully read section 1.2.5, looking for my situation. Since I am printing bar numbers in the default manner,

Re: bar count not displayed after partial measure followed by forced line break

At 14:36 20/02/2022 -0800, Kenneth Wolcott wrote: I'm not sure I totally understand your response. Evidently so. I'd like to see the bar number displayed on the next line as that is when the incomplete measure is completed. What, please, makes you think I didn't understand that? I indeed

Re: bar count not displayed after partial measure followed by forced line break

ure followed by forced line break > > > >I am engraving some music where there is a partial measure starting > >the music and later a measure is broken at a line break. To > >implement this I tried using: > >\bar "||" > >\break > >to display the end

Re: bar count not displayed after partial measure followed by forced line break

At 17:16 19/02/2022 -0800, Kenneth Wolcott wrote: bar count not displayed after partial measure followed by forced line break I am engraving some music where there is a partial measure starting the music and later a measure is broken at a line break. To implement this I tried using: \bar

Re: warning: forced break was overridden by some other event, should you be using bar checks?

gt; > Ken > > > > > > On Wed, Jan 12, 2022 at 2:20 PM Kenneth Wolcott > > > > > > wrote: > > > > Hi; > > > > > > > > Is there a bug in the Lilypond parser regarding bar checks? > > > > >

Re: warning: forced break was overridden by some other event, should you be using bar checks?

> On Wed, Jan 12, 2022 at 2:20 PM Kenneth Wolcott > > > > wrote: > > > Hi; > > > > > > Is there a bug in the Lilypond parser regarding bar checks? > > > > This isn't a parsing problem, it's an interpretation problem It s

Re: warning: forced break was overridden by some other event, should you be using bar checks?

; > >There is no problem with the bar checks after I disable the forced > > line breaks. > > > While bar checks are one frequent cause of inability > to honor a break, there can be others. Carl already > mentioned note extending their duration across the > break.

Re: warning: forced break was overridden by some other event, should you be using bar checks?

. The problem goes away when I disabled the forced line breaks, so I do think that there is a problem here, although it is an annoyance, not severe. There is no problem with the bar checks after I disable the forced line breaks. While bar checks are one frequent cause of inability to honor a break

Re: warning: forced break was overridden by some other event, should you be using bar checks?

s isn't a parsing problem, it's an interpretation problem It shows up > after parsing is completed. > > It is somewhere between bars 32 and 40. > > It will be somewhere where you have a /break command. > > You are trying to break a line where there is music on either side of a break > (e

Re: warning: forced break was overridden by some other event, should you be using bar checks?

ter parsing is completed. It is somewhere between bars 32 and 40. It will be somewhere where you have a /break command. You are trying to break a line where there is music on either side of a break (e.g. one voice has c1, the other voice has a2 \break a2.) Bar checks will catch this because you will have

Re: warning: forced break was overridden by some other event, should you be using bar checks?

k comment (determine location by use > of bisection), but, still, why can't Lilypond tell me which line in > the source is problematic? > > Thanks, > Ken Wolcott > > GNU LilyPond 2.22.1 > Processing `Walzer.ly' > Parsing... > Interpreting music...[8][16][24][32] > warning: f

warning: forced break was overridden by some other event, should you be using bar checks?

][32] warning: forced break was overridden by some other event, should you be using bar checks? [40][48][56] Preprocessing graphical objects... Interpreting music... MIDI output to `Walzer.midi'... Finding the ideal number of pages... Fitting music on 1 or 2 pages... Drawing systems... Converting

RE: Start new piece without line break (with title)

Hi Lukas and Leo, thank you for the extra suggestions. The line break issue was btw the next thing I wanted to learn. It still needs a little tweaking (e.g. horizontal spacing) but much more improved since the beginning. I think it would finally result in a quite acceptable output. Best

Re: Start new piece without line break (with title)

Some other changes: - encapsulate the piece-break machinery in a function - deal with pieces in c major :-) - reset clef/key change settings - etc. Lukas Am 07.01.22 um 17:20 schrieb Leo Correia de Verdier: Adding \once \override Staff.KeySignature. break-visibility = ##(#f #f #f

Re: Start new piece without line break (with title)

Adding \once \override Staff.KeySignature. break-visibility = ##(#f #f #f) \once \override Staff.Clef.break-visibility = ##(#f #f #f) \once \omit Score.BarNumber Together with \stopStaff helps avoids some of the strangeness if the new piece’s start happens to coincide

RE: Start new piece without line break (with title)

, 2022 11:14 PM To: lilypond-user@gnu.org Cc: Ruzsa Krisztián Subject: Re: Start new piece without line break (with title) Hi Ruzsa, Maybe this would be a slight improvement. Cheers, Valentin Am Donnerstag, 6. Jänner 2022, 17:10:09 CET schrieb Ruzsa Krisztián: > Hi everyone, > > I'd lik

Re: Start new piece without line break (with title)

Hi Ruzsa, Maybe this would be a slight improvement. Cheers, Valentin Am Donnerstag, 6. Jänner 2022, 17:10:09 CET schrieb Ruzsa Krisztián: > Hi everyone, > > I'd like to copy the layout of a small tune book. New pieces don't always > start in a new line, it usually occurs that the next song

Start new piece without line break (with title)

Hi everyone, I'd like to copy the layout of a small tune book. New pieces don't always start in a new line, it usually occurs that the next song starts somewhere in the middle of the line. Titles are placed before each piece (not above the staff) I found two helpful topics in the archive but

Re: parentheses break behaviour

Hi Jean, > In 2.22, you can try Thanks — that fixes this score. =) Kieren.

Re: parentheses break behaviour

Le 27/12/2021 à 23:01, Kieren MacMillan a écrit : Hi all, Is this expected and/or known behaviour? \version "2.21" { c'1 \tweak font-size 5 \parenthesize \breathe \break c'1 } I see that it's fixed in 2.23 [possibly as a side-effect of other changes]. What's the best workaroun

  1   2   3   4   5   6   7   8   9   10   >