Is there a way that I can take *total* control of page breaking?
I have a file in the form:
\version "2.24.3"
\include "file1" \noPageBreak
\include "file2" \pageBreak
% lots more lines like the above
\include "fileN"
and individual files such as:
% file1
\score {
\autoPageBreaksOff
%music
>> Is there a way that I can take *total* control of page breaking?
>
> I don't have a solution to offer but will comment that this is an
> issue I also ran into recently while trying to engrave parts for
> piano four hands.
See
https://gitlab.com/lilypond/lilypond/-/issues/902
Werner
On Mon, 23 Sep 2024, Werner LEMBERG wrote:
> See
>
> https://gitlab.com/lilypond/lilypond/-/issues/902
Yes. There are several different issues involved here - choosing the page
breaks based on both parts; engraving each part with exactly those breaks
even though they are not the breaks that wo
Hi,
When writing a simple song lead sheet i have the chord(name) above the
normal melody line.
Some guitarists like to use a capo and so I place a transposed chord(name)
below the main one.
To do this I used a function called "parenthesizeAllchords" which I freely
admit I plagarized from somewhere
On Mon, Sep 23, 2024 at 9:04 AM Colin Baguley wrote:
> Hi,
> When writing a simple song lead sheet i have the chord(name) above the
> normal melody line.
> Some guitarists like to use a capo and so I place a transposed chord(name)
> below the main one.
> To do this I used a function called "paren
Paul Scott writes:
> How can I make this happen in one staff with all the stems down?
>
> \version "2.25.19"
>
> \fixed c'' { << { e8( f~2.) } { e8( f d2.) } >> }
By telling LilyPond you want it in one Staff:
\new Staff \fixed c'' { << { e8( f~2.) } { e8( f d2.) } >> }
However, this also puts
On 2024-09-22 22:13, Paul Scott wrote:
How can I make this happen in one staff with all the stems down?
\version "2.25.19"
\fixed c'' { << { e8( f~2.) } { e8( f d2.) } >> }
In addition to the responses you already received:
- The reason that you get two staves is that you start the score w
On Mon, 23 Sep 2024, David Sumbler wrote:
> Is there a way that I can take *total* control of page breaking?
I don't have a solution to offer but will comment that this is an issue I
also ran into recently while trying to engrave parts for piano four hands.
These are usually printed on alternatin
Mats Bengtsson writes:
> or using the \voices command:
> \version "2.25.19"
> \new Staff \fixed c'' { \voices 2,4 << { e8( f~2.) } \\ { e8( f d2.) } >> }
LilyPond's normal order for stem-down voices top to bottom would rather
be
\voices 4,2
--
David Kastrup
On 2024-09-23 16:28, David Kastrup wrote:
Mats Bengtsson writes:
or using the \voices command:
\version "2.25.19"
\new Staff \fixed c'' { \voices 2,4 << { e8( f~2.) } \\ { e8( f d2.) } >> }
LilyPond's normal order for stem-down voices top to bottom would rather
be
\voices 4,2
Yes, but
On Mon, Sep 23, 2024 at 2:06 AM David Sumbler wrote:
> Is there a way that I can take *total* control of page breaking?
>
>
Here's what I do when I want to take total control of line and page
breaking (this is for 3/4 time):
%%%
forceBreaks = {
% page 1
\repeat unfold 3 { s2.\noBreak } s2.\b
Excellent. That is working. Thanks for helping me understand the issue.
On 9/22/2024 11:07 PM, Peter Chubb wrote:
"Walt" == Walt North writes:
Walt> I'm just checking if this is
Walt> expected behavior. My goal was to have ChordNames above the
Walt> matching rhythm notation. But it seems t
Hi folks
I've just come across a really weird error.
I'll try to make a minimal example tomorrow, but maybe you can give me
some hints.
The piece I'm writing is copyrighted but I can send it privately to
anyone who wants to help to debug this weird error. It uses a custom
guitar tuning.
I'm
This is a variation on issue #34 (grace note synchronization) where
\stemNeutral gets ignored in one staff if there's a grace note in the other.
%%%
\version "2.25.18"
rightHand = \relative {
c'1 |
\grace { c8 } c2
}
leftHand = \relative {
\clef bass
\stemDown f,2 f |
% \grace { s8 } %
On Mon, 23 Sept 2024 at 21:32, Colin Baguley wrote:
>
> Hi
> Thank you for trying - but I've just copied and pasted your code - and it
still doesn't do the parentheses.
> I've attached the PDF I get ..
Hello,
\override ChordName.parenthesized = ##t
Kind regards,
Xavier
Thank you - that worked perfectly.
I assume then I must have deleted that line in my original template from
years ago.
Kind regards
Colin
On Mon, 23 Sept 2024 at 21:10, Xavier Scheuer wrote:
> On Mon, 23 Sept 2024 at 21:32, Colin Baguley wrote:
> >
> > Hi
> > Thank you for trying - but I've jus
Hi
Thank you for trying - but I've just copied and pasted your code - and it
still doesn't do the parentheses.
I've attached the PDF I get ..
On Mon, 23 Sept 2024 at 19:00, Knute Snortum wrote:
>
> On Mon, Sep 23, 2024 at 9:04 AM Colin Baguley wrote:
>
>> Hi,
>> When writing a simple song lead
Folks,
in case you are an owner or a user of a recent Sibelius or Dorico
version, please send me privately screenshots of an import of the two
attached MusicXML files (and please also tell which software version
you are using). [Just in case: I have access to MuseScore and Finale,
so I don't ne
18 matches
Mail list logo
