On Fri, Mar 5, 2021 at 5:29 AM bb wrote:
>
> \version "2.20.0"
> \relative c'' {\repeat volta 2 { f1 ( | }
>\alternative { {f2) r2}
> { f1) } } }
>
> No slur with the second alternative, warning that slur cannot be ended
>
> Warnung: slur kann nicht beendet werden
>
On Tue, Nov 12, 2019 at 10:07 AM Malte Meyn wrote:
>
> Hi list,
>
> slurring a grace note to a specific note in a chord gives ugly results.
> The output of the following code is different in 2.19.82 and
> 2.19.83/2.21.0 (see attachments) but there are collisions in both cases.
>
Thanks for the em
On Sun, Nov 10, 2019 at 5:40 AM Pierre Perol-Schneider
wrote:
> Hi Bug-squad,
>
> See the Y-offset tuplet number difference here:
>
> \version "2.19.83" % and "2.21"
>
> \markup\italic "Output:"
> \relative c''' {
> \tuplet 3/2 4 { b8 c d e f g }
> }
>
> \markup\italic "Attended output:"
> \rela
On Tue, Aug 13, 2019 at 5:38 PM Urs Liska wrote:
>
> 13. August 2019 22:44, "Malte Meyn" schrieb:
>
> > Am 13.08.19 um 21:45 schrieb Ruth Mersmann:
> >
> >> \version "2.18.2"
> >>
> >> \relative c'' {
> >> \time 9/8
> >>
> >> d8\(( e-4 d) e-0( f e) g( a g)\)
> >>
> >> }
> >
> > Seems like Fingeri
On Mon, Jul 22, 2019 at 3:12 PM Jörn Eichler wrote:
>
> Hi to everybody,
>
> this is my first post to this list. I experienced a problem in v2.19.83
> when I tried to produce orchestral parts from a score. Since I couldn't
> find it on the issue tracker, I hope it's OK to post here:
>
> \score {
>
On Mon, Jul 15, 2019 at 12:55 PM Mark Knoop wrote:
>
> There seems to be a problem with the \bendAfter command which is affected
> when used with chords, even in another voice. Not sure what's going on here.
>
Thanks, Mark Knoop. This has been submitted as Issue #5538 bendAfter
broken by chords
On Sat, Feb 16, 2019 at 4:30 PM Trevor Bača wrote:
>
> Hi,
>
> LilyPond incorrectly compresses consecutive, proportionally spaced measures
> when the following conditions hold:
>
> 1. first measure in the sequence sets \proportionalNotationDuration; and
> 2. last measure in sequence is followed by
On Tue, Feb 12, 2019 at 5:19 PM Trevor Bača wrote:
> This very specific combination of circumstances causes Lily to core dump:
Thanks, Trevor. This has been entered as issue #5479.
All the best,
Ralph
___
bug-lilypond mailing list
bug-lilypond@gnu.org
Hi, Harm - Thanks. This has been entered as issue #5476.
All the best,
Ralph
On Mon, Jan 21, 2019 at 4:03 PM Thomas Morley wrote:
>
> Hi,
>
> the following code is problematic
>
> {
> \set fingeringOrientations = #'(left)
> \override Fingering #'stencil = ##f
> %% chord needs two elements
On Mon, Jan 14, 2019 at 11:48 AM Federico Bruni wrote:
>
> Hi
>
> In the Notation Reference, chapter 4.2.2, there's this warning:
>
> layout-set-staff-size does not change the distance between the staff
> lines.
>
> What does it mean with "distance between the staff lines"?
> Isn't it the staff he
On Mon, Nov 5, 2018 at 4:35 PM Thomas Morley wrote:
>
> Hi,
>
> with Metronome_mark_engraver in Staff and a changed TimeSignature a
> broken Tie is collopsed and misplaced.
>
Greetings, Thomas Morley - This has been entered as Issue #5436
Collapsed and misplaced Tie under certain conditions
Than
Hi, Urs -
This has been entered as Issue #5403 Trailing slash required on -I
option on Windows
Thanks,
Ralph
On Tue, Aug 14, 2018 at 9:30 AM Urs Liska wrote:
. . . if LilyPond on Windows requires
> a trailing slash for the -I option we should mention it in the manual.
Hi, Malte -
This has been created as issue #5379 Collision: Slur/Script/TupletBracket
Thanks,
Ralph
On Tue, Jul 10, 2018 at 1:18 PM Malte Meyn wrote:
>
> Hi list,
>
> the slur seems to cause a collision of fermata and tuplet bracket
> although it’s not above the staff.
>
__
Hi, Urs -
I've entered this as Issue #5378 Temporary staff not ending.
I labelled it as Documentation, because that can happen right away. If
you (or anyone else on the Bug List) thinks it should be a defect,
please request another ticket.
Ralph
On Sat, Jul 7, 2018 at 7:21 AM Urs Liska wrote:
On Sun, Jul 1, 2018 at 8:39 AM Malte Meyn wrote:
> The function alteration->text-accidental-markup (l. 33ff. in
> scm/chord-name.scm) seems to ignore current font size while raising the
> accidental:
>
Hi, Malte -
This has been entered as Issue
#5371 ChordName accidentals don’t scale properly
On Sun, Jul 1, 2018 at 8:35 AM Malte Meyn wrote:
> is there a reason why \germanChords raises accidentals higher than in
> other cases? In the past few years I’ve read now several users
> complaining about that.
>
> Shouldn’t we remove line 92 (and a closing parenthesis) from
> scm/chord-name.scm?
On Fri, Jun 22, 2018 at 8:35 AM, David Kastrup wrote:
> Palmer Ralph writes:
>
>> Hi -
>>
>> Thanks to all of you for all your hard work.
>
> My impression is that you _have_ been missed but I cannot really speak
> for those who have been tasked with picking u
Hi -
Thanks to all of you for all your hard work.
In the rush up to leaving on a 2-month road trip that began March 29,
I neglected to let anyone on the bug list know that I would be out of
touch and unable to review the new bug requests while I was gone.
After I returned, I was busy with settlin
On Wed, Dec 13, 2017 at 6:28 AM, Robin Bannister wrote:
>
> Hallo,
>
> http://lists.gnu.org/archive/html/lilypond-user/2017-12/msg00298.html
> This user thread prompted me to look up \markuplist because
> - I didn't recognise it
> - from the example I couldn't guess what it was doing.
>
> It t
On Mon, Oct 9, 2017 at 5:44 AM, Malte Meyn wrote:
> Hi list,
>
> could the snippets http://lsr.di.unimi.it/LSR/Item?id=1008 and
> http://lsr.di.unimi.it/LSR/Item?id=574 become part of LilyPond? Maybe
> with all or some of the following additions/changes:
>
> Snippet 1008:
> • To make it backwards
On Wed, Oct 11, 2017 at 8:58 AM, Malte Meyn wrote:
>
>
> Am 11.10.2017 um 14:55 schrieb Malte Meyn:
>
>>
>>
>> Am 11.10.2017 um 14:42 schrieb Jan-Peter Voigt:
>>
>>> Hi fellows,
>>>
>>> I have a footnote in a score. This footnote is separated by a centered
>>> horizontal line. Is there a possibil
On Thu, Jun 8, 2017 at 9:51 PM, Kieren MacMillan <
kieren_macmil...@sympatico.ca> wrote:
>
> I see this is still a problem, so I thought I'd post it to -bug.
>
> %%% SNIPPET BEGINS
> \version "2.19.61"
>
> musicA = {
> g'1\> R1\!
> }
> musicB = {
> b'1\> R1\!
> }
>
> \new Staff \partcombine \
On Wed, Jun 7, 2017 at 7:55 AM, Rutger Hofman wrote:
> Good afternoon Bug List,
>
> I stumble into a partcombine bug. At times, \partcombine extends hairpins
> over (possibly long) stretches to the wrong terminating dynamic. In the top
> staff of the attached MWE, the erroneous behaviour is shown
On Fri, Jan 20, 2017 at 2:32 AM, Johannes Roeßler wrote:
> Hi,
>
> on http://lilypond.org/doc/v2.19/Documentation/notation/
> typesetting-mensural-music
> the example for "Mensuraler F-Schlüssel im Petrucci-Stil" is not f-key but
> c-key...
>
> Joei
Thanks, Joei - entered as Issue #5044 -
https
On Thu, Jan 19, 2017 at 4:08 PM, Noeck . IMHO the output
>
> would look better like this:
Thanks, Noeck - This has been entered as Issue #5036 128 beaming.
Ralph
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/
On Tue, Jul 5, 2016 at 10:42 AM, Heikki Tauriainen
wrote:
> Hi,
>
> The post-2.18 changes to the default handling of articulations in MIDI
> (without using articulate.ly) are currently mentioned only near the
> bottom of the Changes document. The options available for customizing
> the behavior d
On Thu, Jun 23, 2016 at 7:36 AM, Federico Bruni wrote:
> Should we say explicitly in the doc that -I or --include option requires
> absolute path(s)?
> Paragraph to be modified is in Usage 1.2:
>
> -I, --include=directory
>
>Add directory to the search path for input files.
>
Hi, Federico -
Greetings, and apologies!
I'm going to be pretty much out of touch again until June 1st. I'll try to
check on Fridays, but I can't make any promises.
Ralph
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lil
On Wed, Mar 9, 2016 at 8:04 PM, Mark D. Blackwell <
markdblackwel...@gmail.com> wrote:
> After an extremely long syllable in the lyrics, the next measure's
> spacing is quite wide, even with ragged-right (in version 2.19.37).
>
> The problem does not occur in version 2.18.2.
>
Greetings, Mark D.
Greetings -
Had a wonderful trip to Cuba. Lots of good music, and shared Lilypond with
a couple of (new) users, I hope. I'm back and doing Friday again.
Ralph
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-li
On Sat, Mar 5, 2016 at 4:11 AM, Urs Liska wrote:
>
>
> Am 05.03.2016 um 09:51 schrieb Blöchl Bernhard:
> > I would recommend to add the options a user has to any item in the
> > chapter (maybe in other chapters as well)
> > 4.1.6 Other \paper variables
> > in the actual example that would mean
>
Greetings, All -
I shall not be able to do Fridays after today until March 18. Please help
cover for me.
Thanks for your help,
Ralph
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
On Mon, Feb 1, 2016 at 4:02 AM, Urs Liska wrote:
> Hi all,
>
> I've always found that beams with three or more beams look too tight,
> but now reading Gould, p. 19 confirms that, and I consider this a
> type-ugly bug:
Thanks, Urs. This has been submitted as Issue #4765 :
https://sourceforge.net
On Wed, Jan 27, 2016 at 6:57 AM, Malte Meyn wrote:
>
>
> Am 27.01.2016 um 10:19 schrieb Urs Liska:
> > In such situations one will usually shift the dynamics to the left, and
> > Lily will automatically use the space better. You can see that when you
> > uncomment one of the lines in \off.
> >
>
On Sun, Jan 3, 2016 at 12:18 PM, Simon Albrecht
wrote:
>
> I’ve noticed that in aligning instrument names, different widths of
> SystemStart* grobs are not taken into account, which yields unpleasant
> gaps. Rather, the upper instrument name in the attached example should
> cling closer to the Sys
On Fri, Jan 1, 2016 at 8:21 PM, Thomas Morley
wrote:
> Overriding OttavaBracket.text fails for unknown reasons. Has to be
> done after/before-line-breaking.
> It fails for \propertyOverride Staff.OttavaBracket.text as well, which
> prevents alterBroken from working.
Thanks, Harm - This has been
On Wed, Dec 9, 2015 at 6:38 PM, Simon Albrecht
wrote:
> Hello,
>
> maybe Lily should not give a ‘no viable initial configuration found: may
> not find good beam slope’ warning if the user has already taken care of the
> problem through the Beam’s positions property:
>
> \version "2.19.32"
> {
>
On Tue, Dec 1, 2015 at 7:34 PM, Gilberto Agostinho <
gilbertohasn...@googlemail.com> wrote:
> Hello list,
>
> Here is a bizarre little bug I came across today: for some reason, an
> invisible rest on a different Staff seems to affect the kneed beamed stems
> on a PianoStaff when using \autochange
On Fri, Nov 6, 2015 at 8:17 AM, pls wrote:
> Hi Harm,
>
> looks like fret label values are not computed correctly when
> predefined fretboards contain text strings instead of fingering
> indications.
> This small issue only shows when alternate fretboards are defined and
> used. That's why my mi
On Fri, Oct 30, 2015 at 4:11 AM, Federico Bruni wrote:
> Hi all
>
> I'm updating the Usage manual and I find this description not clear enough
> (disclaimer: I don't know anything about this font stuff):
>
> """
> @item @code{svg-woff}
> @tab @code{#f}
> @tab Use woff font files in SVG backend.
>
On Sun, Oct 4, 2015 at 5:41 AM, Simon Albrecht
wrote:
> Hello,
>
> in the following snippet the MMR should be displayed with the "rests.M1"
> glyph (vertical bar between two staff lines). But with Timing_translator
> moved to staff level, this works only if the staff is not explicitly
> instantia
41 matches
Mail list logo
