Hello,
I’ve done a draft of changes for allowing a clef change at the beginning.
Leaving it here for discussion:
https://gitlab.com/lilypond/lilypond/-/merge_requests/2362
Cheers,
Valentin
signature.asc
Description: This is a digitally signed message part.
Hello,
I’ve been wondering just now: Wouldn’t it be possible to use the break-align-
symbol mechanism to allow for dynamic indents? Take this as example:
<<
\new Staff \with { instrumentName = "ins" } {
\override Score.BreakAlignment.break-align-orders =
#(make-vector 3 '(cue-end-clef
But I feel that this is a bigger issue. Generally the issue here is that
systems-per-page only cares about systems of music and not about anything else
that may be placed on the page, as one can see here:
\paper {
systems-per-page = #16
}
\markup\column { a a a a a a a a a a a a a a a a a a
Hello Pondmates,
I’ve just stumbled upon a music SE question regarding the formatting of page
numbers. Currectly we do not have any hooks to change formatting of such
things, rather the general approach to this is "you need to change the whole
titling procedure, here is the default value".
Hello Paul,
while I’m not entirely sure what is going on there it seems like the iterator
for quoted music is messing with the logic of the iterator for percent
repeated music. This is done not by the engraver, but by the iterator.
Basically the iterator decides on whether to create
Hello you all,
on SE I’ve encountered a weird issue: BarLine stencils in Lilypond do not have
rounded corners, but they are shortened by half a staff line, so the rounded
ends of the staff lines lead to some rounded effect for the last bar line. But
when changing the color of the BarLine it
24, 2022 at 6:46 PM Valentin Petzel wrote:
> > Hello,
> >
> > Lilypond handles slanted Beams in a geometrically weird way, that is, the
> > thickness is not measured as the shortest distance between the opposing
> > sides
> > of the boundary, but as vertical
Hi Simon,
none of these slopes are extreme enough to really make a difference.
Am Freitag, 25. März 2022, 14:21:12 CET schrieb Simon Albrecht:
> Hi everyone,
>
> On 25/03/2022 01:44, Valentin Petzel wrote:
> > Hello,
> >
> > Lilypond handles slanted Beams i
Hello all,
@Abraham: In fact this is not done at scheme level here, but at C++ level.
There reason is that we do not want to change the value of the thickness, but
for Lilypond to think about this thickness in a more natural way. Also this
example already handles the beam distance. For some
Hello,
Lilypond handles slanted Beams in a geometrically weird way, that is, the
thickness is not measured as the shortest distance between the opposing sides
of the boundary, but as vertical distance. This results in Beams getting
optically thinner and closer the higher the slope is. But we
I do not really like the idea that much to be honest. Of course it would be
cool if we just have to specify the music and no duration, but in the end
\partial is not really a command about the music, but about the measure
structure. Binding it to some music would be a bit like having \time take
Am Sonntag, 6. März 2022, 20:02:21 CET schrieb Luca Fascione:
> - Your code "just prepends" a new cell with a key we're interested in
> right in front of the old content (with which shares structure)
> - It relies on lists being ordered, and all access to alists being a
> straight linear scan
wrote:
> > Thanks Valentin, this is useful.
> >
> > Sounds like I'll be back with questions :-)
> >
> > L
> >
> > On Sat, Mar 5, 2022 at 5:46 PM Valentin Petzel wrote:
> >> Hello Luca,
> >>
> >> the design of Lilypond inheren
source", it's all in "scm/ filenames>". Vague pointers like that are hopefully all I'll need.
>
> Many thanks,
> Luca
>
> On Mon, Feb 21, 2022 at 6:49 PM Luca Fascione wrote:
> > Yes exactly, because of how our finger to note relation works, the
> > enhan
Hello Johannes,
using page-turn-breaking only acts like this if ragged-bottom is set to #t
(which should be considered as weird behaviour). I suppose what’s happening
there is that with ragged-bottom set to #t there is no demerit for short
pages, as the pages are not stretched out (which is
ight in your head what fingers you use
> on what note that way
>
> L
>
> On Mon, Feb 21, 2022 at 5:42 PM Valentin Petzel wrote:
> > No, not nescessarily. If we want all Fingerings on top or below there is
> > no real benefit of doing the chord thing. In fact doing that
t; L
>
> On Mon, 21 Feb 2022, 12:32 Valentin Petzel, wrote:
>> Hello Luca,
>>
>> changing the X-parent to the NoteHead would mean that we are aligning the
>> Fingering horizontally wrt. the NoteHead instead of the whole NoteColumn.
>> This
>> wou
Hello Luca,
changing the X-parent to the NoteHead would mean that we are aligning the
Fingering horizontally wrt. the NoteHead instead of the whole NoteColumn. This
would then mean that if for example due to some chord some note heads are on
the other side of the Stem the alignment of
:
> where does that come from? (I suspect it's some kind of name available
> where the engraver is invoked, but again: how would I go at discovering
> this?)
>
> Many thanks, this is very helpful
> Luca
>
> On Sun, Feb 20, 2022 at 11:07 PM Valentin Petzel wrote:
> >
Hello Harm,
That is not exactly true. As I have done in my previous reply we can create an
engraver that acknowledges Fingerings and NoteHeads and store a reference to
the NoteHead grob in the Fingerings details property.
Cheers,
Valentin
Am Montag, 21. Februar 2022, 01:22:18 CET schrieb
Hello,
our problem here is that such things like the positioning of beams are not
known for quite some time. But we could use something like after-line-breaking
to adjust the results. Somewhat like here.
Valentin
Am Sonntag, 20. Februar 2022, 21:17:31 CET schrieb Luca Fascione:
> So... would
Hello Jean,
That sounds interesting. Maybe one way to do this would be allowing nested
\contexts? For example
\layout {
\context {
\StaffGroup
\context {
\Staff
something
}}}
to specifically target contexts that are children of other context. This way it
would be possible to have
\new
Hello Jean, hello everyone,
this does sound like a good idea. But what I've been thinking about for a while
is: For many incompabilities Lilypond could very well know how to handle
things. With things like music functions or grobs changing names we could
simply have a set of includes to make
.
This would make clear that Lilypond does in fact not offer any support for
files written in previous versions.
Valentin
09.02.2022 15:46:36 Jean Abou Samra :
>> Le 09/02/2022 15:15, Valentin Petzel a écrit :
>>
>>
>> Hello Jean, hello everyone,
>>
>> this d
Hello,
while paper blocks can be specified in books and bookparts, layout blocks
cannot. This makes having different default layouts for multiple books or
bookparts quite a hassle, as it requires specifying it for each score. Also
this makes having different stylesheets for different bookparts
Hello,
https://gitlab.com/lilypond/lilypond/-/merge_requests/1126
I’ve proposed some changes to ly:context-find to allow better music
function support for talking to other contexts.
Feel free to throw in your opinion about the matter and the interface.
Cheers,
Valentin
signature.asc
by context name (and not id)? If not I’d revise this, as
the context id based approach would require such functionality.
Cheers,
Valentin
Am Sonntag, 2. Jänner 2022, 17:00:20 CET schrieb Jean Abou Samra:
> Le 02/01/2022 à 09:20, Valentin Petzel a écrit :
> > Sorry, that was not meant
Sorry, that was not meant that way. This was intended to demonstrate the
usefulness of having such an id for the line, no matter if it is a separate
property or a value of details.
(Having one id property for all grobs does seem reasonable.)
About the other thing: It gets more complicated for
Abou Samra:
> Le 01/01/2022 à 21:14, Valentin Petzel a écrit :
> > Hello,
> >
> > I’ve started an attempt for allow multiple different Grids by giving ids.
> > See the MR: https://gitlab.com/lilypond/lilypond/-/merge_requests/1099
> >
> > I’d love to hear you
Hello,
I’ve started an attempt for allow multiple different Grids by giving ids. See
the MR: https://gitlab.com/lilypond/lilypond/-/merge_requests/1099
I’d love to hear your thoughts and critique on that. Also I suppose it would
be reasonable to add more controllable way of doing GridPoints
Thank you so much!
That does the trick!
Am Montag, 6. September 2021, 09:58:15 CEST schrieb Han-Wen Nienhuys:
> On Mon, Sep 6, 2021 at 12:41 AM Lukas-Fabian Moser wrote:
> > >>> Would it be considered okay if we included a scheme function to read a
> > >>> binary file to a byte array?
> > >>
>
Hello Jonas. Ly:gulp-file handles Unicode, so probably no. But even though it
would be possible to work around this (for example by parsing each char and
counting the bits) this does seem like a very messy solution for me, as it
goes bit stream (file) → string → bit stream, with a completely
, 19:45:31 CEST schrieb Han-Wen Nienhuys:
> On Sun, Sep 5, 2021 at 3:10 PM Valentin Petzel wrote:
> > Would it be considered okay if we included a scheme function to read a
> > binary file to a byte array?
>
> GUILE already supports this out of the box. Have you seen
>
Hello,
Would it be considered okay if we included a scheme function to read a binary
file to a byte array?
This would be useful for correct handling of eps-files (which currently does
not support the actual eps specification).
Basically an eps-file appears to be mixed content, with some
Hello Al,
The problem is that guile-1.8 is not supported by modern distros anymore.
I’m not sure if Ubuntu handles this well, but under Debian you can fetch the
source code with apt-get source lilypond. (Ubuntu just uses the version
maintained by Debian, so I think this should work out.)
This
No, I was talking about the thing with the parentheses I sent you before.
Valentin
signature.asc
Description: This is a digitally signed message part.
As said before, I’ve done a small testing implementation. It is not perfect,
but a start. Would love any aesthetic opinion you might have on this.
I’ll fork the changes into a new branch tomorrow, so you all can try them out,
but I have to go to bed now, it’s far to late ...
Valentin
Ohne
This is a quick mockup that still needs lots of tweaking and testing. For
example currently the width of the Parenthesis is in an order of the square
root of the height of the actual markup. This should be not too bad, as we’d
expect a good bracket to grow faster horizontally than vertically.
We can probably move a lot of stuff to \parenthesize,the question is if that
is wanted, as it will be a change of the default behaviour.
Basically one needs to do to things:
→ figure out the font-size and set thickness appropriately. In case the text
is bold the parentheses should probably be
Actually, as long as a stack of two is always larger than the Chord Symbol, we
can easily do this, see example!
Ohne Titel2.pdf
Description: Adobe PDF document
signature.asc
Description: This is a digitally signed message part.
Yes, I was thinking of that too, but I left it for now. That being said, I
think I can quite easily come up with something. The important thing would be:
I’d have to check the height of this markup (which either needs a good
approximation or simply an on-the-fly call), from there I can work out
Yes. That was a deliberate decision, because I thought maybe it’s better that
way. We simply need to change change #:general-align Y 0 to #:general-align Y
-1 in line 462 for the behaviour shown in the example.
Control over the parathesis style should be no problem, we can for example
have a
Hi everyone,
I’m looking into doing large time sigs found in modern conducting scores in
lilypond. For that reason I need to place TimeSignatures that are not in a
Vertical axis group on the score. Is there any way to vertically align such
objects relative to the bottom of the system instead
Hello,
As it is I think one of the important features missing in Lilypond is the
ability to split one staff into multiple staves, which is a feature quite
nescessary for orchestral and choral settings. There is an ”official“ hack to
do
it by using different staves and switching context, but
-spacing #'basic-distance = #5
}
\header {
title = "Shaping slurs: The penalty approach"
author = "Valentin Petzel"
}
\markup \vspace #1
\markup {\italic "All examples and snippets are taken from this post:"}
\markup { \typewriter "https://lists.gnu.org/archive
Hello.
I’ve been thinking about how to get these S-shaped slurs you tend to find in
piano music (e.g. in Staff changes) done properly in Lilypond. Usually this is
done by manually overriding the Coefficients to the Bernsteinpolynomials, which
I think should be avoided if possible.
I guess
46 matches
Mail list logo
