Re: Fonts for tablature?
Dear Jean - many thanks. In fact, I've discovered since my query that if you go to the Fronimo website, you'll find a "Pavan" font available for use. Also, if you download and install the Fronimo executable - even its demo package (which doesn't allow you to save your files) - you'll get several fonts which can be used. Orlando Lutes provide a package called LuteScribe which includes a font called LeRoy. This latter font is probably the closest to the font used in some early 17th century publications. I'm not fully sure of the copyright issues with these fonts. For my own personal use, it doesn't matter. But I'm not sure about the legality of using these fonts in files made available, for example, on IMSLP. On Wed, 16 Aug 2023 at 10:11, Jean Abou Samra wrote: > > > Le 16 août 2023 à 01:50, Alasdair McAndrew a écrit : > > > If you look at > https://musescore.org/sites/musescore.org/files/2020-05/lute-tab-bug.png > (don't worry about the colours) there's a font which I like. A similar > font is used in abctab2ps (it's called "frFrancisque" there), and you can > see it in use at https://www.lautengesellschaft.de/cdmm/sample.png > > Is a similar font available for Lilypond?There are unicode glyphs at > > > https://www.w3.org/2019/03/smufl13/tables/french-and-english-renaissance-lute-tablature.html > > but these are in fact "private use characters". > > > > Some people have created fonts where these characters of a SMuFL font are > moved to the normal code points for a, b, c, ... You should be able to use > such a font (adding it to the font search path with > ly:font-config-add-file). > https://lists.gnu.org/archive/html/lilypond-user-fr/2019-03/msg00062.html > -- Alasdair McAndrew (he/him) mob: 0432 854 858 https://numbersandshapes.net
Re: Is there a better way to have a boxed part letter at the beginning of an arbitrary line?
Le mercredi 16 août 2023 à 14:50 -0400, Kevin Cole a écrit :
> While this is also good to know about, and I thank you, it turns out
> that the \sectionLabel is more of what I'm looking for. In your
> example, the boxed text is too far to the right, whereas the
> \sectionLabel put the label right above the clef sign, which is what I
> was trying to achieve.
That's tweakable.
\layout {
\override Score.RehearsalMark.break-align-symbols = #'(left-edge staff-bar)
}
signature.asc
Description: This is a digitally signed message part
Print brace, clef and key signature at start of Coda separated by blank space
Hello everyone, example:
\version "2.24.1"
upper = {
\key as \minor
c'1
\stopStaff
s1*4
\startStaff
\section
\sectionLabel "Coda"
c'1
\bar ".|"
}
lower = {
\key as \minor
c'1
\stopStaff
s1*4
\startStaff
\section
\sectionLabel "Coda"
c'1
\bar "|."
}
\score {
\new PianoStaff
<<
\new Staff = "upper" \upper
\new Staff = "lower" \lower
>>
}
How can I force lilypond to print pianostaff brace, clef and key signature
at the beginning of Coda that is not on line break?
Re: Is there a better way to have a boxed part letter at the beginning of an arbitrary line?
On Wed, Aug 16, 2023 at 2:42 PM Michael Werner wrote: > > Hi Kevin. > > It sounds like you might be able to do want you want with rehearsal marks. > They're built into Lilypond and do pretty much what you seem to be > describing. Details at > http://lilypond.org/doc/v2.24/Documentation/notation/bars#index-rehearsal-mark While this is also good to know about, and I thank you, it turns out that the \sectionLabel is more of what I'm looking for. In your example, the boxed text is too far to the right, whereas the \sectionLabel put the label right above the clef sign, which is what I was trying to achieve. (Nonetheless, I'll file this message in my tips drawer as well. I can see where it may come in handy.)
Re: Is there a better way to have a boxed part letter at the beginning of an arbitrary line?
On Wed, Aug 16, 2023 at 2:18 PM William Rehwinkel < will...@williamrehwinkel.net> wrote: > Dear Kevin, > > I use "\sectionLabel"s for this. > I KNEW there had to be a simpler way. Thanks. \sectionLabel is exactly what I was looking for. I should have tried more adjectives for "part" in my searches. ;-)
Re: Is there a better way to have a boxed part letter at the beginning of an arbitrary line?
Hi Kevin.
It sounds like you might be able to do want you want with rehearsal marks.
They're built into Lilypond and do pretty much what you seem to be
describing. Details at
http://lilypond.org/doc/v2.24/Documentation/notation/bars#index-rehearsal-mark
A modification of your MWE using them:
\version "2.24.2"
\language "english"
melody = \relative c' {
\set Score.rehearsalMarkFormatter = #format-mark-box-letters
\time 6/8
\key d \major
\clef treble
\mark \default
d8[ e8 e8] g8[ a8 b8] |
\break
\mark \default
d8[ e8 e8] g8[ a8 b8] |
\fine
}
\score {
\new Voice = "mel" { \melody }
\layout {
\autoBeamOff
indent = 0\mm
}
}
The \set Score.rehearsalMarkFormatter = #format-mark-box-letters part
reformats the marks to display as letters inside a box - the default is
just a letter. By doing \default after the \mark Lilypond simply uses the
letters sequentially. If needed, the position of the marks can be adjusted.
Again, details on that are in the page linked above.
--
Michael
Re: Is there a better way to have a boxed part letter at the beginning of an arbitrary line?
Dear Kevin,
I use "\sectionLabel"s for this.
*\version "2.25.6"**
**\language "english"**
**melody = \relative c' {**
** \time 6/8**
** \key d \major**
** \clef treble**
** \sectionLabel \markup{ \box \pad-markup #0.5 "A" }**
** d8[ e8**
**e8] g8[ a8 b8] |**
** \break**
** \sectionLabel \markup{ \box \pad-markup #0.5 "B" }**
** d8[ e8**
**e8] g8[ a8 b8] |**
** \bar "|."**
**}**
**\score {**
** \new Voice = "mel" { \melody }**
** \layout {**
** \autoBeamOff**
** indent = 0\mm**
** }**
**}*
BTw, I just saw the second email you sent in this thread, and I'm not
exactly sure what you mean but I would probably have a separate variable
with the section labels, and you can combine them, a bit like this:
*\version "2.25.7"**
**
**sections={ \sectionLabel "1" s1 \sectionLabel "2"}**
**music = { c'4 d' e' d' c' e' g' c' }**
**
**\score {**
** \new Staff << \sections \music >>**
**}*
thanks,
-William
On 8/16/23 14:02, Kevin Cole wrote:
A minimum working example will make the question clearer: Although the
following produces what I want, it seems very ugly, and I suspect
there's a better way to accomplish the same thing: Placing the [A] and
[B] boxed letters for the tune parts at the beginning of a line.
\version "2.24.2"
\language "english"
melody = \relative c' {
\time 6/8
\key d \major
\clef treble
d8^\markup \translate #'(-10 . 0) { \box \pad-markup #0.5 "A" }[ e8
e8] g8[ a8 b8] |
\break
d8^\markup \translate #'(-10 . 0) { \box \pad-markup #0.5 "B" }[ e8
e8] g8[ a8 b8] |
\bar "|."
}
\score {
\new Voice = "mel" { \melody }
\layout {
\autoBeamOff
indent = 0\mm
}
}
--
+ --- +
| William Rehwinkel - Oberlin College and |
| Conservatory '24 |
|will...@williamrehwinkel.net |
| PGP key:|
|https://ftp.williamrehwinkel.net/pubkey.txt |
+ --- +
OpenPGP_signature
Description: OpenPGP digital signature
Re: Is there a better way to have a boxed part letter at the beginning of an arbitrary line?
P.S. Ideally, I want to make it part of a template, and be able to quickly replace the notes in the first measure of each part without having the part letter markup "embedded" in the measure between the first and second notes. I'm hoping for a way to specify it so that it is not tied to a note, but tied to the beginning of a line.
Is there a better way to have a boxed part letter at the beginning of an arbitrary line?
A minimum working example will make the question clearer: Although the
following produces what I want, it seems very ugly, and I suspect
there's a better way to accomplish the same thing: Placing the [A] and
[B] boxed letters for the tune parts at the beginning of a line.
\version "2.24.2"
\language "english"
melody = \relative c' {
\time 6/8
\key d \major
\clef treble
d8^\markup \translate #'(-10 . 0) { \box \pad-markup #0.5 "A" }[ e8
e8] g8[ a8 b8] |
\break
d8^\markup \translate #'(-10 . 0) { \box \pad-markup #0.5 "B" }[ e8
e8] g8[ a8 b8] |
\bar "|."
}
\score {
\new Voice = "mel" { \melody }
\layout {
\autoBeamOff
indent = 0\mm
}
}
Re: s-curve slurs across staves?
> Le 16 août 2023 à 18:52, Jin Choi a écrit : > > I came across a PDF describing updates to \shape that let you use head > centered coordinates and polar coordinates that would make this easier. But > my 2.24.0 version of lilypond doesn’t seem to include \shapeII. What is the > status of that? > It has never been part of LilyPond proper. You can find it the code here: https://github.com/openlilylib/bezier/blob/master/shapeII/module.ily (I haven't tested it on newer versions.)
Re: s-curve slurs across staves?
What PDF did you find this in?
-William
On 8/16/23 12:50, Jin Choi wrote:
I came across a PDF describing updates to \shape that let you use head centered
coordinates and polar coordinates that would make this easier. But my 2.24.0
version of lilypond doesn’t seem to include \shapeII. What is the status of
that?
On Aug 16, 2023, at 5:33 AM, Lukas-Fabian Moser wrote:
Hi Jin,
Am 16.08.23 um 04:48 schrieb Jin Choi:
Is it possible to get this style of s-curve shaped slurs across staves?
It's possible, but it's not fun.
\version "2.24.0"
\new PianoStaff
<<
\new Staff = upper {
<<
{
r8
\shape #'((0 . 0) (4 . -2) (0 . 6) (1 . 3)) Slur
8_( \change Staff = lower 4)
}
\new Voice { s2 r }
>>
}
\new Staff = lower \with { \clef bass } {
cis,4 r s r
}
Slurs live in a single voice (that's something I'm working on, but I don't have much time for
LilyPond work at the moment), so we have to create one voice that switches to the other staff on
the way. Then we have to adjust the control points manually, a task which is made harder by the
need to manually move the right tip of the slur from "under the note" to "above the
note".
There's definitely room for improvement, both in my example and in LilyPond
proper.
Lukas
--
+ --- +
| William Rehwinkel - Oberlin College and |
| Conservatory '24 |
|will...@williamrehwinkel.net |
| PGP key:|
|https://ftp.williamrehwinkel.net/pubkey.txt |
+ --- +
OpenPGP_signature
Description: OpenPGP digital signature
Re: s-curve slurs across staves?
I came across a PDF describing updates to \shape that let you use head centered
coordinates and polar coordinates that would make this easier. But my 2.24.0
version of lilypond doesn’t seem to include \shapeII. What is the status of
that?
> On Aug 16, 2023, at 5:33 AM, Lukas-Fabian Moser wrote:
>
> Hi Jin,
>
> Am 16.08.23 um 04:48 schrieb Jin Choi:
>> Is it possible to get this style of s-curve shaped slurs across staves?
>
> It's possible, but it's not fun.
>
> \version "2.24.0"
>
> \new PianoStaff
> <<
> \new Staff = upper {
> <<
> {
> r8
> \shape #'((0 . 0) (4 . -2) (0 . 6) (1 . 3)) Slur
> 8_( \change Staff = lower 4)
> }
> \new Voice { s2 r }
> >>
> }
> \new Staff = lower \with { \clef bass } {
> cis,4 r s r
>
> }
> >>
>
> Slurs live in a single voice (that's something I'm working on, but I don't
> have much time for LilyPond work at the moment), so we have to create one
> voice that switches to the other staff on the way. Then we have to adjust the
> control points manually, a task which is made harder by the need to manually
> move the right tip of the slur from "under the note" to "above the note".
>
> There's definitely room for improvement, both in my example and in LilyPond
> proper.
>
> Lukas
>
Re: auto-first-page-number add extra blank page
Hi Pierre-Luc,
>> Are you thinking about a conditional bookpart markup that would
>> (could) add a blank (or similar) page at page-number 0 *only* when the
>> music starts on the left page ?
> 'ment page-number "1"... got confused :-)
Yeah… but “conditional” = “manual” in my case: I just do something like
\bookpart {
\noTitles
\markup “This page left intentionally blank [or whatever]”
}
\bookpart {
\realScore
}
and adjust titling, margins, etc., accordingly.
Hope that helps!
Kieren.
__
My work day may look different than your work day. Please do not feel obligated
to read or respond to this email outside of your normal working hours.
Re: auto-first-page-number add extra blank page
Hi Kieren, > > Is there a way to add an extra blank page automatically as page 1 only > > when the auto-first-page-number sets the first (title) page to be 2 ? > I tend to just use a top-level bookpart/markup. > Will that work for you? Are you thinking about a conditional bookpart markup that would (could) add a blank (or similar) page at page-number 0 *only* when the music starts on the left page ? -- Pierre-Luc Gauthier
Re: "Slash" in figured bass
> From Förster's book: > https://www.digitale-sammlungen.de/view/bsb10527178?page=64 ex. 141 > I also attach an example from his "Practische Beyspiele", in which a > slightly different layout is being used in which the slash and the > figure are put separately over their respective notes. > > Of course it wouldn't be hard to cook up a solution (using \markup > in figures) for both styles, but I'd like to do it "the right way": > Do we already have a suitable slash symbol? If not, how should it be > designed? Has anybody of you already used this symbol? I haven't seen this before, and I believe this is an ad-hoc invention of Förster for pedagogical purposes. In particular, there is no fitting glyph in the SMuFL specification (AFAICS). Consequently, a simple `\markup` solution is probably the way to go. Werner
Re: auto-first-page-number add extra blank page
Hi Pierre-Luc, > Is there a way to add an extra blank page automatically as page 1 only > when the auto-first-page-number sets the first (title) page to be 2 ? I tend to just use a top-level bookpart/markup. Will that work for you? Hope that helps! Kieren. __ My work day may look different than your work day. Please do not feel obligated to read or respond to this email outside of your normal working hours.
"Slash" in figured bass
Folks (& especially: Dear Werner), in his "Anleitung zum Generalbasse" (and the accompanying "Practische Beyspiele") from the early 1800s, E. A. Förster uses a "slash" symbol in figured bass to denote a chord that is being described relative not to the current but to the next bass note. From Förster's book: https://www.digitale-sammlungen.de/view/bsb10527178?page=64 ex. 141 I also attach an example from his "Practische Beyspiele", in which a slightly different layout is being used in which the slash and the figure are put separately over their respective notes. Of course it wouldn't be hard to cook up a solution (using \markup in figures) for both styles, but I'd like to do it "the right way": Do we already have a suitable slash symbol? If not, how should it be designed? Has anybody of you already used this symbol? Lukas PS. Let me take this opportunity to say huge thanks again to Werner for his massive recent improvements in figured bass: With the new proper glyphs for slashed and plussed figures LilyPond can finally be used for scientifically accurate figured bass engraving.
Re: s-curve slurs across staves?
Hi Jin,
Am 16.08.23 um 04:48 schrieb Jin Choi:
Is it possible to get this style of s-curve shaped slurs across staves?
It's possible, but it's not fun.
\version "2.24.0"
\new PianoStaff
<<
\new Staff = upper {
<<
{
r8
\shape #'((0 . 0) (4 . -2) (0 . 6) (1 . 3)) Slur
8_( \change Staff = lower 4)
}
\new Voice { s2 r }
>>
}
\new Staff = lower \with { \clef bass } {
cis,4 r s r
}
>>
Slurs live in a single voice (that's something I'm working on, but I
don't have much time for LilyPond work at the moment), so we have to
create one voice that switches to the other staff on the way. Then we
have to adjust the control points manually, a task which is made harder
by the need to manually move the right tip of the slur from "under the
note" to "above the note".
There's definitely room for improvement, both in my example and in
LilyPond proper.
Lukas
Re: strange detached beam issue
I note some other differences between your image and what the code sample generates, in the slur and dynamic positions. I can't suggest what in particular is happening, but if this happened to me, I'd be looking for an earlier tweak or override which hadn't been cancelled. Paul From: Jin Choi To: Sent: 15/08/2023 23:11 Subject: strange detached beam issue I have a section of piano music where two voices start in the treble clef and subsequently move down into the bass clef. When the right hand moves down, the beam stays in the treble clef unattached to anything: When I try to isolate this section, the problem does not occur. I am mystified as to what is going on. What might be some things I could try?
Re: Question about condensed score
Good morning everyone,
going back to the solution written by David, I found that simply adding the
Duration_line_engraver causes the example to fail to compile.
Can anyone tell me why this happens?
Below is the minimal example:
%%%
global = {
s1\break
s1\break
s1
}
flOne = \relative c' {
e1
r1
e1
}
flTwo = \relative c' {
c1
r1
c1
}
\new StaffGroup \with { \consists "Keep_alive_together_engraver" }
<<
\new Staff \with {
\RemoveAllEmptyStaves
\override VerticalAxisGroup.remove-layer = 1
instrumentName = "Flute 1"
shortInstrumentName = "Fl. 1"
} <<\global \flOne>>
\new Staff \with {
\RemoveAllEmptyStaves
\override VerticalAxisGroup.remove-layer = 1
instrumentName = "Flute 2"
shortInstrumentName = "Fl. 2"
} <<\global \flTwo>>
\new Staff \with {
instrumentName = "Flutes"
shortInstrumentName = "Fl. 1-2"
\override VerticalAxisGroup.remove-layer = 2
} \partCombine \flOne \flTwo
>>
\layout {
\context {
\Voice
\consists "Duration_line_engraver"
}
}
%%%
Il giorno lun 14 ago 2023 alle ore 21:24 David Kastrup ha
scritto:
> Rip _Mus writes:
>
> > wow!!
> > Now I understand Knute's answer too.
> > Unfortunately, opening the page in the Italian version, the documentation
> > relating to the Keep_alive_together_engraver is not there.
>
> Its internals are documented, but its remove-layer settings are not
> really documented as a user-level feature. Part of the reason is that
> there should actually be a user-level layer of commands around the core
> settings, and _that_ should then get user-level documentation.
>
> But the skeleton of the feature can be made to walk without being
> fleshed out.
>
> > Thank you very much for the solution, thank you very much!
>
> Well, it is more embarrassing than anything. But occasionally I do
> catch questions for that functionality.
>
> --
> David Kastrup
>
