Hi Knute,
thanks for the info. Because the discussion of the links I provided took place
in 2019 I was wondering if it was something still under consideration since
then. It could be that no official bug report was ever made. I'll have to
investigate and make the correspondin
This is a good place to start if you have patched a bug:
https://lilypond.org/bug-reports.html
or
https://lilypond.org/help-us.html
--
Knute Snortum
On Fri, Mar 11, 2022 at 3:29 AM Martín Rincón Botero
wrote:
>
> Hi all,
>
> I stumbled into this bug
> https://marc.info/?l=lilypond-user&m=142
Hi all,
I stumbled into this bug
https://marc.info/?l=lilypond-user&m=142300498620076&w=2 which I solved
with this patch https://marc.info/?l=lilypond-user&m=142477756707049&w=2
(the line numbers seem to be different nowadays). I'm using Lilypond 2.22.
Is there any chance that this small patch get
> From: Simon Albrecht
> Subject: Re: Bug in articulate.ly
>
> > Another example is that you could indicate "tempo rubato" and then
> > specify as interpretation one of the many possible actual tempo(s) that
> > would be used for rendering the MIDI.
> I
On Sun, Mar 01, 2015 at 10:44:24AM +0100, Anton Curl wrote:
>
> On 28/02/2015 20:11, H. S. Teoh wrote:
> >Ideally, I'd like to be able to specify interpretations of elements
> >in the typeset score, for example, something like: % (This is
> >hypothetical syntax) | \interpret{ a1\prall } { b16 a gi
On Sun, Mar 01, 2015 at 11:40:29PM +0100, Simon Albrecht wrote:
> Am 28.02.2015 um 20:11 schrieb H. S. Teoh:
[...]
> >Another example is that you could indicate "tempo rubato" and then
> >specify as interpretation one of the many possible actual tempo(s) that
> >would be used for rendering the MIDI
Am 28.02.2015 um 20:11 schrieb H. S. Teoh:
On Fri, Feb 27, 2015 at 05:14:09PM -0800, Flaming Hakama by Elaine wrote:
[...]
I've recently been using lilypond with articulate.ly to produce midi
versions of pieces and have to say that, despite its limitations, I've
been getting results that are not
On 28/02/2015 20:11, H. S. Teoh wrote:
Ideally, I'd like to be able to specify interpretations of elements in
the typeset score, for example, something like: % (This is
hypothetical syntax) | \interpret{ a1\prall } { b16 a gis b a2. } |
which would cause the { a1\prall } appear on the score, b
On Fri, Feb 27, 2015 at 05:14:09PM -0800, Flaming Hakama by Elaine wrote:
[...]
> I've recently been using lilypond with articulate.ly to produce midi
> versions of pieces and have to say that, despite its limitations, I've
> been getting results that are not terrible.
I've been getting mixed resu
> From: "H. S. Teoh"
>
> On Wed, Feb 25, 2015 at 08:58:07AM +1100, Peter Chubb wrote:
> [...]
> > BTW, articulate was developed as a hack for the Artemis robot
> > instrument challenge; changes in Lilypond since then mean that it's
> > rather out of date. Some of the functionality is now already
On Wed, Feb 25, 2015 at 08:58:07AM +1100, Peter Chubb wrote:
[...]
> BTW, articulate was developed as a hack for the Artemis robot
> instrument challenge; changes in Lilypond since then mean that it's
> rather out of date. Some of the functionality is now already in the
> Lilypond C++ core (shorte
> "Davide" == Davide Liessi writes:
Davide> Dear Peter, Il 24/02/15 06.48, Peter Chubb ha scritto:
>> I had a brainstorm -- the problem is SkipMusic which isn't handled
>> anywhere. But we can use a SkipEvent instead, and it all works!!!
Davide> Alas it does not: I get the same barcheck fai
Dear Peter,
Il 24/02/15 06.48, Peter Chubb ha scritto:
> I had a brainstorm -- the problem is SkipMusic which isn't handled
> anywhere. But we can use a SkipEvent instead, and it all works!!!
Alas it does not: I get the same barcheck failures both in the minimal example
I posted and in the real
> "Davide" == Davide Liessi writes:
Davide> Dear Peter, Il 04/02/15 09.46, Peter Chubb ha scritto:
>> Looks like the code that was added to do agogic accents (aka swing)
>> expands MultiMeasureRestMusic and throws away any articulation
>> events (like the end of the trill spanner) on the way.
> "Davide" == Davide Liessi writes:
Davide> Dear Peter, Il 04/02/15 09.46, Peter Chubb ha scritto:
>> Looks like the code that was added to do agogic accents (aka swing)
>> expands MultiMeasureRestMusic and throws away any articulation
>> events (like the end of the trill spanner) on the way.
Dear Peter,
Il 04/02/15 09.46, Peter Chubb ha scritto:
Looks like the code that was added to do agogic accents (aka swing)
expands MultiMeasureRestMusic and throws away any articulation events
(like the end of the trill spanner) on the way.
The fix is probably to add the ariculations in at the
> "Noeck" == Noeck writes:
Noeck> Hi Davide,
>> I would expect \articulate to correctly handle trill spanners
>> regardless to what \stopTrillSpan is attached to.
Noeck> Yep, me too. That’s why I said: I don’t know how to fix it.
Looks like the code that was added to do agogic accents (ak
Hi Davide,
> I would expect \articulate to correctly handle trill spanners regardless
> to what \stopTrillSpan is attached to.
Yep, me too. That’s why I said: I don’t know how to fix it.
Joram
___
lilypond-user mailing list
lilypond-user@gnu.org
https
Dear Joram,
Il 04/02/15 00.19, Noeck ha scritto:
I don’t know how to fix it in articulate but adding <> and moving the
\stopTrillSpan before the rest seems to work:
Thanks, that is a nice workaround!
However I believe this is a bug in articulate.ly.
This means: The trill stops visua
Hi Davide,
I don’t know how to fix it in articulate but adding <> and moving the
\stopTrillSpan before the rest seems to work:
\version "2.19.15"
\include "articulate.ly"
mus = {
b1 \startTrillSpan |
<> \stopTrillSpan R1 |
b2 r |
}
\new Staff \mus
\articulate \mus
This means: The trill st
Dear all,
I found a strange behaviour in the interaction of articulate.ly with
TrillSpan and full-measure rests.
This snippet:
\version "2.19.15"
\include "articulate.ly"
\articulate {
b1 \startTrillSpan |
R1 \stopTrillSpan |
b2 r |
}
gives a warning: barcheck failed at: 1/2
b2 r
21 matches
Mail list logo
