Re: Font sizes change on change of font
Yes, changing the font factor will scale all fonts, including notation fonts. This will result in the noteheads not fitting inside the lines and similar stuff. So you need to set the factor to 22/20 and then override the font-size for those texts that need to be bigger. Sadly Lilypond does not allow for scaling single fonts, such as fontspec. Valentin 22.08.2021 23:22:40 Paul Hodges : > Don't worry - I wasn't offended. > > Anyway, yes - I also found that 18 gives me the same size as Century > Schoolbook. But changing the factor also affects other text, such as > dynamics symbols - so the relationship, e.g. if I want to type "\dynamic > p \italic sempre", is still off unless I change the fontsize in every > such markup. > > For my part, I prefer Century Schoolbook anyway, but the use of Times > New Roman is being imposed on me. > > Paul > > On 22/08/2021 21:07:46, "Valentin Petzel" wrote: > >> Hello Paul. I'm sorry if I offended you. But it's just very simple to change >> 22 to 20 and see if this solves the problem. >> >> TNR is a smaller font than the Century Schoolbook clone Lilypond uses, so >> maybe you need to increase the scale further. >>
Re: Custom Barline
All you're missing is the closing angle brackets ">>", which maybe your
mail program saw as quote marks.
Paul
On 22/08/2021 22:34:47, "ole" wrote:
>> \new StaffGroup
>> <<
>> \new Staff { b1 \mark \default \bar "p|" b \break \bar "p|" b }
>> \new Staff { b1 b b }
>>
>>
>>
>> HTH,
>> Harm
>>
>
>
>Unfortunatly your example is not complete here, can you please send it again,
>thanks!
Re: Custom Barline
> Am 22.08.2021 um 18:16 schrieb Thomas Morley :
>
> Am So., 22. Aug. 2021 um 13:42 Uhr schrieb Paul Hodges :
>>
>> Encouraged by the fantastic responses to my first problem, I now offer my
>> other issue.
>>
>> The composer uses a special barline to mark the phrase pattern of a piece.
>> The form of this barline is like this:
>> (MS) https://cassland.org/images/PhraseBarMS.jpg
>> (Printed elsewhere) https://cassland.org/images/PhraseBarSet.jpg
>>
>> In this case I can't even think where to start...
>>
>> Thanks,
>> Paul
>
> How about:
>
> %% Define a new bar-line drawing-procedure
> #(define (make-thick-phrase-bar-line grob extent)
> "Draw a smaller thick bar line."
> (let* ((line-thickness (layout-line-thickness grob))
> (thick-thickness (* (ly:grob-property grob 'thick-thickness 1)
> line-thickness))
> (inner-extent
> (interval-widen extent (- (ly:staff-symbol-staff-space grob
> (final-extent-thick
> (bar-line::widen-bar-extent-on-span grob inner-extent)))
>
>(bar-line::draw-filled-box
> (cons 0 thick-thickness)
> final-extent-thick
> thick-thickness
> final-extent-thick
> grob)))
>
> %% Assign "p" to the new bar-line drawing-procedure
> #(add-bar-glyph-print-procedure "p" make-thick-phrase-bar-line)
>
> %% Define a ready to use new BarLine
> #(define-bar-line "p|" "p|" #f " |")
>
> \layout {
> \context {
> \Score
> %% Actually not really needed:
> \override BarNumber.break-visibility = ##(#t #t #t)
> \override BarNumber.self-alignment-X = 0
> }
> \context {
> \Staff
> %% Needed:
> %% If "p|"-BarLine is used, set 'kern to zero.
> \override BarLine.before-line-breaking =
>#(lambda (grob)
> (if (equal? (ly:grob-property grob 'glyph) "p|")
> (ly:grob-set-property! grob 'kern 0)))
> }
> }
>
> \new StaffGroup
> <<
>\new Staff { b1 \mark \default \bar "p|" b \break \bar "p|" b }
>\new Staff { b1 b b }
>>>
>
>
>
> HTH,
> Harm
>
Unfortunatly your example is not complete here, can you please send it again,
thanks!
Re: Font sizes change on change of font
Don't worry - I wasn't offended. Anyway, yes - I also found that 18 gives me the same size as Century Schoolbook. But changing the factor also affects other text, such as dynamics symbols - so the relationship, e.g. if I want to type "\dynamic p \italic sempre", is still off unless I change the fontsize in every such markup. For my part, I prefer Century Schoolbook anyway, but the use of Times New Roman is being imposed on me. Paul On 22/08/2021 21:07:46, "Valentin Petzel" wrote: >Hello Paul. I'm sorry if I offended you. But it's just very simple to change >22 to 20 and see if this solves the problem. > >TNR is a smaller font than the Century Schoolbook clone Lilypond uses, so >maybe you need to increase the scale further. >
Re: Font sizes change on change of font
Hello Paul. I'm sorry if I offended you. But it's just very simple to change 22 to 20 and see if this solves the problem. TNR is a smaller font than the Century Schoolbook clone Lilypond uses, so maybe you need to increase the scale further. Then, you are not telling Lilypond it's default. The factor takes a number. The expression (/ a b) where a,b are two numbers is the number a/b. So basically you calculate the factor for the font to be proportional to the change in staffsize. E.g. if your staffsize is 10 (half the default) you use factor 1/2. Valentin 22.08.2021 21:51:09 Paul Hodges : > I'm not arguing - I'm trying to understand. It is not clear to me from > the reference manual that I have to put the default staff size in there. > My mind suggested that telling LilyPond what its own default is would > be redundant, so the other (changed) value should go there. It turns > out it was wrong. > > Anyway, following your instructions improves matters, though TNR is > still substantially smaller than the default font; but it's acceptable > now. > > Thanks, > Paul > > On 22/08/2021 20:30:57, "Valentin Petzel" wrote: > >> Hello Paul. That does not matter. Lilipond will always assume factor 1 to be >> staffsize 20. >> So when using staffsize 22 you need to use factor 22/20. Please try it out >> at least instead of immediately arguing against it. >> >> Valentin >> >> 22.08.2021 18:42:07 Paul Hodges : >> >>> On 22/08/2021 17:20:54, "Thomas Morley" >>> wrote: >>> Use "Times New Roman," Note the trailing comma (see NR for the issue). >>> Sadly this has no discernible effect. >>> I may try to get away with only changing the font in the title fields, >>> using markup, which would be no bother. >>> >>> Paul >>> >>> PS: >>> On 22/08/2021 15:32:23, "Valentin Petzel" wrote: the default staff-size is 20, not 22, so you need to divide by 20. >>> >>> My global-staff-size is 22 (to match another piece, and for printing on >>> larger JIS B4 paper)
Re: Font sizes change on change of font
I'm not arguing - I'm trying to understand. It is not clear to me from the reference manual that I have to put the default staff size in there. My mind suggested that telling LilyPond what its own default is would be redundant, so the other (changed) value should go there. It turns out it was wrong. Anyway, following your instructions improves matters, though TNR is still substantially smaller than the default font; but it's acceptable now. Thanks, Paul On 22/08/2021 20:30:57, "Valentin Petzel" wrote: >Hello Paul. That does not matter. Lilipond will always assume factor 1 to be >staffsize 20. >So when using staffsize 22 you need to use factor 22/20. Please try it out at >least instead of immediately arguing against it. > >Valentin > >22.08.2021 18:42:07 Paul Hodges : > >> On 22/08/2021 17:20:54, "Thomas Morley" >> wrote: >> >>> Use >>> "Times New Roman," >>> Note the trailing comma (see NR for the issue). >> Sadly this has no discernible effect. >> I may try to get away with only changing the font in the title fields, >> using markup, which would be no bother. >> >> Paul >> >> PS: >> On 22/08/2021 15:32:23, "Valentin Petzel" wrote: >>> the default staff-size is 20, not 22, so you need to divide by 20. >> >> My global-staff-size is 22 (to match another piece, and for printing on >> larger JIS B4 paper)
Re: Font sizes change on change of font
Hello Paul. That does not matter. Lilipond will always assume factor 1 to be staffsize 20. So when using staffsize 22 you need to use factor 22/20. Please try it out at least instead of immediately arguing against it. Valentin 22.08.2021 18:42:07 Paul Hodges : > On 22/08/2021 17:20:54, "Thomas Morley" > wrote: > >> Use >> "Times New Roman," >> Note the trailing comma (see NR for the issue). > Sadly this has no discernible effect. > I may try to get away with only changing the font in the title fields, > using markup, which would be no bother. > > Paul > > PS: > On 22/08/2021 15:32:23, "Valentin Petzel" wrote: >> the default staff-size is 20, not 22, so you need to divide by 20. > > My global-staff-size is 22 (to match another piece, and for printing on > larger JIS B4 paper)
Re: Custom Barline
Once again - spot on!
I will try to learn from such examples so that I don't need to leech
like this in the future...
Thanks,
Paul
On 22/08/2021 17:16:48, "Thomas Morley"
wrote:
>Am So., 22. Aug. 2021 um 13:42 Uhr schrieb Paul Hodges :
>>
>> Encouraged by the fantastic responses to my first problem, I now offer my
>> other issue.
>>
>> The composer uses a special barline to mark the phrase pattern of a piece.
>> The form of this barline is like this:
>> (MS) https://cassland.org/images/PhraseBarMS.jpg
>> (Printed elsewhere) https://cassland.org/images/PhraseBarSet.jpg
>>
>> In this case I can't even think where to start...
>>
>> Thanks,
>> Paul
>
>How about:
>
>%% Define a new bar-line drawing-procedure
>#(define (make-thick-phrase-bar-line grob extent)
> "Draw a smaller thick bar line."
> (let* ((line-thickness (layout-line-thickness grob))
> (thick-thickness (* (ly:grob-property grob 'thick-thickness 1)
>line-thickness))
> (inner-extent
>(interval-widen extent (- (ly:staff-symbol-staff-space grob
> (final-extent-thick
>(bar-line::widen-bar-extent-on-span grob inner-extent)))
>
> (bar-line::draw-filled-box
> (cons 0 thick-thickness)
> final-extent-thick
> thick-thickness
> final-extent-thick
> grob)))
>
>%% Assign "p" to the new bar-line drawing-procedure
>#(add-bar-glyph-print-procedure "p" make-thick-phrase-bar-line)
>
>%% Define a ready to use new BarLine
>#(define-bar-line "p|" "p|" #f " |")
>
>\layout {
> \context {
> \Score
> %% Actually not really needed:
> \override BarNumber.break-visibility = ##(#t #t #t)
> \override BarNumber.self-alignment-X = 0
> }
> \context {
> \Staff
> %% Needed:
> %% If "p|"-BarLine is used, set 'kern to zero.
> \override BarLine.before-line-breaking =
> #(lambda (grob)
> (if (equal? (ly:grob-property grob 'glyph) "p|")
> (ly:grob-set-property! grob 'kern 0)))
> }
>}
>
>\new StaffGroup
> <<
> \new Staff { b1 \mark \default \bar "p|" b \break \bar "p|" b }
> \new Staff { b1 b b }
> >>
>
>
>
>HTH,
> Harm
Re: Font sizes change on change of font
On 22/08/2021 17:20:54, "Thomas Morley" wrote: >Use >"Times New Roman," >Note the trailing comma (see NR for the issue). Sadly this has no discernible effect. I may try to get away with only changing the font in the title fields, using markup, which would be no bother. Paul PS: On 22/08/2021 15:32:23, "Valentin Petzel" wrote: > the default staff-size is 20, not 22, so you need to divide by 20. My global-staff-size is 22 (to match another piece, and for printing on larger JIS B4 paper)
Re: Font sizes change on change of font
Am So., 22. Aug. 2021 um 15:54 Uhr schrieb Paul Hodges : > > I have been asked to change my serif font to Times New Roman. I have > done this, using: > >#(define fonts > (set-global-fonts > #:roman "Times New Roman" Use "Times New Roman," Note the trailing comma (see NR for the issue). Cheers, Harm > #:factor (/ staff-height pt 22) > )) > > as documented (the staff-height matches the global staff size). But all > my non-Emmentaler text (titles, tempo, text markup...) has now shrunk, > and looks wrong alongside the notation and dynamics text. > > Is there any way to enlarge the text globally? > > Thanks, > Paul >
Re: Custom Barline
Am So., 22. Aug. 2021 um 13:42 Uhr schrieb Paul Hodges :
>
> Encouraged by the fantastic responses to my first problem, I now offer my
> other issue.
>
> The composer uses a special barline to mark the phrase pattern of a piece.
> The form of this barline is like this:
> (MS) https://cassland.org/images/PhraseBarMS.jpg
> (Printed elsewhere) https://cassland.org/images/PhraseBarSet.jpg
>
> In this case I can't even think where to start...
>
> Thanks,
> Paul
How about:
%% Define a new bar-line drawing-procedure
#(define (make-thick-phrase-bar-line grob extent)
"Draw a smaller thick bar line."
(let* ((line-thickness (layout-line-thickness grob))
(thick-thickness (* (ly:grob-property grob 'thick-thickness 1)
line-thickness))
(inner-extent
(interval-widen extent (- (ly:staff-symbol-staff-space grob
(final-extent-thick
(bar-line::widen-bar-extent-on-span grob inner-extent)))
(bar-line::draw-filled-box
(cons 0 thick-thickness)
final-extent-thick
thick-thickness
final-extent-thick
grob)))
%% Assign "p" to the new bar-line drawing-procedure
#(add-bar-glyph-print-procedure "p" make-thick-phrase-bar-line)
%% Define a ready to use new BarLine
#(define-bar-line "p|" "p|" #f " |")
\layout {
\context {
\Score
%% Actually not really needed:
\override BarNumber.break-visibility = ##(#t #t #t)
\override BarNumber.self-alignment-X = 0
}
\context {
\Staff
%% Needed:
%% If "p|"-BarLine is used, set 'kern to zero.
\override BarLine.before-line-breaking =
#(lambda (grob)
(if (equal? (ly:grob-property grob 'glyph) "p|")
(ly:grob-set-property! grob 'kern 0)))
}
}
\new StaffGroup
<<
\new Staff { b1 \mark \default \bar "p|" b \break \bar "p|" b }
\new Staff { b1 b b }
>>
HTH,
Harm
Re: LilyPond available on Wikipedia again
On 21/08/2021 06:09, Werner LEMBERG wrote: Due to security concerns the ` ... ` extension to embed LilyPond (and ABC) scores in Wikipedia pages that are displayed automatically were disabled for more than a year. https://phabricator.wikimedia.org/T257066 This has been reactivated now. It seems, however, that not all details have been resolved yet; if you find problems please report them at https://phabricator.wikimedia.org/tag/mediawiki-extensions-score/ Werner Following on from this I'm trying to sort out some existing scores in WP. Most are OK, but one https://en.wikipedia.org/wiki/O_Come,_O_Come,_Emmanuel is giving me some grief. The way I used to do it was by including gregorian.ly, turning off the barline engraver and using \divisioMaxima and \finalis as appropriate. However, includes are not allowed now. I have replaced all the divisios with \bar "|" and the finalis with \bar "||" which seems to work, but only if I turn the barline engraver back on. Unfiortunately the system then applies a default time signature of 4/4 and puts in its own barlines, which is not wanted. I've tried \remove "Default_bar_line_engraver", but that appears to have no effect. Any suggestions? Thanks, Martin -- J Martin Rushton MBCS
Re: Font sizes change on change of font
Hello Paul, the default staff-size is 20, not 22, so you need to divide by 20. Cheers, Valentin 22.08.2021 15:53:57 Paul Hodges : > I have been asked to change my serif font to Times New Roman. I have > done this, using: > > #(define fonts > (set-global-fonts > #:roman "Times New Roman" > #:factor (/ staff-height pt 22) > )) > > as documented (the staff-height matches the global staff size). But all > my non-Emmentaler text (titles, tempo, text markup...) has now shrunk, > and looks wrong alongside the notation and dynamics text. > > Is there any way to enlarge the text globally? > > Thanks, > Paul
Re: Custom Barline
Hello Paul, I can't give you a working example becauae I am not at home, but you might simply override BarLine.stencil. Override it with a function that uses ly:stencil-combine-at-edges to tie a suitable stencil to (ly:barline::print grob). You might need to mess a bit with the dimensions of that stencil and the padding for the barline. Cheers, Valentin 22.08.2021 13:42:25 Paul Hodges : > Encouraged by the fantastic responses to my first problem, I now offer my > other issue. > > The composer uses a special barline to mark the phrase pattern of a piece. > The form of this barline is like this: > (MS) https://cassland.org/images/PhraseBarMS.jpg > (Printed elsewhere) https://cassland.org/images/PhraseBarSet.jpg > > In this case I can't even think where to start... > > Thanks, > Paul
Font sizes change on change of font
I have been asked to change my serif font to Times New Roman. I have done this, using: #(define fonts (set-global-fonts #:roman "Times New Roman" #:factor (/ staff-height pt 22) )) as documented (the staff-height matches the global staff size). But all my non-Emmentaler text (titles, tempo, text markup...) has now shrunk, and looks wrong alongside the notation and dynamics text. Is there any way to enlarge the text globally? Thanks, Paul
Re: Custom Barline
It looks to me very close to a repetition sign, is there a Postscript definition somewhere (which can be tweaked by someone having more knowledge than me:-))? > Am 22.08.2021 um 13:41 schrieb Paul Hodges : > > Encouraged by the fantastic responses to my first problem, I now offer my > other issue. > > The composer uses a special barline to mark the phrase pattern of a piece. > The form of this barline is like this: > (MS) https://cassland.org/images/PhraseBarMS.jpg > (Printed elsewhere) https://cassland.org/images/PhraseBarSet.jpg > > In this case I can't even think where to start... > > Thanks, > Paul
Custom Barline
Encouraged by the fantastic responses to my first problem, I now offer my other issue. The composer uses a special barline to mark the phrase pattern of a piece. The form of this barline is like this: (MS) https://cassland.org/images/PhraseBarMS.jpg (Printed elsewhere) https://cassland.org/images/PhraseBarSet.jpg In this case I can't even think where to start... Thanks, Paul
Re: Stems for rests under quaver beam
Hi Paul, This is fairly common in new music. I've found the most consistent way to get it to look good is by using overrides. Here's how I code it: - \override Stem.stemlet-length = #0.5 \override Stem.details.beamed-lengths = #'(4.75) f16->[ f r f] f-> f f f \revert Stem.stemlet-length \revert Stem.details.beamed-lengths --- You can adjust the beamed length to whatever value you prefer to keep the rest centered on the stave vertically. You don't need to revert the overrides until you're done with the stemlets. It's a bit tedious to do this for every beamed group, but it gives you fine control over exactly how they look. Cheers, A On Sun, Aug 22, 2021 at 11:41 AM Paul Hodges wrote: > I have been asked to set a modern piece for Flute, and it has some > elements which are new to me, and which I have been unable to find a way > to present. The first of these is that the composer regularly writes > rests within (or at the ends of) groups of quavers beamed together. > Using manual beaming it is easy to get the beams to extend over the > rests as required; however, in the manuscript (and in a printed copy of > some other music of his) there is a stub stem from the beam towards the > rest. > > I suppose I can draw this as an individual markup on each occasion, but > doing this for dozens of cases is daunting, and I wonder if anyone can > suggest a more practical approach? > > Thanks for any ideas! > Paul > >
Re: Stems for rests under quaver beam
Brilliant! That's perfect.
I'd tried writing a note with the rest glyph as notehead, but then the
stem was too long - your solution is both easier and more controllable.
Thanks,
Paul
On 22/08/2021 11:33:47, "Thomas Morley"
wrote:
>Am So., 22. Aug. 2021 um 11:41 Uhr schrieb Paul Hodges :
>>
>> I have been asked to set a modern piece for Flute, and it has some
>> elements which are new to me, and which I have been unable to find a way
>> to present. The first of these is that the composer regularly writes
>> rests within (or at the ends of) groups of quavers beamed together.
>> Using manual beaming it is easy to get the beams to extend over the
>> rests as required; however, in the manuscript (and in a printed copy of
>> some other music of his) there is a stub stem from the beam towards the
>> rest.
>>
>> I suppose I can draw this as an individual markup on each occasion, but
>> doing this for dozens of cases is daunting, and I wonder if anyone can
>> suggest a more practical approach?
>>
>> Thanks for any ideas!
>> Paul
>>
>
>How about:
>
>\relative {
> r8[ b b r] b[ r r b]
> \override Stem.stemlet-length = #1.0
> r8[ b b r] b[ r r b]
>}
>
>Cheers,
> Harm
>
Re: Stems for rests under quaver beam
Am So., 22. Aug. 2021 um 11:41 Uhr schrieb Paul Hodges :
>
> I have been asked to set a modern piece for Flute, and it has some
> elements which are new to me, and which I have been unable to find a way
> to present. The first of these is that the composer regularly writes
> rests within (or at the ends of) groups of quavers beamed together.
> Using manual beaming it is easy to get the beams to extend over the
> rests as required; however, in the manuscript (and in a printed copy of
> some other music of his) there is a stub stem from the beam towards the
> rest.
>
> I suppose I can draw this as an individual markup on each occasion, but
> doing this for dozens of cases is daunting, and I wonder if anyone can
> suggest a more practical approach?
>
> Thanks for any ideas!
> Paul
>
How about:
\relative {
r8[ b b r] b[ r r b]
\override Stem.stemlet-length = #1.0
r8[ b b r] b[ r r b]
}
Cheers,
Harm
Re: Stems for rests under quaver beam
Hi Paul,
It's hard to understand exactly what you're trying to do without being
able to see it. Does the following in any way resemble what you're
trying to do?
\score {
\new RhythmicStaff {
\set stemLeftBeamCount = #0
c16[]
r8.
}
}
Kevin
On Sun, 22 Aug 2021 at 10:44, Paul Hodges wrote:
>
> I have been asked to set a modern piece for Flute, and it has some
> elements which are new to me, and which I have been unable to find a way
> to present. The first of these is that the composer regularly writes
> rests within (or at the ends of) groups of quavers beamed together.
> Using manual beaming it is easy to get the beams to extend over the
> rests as required; however, in the manuscript (and in a printed copy of
> some other music of his) there is a stub stem from the beam towards the
> rest.
>
> I suppose I can draw this as an individual markup on each occasion, but
> doing this for dozens of cases is daunting, and I wonder if anyone can
> suggest a more practical approach?
>
> Thanks for any ideas!
> Paul
>
Stems for rests under quaver beam
I have been asked to set a modern piece for Flute, and it has some elements which are new to me, and which I have been unable to find a way to present. The first of these is that the composer regularly writes rests within (or at the ends of) groups of quavers beamed together. Using manual beaming it is easy to get the beams to extend over the rests as required; however, in the manuscript (and in a printed copy of some other music of his) there is a stub stem from the beam towards the rest. I suppose I can draw this as an individual markup on each occasion, but doing this for dozens of cases is daunting, and I wonder if anyone can suggest a more practical approach? Thanks for any ideas! Paul
