[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: move tremolo beams
From: |
Thomas Morley |
Subject: |
Re: move tremolo beams |
Date: |
Sat, 27 Jun 2015 15:43:26 +0200 |
2015-06-27 14:22 GMT+02:00 Luca Danieli <address@hidden>:
> I am sorry... something went wrong when cleaning the code
>
> \repeat tremolo 8 {
> \once\override Hairpin.circled-tip = ##t e'16\<
> \once\override Hairpin.circled-tip = ##t eih!\>\fermata }
>
>
>
>> Date: Sat, 27 Jun 2015 14:04:15 +0200
>> Subject: Re: move tremolo beams
>> From: address@hidden
>> To: address@hidden
>> CC: address@hidden
>>
>> 2015-06-27 13:43 GMT+02:00 Luca Danieli <address@hidden>:
>> > Hello Lilyponders,
>> >
>> > I happened to write this code
>> >
>> > \repeat tremolo 8 {
>> > \once\override Hairpin.circled-tip = ##t
>> > e'16\<
>> > \once\override Hairpin.circled-tip = ##t
>> > eh\>\fermata
>> > }
>> >
>> > and I see that the accidental and the beams overlap.
>> > How to fix this problem to clear the view for the performer?
>> >
>> > Luca
>>
>>
>> GNU LilyPond 2.19.21
>> Processing `atest-27.ly'
>> Parsing...
>> atest-27.ly:3029:9: error: unrecognized string, not in text script or
>> \lyricmode
>>
>> eh\>\fermata
>> Interpreting music...
>> atest-27.ly:3029:11: warning: unterminated decrescendo
>> eh
>> \>\fermata
>>
>>
>> ??
>>
>> Please provide a compiling example.
>>
>> Cheers,
>> Harm
It's
https://code.google.com/p/lilypond/issues/detail?id=3143
Try:
\version "2.19.21"
%% using 'gap, will affect both sides of the tremolo beam though
\relative
\repeat tremolo 8 {
\override Beam.gap = #1.7
\once\override Hairpin.circled-tip = ##t e'16\<
%% maybe add:
%\once \override NoteColumn.X-offset = #2
\once\override Hairpin.circled-tip = ##t eih!\!\fermata
}
%% using 'positions to move the Beam in Y-direction
\relative
\repeat tremolo 8 {
\override Beam.positions = #'(0.8 . 0.8)
\once\override Hairpin.circled-tip = ##t e'16\<
\once\override Hairpin.circled-tip = ##t eih!\!\fermata
}
HTH,
Harm
P.S.
Please always compile the snippets you want to post.
Even your corrected snippet returned a unrelated warning and didn't
show the problem.