Oh yeah, one more thing. When you're doing the Dynamics context you don't
need to replace the notes with spacer rests. You can just do a direct copy
of the music and add the dynamics to it - the notes don't get printed. So
you can just do this:
\new Dynamics \with {
fontSize = #-5
\override Hairpin.height = #0.4
} { c4\p c-\markup sostenuto c c c\< c c c\! }
and get just the dynamics.
On Tue, Jan 3, 2023 at 9:48 AM Michael Werner <[email protected]> wrote:
> Hi Mark,
>
> Looks like Hairpins have their own sizing properties. A full list is at
> http://lilypond.org/doc/v2.24/Documentation/internals/hairpin but in this
> case looks like height is probably the one you want used something like
> this:
>
> \version "2.24.0"
> \relative c'' {
> <<
> \new Staff \with {
> \magnifyStaff #2/3
> } { c4 c c c c c c c }
> \new Dynamics \with {
> fontSize = #-5
> \override Hairpin.height = #0.4
> } { s\p s-\markup sostenuto s s s\< s s s\! }
> >>
> }
>
> The default height value is 0.6666 so 0.4 is a rough approximation of 2/3
> the default. Adjust to taste.
>
> On Tue, Jan 3, 2023 at 9:19 AM Mark Mathias <[email protected]> wrote:
>
>> Yes, thank you. I overlooked retrying \magnifyStaff having just updated
>> to 2.24.0 after failing in 2.22.2. I just now tried it, but I get the same
>> result as with fontsize, viz., the text changes size, but the hairpins do
>> not.
>>
>> On Tue, Jan 3, 2023 at 8:49 AM Xavier Scheuer <[email protected]>
>> wrote:
>>
>>> On Tue, 3 Jan 2023 at 14:30, Mark Mathias <[email protected]> wrote:
>>> >
>>> > Using dynamics separately from a staff is useful, but for some reason
>>> changing the size affects the DynamicText but not the hairpins. I'd like
>>> the hairpins to match the staff size if possible.
>>>
>>> Hello,
>>>
>>> If you use Lilypond version > 2.23.6 (which seems to be the case
>>> according to your version statement), you should be able to use
>>> \magnifyStaff in Dynamics context.
>>> https://gitlab.com/lilypond/lilypond/-/issues/6188
>>>
>>> Cheers,
>>> Xavier
>>>
>>> --
>>> Xavier Scheuer <[email protected]>
>>>
>>>
