Hi Harm, hi list,
I did some simple tests and looked through the code in more detail:
---
The customization features are great! Also, I like the dashed line of
the pre-pend-hold use cases.
The dashed line would also be great in cases like those:
c'\3\startBend d'\3\stopBend~ d'\3
% bend up,
> The issue occurs when writing closely spaced chords with an
> augmentation dot in the rhythm. Dots are placed only on spaces
> (which we should expect), but in certain very easy to reproduce
> conditions, the dot appears in an unexpected place.
Cf. `regression/chord-dots.ly'; this is controlled
On 09/11/2016 05:53 AM, Thomas Morley wrote:
as result of my private None-Google-Summer-of-Code, I'd like to
announce a BendSpanner-engraver.
Hi Harm, Wow, I just took a quick look and congratulations! this is
quite a project. I look forward to looking closer to see how you did it
when I ha
Hi Harm,
On 09/10/2016 02:48 PM, Thomas Morley wrote:
many thanks for looking into it and adding a diff, much easier to
compare the versions. :)
You're welcome! Thanks for writing the code for me to test out. :)
Also for the insufficient
(if duration-marks
which was kept from an earlier
Hi Knut,
Sounds cool! I'd like to check it out when I get a chance. I'm curious
how it compares with ly2video?
https://github.com/aspiers/ly2video
Cheers,
-Paul
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/l
> > Hallo,
> >
> > I am learning how to write bagpipe tunes with Lilypond. Bagpipe tunes
> > are usually in parts with a partial measure at the start and end of
> > each part. In order to avoid the warnings about use of "\partial"
> > within the body of the score I am trying to use "\set
> > Timing
Hi all,
I have only rarely typeset piano music in the past, which is probably why I
haven't come across this issue before.
The issue occurs when writing closely spaced chords with an augmentation
dot in the rhythm. Dots are placed only on spaces (which we should expect),
but in certain very easy
On Mon 12 Sep 2016 at 20:10:23 (+0200), Roderick Mackenzie wrote:
> I am learning how to write bagpipe tunes with Lilypond. Bagpipe tunes
> are usually in parts with a partial measure at the start and end of
> each part. In order to avoid the warnings about use of "\partial"
> within the body of th
Roderick Mackenzie writes:
> Hallo,
>
> I am learning how to write bagpipe tunes with Lilypond. Bagpipe tunes
> are usually in parts with a partial measure at the start and end of
> each part. In order to avoid the warnings about use of "\partial"
> within the body of the score I am trying to use
On 9/7/2016 11:56 PM, David F. wrote:
> Is there a way to combine two voices and print both stems (up and down) when
> the voices share a note? \partcombine does not appear to do this by default.
>
> American SATB hymns are typically engraved with the soprano and alto voices
> combined and the t
Hallo,
I am learning how to write bagpipe tunes with Lilypond. Bagpipe tunes
are usually in parts with a partial measure at the start and end of
each part. In order to avoid the warnings about use of "\partial"
within the body of the score I am trying to use "\set
Timing.measurePosition = #(ly:mak
On Mon, Sep 12, 2016 at 10:24 AM, Urs Liska wrote:
>
>
> Am 12.09.2016 um 17:04 schrieb David Nalesnik:
>> Hi Urs,
>>
>> On Mon, Sep 12, 2016 at 9:18 AM, Urs Liska wrote:
>>> In this sample:
>>>
>>> \version "2.19.48"
>>>
>>> {
>>> c2 ^\markup "First markup"
>>> c2 ^\markup "Second markup"
>>
Am 12.09.2016 um 17:04 schrieb David Nalesnik:
> Hi Urs,
>
> On Mon, Sep 12, 2016 at 9:18 AM, Urs Liska wrote:
>> In this sample:
>>
>> \version "2.19.48"
>>
>> {
>> c2 ^\markup "First markup"
>> c2 ^\markup "Second markup"
>> c2 ^\markup "Third markup"
>> }
>>
>> The markups are starting
Hi Urs,
On Mon, Sep 12, 2016 at 9:18 AM, Urs Liska wrote:
> In this sample:
>
> \version "2.19.48"
>
> {
> c2 ^\markup "First markup"
> c2 ^\markup "Second markup"
> c2 ^\markup "Third markup"
> }
>
> The markups are starting at the staff and when overlapping are printed
> above the precedi
In this sample:
\version "2.19.48"
{
c2 ^\markup "First markup"
c2 ^\markup "Second markup"
c2 ^\markup "Third markup"
}
The markups are starting at the staff and when overlapping are printed
above the preceding one.
Is there a way to have this behaviour reversed so that they are
startin
Wow Pierre, thank you very much! Problem solved :-)
Brent.
On 12 September 2016 at 19:54, Pierre Perol-Schneider <
pierre.schneider.pa...@gmail.com> wrote:
> Hi Brent,
>
> Simply delete these lines.
> See enclosed file.
> You'll get some warnings. See here to change the beam slope manually
> (cl
Hi Brent,
Simply delete these lines.
See enclosed file.
You'll get some warnings. See here to change the beam slope manually (click
on the image to see the coding):
http://lsr.di.unimi.it/LSR/Item?id=97
HTH,
Pierre
2016-09-12 10:24 GMT+02:00 Brent Annable :
> Hello everyone,
>
> I am not a fre
On Mon, 12 Sep 2016 18:24:53 +1000, Brent Annable wrote:
Hello everyone,
I am not a frequent Lilypond user, and am writing to ask for a
(hopefully
quick) favour here. I hope that's okay.
I wanted to transpose BWV 848 from c-sharp major into d-flat major to
make
it easier for me to read, so I
18 matches
Mail list logo
