I could reproduce it with the 2.25.14 Windows
build using scheme-sandbox.ly as well as using the -e command-line
option:
lilypond -e "(let* ((a 1) (b -3) (c (+ b 0.3))) (> (- b (/ a 2)) c))"
-- Aaron Hill
staff highlights [1].
[1]:
https://lilypond.org/doc/v2.25/Documentation/notation/staff-highlights
The source of the error is how colors need to be handled. Add an
explicit call to normalize-color:
(ly:make-stencil (list 'color (normalize-color color)
-- Aaron Hill
created to demonstrate the technique, but would we want it in the docs?
-- Aaron Hill
o they do not visually interfere with the SpanBar, but
they still take up space.
-- Aaron Hill
ersion into threads.
-- Aaron Hill
as all grobs support the
properties show-horizontal-skylines and show-vertical-skylines.
So, swap out that \override with:
\override NonMusicalPaperColumn.show-horizontal-skylines = ##t
-- Aaron Hill
, referring to this e-mail thread.
First time creating an issue, so hopefully this is up to snuff.
Added: https://gitlab.com/lilypond/lilypond/-/issues/6703
By the by, I do not appear to have permissions for setting labels, but I
think this issue would qualify for the "Ugly" tag.
Staff { \improvisationOn b'4 4 4 8. 16~ | 4 4 4 4 }
>>
}
Still sounds like a defect of some sort, as the default behavior should
probably be handling things. But perhaps this trick above might be
useful in whatever score you are working on as a stopgap.
-- Aaron Hill
between versions, resulting in different behavior.
You might want to utilize annotate-spacing as well, as it might help
visualize where spacing occurs.
-- Aaron Hill
Sorry, I thought the bug alias was still on the CC line. Resending to
ensure broad visibility.
On 2024-02-04 4:37 am, Aaron Hill wrote:
On 2024-02-04 12:40 am, Rudi Radler wrote:
it shows german to me.
Okay, this section of the documentation is out-of-date for some
translations
no corresponding link back to the URL above.
-- Aaron Hill
in the count. This is likely
the origin of the off-by-one error.
-- Aaron Hill
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
resence of the (U+1F670) character in a comment in the \paper
block is the problem. Frescobaldi is not handling Unicode surrogate
pairs properly, so there is an off-by-one error when counting
characters.
-- Aaron Hill
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
syntactic shorthand.
-- Aaron Hill
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
-breaking #offsetter-fn $ev #})
{
2\off \< 2\f
2\tweak Y-offset #-0.5 \off \< 2\f
2\offset Y-offset #0.5 \off \< 2\f
}
-- Aaron Hill
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
xts are moving in the same
direction (relative to the note center).
Perhaps an unspecified parent-alignment-X should take self-alignment-X's
value but clamped to [LEFT, RIGHT]:
\override LyricText.parent-alignment-X =
#(lambda (grob) (max LEFT (min RIGHT (
rC 2 } }
\score { \music \layout { } }
\score { \articulate \unfoldRepeats \music \midi { } }
-- Aaron Hill
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
= #(lambda (text) #{ \markup \box #text #})
jitter = #(lambda (text) #{ \markup \rotate #(- (random 20) 10) #text
#})
\new Lyrics \lyricmode {
\transformText \boxify lorem ipsum dolor sit amet
\transformText \jitter lorem ipsum dolor sit amet
}
-- Aaron Hill
ng to all words/syllables without
needing to use \markup:
\lyricsto "melody" {
\override LyricText.font-shape = #'italic
\override LyricText.color = #red
Here are the words
}
-- Aaron Hill
___
bug-lilypond mailing list
bug-lil
."
e'4 f' g' |
}
{
d'4 c' b' |
}
{
\changeVoltaText \markup \with-color #red "4."
g'4 a' b' |
}
}
c'1
}
\score {
\test
}
-- Aaron Hill
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
|
}
\alternative {
{
\changeVoltaText "1., 3."
e'4 f' g' |
}
{
d'4 c' b' |
}
{
\changeVoltaText \markup \with-color #red "4."
g'4 a' b' |
}
}
c'1
}
\score {
\test
}
NOTE: I'm using \markup in the final alternative just to
ing-shapes
-- Aaron Hill
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
parent-alignment-X as desired:
\version "2.22.0"
{ a'1 a'1
c'' -\tweak parent-alignment-X #CENTER
^\markup \center-align \box \bold \fontsize #10
\center-column { "|" "" "bbb" "|" } }
-- Aaron Hill
_
On 2020-12-28 6:18 pm, Aaron Hill wrote:
On 2020-12-28 5:31 pm, Freeman Gilmore wrote:
LilyPond Internals Reference, 2.2.58 key_engraver
keyAlterationOrder(list)
It should read: "… *step *is a number from 0 to 6 and *alter
*from
-2 (flat) to 2 (sharp)."
(Not
lterations, use
symbols, e.g. keyAlterations = #`((6 . ,FLAT)).
-- Aaron Hill
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Wrong type argument in position 1: (1 "4.." . #f)
What am I missing here?
The syntax changed. You no longer specify the duration as a string, but
as a duration:
%%%%
\markup { \note 4.. #UP }
-- Aaron Hill
___
bug-lilypond mailing list
On 2020-10-12 5:27 pm, Matthew Fong wrote:
I was engraving a piece of chant in modern notation recently, and
discovered that none of the custodes will draw a ledger for middle C
(C4)
or A5, notes beyond the 5-line staff. These notes do occur in chant and
polyphony.
Is there a workaround for
On 2020-10-05 9:50 am, Rutger Hofman wrote:
Good evening bug list,
when a beam of notes with stem tremolo switches staff, the result is
decidedly buggy. See source and png. Adding \stemUp|Down doesn't make
things better. Without stem tremolo or without staff switch, things
are fine.
You can
/changing_staves_with_tremolo_on_single_eighth/
-- Aaron Hill
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
skip the searching, do this:
(if (and (null? quote-contents) (pair? raw-voice))
Absolutely no idea which is correct. Sorry. :/
-- Aaron Hill
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
e g'8 \set fontSize = #-3 a'16_( b' \unset fontSize bes'2*3/4) }
-- Aaron Hill
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
presume you are compiling things that worked on Ubuntu, but could you
provide a MWE for reference? It would be good to rule out problems on
the user input side before diving too deeply into anything system- or
distribution-specific.
-- Aaron Hill
re.
[1]: https://github.com/frescobaldi/frescobaldi/issues
-- Aaron Hill
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
that
logic is necessary? In any event, I omitted it from my Scheme engraver.
-- Aaron Hill\version "2.20.0"
System_start_delimiter_engraver_patched =
#(lambda (context)
(let ((nesting #f))
(define (nesting-node node-type)
(let ((node-grob #f)
(prior-
it can clean up and rebuild its
StaffSymbol collection rather than just append to the existing one.
-- Aaron Hill
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
note durations. You need to use "f2.:maj7" not
"f1:maj7".
-- Aaron Hill
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
On 2020-03-06 9:13 am, Torsten Hämmerle wrote:
Jean ABOU SAMRA wrote
You likely have a special character in the name of your file.
Windows handles this poorly and LilyPond (actually Python,
behind the scenes) can't do much for this. Try removing
special characters from the file
in 2.19.60, so lilybin
is just slightly too old.
This is why the \version statement is useful and should not be so
casually cast aside.
-- Aaron Hill
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
e presence of a score.
Could this be an issue with font caching?
-- Aaron Hill
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
On 2020-01-19 10:20 pm, Aaron Hill wrote:
The following patch seems to address the issue:
[ . . . ]
After my work on \svgPath (submitted to the main mailing list), I do not
believe the patch is correct. closepath should only be setting
current-point to start-point, while start
The logic within the \path markup command ignores the effect of
closepath when converting relative coordinates to absolute ones.
closepath moves the pen back to the starting point of the path.
Relative coordinates are based on the current pen position, not the most
recently specified point.
Forwarding for visibility...
On 2019-11-20 12:57 pm, Артем Тартаковский wrote:
There is another problem with musicxml2ly. It gives me an error:
Traceback (most recent call last):
File "musicxml2ly.py", line 3297, in ?
main()
File "musicxml2ly.py", line 3279, in main
basefilename =
, 20 нояб. 2019 г. в 20:18, Aaron Hill :
On 2019-11-20 9:40 am, m.tarensk...@zonnet.nl wrote:
> There are more python2 vs python3 issues in those scripts than just
> that one. You can try to check ( and fix) using the 2to3 script.
Fair point. I was only intending to address Артем's qu
Python2 to run the scripts.
That is probably the best advice, until such time as folks get around to
fully addressing all of the porting/compatibility issues.
-- Aaron Hill
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org
On 2019-11-20 12:00 am, Артем Тартаковский wrote:
ср, 20 нояб. 2019 г., 2:00 Aaron Hill :
It's a compatibility issue between Python 2 and 3. The backtick
operator was removed [1] in Python 3, in favor of the repr()
procedure.
[1]:
https://portingguide.readthedocs.io/en/latest/syntax.html
n/latest/syntax.html#backticks
It is my understanding the scripts shipping with LilyPond are not
expected to be interpretable by Python 3 yet.
-- Aaron Hill
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
/search/?q=%22layout-set-staff-size%22
-- Aaron Hill
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
On 2019-11-01 1:19 pm, David Kastrup wrote:
Aaron Hill writes:
That said, I feel the hard-fail approach of an assertion is too
strong, and what we need is to simply emit a warning that the function
will be returning the midpoint of the interval's bounds despite the
interval appearing
On 2019-10-30 2:24 am, Aaron Hill wrote:
On 2019-10-30 2:05 am, Rutger Hofman wrote:
Sincere request: can this assert please be removed? Its validity
appears
debatable, and it is a showstopper for me!
If we agree that an empty interval does not have a well-defined
center, then the assertion
ds despite the interval
appearing to be invalid (read: empty).
-- Aaron Hill
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
On 2019-09-01 7:50 pm, Jason Miller wrote:
On Sun, 01 Sep 2019 16:45:16 -0700, Aaron Hill
wrote:
On 2019-09-01 3:44 pm, Jason Miller wrote:
> See attached example. This was originally encountered on nixos, but I
> confirmed it also happens on Ubuntu.
Is this a valid case? Th
rror: failed files: "foo.ly"
The terminal process terminated with exit code: 1
-- Aaron Hill
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
system?
I tried this on Ubuntu 18.04 with LilyPond 2.19.83 and encountered no
errors (results attached).
-- Aaron Hill
lilypond issue.pdf
Description: Adobe PDF document
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman
that font-shape. This is not the same thing as
OpenType caps, from what I can tell.
\override #'(font-features . ("smcp")) is the (only?) way to use
OpenType features to select small caps.
-- Aaron Hill
___
bug-lilypond mailing list
bug-li
http://lilypond.org/doc/v2.19/Documentation/notation/horizontal-spacing.en.html
-- Aaron Hill
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
\override TrillPitchAccidental.before-line-breaking =
#hideUnforcedNaturals
\pitchedTrill cis2\startTrillSpan dis cis\stopTrillSpan
\pitchedTrill cis2\startTrillSpan d cis\stopTrillSpan
\pitchedTrill cis2\startTrillSpan d! cis\stopTrillSpan
}
--
ot sure how this helps with musicxml2ly though. Is it capable of
computing the length of music to be able to insert such spacer rests
automatically? Or is there some way to link two contexts together so
that they keep each other alive without needing manual interven
\score {
\new Staff \with { \omit Clef \omit TimeSignature } { s }
\layout { indent = 0 ragged-right = ##f }
}
}
-- Aaron Hill\version "2.19.82"
\paper {
scoreTitleMarkup = \markup \overlay {
\lower #1 \fontsize #2 \fill-line {
\rotate #5 \conca
.:32 g32 8..:32 a32 8..:32
}
Of course, this is not to say that Stem::calc_stem_info is definitely in
the wrong, but its output is not always what Stem_tremolo::pure_height
would seem to expect.
-- Aaron Hill
___
bug-lilypond mailing list
) 2)))
(format #t "\nwarning: Fixing invalid X-positions ~a" xpos)
(cons mid mid))
xpos)))
This variant of my prior procedure opts to use the artificial "center"
of the invalid interval as the result.
-- Aaron Hill
On 2019-03-23 3:39 pm, Thomas Morley wrote:
Am Sa., 23. März 2019 um 21:41 Uhr schrieb Aaron Hill
:
\override TupletBracket.X-positions = #(lambda (grob)
(let ((xpos (ly:tuplet-bracket::calc-x-positions grob)))
(if (> (car xpos) (cdr xpos))
(format #t "\
os) (cdr xpos)
This will emit a warning when it detects that the calculated X-positions
are inverted, but it also patches the issue by making the interval
valid.
-- Aaron Hill
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://
with 2.18.2 has problems. In
particular, there were changes made only a few years ago to improve how
LilyPad detects file encodings when opening files. Perhaps this is
related.
-- Aaron Hill
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https
On 2019-03-15 12:20 pm, Edward McGuire wrote:
On Fri, Mar 15, 2019 at 11:34 AM Aaron Hill
wrote:
I thought articulate.ly was *only* for \midi, and its modifications
are
not intended to be printed.
The full work from which the tiny example is taken generates both
printed output and MIDI
ate.ly was *only* for \midi, and its modifications are
not intended to be printed.
Or is this an issue where the modifications are inappropriate resulting
in bad MIDI output?
-- Aaron Hill
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
.10 -12.05 #
10 -12.05 #
10 -4.57775475073964 #
10 -5.45702919685039 #
You can see that the staff-padding is still 10 for all of the spanners.
But only the first two that have a valid StaffSymbol end up with the
expected Y-offset.
-- Aaron Hill
_
scores. To date, I have only needed to typeset vocal parts.
However, engraving a piano part is something that I likely will need to
do in the coming months. I would greatly appreciate any additional
reference materials.
-- Aaron Hill
___
bug
en a Staff within the \score.
-- Aaron Hill
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
lumn.line-break-system-details
#'((extra-offset . (5 . 5)))
s1*2 \break
s1*2 \break
}
\new Voice \repeat unfold 24 b'4
>>
\new Staff \repeat unfold 12 b'2
When rendered normally, the middle system is properly offset. When
using -dcrop, no off
On 2018-12-21 4:53 pm, Aaron Hill wrote:
I tried the following approach to break up the piece into three scores:
\score {
{ \time 4/4 \repeat unfold 1000 { c4 d e f } }
}
\score {
{ \set Score.currentBarNumber = #1001 \bar ""
\time 4/4 \repeat unfold 1000 { f1 } }
}
}
\score {
{ \set Score.currentBarNumber = #2001 \bar ""
\time 4/4 \repeat unfold 1000 { c4 d e f } }
\layout { indent = 0 }
}
This only took 42 seconds to complete and I believe it peaked under
2GiB.
-- Aaron Hill
___
bug-lilyp
This appears to be due to an odd interaction between one-page-breaking
and the default staff-affinity for ChordNames (which is #DOWN).
Adding this to the \score fixes it:
\layout { \context { \ChordNames
\override VerticalAxisGroup.staff-affinity = #UP } }
-- Aaron Hill
8 (lilybin.com)
Repros on 2.19.82 (local Linux 64 build)
Interestingly, PNG 200dpi cropped is 164x137069 but only 291KB. Good
compression. ;-)
-- Aaron Hill
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
h assumes that folks *want* collation. It could very well end up
an optional feature to enable/disable as desired.
P.S. My Italian is rather lacking, so I only just realized I have been
saying "primo/secondo" as opposed to "prima/seconda". Is this a case of
grammatic
arithmetic to show
up as odd-only or even-only.
** Providing things do not align by chance, adding explicit \pageBreak
commands would ensure that page turns happen at the same moment.
-- Aaron Hill
___
bug-lilypond mailing list
bug-lilypond@gnu.org
On 2018-08-10 10:29, Aaron Hill wrote:
On 2018-08-10 08:52, James Lowe wrote:
Here are some procmon csv logs
Three of them (zipped)
1. Where I ran it from a local dir - success
2. Where I ran it on a UNC share - fail
3. Where I pushd the UNC share (mounts on W:) and then run - success
Hope
letters, since that seems to work fine.
-- Aaron Hill
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
the
Windows version of LilyPond, so I cannot immediately test this on my
setup without having to set up a VM first. If it is possible to run
LilyPond in a portable mode without installation, then that would save
significant time getting a test environment.
-- Aaron Hill
On 2018-07-17 11:46, David Kastrup wrote:
Aaron Hill writes:
I tried manually duplicating the music:
\version "2.19.82"
music = { \once \offset length 5 Stem c'4 c'4 }
musicCopy = { \once \offset length 5 Stem c'4 c'4 }
\new Staff { c'4 << \music \
On 2018-07-15 20:09, Aaron Hill wrote:
Seems the custom music function is not needed to reproduce a crash.
\version "2.19.82"
music = { \once \offset length 5 Stem 4 4 }
<< \music \music >>
This also results in:
GNU LilyPond 2.19.82
Process
confused by the naked duration, I
tried this:
\version "2.19.82"
music = { \offset Stem.length 5 c'4 4 }
<< \music \music >>
It compiles, but produces two staves as output rather than combining the
notes on one staff. I am almost certainly overl
in
the functionality running twice.
I suppose that, depending on how you have your EDITOR or LYEDITOR
variables configured, you might not notice a double launch; but I was
certainly confused at first why I was getting repeated behavior.
-- Aaron Hill
t included.
-- Aaron Hill
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
With the release of 2.19.82, I pulled down the latest docs in PDF form
for reference. However, it appears nearly all of them have notation
with missing or incorrect fonts. The HTML versions seem fine and show
the notation snippets correctly.
-- Aaron Hill
repositories are sorely out
of
date with respect to lilypond:
https://www.archlinux.org/packages/community/x86_64/lilypond/
Hi Aaron,
The development version 2.19.81 does appear to be on the AUR as
lilypond-devel:
https://aur.archlinux.org/packages/lilypond-devel/
-- Aaron Hill
ord changes align with words. But that is more of a
personal preference.
P.S. As advised earlier, we should really move any more non-bug
discussion to lilypond-user.
-- Aaron Hill
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
elp reduce the need to switch to Scheme for this type of thing.
Will this convenient syntax support more than one argument, or is that
beyond the scope of the feature?
-- Aaron Hill
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lis
On 2018-06-07 07:58, David Kastrup wrote:
Aaron Hill writes:
On 2018-06-07 06:34, Aaron Hill wrote:
Hi David,
Correct me if I am wrong, but the second definition is ***not***
usable as a
function. That is, it cannot accept a parameter for customizing the
markup. Unless `\etc` is something
On 2018-06-07 06:34, Aaron Hill wrote:
Hi David,
Correct me if I am wrong, but the second definition is ***not*** usable
as a
function. That is, it cannot accept a parameter for customizing the
markup. Unless `\etc` is something magical that is undocumented, the
resulting `\doubleBox` would
, the
resulting `\doubleBox` would have to be a complete idea.
It would seem Urs' version is necessary if you need to be able to
provide a parameter, which more closely matches the intention of the
original `\doubleBox` as a markup function.
-- Aaron Hill
\override Stem.direction = #UP
a'( ges'') a'( gis'') % Collision with flat only.
}
-- Aaron Hill
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
not worth spending any more
time if it cannot be reproduced reliably and on other platforms.
-- Aaron Hill
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
On 2018-05-05 17:01, Aaron Hill wrote:
How about this repro:
%%%
\version "2.19.80"
\repeat unfold 36 {
<< { e'8 f' } \\ { c'4 } >> d'4
<< { g'4. f'8 } \\ { e'16 d' e'4 d'8 } >>
}
%%%
On my machine, I cannot compile this as-is without the LilyPond
process
available
I could install WinDbg and dig in further, if it would help. However, I
would need symbols for the Windows build.
-- Aaron Hill
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
%%
The only references I could find to "mis-predicted force" are in
relation to an issue regarding grace notes and possible floating-point
arithmetic issues in the Windows/MinGW build. Presuming this is
related, here is hoping this repro can help shed some light on the
underlying issue
95 matches
Mail list logo
