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
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 othe
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 B
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 d
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)
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 br
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
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 rea
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 workin
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
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 -0
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:4
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
13 matches
Mail list logo
