> Hi,
>
> I’m transcribing the pictured piece, and want my fermata to be a bit smaller
> with a ‘poco’ above it. When I run the attached code it says:
>
> programming error: Cannot get a text stencil from this font
>
> continuing, cross fingers
>
> … and prints a normal fermata. What am I doin
>
> There is however one residual issue. If the following MWE is compiled under
> lilypond 2.25.18, the PDF output is as expected. However if it is compiled
> under 2.25.25, an unwanted markup "[semibreve] = 50" appears at bar 2. How
> is this best avoided?
>
While it may be a quick-fix s
> I'm on 2.24.1, BTW
>
> I'm still curious what the # commands refer to in the Lilypond manual
> example.
>
> Also, does anyone know the whereabouts of an arrow symbol I could use in a
> similar markup?
>
> It doesnt happen all that often, but sometimes "note = note" will be written
> "
Hello Tamura-san,
Having run into this problem myself before and discovered that there had been a
solution previously proposed in this mailing list about ten years ago
(https://lists.gnu.org/archive/html/lilypond-user/2015-04/msg00105.html), my
solution is modeled after that:
%%% BEGIN %%%
\v
> > Am 25.04.2025 um 07:50 schrieb Henning Hraban Ramm :
> >
> > I’d guess your different installations of MIDI synths interfere
>
> I have tried every possible single and combined installations.
> Fluidsynth and Qsynth from MacPorts btw.
I have MacBook Pro, M2 Max, 14.7.4, and I have set it up
That’s enlightening; thanks Kieren!
I would add the following near beginning of the code:
\unset systemStartDelimiter
So it looks like:
\defineBarLine "|-dashedSpan" #'(#t #f "!!")
\layout {
\context {
\GrandStaff
\name GrandStaffDashed
\override SpanBar.glyph-name = #"|-dashedSpan"
> Hi,
>
> I'm trying to put dashed bar lines between PianoStaff like in this screenshot.
>
> I believe it's the same with StaffGroup.
>
> However I haven't been able to find a solution.
> Writing several with \with measureBarType or \defineBarLine was to no avail
> on me, e.g. all dashed.
> Hav
Dear Federico and the entire Frescobaldi development team,
I would like to thank you all so much for all your work. I downloaded 4.0.1 on
my MacOS, and I am so happy to see that the “crash upon exit” error is gone. I
feel that compared to 3.3.0, the version is quicker to run, thanks to the
abil
Dear Werner,
Here are the Japanese translations of the lines you requested (I copied it from
the linked GitLab code page, lines 227 and 228:
'Other Regression tests for ': ‘その他の回帰テスト バージョン ',
'PDF of other regtests for ': ‘その他の回帰テスト (PDF 版) バージョン ‘,
Also, just to get things started with French
> Hello. I'm writing a book and after my ToC I need a blank page ("this page is
> left blank purposefully") only if this blank page would have an odd page
> number. If it falls under an even page number it must not be printed. I've
> looked in the manual and didn't find an answer... any help wou
> Thought this audience might be interested in this New York Times
> article entitled, "Inside the Detail-Obsessed, Essential World of Music
> Editing." There's some quotes from Elaine Gould, and a link to "Behind
> Bars." No mention of Lilypond, but does mention Sibelius.
>
I came across this ar
... I tried to use \shape #'(alist) Tie option when I was crafting my
solution, but I suppose I wasn't patient enough here. Good to know that
\shape indeed works. To be fair, mine does allow the overlapping of the
tie/slur over accidentals, but my solution isn't elegant.
On Fri, Feb 21, 2025 at 5:
> Here the ties are perfectly aligned:
>
> (See attachment s1)
> \version "2.25.23"
> \fixed c'
> {
> 2^~
>
> }
>
> But when I change the last chord from...
>
>
> to
>
>
> ... the resulting tie between g appears small and not clear (to me). (See
> attachment s2)
>
> What's the best wa
>
> On Tue 18 Feb 2025 at 17:56:02 (+), Richard Shann wrote:
> > At https://lilypond.org/doc/v2.25/Documentation/notation/glissando
> > under the section
> > Contemporary glissando
> > is this example (without the whole bar rest at the end).
> > 8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><
> Hi all,
>
> I'm trying to place a footnote mark, but I can't manage to get it exactly
> where I want it to be.
>
> \version "2.24.2"
>
> \score {
> <<
> \new Staff { \override Footnote.annotation-line = ##f %%this doesn't seem to
> affect the issue but reduces visual clutter so makes it clea
Stu McKenzie via LilyPond User List
> wrote:
>
>
> On 2025-01-28 19:40, Yoshiaki Onishi wrote:
>>> I sometimes add sticking to drum scores to assist readers by showing the
>>> preferred hand for each stroke.
>>>
>>> I'm aware of the a
> I sometimes add sticking to drum scores to assist readers by showing the
> preferred hand for each stroke.
>
> I'm aware of the ability to change the horizontal position of lyrics using
> '\override LyricText.self-alignment-X'.
>
> When I use '= #LEFT', the lyric is under the notehead, rather
Dear Simon,
> The \use-color function you refer to has to be a custom command of yours, no?
Gah! I’ve meant \with-color. So replacing \whiteout with:
\whiteout \with-color #black
… is what I meant. Apologies for the blunder!
Yoshi
> “Final” version of the file as submitted to LSR.
What a wonderful implementation! I am trying it on my current project, and it
works like a charm. It is so friendly to my eyes, too. Thank you so much for
all your work, everyone!
One thing I noticed that might be helpful to know to anyone usin
gt;
> %%
> \set Staff.middleCPosition = -11
> \once \override Staff.Clef.stencil = ##f
> \startStaff
> <<
>{
> \clef bass % inserted bass clef for left hand/bass comping.
> {\repeat unfold 4 {c1 d e f} }
> }
>\new Staff \with {
>%%
>
>
P.S. After hitting “send,” it occurred to me that the code I sent would not
account music after a new system starts. The clef would appear incorrectly
placed. I amended the code as below, and in this version, I tweaked the Scheme
code setting so that the two clefs would not collide in the new sy
> Is there any possibility of doing something like this picture below? On top
> is lilypond's default output and on the bottom is what I seek to write.
>
Dear Lucas,
Referring to the following pages on LilyPond Documentation:
https://lilypond.org/doc/v2.23/Documentation/notation/modifying-sing
> I'd like to specify which note heads should be printed left or right of
> the stem. Here is my minimal example:
>
> \version "2.24.1"
> \relative c'' {
> 8
> }
>
> I'd like the e to always be left of the stem for continuity, is it
> possibly to specify that?
>
> Best Regards,
> Alexander
D
> I have a Chopin piece where the notes form a broken beam across a key change
> and break (see first attachment broken-beam-over-key-change.) LilyPond has
> drawn the stem and beam long in the upper right-hand corner to avoid the key
> change. I'm not sure I like that and I'm trying to chang
P.S. In case the attached .ly file did not open properly, here is its content:
\version "2.24.4"
squiggly =
\once \override Voice.NoteHead.stencil =
#(grob-transformer
'stencil
(lambda (grob original )
(let* ((added-markup
#{
\markup
{
> Engraving a musical theater score and I've got a handful of spots that have
> some ad lib./"wild" harp glisses (as seen in the example images below.) Does
> anyone have a good reliable/reusable way to engrave these without needing to
> manually adjust the positions of the glissando spans for e
On Tue, Dec 17, 2024 at 12:36 AM Werner LEMBERG wrote:
>
> >> The best place to contribute to would be the LilyPond Notation
> >> Reference manual, whose Contemporary music section has been a stub
> >> for years:
> >>
> https://lilypond.org/doc/v2.25/Documentation/notation/contemporary-music
> >
On Sun, Dec 15, 2024 at 11:20 AM Knute Snortum wrote:
>
> You seem to have the TeX / LilyPond interface worked out but I was
> wondering if you knew about lilypond-book (
> https://lilypond.org/doc/v2.24/Documentation/usage/lilypond_002dbook)?
> It's designed for exactly your situation: where you
Dear LilyPonders,
Ever since I started learning LilyPond a little over three months ago, I
started to write codes for handling contemporary notations, and I started
to make a document cataloging them. I just wanted to share the link to the
GitHub repository here, in the event it could be useful fo
> > On Dec 7, 2024, at 11:58 AM, Tim McNamara via LilyPond user discussion <
> lilypond-user@gnu.org> wrote:
> >
> > I use Lilypond with Frescobaldi, updated to 3.3.0, which has a
> work-around-able oddity: if launching the app from the Dock or by double
> clicking it, it is unresponsive and the m
Dear Michael,
I have v. 2.24.4 so I had to replace \musicLength 16 to #(ly:make-moment 1/16).
But it appears that the proportionalNotationDuration computes as expected if a
measure is complete. Combining concatenated scores in complete measure(s)
against those in incomplete measures will cause
Dear LilyPonders,
I am grateful for all your input. Synthesizing all the points raised in
this thread,
I realized the solution was to make the .ly file in which I made the
function in
the absolute pitch mode. Then the original function worked as expected.
Thank you once again—
Yoshi
On Fri, S
c' and cause the apostrophe to be parsed twice. I'm away from my
> computer right now so can't actually test the example.
>
> Saul
>
> On Fri, Sep 13, 2024, 10:58 AM Yoshiaki Onishi
> wrote:
>
>> Dear LilyPond Community,
>>
>> In the inter
Dear LilyPond Community,
In the interest of learning more about Scheme as used in LilyPond (and
learning LilyPond in general!), I am currently in the process of making a
shortcut function that handles the artificial harmonic notation of string
instruments instead of typing ""However, something
mus
34 matches
Mail list logo
