After inserting a version statement and running `convert-ly` on
http://lsr.di.unimi.it/LSR/Item?id=1000
I get this ominous error:
```
init.ly:64:2: error: Guile signaled an error for the expression beginning here
#
(let ((book-handler (if (defined? 'default-toplevel-book-handler)
In
> I try to set this ligature for an incipit:
>
>
> using
>
> ```
> \version "2.24.0"
>
> {
> \override NoteHead.style = #'mensural
> \[ a'1 c''
> \override NoteHead.ligature-flexa = ##f
> a'\breve \]
> }
>
> \layout {
> \context {
> \Voice
> \remove
>> This smells like a bug: `\wordwrap-string` returns a bunch of lines
>> spaced by `baseline-skip`, but no such skip is applied after the
>> last line, for whatever reason.
>
> Why would it be applied after the last line?
Oh, I didn't mean that `\wordwrap-string` actually should insert such
a
> btw: why is it named "baseline-skip" and not "baseline-distance"?
This is historical: LilyPond's origins are with TeX, and a 'skip' in
TeX is a stretchable and/or compressable whitespace (either horizontal
or vertical).[0] The baseline-to-baseline distance is such a skip in
TeX; the
> Maybe I'm missing something here, but how can I make the space
> between items in a markup column regular? As you can see in the
> example, if the text is short so that there is no wrapping
> necessary, the space is fine. But the "a a a" item does wrap around
> and overlaps a bit with the "b
> What do you mean by “convert”?
Probably bad wording: I mean to wrap a markup list into a markup.
> I don’t know what it means to convert a markup list to a markup,
> since there are many ways in which you can combine the stencils:
> \column, \center-column, \line, \concat, \fill-line, etc.
I
What's the proper way to convert a `\markuplist` to a `\markup`?
`lilypond-book` splits a top-level `\table` into separate lines; I
want to avoid that because it prevents fine-tuning of the vertical
spacing of rows. Right now I do
```
\markup \column {
\table ...
}
```
Werner
>> I expect that both the 'x' and the 'g' are aligned at the baseline.
>> However, it doesn't work.
>>
>> AFAICS, the `TextMark` grob contains `side-position-interface`. What
>> am I missing?
>
> See https://gitlab.com/lilypond/lilypond/-/issues/342
Interesting, thanks! I wouldn't have
Please have a look at this snippet:
```
{
\override Score.TextMark.staff-padding = 2
\textMark "x" c''
\textMark "g" c''
}
```
I expect that both the 'x' and the 'g' are aligned at the baseline.
However, it doesn't work.
AFAICS, the `TextMark` grob contains `side-position-interface`.
Dear Frescobaldi team,
> We are glad to announce the availability of Frescobaldi 3.3.0.
> [...]
Is it necessary to update the Frescobaldi installation instructions in
LilyPond's Learning Manual?
https://lilypond.org/doc/v2.25/Documentation/learning/installing
> Consider the following snippet:
>
> ```
> Emaj = \markup { E \raise #1 maj }
>
> \markup \Emaj
>
> \markup \fontsize #10 \Emaj
> ```
>
> As can be seen, `\raise #1` is not the right value in the second
> case. [...]
This is now
https://gitlab.com/lilypond/lilypond/-/issues/6576
Consider the following snippet:
```
Emaj = \markup { E \raise #1 maj }
\markup \Emaj
\markup \fontsize #10 \Emaj
```
As can be seen, `\raise #1` is not the right value in the second case.
What I would like to have instead is an equivalent to TeX's relative
units `em` and `ex`, being multiples
> [https://gitlab.com/lilypond/lilypond/-/issues/6566](https://gitlab.com/lilypond/lilypond/-/issues/6566)
>
> I am pretty surprised that this fundamental bug went unnoticed over
> the years (not sure for how long it has been around). LilyPond's
> page layout is smart, but sometimes I think it's
> `\rounded-box` does not displace its argument, it only adds a box
> around it. In the first case, the stencil has protrusion on the left
> (the start of its horizontal extent is negative). This doesn't
> happen in the second case because `\table` realigns everything. Try
>
> ```
> \markup
Consider the following example.
```
\paper {
left-margin = 0
}
\markup \rounded-box { foo }
\markuplist \table #'(-1) {
\rounded-box { foo }
}
```
Why is there a difference in the formatting? I would like to have the
same behaviour – ideally, `\markup` should also take the rounded box
>> Or am I still missing the one place where that explanation is
>> provided?
>
> It's here:
>
> https://lilypond.org/doc/v2.24/Documentation/usage/other-programs
I've added links.
https://gitlab.com/lilypond/lilypond/-/merge_requests/1901
Werner
> Going back to the manuals didn't help explain tall-page-formats:
> [...]
>
> Maybe the documentation of separate- and tall-page-formats
> should elaborate more.
This is very likely. May I invite you to provide improvements to the
text? You have first-hand experience :-)
Werner
>> >> Alas, it *still* doesn't work as expected. Obviously, I have
>> >> simplified the code example too much: adding a `ChordNames` context
>> >> prevents alignment. Note that the top skyline of the chord symbol
>> >> doesn't show anything suspicious.
>
> I am not yet sure if this is a bug or
>> Alas, it *still* doesn't work as expected. Obviously, I have
>> simplified the code example too much: adding a `ChordNames` context
>> prevents alignment. Note that the top skyline of the chord symbol
>> doesn't show anything suspicious.
>
> Okay, then I think we are hitting something
>
> \markup \with-dimensions #'(0 . 0) #'(2.5 . 0)
> \general-align #Y #UP "foo"
>
>
> The vertical extents #'(0 . -2.5) and #'(2.5 . 0) both have the same
> effective height of -2.5 units, however they have a different
> relative starting point which is important for what may appear
>> [...] the ideal solution would be that the custos is really at the
>> end of the staff line, and the extra note is just there to indicate
>> at which pitch the custos gets typeset.
>
> This should do:
It does, thanks a lot!
Werner
>> It would be cool if this worked some day. However, the next best
>> thing would probably be to allow negative widths and heights for
>> `\markup` boxes (if set with `\with-dimensions` and friends).
>
> Was messing about a bit. Does this work on your side?
Alas, no. It is probably related
>> I would like to have a command that inserts a `Custos` grob. Note
>> that it should really be a `Custos` grob and not something else so
>> that `\BalloonGrobText Custos ...` works.
>>
>> Is there a possibility to do that?
>
> What is the context? Do you want the custos' pitch to be determined
I would like to have a command that inserts a `Custos` grob. Note
that it should really be a `Custos` grob and not something else so
that `\BalloonGrobText Custos ...` works.
Is there a possibility to do that?
Werner
>> I tried
>>
>> ```
>> \markup \with-dimensions #empty-interval #empty-interval {
>> ... }
>> ```
>>
>> and the padding to the next score gets still applied. I suspect
>> that the 'empty interval' trick only works for stuff within a score
>> but not on the top level.
>
> I'd be tempted to
>>> If you don't want vertical padding, your horizontal dimensions
>>> must be an empty interval, not a point interval.
>>
>> OK, but how do I do that for `\markup`?
>
> Maybe this: \markup \with-dimension #X #empty-interval ...
>
> (Assumes you are using 2.24 that supports the axis-specific
>> ```
>> \markup \with-dimensions #'(0 . 0) #'(0 . 0) {
>> ...
>> }
>
> If you don't want vertical padding, your horizontal dimensions must
> be an empty interval, not a point interval.
OK, but how do I do that for `\markup`?
Werner
>> ```
>>
>> I wonder whether it is possible to temporarily override paper
>> variables at the top level, something like
>>
>> ```
>> \once \set markup-system-spacing.padding = 0
>> \markup { ... }
>>
>> \score { ... }
>> ```
>
> Unfortunately, no.
OK, thanks.
> However, you should be able
I wonder whether it is possible to temporarily override paper
variables at the top level, something like
```
\once \set markup-system-spacing.padding = 0
\markup { ... }
\score { ... }
```
Werner
> The "elegant" solution intrigues me, but the link to the thread
> appears to be down.
Yesterday and today there was a hiccup with gnu.org (and nongnu.org);
see
https://hostux.social/@fsfstatus
It seems to be fixed now.
Werner
> > Can you please suggest a better wording that I can add to the
> > documentation?
>
> May I have the day to ruminate?
Please take your time, and thanks for working on this!
Werner
> > > The documentation does not explicitly relate stem direction with
> > > location of command. So I am very fortunate to have your
> > > expertise.
> >
> > Can you please suggest a better wording that I can add to the
> > documentation?
>
> Well, this is the first time I've heard that
> The documentation does not explicitly relate stem direction with
> location of command. So I am very fortunate to have your expertise.
Can you please suggest a better wording that I can add to the
documentation?
Werner
> Is there a way to have a multiline copyright statement in a file?
Use
```
copyright = \markup { ... }
```
to construct a multi-line entry. However, it might also be necessary
to use a custom version of `oddFooterMarkup` to get good formatting;
see `ly/titling-init.ly` for the original
> Hi Werner, With NBN in Australia, the speeds are amazing. [...]
Well, a great percentage of the world does not have such amazing
circumstances...
Werner
> Here's some other compression solutions. This page points out that
> the tradeoff for squishing is lower quality images and text.
Link missing?
> In this day of gigabyte this an terabyte that, does a large PDF
> matter very much?
IMHO yes. Today, PDF files are loaded *and* displayed in a
> I can see that the size of the Cairo-generated PDF is around 3 times
> bigger compared to the same document generated with Ghostscript? Is
> there is way to reduce the size of the Cairo-generated PDF?
You might try `pdfsizeopt`.
https://github.com/pts/pdfsizeopt
Werner
From: Kees van den Doel
Subject: Re: Bach ornaments
Date: Thu, 16 Mar 2023 23:12:03 -0700
>> > Are the ornaments used in Bach's music available in Lilypond?
>
>> Not all of them currently. There is GSoC project that – assuming it
>> is taken by a potential student – would probably add some
>> Are the ornaments used in Bach's music available in Lilypond?
>>
>> These ones: http://www.jsbach.net/images/ornaments.html
>
> Not all of them currently.
However, with some manual trickery, it is possible to generate the
missing ones so that they can be used as if real glyphs existed for
> Are the ornaments used in Bach's music available in Lilypond?
>
> These ones: http://www.jsbach.net/images/ornaments.html
Not all of them currently. There is GSoC project that – assuming it
is taken by a potential student – would probably add some missing
ones.
> use:
>
> ```
> % movement1.ly
> variable = \relative c'' { ... }
> bookpartI = \bookpart { \score { \variable } }
>
> % movement2.ly
> variableII = \relative c'' { ... }
> bookpartII = \bookpart { \score { \variableII } }
>
> % main.ly
> \include "movement1.ly"
> \include "movement2.ly"
>
> By chance, I read the announcing email at 16:59, just in time to
> start the stream and to follow David's lecture on Lilypond and
> Frescobaldi. It was a refreshing experience to watch and listen to
> one of those friendly people involved in the development, [...]
Yeah, David did a good job!
> My experience installing Lilypond is with the Windows Installer.
>
> I know what a Zip file is yet I have never used one to install a
> program. Is there some more detailed instructions than what is
> provided in The Graphical Setup for Windows?
What exactly is your problem?
The basic
> Thanks - my output included no such warning.
> (lyluatex) Compiling score tmp-ly/51d5af77a942f28ac1f5986a0ab47d35
> with LilyPond executable 'lilypond'.
>
> Module lyluatex Warning: The score doesn't contain any music:
> (lyluatex) this will probably cause bad output. on
> I seem to have some sort of platform difference between my desktop
> and laptop computers. I'm rendering a bare time signature and tempo
> in a LaTeX table using lyluatex.
>
> The snippet: [...]
>
> {
> \new RhythmicStaff \with {\remove "Staff_symbol_engraver"}
> { \time 6/8
> > * Replace `--show-rules` with a more common `--verbose` option to
> > show rule descriptions while `convert-ly` is running. Right
> > now, `--show-rules` only emits the rules but doesn't do a
> > conversion at the same time, which is rather useless IMHO. Not
> > sure whether my
> > who has ever used option `--show-rules` of `convert-ly`, except for
> > being curious what this option does?
> >
> > In https://gitlab.com/lilypond/lilypond/-/merge_requests/1854 we are
> > discussing whether it would make sense to remove it.
>
> I've definitely used it a number of times
Folks,
who has ever used option `--show-rules` of `convert-ly`, except for
being curious what this option does?
In https://gitlab.com/lilypond/lilypond/-/merge_requests/1854 we are
discussing whether it would make sense to remove it.
Please comment.
Werner
>> In short, is there a way to set "ss03" globally?
>
> This should do:
>
> ```
> \paper {
> text-font-defaults.font-features = #'("ss03")
> }
> ```
I think it would be very beneficial to add documentation for
`text-font-defaults` to the NR.
> I didn't go into detail, but I can assure you user emails are not
> exposed on the web in Discourse, [...]
I didn't say or imply that.
> but a post has to be associated with an account, and an account has
> to be verified by emailing the user, and the email is stored in
> their private
Andrew,
thanks for your long reponse. I have to correct two of your
statements:
> But (contrary to a false statement I made about import into
> Discourse) you can't import mailbox format lists into Discourse
> simply, because, for example, the creation of users from 25 years
> ago who most
> I looked up the other list that moved to Discourse (I think they had
> the same Discourse/Discord confusion), but I remember that being
> sold strongly on the web interface. I was certainly left with the
> very strong impression email was a second class citizen.
As mentioned already: The most
> Additionally, I find value in the archived aspect of web fora in
> which all the discussions remain available in a very convenient
> manner.
If you look at the e-mail fields of any message you receive from the
list, you can see the following
List-Id: LilyPond user discussion
> You can see on the cis
> that the dot is there (sticking to the bottom of the cis).
D'oh, I missed this, thanks!
I've now completely rewritten and simplified LSR #280 to make its
description align with the visual result.
Werner
Please have a look at LSR snippet #280.
https://lsr.di.unimi.it/LSR/Item?id=280
What is the reason that the accent appears from the very beginning,
while the staccato dots are shown later on? I thought that both are
articulations and are handled the same.
Werner
> And joining is actually pretty serious friction for some people - the
> more lists I join, the more likely I am to abandon attempts to help if
> I'm required to register.
I second that concern. Being the maintainer of the FreeType mailing
lists, I face exactly the same problem. Usually, I
> I missed it at first, but it's actually very easy in your example.
Thanks, added to #6533.
Werner
> Is there a simple way to stretch the bar width of short scores to full page
> width?
>
> Example:
>
> \score {
>\relative c' {
> c2( b' a c f, d b' b, c a' g d e c') \bar "|."
>}
>\layout {
> \context {
>\Score
>\hide TimeSignature
>\time 14/2
>
>> The issue I filed is not related to `strict-grace-spacing` at all.
>
> It’s quite related. [...]
With 'related' I meant that there are two separate bugs. I didn't
talk about what the best fix for the whole problem actually is.
> In strict-grace-spacing mode, grace columns are not part of
> Well, that’s what you get if the LilyPond version is too old. The
> question was for a version that is “too new”.
D'oh, right :-)
Werner
>>> I tried that, but as soon as a group of grace notes has some
>>> accidentals it produces bad output.
>>
>> Doesn't that sound more like the issue should be
>> "strict-grace-spacing produces bad output if grace note has
>> accidental" rather than "strict-grace-spacing should be the
>>
> What is expected to happen when Lilypond 2.24.1 encounters a score
> with a version of 2.22.2 in it? Well, I'll try to carefully reproduce
> (or not!) my experience!
It prints a thick fat warning that the LilyPond version is too old to
handle this score. It proceeds, but it returns an
> I did not previously realize that Lilypond would automatically update
> pre-existing scores.
It doesn't. Are you using Frescobaldi? Maybe this front-end can be
set to automatically run `convert-ly`.
Werner
>> I tried that, but as soon as a group of grace notes has some
>> accidentals it produces bad output.
>
> Doesn't that sound more like the issue should be
> "strict-grace-spacing produces bad output if grace note has
> accidental" rather than "strict-grace-spacing should be the
> default"?
The
> Try playing around with spacing parameters. As a starting point:
>
> \override Score.SpacingSpanner.strict-grace-spacing = ##t
I tried that, but as soon as a group of grace notes has some
accidentals it produces bad output.
This is now
https://gitlab.com/lilypond/lilypond/-/issues/6533
Please have a look at this example.
```
{
\omit Staff.TimeSignature
\repeat unfold 16 { \grace e'8 d'4 } \break
\repeat unfold 8 { \grace e'8 d'4 }
}
\paper { indent = 0 }
```
As can be seen, the spacing between grace notes and the corresponding
main notes increases if the overall
I've further refined and simplified the footnote spacing example; it
is now available in the LSR
https://lsr.di.unimi.it/LSR/Item?id=1165
Werner
>> [...] after doing a grep over the git repository, which leads me to
>> `property-iterator.cc`, it's not really clear to me what's going
>> on...
>
> Well, you can find it in `define-event-classes.scm`. It's the event
> class for events created by `\override`s.
Ah, yes, I missed that while
>> As can be seen, the acciaccatura neither has a slash nor a slur if
>> quoted. [...]
>
> This looks like a real bug, please file an issue.
https://gitlab.com/lilypond/lilypond/-/issues/6531
> AFAICS, this works:
>
> ```
> \version "2.25.2"
>
> \layout {
> \context {
> \Score
>
> I am trying to attach a footnote to the center of a glissando as
> pictured below.
In case you don't mean "footnote" but rather "automatically rotated
word 'gliss.' under the glissando line", have a look at
https://lists.gnu.org/archive/html/lilypond-user/2016-06/msg00422.html
This might
Consider this example.
```
fluteNotes = \relative {
r2. c''4 |
d8 \acciaccatura e c d e fis2 |
g2 d |
}
oboeNotes = \relative c'' {
R1 |
\cueDuring "flute" #UP { R1 } |
g2 d |
}
\addQuote "flute" { \fluteNotes }
<<
\new Staff \fluteNotes
\new Staff \oboeNotes
>>
```
As can be
>> However, there is one problem that I don't understand: Why is the
>> space between footnotes 3 and 4 (and 4 and 5) larger than between 1
>> and 2 (and 2 and 3)?
>
> Well, in footnotes 1 and 2, there is only one strut for the two
> lines. Try this, [...]
Excellent, thanks again! Here's my
> Maybe this was already submitted. I am looking for this particular
> symbol to use as alteration for 1/8th tones. (cf. screenshot
> attached) However it seems missing in the Emmentaler font. Is it
> possible to include it or this is a complicated task? I have
> fontforge on my computer. I
> To change those properties, you could do
>
> ```
> \paper {
> text-font-defaults.baseline-skip = 3
> }
> ```
>
> [...]
>
> ```
> \override Score.Footnote.footnote-text =
> #(grob-transformer
> 'footnote-text
> (lambda (grob orig)
> #{ \markup { \strut #orig
> Maybe it would be useful to be able to override the formatting of
> the footnote block, similar to how we have toItemMarkup. We could
> allow the user to format footnotes using some footnoteMarkup
> callback?
This is issue https://gitlab.com/lilypond/lilypond/-/issues/2561
Werner
>> Am I the only one who thinks users shouldn’t have to add
>> transparent letters with ascenders and descenders in order to have
>> a consistent line height?! Working with text should not require
>> such efforts…
>
> Unfortunately, LilyPond's idea of stencils is not prepared for doing
> that
Consider this example.
```
#(set-default-paper-size "a8landscape")
\book {
\header { tagline = ##f }
\markup "time-based footnotes"
\relative c'' {
r1 |
\footnote #'(-0.5 . -1) "Meter change." Staff.TimeSignature
\time 3/4
\footnote #'(1 . -1) "Chord stem." Stem
4 q q
> That is because you are using 1 instead of a note name such as c'1. after-
> grace does not handle this mechanism.
Thanks (and thanks to Lukas, too)!
> Instead of manually extra-offsetting the Clefs you might also do
> something along the lines of [...]
Nice! I will use that.
Werner
>> Can someone please explain to me why the 'p sub.' in the first
>> system is badly spaced compared to the second one? How can I avoid
>> this? Actually, this smells like a bug...
>
> You can read your own answer to this question here:
>
> https://gitlab.com/lilypond/lilypond/-/issues/6350
Can someone please explain to me why the 'p sub.' in the first system
is badly spaced compared to the second one? How can I avoid this?
Actually, this smells like a bug...
```
\version "2.25.2"
psub = \tweak DynamicText.self-alignment-X #-0.7
#(make-dynamic-script
#{ \markup {
> [...] I'm rather inclined to count the behaviour of `space-alist`
> for clefs as a buglet: It doesn't make sense allowing the clef to
> move 'under' other notes in different staves while its `space-alist`
> values are applied globally to all staves.
This is now issue #6529.
Hello Valentin,
> My suggestion to getting around this would be the tell Lilypond that
> the clef stencil is in fact narrower than it actually is, which will
> allow the Clef stencil to protrude arbitrarily much: [...]
Thanks! Interestingly, the clef still gets some extra horizontal
space,
Please look at this example.
```
\relative c' {
<<
{ \afterGrace f1 { e16[ f] } | g1 }
{ c1 \clef "bass" | c,1 }
>>
}
\relative c' {
<<
{ f2.. e16[ f] | g1 }
{ c1 \clef "bass" | c,1 }
>>
}
```
What can I do to make the clef move 'under' the grace, similar to the
> This is because it assumes that Slur.control-points is still set to
> its original callback at the time `after-line-breaking` is run,
> which isn't true if something like
> `ly:side-position-interface::move-to-extremal-staff`, in
> `BarNumber.after-line-breaking`, reads `control-points`
I'm using the `\offsetPosition` command
(https://lsr.di.unimi.it/LSR/Item?id=748). Unfortunately, it fails in
a multi-staff, real-world piece: it has zero effect, and I don't know
why. What could be the cause for that? If I had a hint, creating an
MWE would perhaps be more straightforward...
> I actually looked, but found this page -
> https://lilypond.org/doc/v2.22/Documentation/notation/clef-styles
> there it's not mentioned :(
https://gitlab.com/lilypond/lilypond/-/merge_requests/1838
Werner
> REDACTED/source/The_Way_We_Were.ly:259:1: warning: cannot find
> context to change to: Staff = lower
This is because you are already in the "lower" staff. As the name
`\change Staff` implies, it is intended to display material
temporarily in another staff. In other words, the eighth notes
>> {
>> e1\< | g''1\breakDynamicSpan\ff |
>> }
>
> I'll eventually submit a patch to fix that.
This is now
https://gitlab.com/lilypond/lilypond/-/merge_requests/1829
Werner
> I've always terminated my cresc/decres with \!
> I found that in the docs a while ago, but is that still the case?
>
> e1\< | a2\!\ff b2
>
> Is the way I'd have done it.
AFAIK, this has never worked. If `\!` and `\ff` are at the same
moment, `\!` gets ignored.
Note that
>> Strange transposition rules also exist for horns, where in the
>> violin clef you transpose down, and in the bass clef you transpose
>> up.
>
> Violin clef?
Sorry, bad translation from German: I meant horn parts notated with a
treble clef.
Werner
>> What is the 'official' way to break the alignment between, say, a
>> crescendo wedge and a subsequent forte sign? What I want is
>> automatic placement of the 'f' by LilyPond as if there were no
>> crescendo wedge.
>
> \version "2.24.0"
>
> {
> e1\< | g''1\breakDynamicSpan\ff |
> }
Aah,
>> But the user shouldn't see an assertion error even in case of a wrong
>> argument, right?
>
> Yeah,
> https://gitlab.com/lilypond/lilypond/-/merge_requests/1828
Thanks!
Werner
What is the 'official' way to break the alignment between, say, a
crescendo wedge and a subsequent forte sign? What I want is automatic
placement of the 'f' by LilyPond as if there were no crescendo wedge.
```
{
e1\< | g''1\ff |
}
```
Werner
>> When I attempt to change the "direction" property of a slur,
>> whether that is with \tweak or \override, I cannot set the
>> direction to neutral (0). UP (1) and DOWN (-1) work fine, but when
>> setting to 0, I get the following error:
>>
>> "Assertion failed: d, file
>>
> The "R.H." instruction with 45 degree slope down and up from treble
> to bass clef: How?
Look up 'staff-change lines' in the Notation Reference index to get
details on the `\showStaffSwitch` command.
Werner
>> Veeery nice, thanks! I only wonder what situation you envision to
>> add a special property for skips...
>
> \version "2.24.0"
>
> \new Staff \relative
> <<
> { c'8[ s s c] }
> \\
> { s c c s }
>>>
>
> doesn't seem unreasonable to me (for example in piano music).
OK, thanks.
> > IMHO, there are definitely valid situations where
> > automatic beaming over rests does make sense.
>
> this would not be hard to get done. Here’s an experimental commit:
> [...]
Veeery nice, thanks! I only wonder what situation you envision to add
a special property for skips...
> jetéMarkup =
> \markup \undertie \pad-x #0.3
> \pattern #4 #X #0.1 \musicglyph "dots.dot"
Note that this kind of markup is not only used for jeté but also for
staccati under a slur if the note has a stem tremolo, as shown in the
attached image.
Ideally, it would be very nice if we could
>> The NR says that autobeaming doesn't work over rests. In some
>> situations this means a lot of additional work. As an example,
>> consider a piece that uses almost exclusively a saltarello-like
>> rhythm:
>>
>> ```
>> \time 6/8 d8[ r d] d[ r d]
>> ```
>>
>> I now wonder whether it makes
The NR says that autobeaming doesn't work over rests. In some
situations this means a lot of additional work. As an example,
consider a piece that uses almost exclusively a saltarello-like
rhythm:
```
\time 6/8 d8[ r d] d[ r d]
```
I now wonder whether it makes sense to control this
201 - 300 of 1738 matches
Mail list logo
