[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Forcing a DynamicText to appear inside the staff
From: |
David Kastrup |
Subject: |
Re: Forcing a DynamicText to appear inside the staff |
Date: |
Thu, 11 Aug 2016 12:34:33 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/25.1.50 (gnu/linux) |
Richard Shann <address@hidden> writes:
> On Wed, 2016-08-10 at 19:13 +0200, Thomas Weber wrote:
>> Hi all,
>>
>> in old orchestral scores one can observe that engravers did not
>> hesitate to make more room in dense situations by moving dynamics
>> into the staff rather than putting them below (or above). To
>> achieve the same effect, I tried the following:
>>
>>
>> {
>> \once \override Staff.DynamicText #'X-offset = -4
>> \once \override Staff.DynamicText #'Y-offset = 3
>> c' \f
>> }
>>
>>
>> But Lilypond insist on keeping the dynamic outside of the staff.
>> I'm not an experienced Lilypond user, so I'm most likely missing
>> something. How can I achieve this effect? (And are there
>> counterparts to X-offset and Y-offset that allow specifying an
>> absolute position? At least staff-position does not seem to work.)
>>
>
>
> This seems to work
>
> \version "2.19.43"
> {
> c'-\tweak #'extra-offset #'(-4 . 3) \f
> }
>
> Can someone expert let me know if that has some hidden implications?
extra-offset is a last-minute measure after all positioning and
collision avoidance has already been done. So whenever the positioned
idea of \f is moved in order to avoid a collision due to new elements
appearing, the extra-offsetted actual \f moves along. extra-offset is a
blind brute-force control. It most reliably does what you ask of it,
but it does not notice when the given task/offset stops making sense.
--
David Kastrup