[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Make \upbow an empty command + Segmentation fault
From: |
Dan Eble |
Subject: |
Re: Make \upbow an empty command + Segmentation fault |
Date: |
Sat, 14 Jun 2014 22:37:12 +0200 |
On 12/04/14 14:22, Felix Janda wrote:
> Hi,
>
> say I have a violin part with bowing instructions in a variable. Now I want
> to use the same variable in the full orchestral score but the bowing marks
> should be suppressed.
>
> \upbow is treated by lilypond as an articulation, but the other
> articulations should be unaffected by the suppressing of \upbow.
>
> upbow={}
>
> doesn't work because it breaks things like
>
> a\upbow ~ a
I’m sorry I haven’t spent time to thoroughly understand your needs, but it
sounds like there is a chance that something derived from this (which I have
actually used) would help:
stripArticulation =
#(define-music-function
(parser location music) (ly:music?)
(music-filter
(lambda (m) (not (eq? (ly:music-property m 'name) 'ArticulationEvent)))
music))
Rather than redefining \upbow, use \stripBowings \yourMusic to filter out the
articulations you don’t want to see.
Another approach that might work is to put the articulations in a different
music variable attached to spacers (e.g. “s1”) and then put it in simultaneous
music like <<\yourMusic \yourBowings>>, but I can’t say much about that because
I don’t do it.
—
Dan