At 13:09 on 16 Apr 2022, Thomas Morley wrote:
Am Mo., 11. Apr. 2022 um 11:03 Uhr schrieb Thomas Morley
:
I hesitate to post untested wip-code on the user-list, I'll send it privately.
Hi Mark,
MR is now open:
https://gitlab.com/lilypond/lilypond/-/merge_requests/1310
Apart from huge simplif
After some digging, in note-performer.cc I found
velocity += from_scm (get_property (ev, "midi-extra-velocity"), 0);
After tracking this string throughout the source code, I finally found where
the property is set: ly/script-init.ly
accent = #(make-articulation 'accent
'midi-extra-ve
Hi, it seems removing the Dynamic_performer doesn’t actually remove performance
of articulations. E.g.,
\version "2.22.2"
\include "english.ly"
hits = \relative c { c''4\mp c-^ c-> c }
\score {
\hits
\layout {}
\midi {
\context {
\Voice \remove "Dynamic_performer"
}
}
On Sat, Apr 16, 2022 at 8:04 AM Jean Abou Samra wrote:
>
>
> > Le 16/04/2022 16:55, Knute Snortum a écrit :
> >
> >
> > I have run into a LilyPond issue [1] where the accidental spacing is
> > wrong when there is a tie to the next measure. This is my tiny
> > example (and there's a good one in th
> Le 16/04/2022 16:55, Knute Snortum a écrit :
>
>
> I have run into a LilyPond issue [1] where the accidental spacing is
> wrong when there is a tie to the next measure. This is my tiny
> example (and there's a good one in the issue, too):
>
> %%%
> \version "2.22.2"
>
> \relative {
> \clef
I have run into a LilyPond issue [1] where the accidental spacing is
wrong when there is a tie to the next measure. This is my tiny
example (and there's a good one in the issue, too):
%%%
\version "2.22.2"
\relative {
\clef bass
s2. gis4~ | 2
}
%%%
My question: is there a work-around? I've
I’m trying to put some beamed notes (no staff lines, time signature, or
anything else) in a \markup block. To do this, I’m using a Staff with several
engravers \remove’d, using \stopStaff to eliminate staff lines, and then
setting Stem.details.beamed-lengths to reduce the length of stems. Howeve
Am Mo., 11. Apr. 2022 um 11:03 Uhr schrieb Thomas Morley
:
>
> I hesitate to post untested wip-code on the user-list, I'll send it privately.
>
Hi Mark,
MR is now open:
https://gitlab.com/lilypond/lilypond/-/merge_requests/1310
Apart from huge simplifictions it fixes the initial problem of this
t
