us
music constructs (namely << ... >> ) to enter the clefs into the current
Staff .
--
David Kastrup
empty, and that is the usual way to access such a variable. So
it is unlikely that this ever had been a part of LilyPond.
> Maybe you redefined a title using one of the xxxTitleMarkup variables, and you
> used \fromproperty #'header:number there?
>
> Or maybe you're just confusing this with the 'opus' variable?
I guess the latter.
--
David Kastrup
operations on it). This is easy to get wrong since
frenched scores are not typically specifically tested for.
Putting its original author in Cc.
--
David Kastrup
ble fix for this since \with does double
duty for passing named arguments to functions. You may want to argue
that \override/\revert should not be used in that fashion, but
assignments/\set have sort of the same problem (though admittedly
different syntax anyway).
--
David Kastrup
Viktor Mastoridis writes:
>>
>> \layout {
>> \shrink Staff.PercentRepeat
>> \shrink Staff.RepeatSlash
>> \shrink Staff.DoubleRepeatSlash
>> }
>
>
> Thank you for this, David. It's a handy little shortcut.
It's actually several shortcuts playing
(lambda (grob orig) (ly:stencil-scale orig 0.7
0.7)))
\etc
\layout {
\shrink Staff.PercentRepeat
\shrink Staff.RepeatSlash
\shrink Staff.DoubleRepeatSlash
}
\new TabStaff \with {
stringTunings = #ukulele-tuning
}
\relative c {
\tabFullNotation
\repeat percent 2 { c'4 d e g}
\repeat percent 2 { c,16 d16 e8}
\repeat percent 2 { c8 d8}
}
--
David Kastrup
or the solution, thank you very much!
Well, it is more embarrassing than anything. But occasionally I do
catch questions for that functionality.
--
David Kastrup
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
>>
--
David Kastrup
with a staff name showing the indication "fl. 1-2").
>
> Could you help me get this result?
I am not going to compose a whole example. Please provide sufficient
material for showcasing your problem.
--
David Kastrup
:music? ly:music?)
(music-clone seq 'elements
(map (lambda (p) #{ \transpose c #(ly:music-property p 'pitch ) $motiv #})
(ly:music-property seq 'elements
motiv = { c'4 d' e' c' }
\multitranspose { d e fis gis } \motiv
--
David Kastrup
Lukas-Fabian Moser writes:
> \new Staff = down \with { \clef bass } {
That sentiment was part of why I chose to switch from tenor to male alto
instead of bass. An easier change for sight-reading.
--
David Kastrup
ency.
> Without extra arguments, (music-clone m) should be strictly
> equivalent to (ly:music-deep-copy m).
The extra arguments are different, and, well, it is shorter to write.
--
David Kastrup
n "2.24.0"
>
> mus = { c' d' 4. f'8 }
>
> <<
> \new RhythmicStaff \mus
> \new Staff \mus
>>>
>
> I'm not sure whether that should be called a bug: one would have to
> think a bit about the most natural way to deal with chords here.
\new RhythmicStaff #(event-chord-reduce (music-clone mus))
--
David Kastrup
Alasdair McAndrew writes:
>> On Mon, 7 Aug 2023 at 00:11, David Kastrup wrote:
>>
>>> Alasdair McAndrew writes:
>>>
>>> > Thank you very much indeed for your offer. I'll try to put something
>>> > together: currently my files are split up
> {\override NoteName.#'stencil = #ChimeNoteNames }
> and the warning disappear with this notation
Ugh. Please just write NoteName.stencil here. This is 2.18+ syntax.
--
David Kastrup
aim to make a simple
> representative file which includes the lot!
>
> But as I said earlier the music is split into two definitions: one
> contains the pitch information, and the other the rhythm. These are
> then put together as I described in my first post.
Why?
--
David Kastrup
:music?)
Just a warning: inventing unconventional formattings like this (putting
# on a different line as the opening paren) carries the danger of
keeping convert-ly (and syntax highlighters and syntax-sensitive
editors) from recognizing the construct.
--
David Kastrup
rouble envisioning where you'd want the dot to go. Maybe
LilyPond is having similar trouble?
--
David Kastrup
Jean Abou Samra writes:
> Le vendredi 21 juillet 2023 à 23:38 +0200, David Kastrup a écrit :
>> > As of 2.25.6, the difference between the two forms of \tweak no longer
>> > appears necessary: globally replacing thousands of "- \tweak ..." with
>> > just
weak thickness #5 ( d e f) } % hyphen
>
> ... even though ...
>
> \relative { c' \tweak thickness #5 ( d e f) } % no hyphen
>
> ... works under 2.25.6.
As long as you cannot rely on it working outside of simple cases, it is
not a good idea to advertise it.
> Thanks so much for this!
If you want to check the discussion, this was issue 5181. It's a
Pyrrhic horse, really.
--
David Kastrup
oblem is that successive \override incantations revert
previous incantations in the same context _unless_ you use \temporary
\override .
If you do your second grob-transformer invocation (or both) with a
\temporary \override, it will leave the first call in place. Of course
you'll need a double \revert then if you want to get rid of both calls.
--
David Kastrup
does not need to retain a
useful stack when generating a stack trace? Because the option is not
called "invalidate stack" but "no return".
In contrast, I find the optimisation that assumes that constants will
not be modified comparatively understandable. Without that assumption,
you'll never be able to fold multiple constants.
--
David Kastrup
t; \startTextSpan
> c'1
> \stopTextSpan
> }
>
> %%% END %%%
>
> What's the right way to return markup from a Scheme function?
You are doing fine in that regard, but subproperties don't have callback
evaluation.
--
David Kastrup
Виноградов Юрий writes:
> 12:51, 11 июля 2023 г., David Kastrup :
>>
>> Please never, never, never, ever quote an entire week's digest to the
>> list with any new post to the list. The entirety of your mail,
>> including the last week's digest, will clog up the nex
e counted in the measure.
>
> Thank you all in advance.
Please never, never, never, ever quote an entire week's digest to the
list with any new post to the list. The entirety of your mail,
including the last week's digest, will clog up the next week's digest.
And so the digests will keep piling up.
--
David Kastrup
Valentin Petzel writes:
> Am Sonntag, 9. Juli 2023, 09:42:52 CEST schrieb David Kastrup:
>> The latter is definitely the _natural_ way to enter this construct
>> (single voice simultaneity) but I do seem to remember that LilyPond did
>> not deal well with it?
>
> The
page. I've looked at some of the vertical spacing controls, and so
> far my attempts to use them seem to make things look worse. Can anyone
> share some general tips for the order of things to try to do some gentle
> squeezing?
How about just telling LilyPond you want 6 pages?
\paper {
piano, so you wouldn't want the note to
> sound louder than the surrounding notes, because the doubled note is played
> by only one hand.
Frankly, a player who does not differentiate overlapping identical notes
in momentarily converging voices from single notes is not doing the
listener a favor.
--
David Kastrup
different strings makes the result louder
than playing it on a single string.
--
David Kastrup
ecessary as there has been no music before this, so there
> does not exist a voice, and Lilypond will then create one Voice for each
> parallel music).
The latter is definitely the _natural_ way to enter this construct
(single voice simultaneity) but I do seem to remember that LilyPond did
not deal well with it?
--
David Kastrup
non-English languages where vowels
aren't pronounced in dozens of different ways depending on how a word
completes.
--
David Kastrup
Jean Abou Samra writes:
> Le lundi 03 juillet 2023 à 22:08 +0200, David Kastrup a écrit :
>> Ugh, that's a can of worms. #xxx will only accept a context-dependent
>> set of values and reject values not fitting the context. But the
>> context includes whether or
David Kastrup writes:
> Lukas-Fabian Moser writes:
>
>> Or maybe even:
>>
>> \version "2.25.6"
>>
>> parts = {
>> { c' }
>> { d' }
>> { e' }
>> { f' }
>> }
>>
>> group = #
>> (define-music-func
magical word "SimultaneousMusic". Admittedly, my approach required
knowing the magical word "elements".
--
David Kastrup
quot;
parts = {
{c'}
{d'}
{e'}
{f'}
}
group =
#(define-music-function
(parts) (ly:music?)
#{\new StaffGroup << #@(ly:music-property parts 'elements) >>#})
\group \parts
```
--
David Kastrup
Valentin Petzel writes:
> Am Samstag, 1. Juli 2023, 18:48:31 CEST schrieb David Kastrup:
>> The funny thing is that I suspect Han-Wen might still be surprised to
>> hear what Staff.property "actually means".
>>
>> It's been around for quite longer than its
like this
[...]
The funny thing is that I suspect Han-Wen might still be surprised to
hear what Staff.property "actually means".
It's been around for quite longer than its "actual meaning". But of
course I should be the last person to complain about my retconning
making headcanon.
--
David Kastrup
Jean Abou Samra writes:
> Le jeudi 29 juin 2023 à 17:56 +0200, David Kastrup a écrit :
>
>> No, none of the "standards" say anything like that. #(...) is a
>> self-quoting form, like #t and #f and numbers and strings and some other
>> things. Q
say anything like that. #(...) is a
self-quoting form, like #t and #f and numbers and strings and some other
things. Quoting them doesn't change a thing.
And to be honest, I don't know of any _convention_ that would recommend
explicitly quoting them or other self-quoting forms, either.
--
David Kastrup
FAIK,
> acc = #acciaccatura
> and likewise
> af = #after
> will have the same effect.
True. The actual value of \etc is when you want to supply some initial
fixed arguments while keeping the rest variable.
For just creating an alias taking the same number of arguments, the
above way is at least conceptually simpler.
--
David Kastrup
define-music-function (dur mus) (ly:duration?) (ly:music?)
#{ \after #dur \! #mus #})
--
David Kastrup
the Ukrainian anthem.
Just a suggestion for possibly low-hanging fruit.
--
David Kastrup
d down.)
I was not thinking in spatial dimensions.
Maybe "linear" or "well-ordered" would have been a better expression.
The priority system essentially states the order of type X and type Y
independent of whether a grob of type Z needs to be accommodated as
well.
--
David Kastrup
lative e'' { \voiceOne e4 \after 8 \tweak outside-staff-priority 0 \turn
> e8.
> f16 e2 }
Bad defaults can be a bug like bad code. Of course that begs the
questions of whether there are better defaults, or whether the
one-dimensional outside-staff-priority system is even well-suited for
expressing the desired rules/constraints.
--
David Kastrup
"Andy Bradford"
writes:
> Thus said David Kastrup on Sat, 17 Jun 2023 18:44:54 +0200:
>
>> Some mail clients may, for that reason, even have a dedicated
>> "Unsubscribe" button. But you can always look in the headers.
>
> It's a shame that so
equ...@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/lilypond-user>,
<mailto:lilypond-user-requ...@gnu.org?subject=subscribe>
Some mail clients may, for that reason, even have a dedicated
"Unsubscribe" button. But you can always look in the headers.
--
David Kastrup
been implemented, I don't remember anybody writing up an error
report about the more subtle semantics when LilyPond now tries to clean
up its parsing after the fact.
--
David Kastrup
(there has been a
"second take" around for a few version that obscurs the distinction, but
it will still show in the output of
\displayLilyMusic c'\nextPad
and similar constructs).
--
David Kastrup
t an error but the standard print-form of the resulting Music
expression. You might want to call displayMusic on it for a better
looking result.
--
David Kastrup
e
is not continued with unbreakable space characters into further code
which turns it into a no-show for Guile.
Once you fix your unbreakable space as well as missing linebreak after
comment problems, things will likely look more normal.
--
David Kastrup
ou are not posting your actual code and your actual error messages.
The above will fail because of a missing space after neomensural alone.
Please try to come up with a complete small example exhibiting your
problem.
--
David Kastrup
"Samuel Sloniker" writes:
> Hello!
>
> How can I unsubscribe from this list?
Like with most bonafide mailing lists, looking at the full headers of
any mail from the list will contain the necessary info for
unsubscribing.
--
David Kastrup
to it which tells it to use \context Voice = "" for the first
part (and no voice-specific settings which is why I have to follow up
with \voiceOne/\oneVoice) and \context Voice = "2" for the second (with
\voiceTwo specific settings).
If your top Voice is not anonymous but an actually named Voice, instead
of writing \voices "", 2 ... you'd need to write
\voices "MyVoiceName", 2 ... in order to get LilyPond to continue your
voice with the given name, in this case "MyVoiceName".
--
David Kastrup
peat volta 3 { chorus
\alternative { { verse 2 }
{ verse 3 }
{ final bar } } } }
do the trick for you?
--
David Kastrup
e?
>
> I am not yet sure if this is a bug or not.
I'd call it more of an inconsistency with regard to behavior of
something for which (ly:stencil-empty ... #X) returns #t (namely
vertical spacing). The behavior inside of markup itself is to space and
pad the adjacent vertical elements as if the vertical spacing weren't
there, then add the spacing.
--
David Kastrup
''4 fs''8 d'' g'' e'' fs'' e'' \bar "|"
>
> I end up with alternating bars which are 1/4 full and 3/4 full the whole
> way through the piece.
>
> Probably missed the section of the manual which I need for this. Any
> direction would be gratefully received.
<https://lilypond.org/doc/v2.24/Documentation/notation/displaying-rhythms#upbeats>
--
David Kastrup
ome 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).
\vspace/\hspace can go backwards.
--
David Kastrup
uld consider me to blame, and also there would be the question of
just how to position a watermark when the spacing specific to its own
kind of vertical element is not being applied. Probably just next to
the preceding element.
--
David Kastrup
and system is always inserted, and I wasn't able to find a
> solution to give the markup a 'negative height'.
If you don't want vertical padding, your horizontal dimensions must be
an empty interval, not a point interval.
--
David Kastrup
ning conversion. So it may make sense to look for
those patterns only in expressions that also talk about
articulation-type or its associated data structures.
--
David Kastrup
ple dal segnos I remember. It would be
interesting to see how much we are still lacking to represent that
particular monstrosity (I don't think I have figured out with confidence
how to actually play it as a human, either) to LilyPond.
--
David Kastrup
Valentin Petzel writes:
> Am Sonntag, 19. März 2023, 11:40:49 CET schrieb David Kastrup:
>> The political system in the U.S. considers bribes by lobbyists a First
>> Amendment protected variant of free speech.
>
> This deserves to be printed on calendars, t-shirts and mu
a year headless, with lobbyists sabotaging an
appointment for the leadership position after the last one had left.
Sometimes it is not sufficient to be good at developing technology...
--
David Kastrup
> My concern is more wondering that if the ordinary PDF is of the
> required quality (defined how?), what is being changed to increase its
> size so much?
Different mostly redundant font subsets for thousands of images add up.
--
David Kastrup
uantisation.
>>>
>>> Of course, Frescobaldi does not use timing at all yet, so that is a moot
>>> point for now.
>
>
> Yes, but an external program could do that too, without being tied to a
> single
> specific editor.
How do you propose an external program to incorporate edits without
being an editor?
--
David Kastrup
ight significantly speed up the process of getting a good quantisation.
Of course, Frescobaldi does not use timing at all yet, so that is a moot
point for now.
--
David Kastrup
unctionality.
The native MIDI support would require recording of timing information to
facilitate better chord/note distinction and quantisation support.
--
David Kastrup
Aaron Hill writes:
> On 2023-03-11 3:55 am, David Kastrup wrote:
>> Hi,
>> just a heads-up for a talk about LilyPond happening at 5pm MET
>> (UTC+1).
>> It's being streamed (and there will be a recording available a few
>> weeks
>> later).
>> Esse
Jean Abou Samra writes:
> Le samedi 11 mars 2023 à 12:55 +0100, David Kastrup a écrit :
>
>
>> Hi,
>>
>> just a heads-up for a talk about LilyPond happening at 5pm MET (UTC+1).
>>
>> It's being streamed (and there will be a recording available a few w
see you later!
--
David Kastrup
pending on how non-local the
memory accesses occur.
--
David Kastrup
quot; inside of a message gets one ">" prepended when put
into an mbox file, and one taken out again when displayed/processed.
--
David Kastrup
ng to
run the server?
--
David Kastrup
Do you really think that the number of mailing lists supported by the
GNU mailing list server could be supported on the same hardware by the
same number of Discourse forums?
I don't really see how "schadenfreude" scales to the problem space.
--
David Kastrup
ibility sets in, drawing \alternative to the
inner \repeat volta. You could put { } before \alternative to block
that.
--
David Kastrup
Nevertheless, I am
occasionally surprised by people being able to find past utterings of
mine to rub my nose in.
--
David Kastrup
well ;-)
>From a practical workflow perspective, I would much rather do all of my
reading using a single keyboard driven interface and application than
have to keep hopping through all-different web interfaces for everything
I am interested in.
--
David Kastrup
on't think that the LilyPond user base is of a size where elitist
thinking is providing a good basis for keeping the
user-poweruser-developer-magician pyramid stable.
--
David Kastrup
y to use one medium instead of a flurry of
different websites with different interfaces.
--
David Kastrup
aybe it's possible to prepare a stock message that you just need to
checkmark? That would go a long way towards being less weary. A
different tradeoff.
--
David Kastrup
d to
> handle this score. It proceeds, but it returns an non-zero error
> code as a sign of protest :-)
No, it doesn't. The warning and error is reserved for the case where
the file requests a newer version than LilyPond provides, not the other
way round.
--
David Kastrup
ave written your override, it removes all of
space-alist and only leaves the entries you state explicitly.
Instead, try overriding just the entry
BreathingSign.space-alist.next-note (and I prefer using a \tweak here)
such as
\relative c'' {
c c \breathe c c \break
c c
\tweak space-alist.next-note #'(fixed-space . -3) \breathe c c
}
--
David Kastrup
Jean Abou Samra writes:
> Le lundi 13 février 2023 à 18:08 +0100, David Kastrup a écrit :
>> That begs the question whether it would make sense to restrict
>> afterGrace scales to values below 1. But I think that making syntactic
>> decisions based on values rather than
values below 1. But I think that making syntactic
decisions based on values rather than types is really icky. It is
probably a bad idea to make syntactic decisions that one would not
expect a syntax highlighter to be able to figure out.
--
David Kastrup
ty?
\new Staff \with
{ \override TupletBracket.outside-staff-priority = 100 }
\fixed c' { \tuplet 3/2 { b4(f) g } }
Don't ask me what's up with the vertical spacing.
--
David Kastrup
ef bass
> \key g \major
> \time 4/4
> fis8
> }
>
> but the lower staff starts with a treble clef followed by the bass clef
> with the key signature.
> This is quite weird
>
> What am I doing wrong?
> Thanks
<https://lilypond.org/doc/v2.24/Documentation/
t; barline in a choirstaff?
>>
>> I tried \once \override Staff.BarLine.transparent = ##f \bar "|"
>>
>> but o course it doesn't work, for its just in a staff...
>>
>> Best regards
>> Johannes
>>
>>
>
>
>
--
David Kastrup
age
example is less than clear since it works with \keepWithTag for
differentiating between layout and midi use.
--
David Kastrup
uning since incrementally tweaking decimal notation tends to be
more hands-on than tweaking fraction notation.
--
David Kastrup
\left
>>>
> }
>
> It gives me a few instances of double sharps as well as some e
> sharps. How can I do that?
You mean, how can you avoid that? Don't transpose to gs instead of af.
> Also, the programmer in me squeals upon seeing all these duplications,
> so I was curious how to reduce this to something a bit more sensible?
Try using
{
#@(map (lambda (p) #{ \transpose c #p \patleft #})
(event-chord-pitches #{ #}))
}
--
David Kastrup
after (i.e. above) stems. Any ideas?
Try
\override NoteHead.layer = 2
--
David Kastrup
orked before that commit.
It seems like a bit of a stretch to still call it a "regression" after
19 years of its existence.
--
David Kastrup
vior
>>>
>>> More like an unintended side effect of implementing obviously intended
>>> behavior.
>
>
> I’d say this is pretty much what we call a regression ...
To be a regression, it has to have worked at some point of time.
Did it?
--
David Kastrup
Ahanu Banerjee writes:
> I suppose there are different definitions for what a "bug" is. I said
> it was not one because it is obviously intended behavior
More like an unintended side effect of implementing obviously intended
behavior.
--
David Kastrup
Ahanu Banerjee writes:
> Never mind, it appears that adding "\etc" does what I am trying to do:
>
> makeRed = -\tweak color "red" \etc
Pretty much the primordial use case for \etc .
--
David Kastrup
>
> Why would this be so? Lilypond does not have issues autobeaming
> { s16 16 16 16}
> for example.
Cannot reproduce what I had been thinking of. Possibly addressed by
some previous autobeaming change.
--
David Kastrup
Lukas-Fabian Moser writes:
> Am 29.01.23 um 17:54 schrieb David Kastrup:
>> Valentin Petzel writes:
>>
>>> Hello David,
>>>
>>> in most cases definitely, but I suppose there might be some cases in
>>> say piano music where something like this
Lukas-Fabian Moser writes:
> Am 29.01.23 um 17:54 schrieb David Kastrup:
>> Valentin Petzel writes:
>>
>>> Hello David,
>>>
>>> in most cases definitely, but I suppose there might be some cases in
>>> say piano music where something like this
on than help.
--
David Kastrup
Valentin Petzel writes:
> Hello Werner,
>
> I felt it a bit inconsistent to make rests optionally auto beamable
> and to leave skips untouched ...
Beaming over skips seems like it would produce incomprehensible results.
--
David Kastrup
101 - 200 of 7439 matches
Mail list logo
