lilypond-user
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: always set beam outside of staff


From: Michael Winter
Subject: Re: always set beam outside of staff
Date: Thu, 8 Sep 2016 09:13:29 -0700
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0

Respectfully,

This is like someone asking for directions but instead of getting an
answer on how to get to their preferred destination, getting asked why
they would want to go there at all.

If this were a question about default lilypond behavior, I would
understand that standard engraving practices should be discussed. But
this is an exceptional case that I would like to do programmatically.
That is, I was not asking for this to be the norm, but rather how I
could enable the exception. After all, lilypond is so, so powerful for
both its automatic behavior and the fact that you can pretty much do
anything that you want.

But to answer your question. I am engraving a score of someone
posthumously. There are uninked copies done by hand, which are probably
some of the most beautiful, albeit admittedly sometimes unconventional,
notation practices I have ever seen. Regardless, I am doing my best to
make the convention for engraving this particular project as close to
possible to the composer's original hand copies. And believe me, I have
yet to find a moment in this composer's work, where his exceptions to
common practices were not well thought out and considered.

Best,

Michael


On 09/08/2016 02:10 AM, Thomas Morley wrote:
> 2016-09-08 8:52 GMT+02:00 Michael Winter <address@hidden>:
>> Is it possible to force a beam to always start (vertically) a minimum
>> distance from the staff regardless of the stem direction?
>>
>> Thanks,
>>
>> Michael
>
>
> Hi Michael,
>
> well, it's doable. But why should I help you making LilyPond-output ugly?
> Is there any usecase which makes sense?
>
> Convince me/us! ;)
> And I will give it a try in the evening, now I have to run, job's calling.
>
> Cheers,
>   Harm





reply via email to

[Prev in Thread] Current Thread [Next in Thread]