Re: Relative Tempo Markings in Lilypond 2.22
On 12/29/21, 6:20 PM, "lilypond-user on behalf of David M. Boothe, CAS"
wrote:
I have a score in 2.18, one section of which uses with the following code:
\tempo \markup { \pad-to-box #'(0 . 0) #'(8 . 10)
\concat {
{ \override #'(font-name . "Linux Biolinum Slanted")
\fontsize #1 "Musette " }
(
\small \general-align #Y #DOWN \note #"8" #1
" = "
\small \general-align #Y #DOWN \note #"8" #1
)
}
}
This produces the section title followed by eighth note equals eighth
note, in parentheses.
When I tried to render the score in 2.22, I received the following
error message:
/music_typeset/tonsing_pm+f/tonsing_pm+f3.ly:147:52: error: wrong type
for argument 1. Expecting duration, found "8"
\small \general-align #Y #DOWN \note
#"8" #1
As best I can tell, I'm using the form given in the manual, so I'm not
sure what this error means or how to fix it. Commenting out the code
to create the "Musette" title makes no difference.
I'm using Lilypond in Frescobaldi on WIndows 10.
convert-ly will fix this for you.
The argument for \note changed from a string ( #"8") to a duration ({8}). See
http://lilypond.org/doc/v2.22/Documentation/changes/
HTH,
Carl
point-and-click default
I'm about to rant about an existing Lilyond default. Really I want to suggest a change for the developers, but I'm not sure where or how to do that. So I'll start with this rant, and I'll be happy to take any more productive steps if someone can suggest what they should be. Or, if this issue has been previosly debated, I'd be interested to have a link to that discussion. Here goes... I've been using Lilypond for a few years, and only yesterday learned about the point-and-click feature in pdf output. In particular, I had no idea that by default Lilypond includes absolute pathnames to local source files on my system as metadata in the pdf output files. So when I uploaded a couple of files to IMSLP recently, that metadata was available for all to see. Having learned (from my son!) about this feature, I have now found it in the manual, and I now know how to disable it. And I have replaced the publicly available files with new ones that do not have the metadata--and are also half the size! This point-and-click seems like a useful feature for editing, *if* it's configured to work on your system. But it apparently is not usually set up that way by default, at least on most Linux systems. (I do appreciate the instructions in the manual for configuring it, and plan to do that.) But even if it is configured to work, it seems like a REALLY BAD IDEA to have this feature enabled *by default*. Or, if it is to be the default, it ought to be mentioned VERY PROMINENTLY, so anyone installing and using Lilypond will see it. As far as I could tell, it is not even mentioned in the Learning Manual. The reference manual does admonish users to disable the feature when producing pdf output for public distribution. But that warning is totally useless if a user does not happen to read that (rather obsure) section of the manual. -- David Zelinsky
\trill fails barcheck with articulate.ly
Minimal example:
\version "2.23.1"
\include "articulate.ly"
\articulate {
c''1\trill |
}
Is this something addressed between 2.23.1 (which I have installed)
and 2.23.5 (current)?
—Joel C. Salomon
Relative Tempo Markings in Lilypond 2.22
I have a score in 2.18, one section of which uses with the following code:
\tempo \markup { \pad-to-box #'(0 . 0) #'(8 . 10)
\concat {
{ \override #'(font-name . "Linux Biolinum Slanted")
\fontsize #1 "Musette " }
(
\small \general-align #Y #DOWN \note #"8" #1
" = "
\small \general-align #Y #DOWN \note #"8" #1
)
}
}
This produces the section title followed by eighth note equals eighth
note, in parentheses.
When I tried to render the score in 2.22, I received the following
error message:
/music_typeset/tonsing_pm+f/tonsing_pm+f3.ly:147:52: error: wrong type
for argument 1. Expecting duration, found "8"
\small \general-align #Y #DOWN \note
#"8" #1
As best I can tell, I'm using the form given in the manual, so I'm not
sure what this error means or how to fix it. Commenting out the code
to create the "Musette" title makes no difference.
I'm using Lilypond in Frescobaldi on WIndows 10.
Me: I've been using Lilypond for 15 or 16 years, but am new to this list.
Thanks for any help.
dB
Re: top/bottom margins?
yep that helped a lot. Thanks. j On 2021-12-29 15:34, Carl Sorensen wrote: On 12/29/21, 3:25 PM, "jh" wrote: very curious. So your example printed better than mine the footnote is very close to the edge and the top is very far down. So I opened librewriter cut the margins to .5 and filled the top and two lines of text at the bottom and there is no loss at the bottom and no extra space at the top. So this is a problem that is connected to the program more than the printer. The github links didn't inform me much as I am not that kind of tech person (as if you couldn't tell) and I have never used github and don't have an account. I think I'm asking "is there a way to manually set the margins in lilypond?" I think the issue is a Frescobaldi issue, not a LilyPond issue, as the links Federico shared point out. Instead of printing from Frescobaldi, try opening up the saved pdf file that is created by LilyPond and stored by Frescobaldi in the working directory. Open the pdf in some pdf viewer (evince is a Free pdf viewer) and try printing from the viewer. See if you still have the problem. HTH, Carl
Re: top/bottom margins?
On 12/29/21, 3:25 PM, "jh" wrote: very curious. So your example printed better than mine the footnote is very close to the edge and the top is very far down. So I opened librewriter cut the margins to .5 and filled the top and two lines of text at the bottom and there is no loss at the bottom and no extra space at the top. So this is a problem that is connected to the program more than the printer. The github links didn't inform me much as I am not that kind of tech person (as if you couldn't tell) and I have never used github and don't have an account. I think I'm asking "is there a way to manually set the margins in lilypond?" I think the issue is a Frescobaldi issue, not a LilyPond issue, as the links Federico shared point out. Instead of printing from Frescobaldi, try opening up the saved pdf file that is created by LilyPond and stored by Frescobaldi in the working directory. Open the pdf in some pdf viewer (evince is a Free pdf viewer) and try printing from the viewer. See if you still have the problem. HTH, Carl
Re: top/bottom margins?
very curious. So your example printed better than mine the footnote is very close to the edge and the top is very far down. So I opened librewriter cut the margins to .5 and filled the top and two lines of text at the bottom and there is no loss at the bottom and no extra space at the top. So this is a problem that is connected to the program more than the printer. The github links didn't inform me much as I am not that kind of tech person (as if you couldn't tell) and I have never used github and don't have an account. I think I'm asking "is there a way to manually set the margins in lilypond?" J btw I do appreciate the help, and attention to my issue. j On 2021-12-29 12:12, Carl Sorensen wrote: On 12/29/21, 12:09 PM, "jh" wrote: thanks- not sure what to do next the printer settings are as expected. will have to think some more about it I guess. J Here's the pdf I created. See if it prints for you. Carl
Re: top/bottom margins?
On Wed, Dec 29 2021 at 12:09:12 -0700, jh wrote: thanks- not sure what to do next the printer settings are as expected. will have to think some more about it I guess. I remember that Frescobaldi had an issue with printing; can't remember if it was fixed. I see some reports in the tracker: https://github.com/frescobaldi/frescobaldi/issues/1365 https://github.com/frescobaldi/frescobaldi/issues/293 Read this: https://github.com/frescobaldi/frescobaldi/issues/1198
Re: top/bottom margins?
On 12/29/21, 12:09 PM, "jh" wrote: thanks- not sure what to do next the printer settings are as expected. will have to think some more about it I guess. J Here's the pdf I created. See if it prints for you. Carl Jay-Hamilton-24-5-Dec.pdf Description: Jay-Hamilton-24-5-Dec.pdf
Re: top/bottom margins?
thanks- not sure what to do next the printer settings are as expected.
will have to think some more about it I guess.
j
On 2021-12-29 12:02, Carl Sorensen wrote:
I added a score to your file to make it pring something.
It generates a perfect PDF on my system. No extra space at the top or
bottom.
\version "2.22.0"
\header {
title = "24-5 Dec"
subtitle = "chaconne"
composer = "Jay Hamilton"
copyright = \markup { \tiny \override #'(baseline-skip . 0.5)
\center-column
{ "CC lic 2.5 some rights reserved Jay Hamilton 2021"
"see http://creativecommons.org/licenses/by-nd/2.5/";
} }
}
#(ly:set-option 'delete-intermediate-files #t)
#(set-default-paper-size "letter" )
#(set-global-staff-size 20)
\score{
{c'4}
}
Carl
Re: top/bottom margins?
I added a score to your file to make it pring something.
It generates a perfect PDF on my system. No extra space at the top or bottom.
\version "2.22.0"
\header {
title = "24-5 Dec"
subtitle = "chaconne"
composer = "Jay Hamilton"
copyright = \markup { \tiny \override #'(baseline-skip . 0.5)
\center-column
{ "CC lic 2.5 some rights reserved Jay Hamilton 2021"
"see http://creativecommons.org/licenses/by-nd/2.5/";
} }
}
#(ly:set-option 'delete-intermediate-files #t)
#(set-default-paper-size "letter" )
#(set-global-staff-size 20)
\score{
{c'4}
}
Carl
Re: top/bottom margins?
attached is the header I use as you can see it is Letter.
Brian suggests that it's the printer and his test does suggest that it
is the printer; But no other pdf produced by other software has this
problem all the others (3) print with an expected top margin and bottom
margin.
So I'm stuck, I'd like to think there's a printer setting but since it
prints normally for everything except lily/fresco-pdfs that doesn't make
sense to me. If you can explain it then I'll look further.
thanks
J
On 2021-12-29 11:34, Carl Sorensen wrote:
On 12/29/21, 9:22 AM, "lilypond-user on behalf of jh"
wrote:
hello using 2.22 and current version of Frescobaldi. using
'letter' and
a new printer Canon
lately the top margin above the header has gotten wider and the
footnote
(2 lines smaller font) on the first page of scores is getting cut
off or
the bottom line is cut in half.
Is the easy solution to go smaller overall my default is 20 or is
there
a paper solution that would do this?
I expect that you are using A4, rather than letter, as your paper
definition.
Can you share a simple file that has the problem?
The Frescobaldi score wizard allows you to select letter as the paper
size. If you do nothing to specify a paper size, you will get A4.
HTH,
Carl \version "2.22.0"
\header {
title = "24-5 Dec"
subtitle = "chaconne"
composer = "Jay Hamilton"
copyright = \markup { \tiny \override #'(baseline-skip . 0.5)
\center-column
{ "CC lic 2.5 some rights reserved Jay Hamilton 2021"
"see http://creativecommons.org/licenses/by-nd/2.5/";
} }
}
#(ly:set-option 'delete-intermediate-files #t)
#(set-default-paper-size "letter" )
#(set-global-staff-size 20)
Re: top/bottom margins?
On 12/29/21, 9:22 AM, "lilypond-user on behalf of jh" wrote: hello using 2.22 and current version of Frescobaldi. using 'letter' and a new printer Canon lately the top margin above the header has gotten wider and the footnote (2 lines smaller font) on the first page of scores is getting cut off or the bottom line is cut in half. Is the easy solution to go smaller overall my default is 20 or is there a paper solution that would do this? I expect that you are using A4, rather than letter, as your paper definition. Can you share a simple file that has the problem? The Frescobaldi score wizard allows you to select letter as the paper size. If you do nothing to specify a paper size, you will get A4. HTH, Carl
top/bottom margins?
hello using 2.22 and current version of Frescobaldi. using 'letter' and a new printer Canon lately the top margin above the header has gotten wider and the footnote (2 lines smaller font) on the first page of scores is getting cut off or the bottom line is cut in half. Is the easy solution to go smaller overall my default is 20 or is there a paper solution that would do this? thanks J -- Thank you Sound & Silence Beginning May 1, 2021 a new address; 1814 Lake Washington Blvd. So., Seattle, Wa. 98144 _206-328-7694 or messages at 206-308-8189_ www.soundand.com and an online short (45 minute) concert of new material on Wayward in Limbo https://www.waywardmusic.org/?p=6082
Re: better control of balloon positioning
Le 26/12/2021 à 10:43, Werner LEMBERG a écrit : [...] What must I do to get, for example, Balloon text / / grob this alignment? Please advise. One solution is to wait for the patch that accidentally I am preparing exactly right now. :=) Aaah :-) Werner This is now https://gitlab.com/lilypond/lilypond/-/merge_requests/1087 Jean
Re: glossary suggestions from novice
Will do. Thanks, -Tom On Wed, Dec 29, 2021 at 9:42 AM Knute Snortum wrote: > This sounds like something that should be treated as a possible bug. > Manual changes go in the bug tracker too. Here's what to do: > > https://lilypond.org/bug-reports.html > > -- > Knute Snortum > > > > On Wed, Dec 29, 2021 at 6:03 AM Tom Sgouros wrote: > > > > Hello all: > > > > I wonder if the "system" entry in the glossary might be enhanced by > including the lilypond-specific definition. Currently it reads like this: > > > > "The collection of staves (staff), two or more, as used for writing down > keyboard, chamber, choral, or orchestral music; a section of the score > spanning the width of a single page." > > > > This seems to imply the word has two meanings, but I think in the > context of Lilypond, it has only one. Should it say "a collection of staves > that span the width of a single page"? (Is that what a "system" means?) > It's not in the technical glossary, either. > > > > Also, there is no entry for "spanner" (also no simple index entry, and > not in the technical glossary, either). It does have a section to itself, > for those bright enough to use the table of contents, but the index entries > only point to it in a fairly indirect way. > > > > Thank you, > > > > -Tom >
Re: Tenuto marking too close to note
Le 29/12/2021 à 09:45, Lukas-Fabian Moser a écrit :
A cleaner and more surgical solution would be:
\version "2.18"
#(assoc-set! (assoc-ref default-script-alist "tenuto") 'padding 0.5)
\new Staff {
\relative c'' {\time 3/4 a g e--}
}
Although this approach manipulates internal data structures of
LilyPond, it has the advantage of dealing with your issue at the root
and not causing side effects for other scripts. Unfortunately, this
approach does not work directly for the (still experimental) LilyPond
builds using Guile2.
Be mindful that assoc-set! is not guaranteed to
mutate its input. You're not the first one tripped
up by this API quirk :-) See
https://www.gnu.org/software/guile/manual/html_node/Adding-or-Setting-Alist-Entries.html.
I'm occasionally using helpers like the following
to set values in nested alists:
\version "2.22.1" % also works in 2.18 and with Guile 2
#(use-modules (ice-9 match))
#(define (set-path path value alist)
(let loop ((path path)
(copy (copy-tree alist)))
(match path
(() value)
((p . rest)
(assoc-set! copy p (loop rest (assoc-get p copy '(
\layout {
\context {
\Score
scriptDefinitions = #(set-path '("tenuto" padding) 0.5
default-script-alist)
}
}
{
\relative c'' {\time 3/4 a g e--}
}
Regards,
Jean
Re: glossary suggestions from novice
This sounds like something that should be treated as a possible bug. Manual changes go in the bug tracker too. Here's what to do: https://lilypond.org/bug-reports.html -- Knute Snortum On Wed, Dec 29, 2021 at 6:03 AM Tom Sgouros wrote: > > Hello all: > > I wonder if the "system" entry in the glossary might be enhanced by including > the lilypond-specific definition. Currently it reads like this: > > "The collection of staves (staff), two or more, as used for writing down > keyboard, chamber, choral, or orchestral music; a section of the score > spanning the width of a single page." > > This seems to imply the word has two meanings, but I think in the context of > Lilypond, it has only one. Should it say "a collection of staves that span > the width of a single page"? (Is that what a "system" means?) It's not in the > technical glossary, either. > > Also, there is no entry for "spanner" (also no simple index entry, and not in > the technical glossary, either). It does have a section to itself, for those > bright enough to use the table of contents, but the index entries only point > to it in a fairly indirect way. > > Thank you, > > -Tom
Re: Tenuto marking too close to note
Thank you for all the answers! The solution that best suits my situation is overriding the script.padding, what Vaughan suggested. I find the staccatos to be too close to notes as well, so having it affect all articulations doesn't seem like a problem (at least at the moment). As Lukas pointed out, dashdash = \tweak padding #0.5 \tenuto does not work in my version of Lilypond. (I'm a bit hesitant to spend my energy on updates, as my old computer might fall apart soon.) Erika
glossary suggestions from novice
Hello all: I wonder if the "system" entry in the glossary might be enhanced by including the lilypond-specific definition. Currently it reads like this: "The collection of staves (staff), two or more, as used for writing down keyboard, chamber, choral, or orchestral music; a section of the score spanning the width of a single page." This seems to imply the word has two meanings, but I think in the context of Lilypond, it has only one. Should it say "a collection of staves that span the width of a single page"? (Is that what a "system" means?) It's not in the technical glossary, either. Also, there is no entry for "spanner" (also no simple index entry, and not in the technical glossary, either). It does have a section to itself, for those bright enough to use the table of contents, but the index entries only point to it in a fairly indirect way. Thank you, -Tom
Re: minimum measure size?
Thank you all (and Brian, who replied directly) for your suggestions. Proportional notation seems to do what I need, simply, but the other seems worth investigating. -Tom On Wed, Dec 29, 2021 at 4:02 AM Valentin Petzel wrote: > Hello Tom, > > Consider using proportional notation to ensure there is always space for > note > values as small as you need them. > > Cheers, > Valentin > > Am Mittwoch, 29. Dezember 2021, 00:18:24 CET schrieb Tom Sgouros: > > Hello all: > > > > How can I set a minimum measure size? I want to make some scratch > > engravings of piano music with lots of room in blank upper or lower > staves > > so I can pencil in my choices as I work them out. But some of the > measures > > have only a couple of notes recorded, so they shrink too small to write > > anything else in. > > > > I was reviewing the settable parameters, but I think maybe I don't > > understand enough of lilypond's native jargon yet to know what to look > for. > > I found setting for counting measures and grouping measures, but what > about > > measuring measures? What tree should I be barking up here? > > > > Thank you, > > > > -Tom
Re: minimum measure size?
Hello Tom,
Consider using proportional notation to ensure there is always space for note
values as small as you need them.
Cheers,
Valentin
Am Mittwoch, 29. Dezember 2021, 00:18:24 CET schrieb Tom Sgouros:
> Hello all:
>
> How can I set a minimum measure size? I want to make some scratch
> engravings of piano music with lots of room in blank upper or lower staves
> so I can pencil in my choices as I work them out. But some of the measures
> have only a couple of notes recorded, so they shrink too small to write
> anything else in.
>
> I was reviewing the settable parameters, but I think maybe I don't
> understand enough of lilypond's native jargon yet to know what to look for.
> I found setting for counting measures and grouping measures, but what about
> measuring measures? What tree should I be barking up here?
>
> Thank you,
>
> -Tom\score{
{ c'4 s2 d'8 e' f'2 s s g'8 a' b'16 c'' d''8 }
\layout { }
}
\score{
{ c'4 s2 d'8 e' f'2 s s g'8 a' b'16 c'' d''8 }
\layout {
\context {
\Score
proportionalNotationDuration = #(ly:make-moment 1/8)
}
}
}
\score{
{ c'4 s2 d'8 e' f'2 s s g'8 a' b'16 c'' d''8 }
\layout {
\context {
\Score
proportionalNotationDuration = #(ly:make-moment 1/12)
}
}
}
signature.asc
Description: This is a digitally signed message part.
Re: Tenuto marking too close to note
Hello Erika,
the problem here is that Lilypond handles many Articulations the same way. So
overriding Script.padding will affect all articulations.
We have recently discussed possibilites to override properties for specific
articulations, but if you are using the shorthand -- for tenuto then you can
simply do
dashDash = \tweak padding #0.5 \tenuto
(use whatever value looks good to you)
somewhere at the beginning of your file to simply override the behaviour of
that shorthand.
Cheers,
Valentin
29.12.2021 02:48:23 Erika Pirnes :
> Hi,
>
> I would like to have the tenuto mark a bit farther away from the note. I had
> a similar issue with tuplet numbers and then "\override TupletNumber.Y-offset
> = #-2.5" fixed the issue. I don't know what I should replace "TupletNumber"
> by in the case of tenuto lines.
>
> Minimal example here:
>
> \version "2.18.2"
>
> \new Staff {
> \relative c'' {\time 3/4 a g e--}
> }
>
> Thank you!
> Erika
Re: Tenuto marking too close to note
Hi Erika,
I would like to have the tenuto mark a bit farther away from the note.
I had a similar issue with tuplet numbers and then "\override
TupletNumber.Y-offset = #-2.5" fixed the issue. I don't know what I
should replace "TupletNumber" by in the case of tenuto lines.
Minimal example here:
\version "2.18.2"
\new Staff {
\relative c'' {\time 3/4 a g e--}
}
With a slightly more recent version of LilyPond, there's this
quick-and-dirty solution:
\version "2.19.83"
dashDash = \tweak padding #0.5 \tenuto
\new Staff {
\relative c'' {\time 3/4 a g e--}
}
This changes all tenutos created by --, but not those created by other
means such as \tenuto (that's the "dirty" part).
A cleaner and more surgical solution would be:
\version "2.18"
#(assoc-set! (assoc-ref default-script-alist "tenuto") 'padding 0.5)
\new Staff {
\relative c'' {\time 3/4 a g e--}
}
Although this approach manipulates internal data structures of LilyPond,
it has the advantage of dealing with your issue at the root and not
causing side effects for other scripts. Unfortunately, this approach
does not work directly for the (still experimental) LilyPond builds
using Guile2.
Lukas
