Re: Line breaking issue
Aww, buried in this explanation is the fact that you are "sharing the gospel" of LilyPond with your students: Fantastic!!! Hwaen Ch'uqi On 8/12/21, Rachel Green wrote: > Thanks all! That did fix the problem. A student typeset this for me, and I > was so fixated on the cadenza measure, I did not check the syntax of the > first measure well. > > Rachel > >> On Aug 12, 2021, at 12:24 PM, David Kastrup wrote: >> >> Valentin Petzel writes: >> >>> Hello Rachel, >>> >>> As others have said before, the Beam syntax is wrong, you need to >>> specify >>> >>> Note[ note note note] >>> >>> Instead of >>> >>> [note note note note] >>> >>> (the same way as slurs work). The big problem here is that Lilypond by >>> default >>> forbids breaks during Beams, which is normally only relevant when you do >>> have >>> Beaming over Measures. But in your case Lilypond is so confused, that it >>> >>> basically does not know exactly, where the beams are. So it thinks you >>> have a >>> beam going on when you haven’t. Fix the beams and it will work! If >>> everythings >>> works, Lilypond will in fact break this by itself, without you telling it >>> to. >>> >>> Just a remark: You are using \voiceOne and \oneVoice for what I assume to >>> be >>> different hands. This is not good, as \oneVoice will change it’s >>> behaviour >>> depending on the note position, so if you were to change the clef or >>> transpose >>> the piece or something this might change the direction. Instead you can >>> either >>> use \voiceOne/\voiceTwo or \stemUp/\stemDown. >> >> \stemUp/\stemDown is pretty much always a very bad idea to use in >> anything but the definitions of more complex voice-changing commands >> that also cater for notehead collision strategies and other stuff. >> >> It was probably a mistake to make those explicit commands rather than >> requiring them to be entered as overrides. >> >> -- >> David Kastrup > >
Re: Line breaking issue
Thanks all! That did fix the problem. A student typeset this for me, and I was so fixated on the cadenza measure, I did not check the syntax of the first measure well. Rachel > On Aug 12, 2021, at 12:24 PM, David Kastrup wrote: > > Valentin Petzel writes: > >> Hello Rachel, >> >> As others have said before, the Beam syntax is wrong, you need to specify >> >> Note[ note note note] >> >> Instead of >> >> [note note note note] >> >> (the same way as slurs work). The big problem here is that Lilypond by >> default >> forbids breaks during Beams, which is normally only relevant when you do >> have >> Beaming over Measures. But in your case Lilypond is so confused, that it >> basically does not know exactly, where the beams are. So it thinks you have >> a >> beam going on when you haven’t. Fix the beams and it will work! If >> everythings >> works, Lilypond will in fact break this by itself, without you telling it to. >> >> Just a remark: You are using \voiceOne and \oneVoice for what I assume to be >> different hands. This is not good, as \oneVoice will change it’s behaviour >> depending on the note position, so if you were to change the clef or >> transpose >> the piece or something this might change the direction. Instead you can >> either >> use \voiceOne/\voiceTwo or \stemUp/\stemDown. > > \stemUp/\stemDown is pretty much always a very bad idea to use in > anything but the definitions of more complex voice-changing commands > that also cater for notehead collision strategies and other stuff. > > It was probably a mistake to make those explicit commands rather than > requiring them to be entered as overrides. > > -- > David Kastrup
Re: Line breaking issue
Valentin Petzel writes: > Hello Rachel, > > As others have said before, the Beam syntax is wrong, you need to specify > > Note[ note note note] > > Instead of > > [note note note note] > > (the same way as slurs work). The big problem here is that Lilypond by > default > forbids breaks during Beams, which is normally only relevant when you do have > Beaming over Measures. But in your case Lilypond is so confused, that it > basically does not know exactly, where the beams are. So it thinks you have a > beam going on when you haven’t. Fix the beams and it will work! If > everythings > works, Lilypond will in fact break this by itself, without you telling it to. > > Just a remark: You are using \voiceOne and \oneVoice for what I assume to be > different hands. This is not good, as \oneVoice will change it’s behaviour > depending on the note position, so if you were to change the clef or > transpose > the piece or something this might change the direction. Instead you can > either > use \voiceOne/\voiceTwo or \stemUp/\stemDown. \stemUp/\stemDown is pretty much always a very bad idea to use in anything but the definitions of more complex voice-changing commands that also cater for notehead collision strategies and other stuff. It was probably a mistake to make those explicit commands rather than requiring them to be entered as overrides. -- David Kastrup
Re: Line breaking issue
Hello Rachel, As others have said before, the Beam syntax is wrong, you need to specify Note[ note note note] Instead of [note note note note] (the same way as slurs work). The big problem here is that Lilypond by default forbids breaks during Beams, which is normally only relevant when you do have Beaming over Measures. But in your case Lilypond is so confused, that it basically does not know exactly, where the beams are. So it thinks you have a beam going on when you haven’t. Fix the beams and it will work! If everythings works, Lilypond will in fact break this by itself, without you telling it to. Just a remark: You are using \voiceOne and \oneVoice for what I assume to be different hands. This is not good, as \oneVoice will change it’s behaviour depending on the note position, so if you were to change the clef or transpose the piece or something this might change the direction. Instead you can either use \voiceOne/\voiceTwo or \stemUp/\stemDown. Cheers, Valentin signature.asc Description: This is a digitally signed message part.
Re: Line breaking issue
Several things do not work when I open the piece with version 22
Notablly, the [ sign must be after the note, not before
f'32[( df df af)] and not [f'32( df df af)]
\up is refused for me
As for the \break, _it works if you add an invisible bar _
\bar ""
before it
\voiceOne {
f'32[( df df af)] \oneVoice f[( df df af)] f''[( df df af)] af'[( f df df)]
\oneVoice af[( f df df)] \voiceOne af''[( f df df)] \oneVoice |
\bar ""
\break
}
Le 12.08.21 à 19:35, Rachel Green a écrit :
For some reason, the \break command doesn’t seem to be working in this example. I need a
new line to start after the first measure so that all the notes of the following measure
can fit on the same line. Any ideas? I’ve tried adding breaks in the cadenza section to
see if they work elsewhere using \bar “” \break , but I can’t get the line to break
anywhere.
Best,
Rachel
\version "2.19.80"
\language "english"
#(set-global-staff-size 20)
\header {
title = \markup \fontsize #2 "Waltz"
}
Treble = \relative c''
{
\clef treble
\tempo "Andante"
\time 6/8
\key df \major
\voiceOne [f'32( df df af)] \oneVoice [f( df df af)] \voiceOne [f''( df df af)] [af'( f
df df)] \oneVoice [af( f df df)] \voiceOne [af''( f df df)] \oneVoice |
\break
\cadenzaOn
\up \ottava #1 f'64([ df df bf af af f f \ottava #0 df df bf af af f f df df
bf af af f f
df df bf af af f f df f f af af bf df df f f af af bf df df f f af af bf df df f f
af af)] |
\break \bar ""
\break
}
\score {
\new GrandStaff
<<
\new Staff = "treble" { \Treble }
>>
}
--
Silvain Dupertuis
Route de Lausanne 335
1293 Bellevue (Switzerland)
tél. +41-(0)22-774.20.67
portable +41-(0)79-604.87.52
web: silvain-dupertuis.org
RE: Line breaking issue
Rachel,
Beaming command starts after the first note, e.g., d [ a b c ]
See if the attached works.
Mark
From: lilypond-user [mailto:lilypond-user-bounces+carsonmark=ca.rr@gnu.org]
On Behalf Of Rachel Green
Sent: Thursday, August 12, 2021 10:36 AM
To: lilypond-user
Subject: Line breaking issue
For some reason, the \break command doesn’t seem to be working in this example.
I need a new line to start after the first measure so that all the notes of the
following measure can fit on the same line. Any ideas? I’ve tried adding breaks
in the cadenza section to see if they work elsewhere using \bar “” \break , but
I can’t get the line to break anywhere.
Best,
Rachel
\version "2.19.80"
\language "english"
#(set-global-staff-size 20)
\header {
title = \markup \fontsize #2 "Waltz"
}
Treble = \relative c''
{
\clef treble
\tempo "Andante"
\time 6/8
\key df \major
\voiceOne [f'32( df df af)] \oneVoice [f( df df af)] \voiceOne [f''( df df
af)] [af'( f df df)] \oneVoice [af( f df df)] \voiceOne [af''( f df df)]
\oneVoice |
\break
\cadenzaOn
\up \ottava #1 f'64([ df df bf af af f f \ottava #0 df df bf af af f f df df
bf af af f f
df df bf af af f f df f f af af bf df df f f af af bf df df f f af af bf df
df f f af af)] |
\break \bar ""
\break
}
\score {
\new GrandStaff
<<
\new Staff = "treble" { \Treble }
>>
}
\version "2.19.80"
\language "english"
#(set-global-staff-size 20)
\header {
title = \markup \fontsize #2 "Waltz"
}
Treble = \relative c''
{
\clef treble
\tempo "Andante"
\time 6/8
\key df \major
\voiceOne f'32[( df df af)] \oneVoice f[(df df af)]
\voiceOne f''[( df df af)] af'[( f df df)]
\oneVoice af[( f df df)] \voiceOne af''[( f df df)] \oneVoice |
\break
\cadenzaOn
\ottava #1 f'64([ df df bf af af f f
\ottava #0 df df bf af af f f df df bf af af f f
df df bf af af f f df f f af af bf df df f f af af bf df df f f af af bf df df f f af af)] |
\break \bar ""
\break
}
\score {
\new GrandStaff
<<
\new Staff = "treble" { \Treble }
>>
}
Re: Line breaking issue
Hi Rachel,
Am 12.08.21 um 19:35 schrieb Rachel Green:
For some reason, the \break command doesn’t seem to be working in this
example. I need a new line to start after the first measure so that
all the notes of the following measure can fit on the same line. Any
ideas? I’ve tried adding breaks in the cadenza section to see if they
work elsewhere using \bar “” \break , but I can’t get the line to
break anywhere.
Best,
Rachel
\version "2.19.80"
\language "english"
#(set-global-staff-size 20)
\header {
title = \markup \fontsize #2 "Waltz"
}
Treble = \relative c''
{
\clef treble
\tempo "Andante"
\time 6/8
\key df \major
\voiceOne [f'32( df df af)] \oneVoice [f( df df af)] \voiceOne [f''(
df df af)] [af'( f df df)] \oneVoice [af( f df df)] \voiceOne [af''( f
df df)] \oneVoice |
\break
\cadenzaOn
\up \ottava #1 f'64([ df df bf af af f f \ottava #0 df df bf af af
f f df df bf af af f f
df df bf af af f f df f f af af bf df df f f af af bf df df f f af
af bf df df f f af af)] |
\break \bar ""
\break
}
\score {
\new GrandStaff
<<
\new Staff = "treble" { \Treble }
>>
}
Unfortunately, the source code you posted does not compile. It uses
undefined commands like \up, and I'm surprised to see constructs like
"[f'32( df df af)]": beams are postfix in LilyPond.
Judging from the picture you attached, I'd suspect that \override
Beam.breakable = ##t might be helpful in your situation.
Lukas
Line breaking issue
For some reason, the \break command doesn’t seem to be working in this example.
I need a new line to start after the first measure so that all the notes of the
following measure can fit on the same line. Any ideas? I’ve tried adding breaks
in the cadenza section to see if they work elsewhere using \bar “” \break , but
I can’t get the line to break anywhere.
Best,
Rachel
[cid:40EAEF33-24D7-4BDF-A7A7-417759FC2330]
\version "2.19.80"
\language "english"
#(set-global-staff-size 20)
\header {
title = \markup \fontsize #2 "Waltz"
}
Treble = \relative c''
{
\clef treble
\tempo "Andante"
\time 6/8
\key df \major
\voiceOne [f'32( df df af)] \oneVoice [f( df df af)] \voiceOne [f''( df df
af)] [af'( f df df)] \oneVoice [af( f df df)] \voiceOne [af''( f df df)]
\oneVoice |
\break
\cadenzaOn
\up \ottava #1 f'64([ df df bf af af f f \ottava #0 df df bf af af f f df df
bf af af f f
df df bf af af f f df f f af af bf df df f f af af bf df df f f af af bf df
df f f af af)] |
\break \bar ""
\break
}
\score {
\new GrandStaff
<<
\new Staff = "treble" { \Treble }
>>
}
Re: line-breaking issue
Hello Ahanu, Thanks for sending the file. I had a good look at it. What we confront all the time when engraving is that music often simply does not fit the page. I can't find any way to make this piece fit on two pages at that staff size. The fact is, it's simply too long. Personally I find it readable if you leave out system-count = 20, but I understand that may not be your preference. If you set systems-per-page = 10 (and remove system-count) it looks good and spacious on three pages. You may have to compromise with that. You could reduce the staff-staff spacing, but I think you don't want that. Apart from these ideas, I am at a loss for a solution. I encountered a similar problem just recently with a 300 page string quartet I am engraving where some dense pages simply ran off (its complicated to explain). In the end the composer suggested going smaller, and it all looks fine and readable. In my case also, there was no other way than reducing the staff size globally. Andrew
Re: line-breaking issue
Greetings Ahanu,
Without seeing something concrete, I think any further advice is
purely speculative at best. Not sure that _I_ will be able to shed
further light on the matter or that someone else will be willing to
wade through what is not an MWE, but it may be worth a shot to attach
your working code for review.
Hwaen Ch'uqi
On 8/9/20, Ahanu Banerjee wrote:
> I tried playing around with base-shortest-duration earlier, and it didn't
> help. Pasted Kevin's text to make sure, and nothing changed.
>
> -Ahanu
>
>
> On Sun, Aug 9, 2020 at 3:48 AM Kevin Barry wrote:
>
>> Hi Ahanu,
>>
>> It might help if you add this:
>> \layout {
>> \context {
>> \Score
>> \override SpacingSpanner.base-shortest-duration = #(ly:make-moment
>> 1/32)
>> }
>> }
>> It might make LilyPond more willing to squash sixteenths closer together
>> than it would normally like.
>>
>> Kevin
>>
>> On Sun, 2020-08-09 at 02:48 -0400, Ahanu Banerjee wrote:
>> > I tried setting systems-per-page to 10. It gave the same error as
>> > setting system-count to 20, and ran off the page.
>>
>> 3 measures per line is less than ideal, but it's readable. I'm
>> typesetting an etude book and am trying to avoid having fold-out pages
>> as much as possible.
>>
>>
>> On Sun, Aug 9, 2020, 02:41 Hwaen Ch'uqi wrote:
>> Greetings Ahanu,
>>
>> What happens if you set the systems-per-page variable to 10 instead
>> of
>> using system-count = 20? Does the music then spill over onto a third
>> page? Just from experience, it seems that 48 sixteenth-notes per
>> line
>> would get rather cramped, no? I usually use 32-40 16ths per line as
>> my
>> guide.
>>
>> Hwaen Ch'uqi
>>
>>
>> On 8/9/20, Ahanu Banerjee wrote:
>> > Hello,
>> >
>> > An étude I'm typesetting needs to fit on 2 pages with reasonable
>> vertical
>> > space. Normally, I'd just set system-count in \paper (in this
>> case, 20
>> > systems in 2 US letter pages), but this time it says "warning:
>> cannot find
>> > line breaking that satisfies constraints" and just runs off the
>> page. If I
>> > don't set system-count, it gives me 25 cramped systems on 2 pages.
>> >
>> > The piece is almost entirely sixteenth notes in 4/4. Some systems
>> fill with
>> > 3 bars, others with 2, and I can't figure out why. Ideally, most
>> would have
>> > 3 bars, but manual line breaks won't fix it. I've checked for
>> rhythmic
>> > errors (every measure has a barcheck) and didn't find any. I don't
>> want to
>> > decrease the font size.
>> >
>> > Unfortunately, I can't come up with a tiny example to demonstrate
>> this
>> > behaviour. If anyone has suggestions or someone would be willing
>> to look
>> > over my file, I'd really appreciate it.
>> >
>> > Cheers,
>> > -Ahanu
>> >
>>
>>
>
Re: line-breaking issue
I tried playing around with base-shortest-duration earlier, and it didn't
help. Pasted Kevin's text to make sure, and nothing changed.
-Ahanu
On Sun, Aug 9, 2020 at 3:48 AM Kevin Barry wrote:
> Hi Ahanu,
>
> It might help if you add this:
> \layout {
> \context {
> \Score
> \override SpacingSpanner.base-shortest-duration = #(ly:make-moment
> 1/32)
> }
> }
> It might make LilyPond more willing to squash sixteenths closer together
> than it would normally like.
>
> Kevin
>
> On Sun, 2020-08-09 at 02:48 -0400, Ahanu Banerjee wrote:
> > I tried setting systems-per-page to 10. It gave the same error as
> > setting system-count to 20, and ran off the page.
>
> 3 measures per line is less than ideal, but it's readable. I'm
> typesetting an etude book and am trying to avoid having fold-out pages
> as much as possible.
>
>
> On Sun, Aug 9, 2020, 02:41 Hwaen Ch'uqi wrote:
> Greetings Ahanu,
>
> What happens if you set the systems-per-page variable to 10 instead
> of
> using system-count = 20? Does the music then spill over onto a third
> page? Just from experience, it seems that 48 sixteenth-notes per
> line
> would get rather cramped, no? I usually use 32-40 16ths per line as
> my
> guide.
>
> Hwaen Ch'uqi
>
>
> On 8/9/20, Ahanu Banerjee wrote:
> > Hello,
> >
> > An étude I'm typesetting needs to fit on 2 pages with reasonable
> vertical
> > space. Normally, I'd just set system-count in \paper (in this
> case, 20
> > systems in 2 US letter pages), but this time it says "warning:
> cannot find
> > line breaking that satisfies constraints" and just runs off the
> page. If I
> > don't set system-count, it gives me 25 cramped systems on 2 pages.
> >
> > The piece is almost entirely sixteenth notes in 4/4. Some systems
> fill with
> > 3 bars, others with 2, and I can't figure out why. Ideally, most
> would have
> > 3 bars, but manual line breaks won't fix it. I've checked for
> rhythmic
> > errors (every measure has a barcheck) and didn't find any. I don't
> want to
> > decrease the font size.
> >
> > Unfortunately, I can't come up with a tiny example to demonstrate
> this
> > behaviour. If anyone has suggestions or someone would be willing
> to look
> > over my file, I'd really appreciate it.
> >
> > Cheers,
> > -Ahanu
> >
>
>
Re: line-breaking issue
Hi Ahanu,
It might help if you add this:
\layout {
\context {
\Score
\override SpacingSpanner.base-shortest-duration = #(ly:make-moment 1/32)
}
}
It might make LilyPond more willing to squash sixteenths closer together
than it would normally like.
Kevin
On Sun, 2020-08-09 at 02:48 -0400, Ahanu Banerjee wrote:
> I tried setting systems-per-page to 10. It gave the same error as
> setting system-count to 20, and ran off the page.
3 measures per line is less than ideal, but it's readable. I'm
typesetting an etude book and am trying to avoid having fold-out pages
as much as possible.
On Sun, Aug 9, 2020, 02:41 Hwaen Ch'uqi wrote:
Greetings Ahanu,
What happens if you set the systems-per-page variable to 10 instead
of
using system-count = 20? Does the music then spill over onto a third
page? Just from experience, it seems that 48 sixteenth-notes per
line
would get rather cramped, no? I usually use 32-40 16ths per line as
my
guide.
Hwaen Ch'uqi
On 8/9/20, Ahanu Banerjee wrote:
> Hello,
>
> An étude I'm typesetting needs to fit on 2 pages with reasonable
vertical
> space. Normally, I'd just set system-count in \paper (in this
case, 20
> systems in 2 US letter pages), but this time it says "warning:
cannot find
> line breaking that satisfies constraints" and just runs off the
page. If I
> don't set system-count, it gives me 25 cramped systems on 2 pages.
>
> The piece is almost entirely sixteenth notes in 4/4. Some systems
fill with
> 3 bars, others with 2, and I can't figure out why. Ideally, most
would have
> 3 bars, but manual line breaks won't fix it. I've checked for
rhythmic
> errors (every measure has a barcheck) and didn't find any. I don't
want to
> decrease the font size.
>
> Unfortunately, I can't come up with a tiny example to demonstrate
this
> behaviour. If anyone has suggestions or someone would be willing
to look
> over my file, I'd really appreciate it.
>
> Cheers,
> -Ahanu
>
Re: line-breaking issue
I tried setting systems-per-page to 10. It gave the same error as setting system-count to 20, and ran off the page. 3 measures per line is less than ideal, but it's readable. I'm typesetting an etude book and am trying to avoid having fold-out pages as much as possible. On Sun, Aug 9, 2020, 02:41 Hwaen Ch'uqi wrote: > Greetings Ahanu, > > What happens if you set the systems-per-page variable to 10 instead of > using system-count = 20? Does the music then spill over onto a third > page? Just from experience, it seems that 48 sixteenth-notes per line > would get rather cramped, no? I usually use 32-40 16ths per line as my > guide. > > Hwaen Ch'uqi > > > On 8/9/20, Ahanu Banerjee wrote: > > Hello, > > > > An étude I'm typesetting needs to fit on 2 pages with reasonable vertical > > space. Normally, I'd just set system-count in \paper (in this case, 20 > > systems in 2 US letter pages), but this time it says "warning: cannot > find > > line breaking that satisfies constraints" and just runs off the page. If > I > > don't set system-count, it gives me 25 cramped systems on 2 pages. > > > > The piece is almost entirely sixteenth notes in 4/4. Some systems fill > with > > 3 bars, others with 2, and I can't figure out why. Ideally, most would > have > > 3 bars, but manual line breaks won't fix it. I've checked for rhythmic > > errors (every measure has a barcheck) and didn't find any. I don't want > to > > decrease the font size. > > > > Unfortunately, I can't come up with a tiny example to demonstrate this > > behaviour. If anyone has suggestions or someone would be willing to look > > over my file, I'd really appreciate it. > > > > Cheers, > > -Ahanu > > >
Re: line-breaking issue
Greetings Ahanu, What happens if you set the systems-per-page variable to 10 instead of using system-count = 20? Does the music then spill over onto a third page? Just from experience, it seems that 48 sixteenth-notes per line would get rather cramped, no? I usually use 32-40 16ths per line as my guide. Hwaen Ch'uqi On 8/9/20, Ahanu Banerjee wrote: > Hello, > > An étude I'm typesetting needs to fit on 2 pages with reasonable vertical > space. Normally, I'd just set system-count in \paper (in this case, 20 > systems in 2 US letter pages), but this time it says "warning: cannot find > line breaking that satisfies constraints" and just runs off the page. If I > don't set system-count, it gives me 25 cramped systems on 2 pages. > > The piece is almost entirely sixteenth notes in 4/4. Some systems fill with > 3 bars, others with 2, and I can't figure out why. Ideally, most would have > 3 bars, but manual line breaks won't fix it. I've checked for rhythmic > errors (every measure has a barcheck) and didn't find any. I don't want to > decrease the font size. > > Unfortunately, I can't come up with a tiny example to demonstrate this > behaviour. If anyone has suggestions or someone would be willing to look > over my file, I'd really appreciate it. > > Cheers, > -Ahanu >
line-breaking issue
Hello, An étude I'm typesetting needs to fit on 2 pages with reasonable vertical space. Normally, I'd just set system-count in \paper (in this case, 20 systems in 2 US letter pages), but this time it says "warning: cannot find line breaking that satisfies constraints" and just runs off the page. If I don't set system-count, it gives me 25 cramped systems on 2 pages. The piece is almost entirely sixteenth notes in 4/4. Some systems fill with 3 bars, others with 2, and I can't figure out why. Ideally, most would have 3 bars, but manual line breaks won't fix it. I've checked for rhythmic errors (every measure has a barcheck) and didn't find any. I don't want to decrease the font size. Unfortunately, I can't come up with a tiny example to demonstrate this behaviour. If anyone has suggestions or someone would be willing to look over my file, I'd really appreciate it. Cheers, -Ahanu
