On 23.10.18 19:11, Lucas Werkmeister wrote:
> In the end, I went for a variation of Graham’s suggestion instead,
> encapsulated in a music function:
>
> extendedNote =
> #(define-music-function
> (parser location note)
> (ly:music?)
>#{
> \aft
Hi Kieren and Graham,
thank you both for your responses. Kieren, I really like the idea in
your suggestion – but it doesn’t seem to be a good fit for my situation:
while the tag solution is neat, in my case the ends of the extenders
align with different voices at different times (there are four vo
Hi everyone,
I’m transcribing an old choral score for LilyPond (full source at [1]),
and while I’ve been mostly successful so far, one thing I haven’t
figured out yet is the extenders. In the original score, several notes
have extenders in the lyrics, to indicate the duration of the note
relative
Hi Kieren, thanks for taking a look!
On 29.03.2018 01:52, Kieren MacMillan wrote:
> Hi Lucas,
>
>> I did find one workaround, and I’ll describe it just in case someone else
>> with the same problem finds this email later, but it is horrible:
> Here’s another… though I’m not sure it’s much less ho
Hi everyone!
In a composition I’m transcribing, there are double slurs between some
notes (see attached image, also uploaded at [1]), and the lower slurs
are right next to the note heads, inside the beams – whereas when
typeset by LilyPond, the slurs are outside the beams. I’m wondering what
the b
Sorry for the even later reply, but this seems to work great as well –
and thanks for updating the snippet already :)
Cheers,
Lucas
On 18.03.2018 19:35, Thomas Morley wrote:
> Hi Lucas,
>
> sorry for the late reply
>
> 2018-03-16 0:50 GMT+01:00 Lucas Werkmeister :
>
>> Pe
On 18.03.2018 12:17, Malte Meyn wrote:
> Am 17.03.2018 um 20:01 schrieb Lucas Werkmeister:
>> Can confirm, coredumpctl shows loads of t1asm core dumps (no idea why
>> there’s no error message in the terminal), and downgrading to t1utils
>> 1.39 fixed the problem (1.40 seems b
On 11.03.2018 19:35, Daniel Johnson wrote:
> In Gentoo it was discovered that there is a buggy version of t1utils which
> segfaults and causes this exact error.
>
> Sent from my iPhone
>
>> On Mar 11, 2018, at 2:18 PM, Werner LEMBERG wrote:
>>
>>
>>> Invoking "t1asm parmesan-noteheads14.pt1 parme
Hi,
thanks a lot for looking into this and finding a better implementation!
On 15.03.2018 23:33, Thomas Morley wrote:
> Hi Lucas,
>
> all below under the condition 'if I understand correctly' ;)
>
> 2018-03-15 18:38 GMT+01:00 Lucas Werkmeister :
>> Hi everyone
Hi everyone,
I was trying to use the \displaceHeads function from snippet 861 [1] [2]
on an eight-note chord, but found that it completely removes the beam
for some reason. I reduced it down to the following code:
\version "2.18.2"
{
\tweak before-line-breaking #(lambda (grob)
On 11.03.2018 01:29, Lucas Werkmeister wrote:
> I’m not sure if the clef behavior would still qualify as a bug (in the
> docs, the grace note isn’t at the very beginning of the score, so the
> clef behavior doesn’t happen)
And it turns out this has also been described [1]. I must just
On 11.03.2018 00:58, Lucas Werkmeister wrote:
> (Or perhaps it’s simply expected that grace notes should be aligned
> between staves? But that would surprise me.)
Color me surprised, then – I just found this issue mentioned in the docs
[1], with the same workaround I also discovered. I’m no
Hi everyone,
I’m getting the following error message when trying to build LilyPond
from git (specifically, building the AUR lilypond-git package).
if test -f out/parmesan-noteheads23.enc; then touch
out/parmesan-noteheads23.enc ; fi
/home/lucas/.cache/pacaur/lilypond-git/src/lilypond/scripts/buil
Hi everyone,
I found what I suspect is a LilyPond bug, but I’m not sure yet :)
minimal example:
\version "2.18.2"
<<
\new Staff { \grace c' c' }
\new Staff { \clef "bass" }
>>
Instead of beginning with a bass clef, the lower staff begins with a
violin clef and then has a bass clef right aft
Hi,
On 04.03.2018 13:54, Thomas Morley wrote:
> Hi Lucas,
>
> 2018-03-04 0:03 GMT+01:00 Lucas Werkmeister :
>> Hi everyone,
>>
>> I stumbled across a bug where Lilypond generates a bad slur if the slur
>> crosses a line break and there is a simultaneous clef
Hi everyone,
I stumbled across a bug where Lilypond generates a bad slur if the slur
crosses a line break and there is a simultaneous clef change in a
different staff. I found a previous report for this bug in the mailing
list archives (2015-05-30, same subject, [1]), but with Google Code
being ar
On 03.03.2018 02:06, Andrew Bernard wrote:
> Try this:
>
> \override Clef.font-size = #-3
>
> Adjust size to taste.
>
> Well worth spending the time to read and digest the material in the
> Internals section of the documentation. Look up Clef in the 'All
> layout objects' section, and then look at
[The email David’s responding to was rejected for the mailing list since
the attachments were too large; you can find the images at
https://imgur.com/a/jc6ga.]
On 03.03.2018 01:11, David Kastrup wrote:
> Lucas Werkmeister writes:
>
>> Hi!
>>
>> Andrew, attached you’ll
gure (left hand, with reversed roles for the clefs), but I’m afraid
the source code of that example is quite beyond me, and my attempts to
extract the relevant (to me) parts of it have failed.
Best regards,
Lucas Werkmeister
[1]: http://lsr.di.unimi.it/LSR/Item?id=326
__
19 matches
Mail list logo