at exporting MusicXML than reading it. This is true even with the
most recent versions.
Werner
`musicxml2ly`; you have to explicitly *export* to MusicXML.
Maybe you've attached the wrong file to the bug report?
Werner
Please add it to the tracker (and
thanks in advance for doing it).
Werner
ion of LilyPond instead; it
renders your example just fine (rendering with `lilypond` will show
warnings, but these warnings are LilyPond bugs and can be ignored for
your test file).
Werner
\version "2.25.20"
% automatically converted by musicxml2ly from xml-test.xml
\pointAndClick
a8 b16 cis b8. a16 } \\ { d,8 cis'16 d e16 d, e fis g4 } >> |
>}
Confirmed, please file an issue.
Werner
his by yourself, see attached example. Do you have to
one or more real-world scores where custodes are combined with ties?
Werner
\version "2.24.3"
custosDown = \override Staff.Custos.neutral-position = -100
custosUp = \override Staff.Custos.neutral-position = 100
Hello Dietmar,
> Abhängig von layout-set-staff-size gibt es Fehler in der
> Darstellung. [...]
Thanks for the report, which I've registered as
https://gitlab.com/lilypond/lilypond/-/issues/6732
Grüße aus Kufstein
Werner
//gitlab.com/lilypond/lilypond/-/merge_requests/2382
Werner
;t know what's going on, sorry. But looking at the version diffs
(2.25.0 vs. 2.14.0) the problem seems to be elsewhere with running the
test suite, so for the moment, I believe, you can ignore those MIDI
tests.
Werner
rt nested tuplets...
Can you retry XML export with a current MuseScore version?
Werner
```xml
C
4
0
...
```
The value of `` must always be a positive number; value 0 is
not allowed. This is just the first of many other notes in this XML
file that have a zero duration. In other words, this file cannot be
handled correctly. Perhaps you should try a newer MuseScore version
and check whether it produces valid XML...
Werner
Hello Thomas,
sorry for the late reply.
> "\staffHighlight" does not work properly if there is a tempo marking
> and a whole bar rest in the first bar.
This is now registered in our bug database.
https://gitlab.com/lilypond/lilypond/-/issues/6730
Werner
run `make bytecode` followed by `make test-baseline` on
'master', then applying your change, then running `make bytecode`
followed by `make check` to create `out/test-restuls/index.html`,
which you can visit in your browser and which shows you all regtest
differences.
Werner
> Hello, I have a file for which `musicxml2ly` fails, because in line 824
> variable `i2` is `None`.
Which LilyPond version? And yes, please provide the input file for
testing (you might send it privately to me if necessary).
Werner
> On my Linux machine with 2.25.16, that file nondeterministically
> compiles, segfaults, or triggers a floating point exception. No time
> to investigate more, though.
Trevor, please open an issue!
Werner
up stuff in
the NR... Anyway it is a known problem that some stuff in the LM is
missing in the NR.
> I guess this is a long-winded way of saying that I think << >>
> should be in the index.
Done.
https://gitlab.com/lilypond/lilypond/-/merge_requests/2359
Werner
that?
Right now you can only manually adjust the vertical position of the
tremolo beams.
Werner
> I am forwarding this bug report here:
>
> https://bugs.gentoo.org/913928
Thanks for the report! I've fixed the problem with the FontForge
version and with the non-portable `test` options.
https://gitlab.com/lilypond/lilypond/-/merge_requests/2301
Werner
eed for being thorough; even the
smallest breadcrumbs are potentially useful for all users.
Werner
quests,
closely following the formatting of other documentation strings. All
documentation that goes into the IR uses Texinfo syntax.
And yes, larger-scale stuff should be discussed first on
'lilypond-devel'.
Werner
is now part of a merge request, see
https://gitlab.com/lilypond/lilypond/-/merge_requests/2291
Werner
;, s)
> ```
Thanks for the report!
https://gitlab.com/lilypond/lilypond/-/merge_requests/2289
Werner
color = #red
\override Accidental.hide-tied-accidental-after-break = ##t
cis''1~( \break 1)
}
\new Staff {
R1 1
}
>>
<<
\new Staff {
\override Tie.color = #red
cis''1~( \break 1)
}
\new Staff {
R1 1
}
>>
<<
\new Staff {
\override Tie.color = #red
c''1~( \break 1)
}
\new Staff {
R1 1
}
>>
```
Werner
>> Since I don't have experience with chord names I ask users who need
>> this feature to check whether it works as expected in general.
>
> It works like a charm in my source! Thanks for researching this.
:-)
https://gitlab.com/lilypond/lilypond/-/merge_requests/2281
Werner
't have experience with chord names I ask users who need
this feature to check whether it works as expected in general.
Werner
hordNames \chordmode { c2. q8. des16:maj9 | q1 }
> \new Staff { \improvisationOn b'4 4 4 8. 16~ | 4 4 4 4 }
> >>
> }
>
>
> I remembered that you can add the Bar_engraver to ChordNames.
> Making them transparent so they do not visually interfere with the
> SpanBar, but they still take up space.
Nice! This begs the question whether we have a real bug or 'just'
insufficient documentation...
Werner
labels,
> but I think this issue would qualify for the "Ugly" tag.
I've just set appropriate tags.
Werner
to this e-mail thread.
Werner
– for good reasons, since it increases legibitily enormously.
There might be exceptional situations to reduce the space. However,
the new values are *much* better defaults IMHO.
Werner
m
binding-offset = 0\mm
}
```
It seems to me that you should adjust the `top-markup-spacing` value
in your settings.
Werner
ond/lilypond/-/merge_requests/2265
Thanks for the report!
Werner
> Snippets manual, MIDI chapter, Staff.midiInstrument list omits "guitar
> harmonics" between "distorted guitar" and "acoustic bass" (position
> 32).
Thanks for report; fixed in LSR #338, and the next import will fix it
in the LilyPond documentation.
Werner
. I can imagine that the
part-combiner becomes more sophisticated to identify such situations
emitting a work-around; however, I don't know whether this is
possible.
Please file an issue in LilyPond's bug tracker at
https://gitlab.com/lilypond/lilypond/-/issues
so that it is not forgotten.
Werner
> I personally lacked this information on the page "1.8.2 Formatting
> text – Selecting font and font size", mainly the fact that
> text-font-size is in pt (as defined in other sections).
https://gitlab.com/lilypond/lilypond/-/merge_requests/2258
Werner
her
> units)?
This is due to history. I agree that it would be better if it had a
dimension attached to it.
Werner
g about,
> because the Pango API
>
> https://docs.gtk.org/Pango/method.FontDescription.set_size.html
>
> expects an integer size scaled by PANGO_SCALE, which is 1024. That
> is, we are limited to a precision of 1/1024 points on the font size.
Shall we document this somehow?
Werner
e at the right moment. Follow-up replies, on the other hand, come
through without further moderation – at least I think this is the
case, but I'm not sure.
Werner
repeats.es.html
>> https://lilypond.org/doc/v2.25/Documentation/notation/long-repeats.it.html
>> https://lilypond.org/doc/v2.25/Documentation/notation/long-repeats.ja.html
The French translation is usually up to date.
Werner
e now
this MR.
https://gitlab.com/lilypond/lilypond/-/merge_requests/2250
Werner
; this is a known issue I missed the notice.
It's a bug, now filed as
https://gitlab.com/lilypond/lilypond/-/issues/6692
Thanks for the report.
Werner
as you turn the page you discover that holding it is
incorrect, and it's too late to re-articulate the new syllable.
My conclusion: LilyPond's documentation is correct.
Werner
>> > The hyperlinks of both the acciaccatura and the appoggiatura
>> > slurs point to ly/grace-init.ly, which is kind of logical, but
>> > also confusing from a user perspective.
>>
>> I think this a bug, so please open an issue.
>
> I apologise.
Why?
Werner
the appoggiatura slurs
> point to ly/grace-init.ly, which is kind of logical, but also
> confusing from a user perspective.
I think this a bug, so please open an issue.
Werner
an
example (with an image) that illustrates what you mean.
Werner
One other thing. I missed noticing that you sent this to the lilypond-bug
list. You'd be better off sending things like this to the lilypond-user
list instead. See https://lists.gnu.org/mailman/listinfo/lilypond-user
--
Michael
Hi Kris,
On Thu, Jan 18, 2024 at 4:53 AM Kris Van Bruwaene via bug-lilypond <
bug-lilypond@gnu.org> wrote:
> I want to put a decrescendo on the last note of a DS al Fine section, but
> it generates an error message (version 2.24.3)
> Example:% lily test \after with DSaF
> \version "2.24.3"
> musi
00910.tar.gz
together with some fonts from TeXLive
(`texgyre{cursor,heros,schola}-*.otf`) to a place where FontConfig
finds them (I guess `~/.fonts` should work).
Werner
t more similar to
LilyPond's output). Nathan, since you sit at the 'source' of the
problem, please also send a report to the FontConfig people if your
time allows it.
https://gitlab.freedesktop.org/fontconfig/fontconfig/-/issues
Werner
pond/lilypond/-/merge_requests/2231
accordingly.
Werner
y), LilyPond outputs:
> [...]
How shall we proceed?
Werner
hows this behaviour?
I suggest you contact the FontConfig people and report the issue, too;
assuming that the font is valid it should be possible to convert the
non-UTF8 data to UTF8.
Werner
t;2.24.2"
> \relative {
> \override Score.SpacingSpanner.shortest-duration-space = #3
> ~ q
> }
Looks like a variant of issue #2368
https://gitlab.com/lilypond/lilypond/-/issues/2368
Werner
> \language "deutsch"
>
> \new NoteNames { b1 }
Already reported as issue #6305, AFAICS.
https://gitlab.com/lilypond/lilypond/-/issues/6305
Werner
> here is example of this bug: [...]
>
> The problem occurs only if the \showStaffSwitch command is found.
Yes, this is a bug. Thanks for the report; filed as
https://gitlab.com/lilypond/lilypond/-/issues/6684
Werner
hange Staff = "1"
\once \stemDown
c2.
\showStaffSwitch
\unHideNotes \change Staff = "2"
c4
}
\new Voice \relative a, {
\voiceTwo a4. b8 c4 e
}
>>
>>
```
Werner
e, the note lands
> precisely on D flat.
Please show a zoomed-in image (PNG) of what you get. For me, your
attached PDF looks just fine with my PDF viewer on a GNU/Linux box.
Werner
cient `texi2html` version to a recent `texi2any`,
and this page was missed during inspection whether everything is OK.
I've opened
https://gitlab.com/lilypond/lilypond/-/issues/6682
for tracking.
Werner
> When I compile a lilypond file I get the following error: [...]
This is due to an upgrade of homebrew to ghostscript 10.02.1, which
removed a function used by LilyPond.
https://gitlab.com/lilypond/lilypond/-/issues/6675
We already have a fix, but until this is out I suggest to use the
bina
> This bug was not observed with Ghostscript 10.02.0.
Thanks, filed as
https://gitlab.com/lilypond/lilypond/-/issues/6675
Werner
> Many thanks. The patch works fine.
Thanks for testing. This is now
https://gitlab.com/lilypond/lilypond/-/merge_requests/2093
Werner
finger) there must be more possibilities. At
> least one1h should be available. But one1q and one3q with all
> combinations with T or F (similar to two (middle finger)). I did
> not see a ring at this hole ever.
Please try the patch below (or change the file manually) and report
back whet
n-working) minimal
example. None of the developers is a bassoon player AFAIK.
Werner
> And no, this is pretty far from perfect and could also benefit from
> being made clear in the NR.
What do you want to have where exactly?
Werner
> So Pango is apparently requesting a font with colored glyphs from
> Fontconfig...
A bug?
Werner
> Following your suggestion, Werner, I tried the test file with the
> cairo back end, and it worked as expected.
Great, please send me the created PDF for further analysis – just to
be sure :-)
> I then deleted the Noto Color Emoji font (synaptic also deleted
> texlive fonts extra
this should be fixed: LilyPond and
Pango no longer use glyph names but glyph indices for communication.
BTW: Have you checked whether the Cairo backend works for you?
```
lilypond -dbackend=cairo ...
```
Perhaps we should disable color fonts similarly to variation fonts, at
least for now (and later on for the PS backend only). Such a change
could be backported to the 2.24 series.
Werner
> ran make successfully, got carried away and may have shot myself in
> the foot by running sudo make install.
You should actually do
```
make bytecode
sudo make install-bytecode
```
Without installing the Guile bytecode, LilyPond is slooow.
Werner
> Thanks for reporting. Werner, can you take a look please? It appears
> that 4494a12ec8d3408981b26f4dc4040e2f985da06f breaks `convert-ly -`
> to read stdin (on Windows).
https://gitlab.com/lilypond/lilypond/-/merge_requests/1948
Werner
its your needs, can
you suggest a better wording (in the 'v2.25' documentation)?
Werner
r styles with considerable overlap of glyphs, that
> may be a more appropriate choice?
>
> Or isn't there actual glyph overlap?
For the Emmentaler fonts, there are overlaps in the used glyphs,
AFAIK. However, this might be different for other SMuFL fonts.
/lilypond/lilypond/-/merge_requests/1296
And yes, this would have been easy to fix for people with less
technical expertise.
Werner
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
>> Please enclose the first argument of `@defun` with @code{...}, like
>> this:
>>
>>@defun @code{foo-bar::@/baz} bar? bar bar
>
> Thanks for the fix proposal; whom are you talking to with "Please"?
You, of course :-)
I wil
> Looks like this comes from the use of "@/", which has been
> introduced with
>
> commit 1f3a6cdc25ab978589fb01894dce34d7d6c1e972
> Author: Werner Lemberg
> Date: Sun Aug 8 15:51:29 2021 +0200
>
> doc: Avoid overlong index entries in generated docume
table of contents, but
> the index entries only point to it in a fairly indirect way.
Will add that, too.
Werner
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Hello Tom,
> I wonder if the "system" entry in the glossary might be enhanced by
> including the lilypond-specific definition. [...]
>
> Also, there is no entry for "spanner" [...]
thanks for the report; I will take
lly it was a sharp accidental
where the two beams now form a wedge instead of being parallel. This
is at least the impression I get if I look at Vaziri's handwritten
documents.
> Nice to get this done after such a long time!
:-)
Werner
___
12½ years earlier I wrote:
>> Persian accidentals (korn, sori) don't look very nice. [...]
>
> Thanks. I've added your report to the bug database (issue #738).
Now something happened :-) Please have a look at
https://gitlab.com/lilypond/lilypond/-/merge_reque
great lilypond program.
Werner Arnhold
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
t of the work, I think we should do what he
prefers. This doesn't prevent other developers to chime in and help
with handling bug reports. And frequent *and experienced* bug
reporters should be told to directly use the bug tracker.
Werner
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
hing helpful to add?
>
> It is mentioned in the documentation around fonts:
>
> http://lilypond.org/doc/v2.23/Documentation/notation/fonts#font-families
Justin, could you suggest an index entry (or whatever) that would have
you enabled to find the necessary information?
Werner
aste works as expected (I have cairo version 1.16.0
installed on my GNU/Linux system). Looking into the uncompressed
version of PDF (created with `pdftk`) I see that it contains proper
ToUnicode cmaps for the two fonts.
Does `-dbackend=cairo` pass markup strings directly to Cairo?
Werner
_
michi-san, could
you submit an issue there so that this gets fixed eventually? I guess
this would be beneficial for other projects, too.
Werner
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
https://gitlab.com/lilypond/lilypond/-/merge_requests/853.
This is good news!
Werner
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
>> AFAICS, to make copy and paste work for CID fonts it is necessary
>> to add a ToUnicode map. We don't do that currently. [This is
>> probably worth an entry in our issues database.]
This is now issue #6162.
https://gitlab.com/lilypond/lilypond/-/i
ther advantage is that
the output file is only 0.2MByte (probably due to good subsetting
capabilities of ghostscript 9.54 on my GNU/Linux box); using the
CID-keyed font the output file is 1.1 MByte.
Werner
___
bug-lilypond mailing list
bug-
ue #3809: the volta number is given as
1.–3.
and LilyPond tries to take the `–` character from font
`c059-roman.svg`, without consulting FontConfig as a possible
replacement.
https://gitlab.com/lilypond/lilypond/-/issues/3809
Werner
___
bug-lilyp
2-11) actually
has glyph names.
> and we would need to translate those to unicode and use the ps show
> operator for a better solution in the postscript backend.
It's not clear to me what exactly the problem is. Please elaborate.
Werner
___
licit
> about the order being guaranteed.
This is the trivial case. The problematic case are constructs like
<< { ... } { ... } ... >>
and similar things.
Werner
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
>> I recently downloaded Lilypond v2.23, and with it the big
>> documentation manual, web.pdf.
>
> I think web.pdf is not really a priority with respect to formatting,
> as the name suggests you should just view the web page at
> lilypo
d-devel' mailing list!
'bug-lilypond' is probably the wrong one.
It probably also makes sense to file issues in the tracker.
Werner
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
ilypond.org'.
What exactly do you want to achieve? What kind of SVGs do you need?
In previous e-mails I mentioned two solutions how SVGs could be
improved:
* using inkscape's option `-T` to convert glyphs to outlines
* conversion from PDF to SVG with inkscape
Doesn't
to the PDFs – I think this
is good enough for having scalable images on web pages and the like.
Werner
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
ed to be above or
below, respectively.
Werner
[*] To be added with merge request #651
https://gitlab.com/lilypond/lilypond/-/merge_requests/651
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
this is as good (or as bad) as a default as 'serif'. If you
want SVG images to be similar to, say, PDF output, you have
* to exactly specify which font you want to use for text, and
* to convert glyphs to paths, for example, by postprocessing
LilyPond's output SVG file with
> I had seen the "-" operator before but could not find it in
> LilyPond's docs.
If you look into the index, you can find it in the notation reference
(NR):
http://lilypond.org/doc/v2.23/Documentation/notation/expressive-marks-attached-to-notes#inde
com/lilypond/lilypond/-/merge_requests/650
Werner
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
TE: This script works as is on Linux because the first line of the
>> script says to run python on the file. But that's for Linux.
>> Windows doesn't know about
>>
>> #!/usr/bin/python3
>
> I consider this a distribution bug that should be fixed for the
&g
se the first line of the
> script says to run python on the file. But that's for Linux.
> Windows doesn't know about
>
> #!/usr/bin/python3
I consider this a distribution bug that should be fixed for the
Windows tarball; I
[...]
>
> The above hack does nothing more than add a fake NoteHead that
> overlaps the Custos grob so that the LedgerLineSpanner does its
> magic.
Thanks for the workaround code! Anyway, I consider this a bug; it
should be added to the tracker.
Werner
___
ould happen with
>
> { \grace { \stemDown c8 } { d8 } }
>
> ?
It seems the best solution is to throw an error. It certainly makes
the least headache.
Werner
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
1 - 100 of 637 matches
Mail list logo
