> c): Add \dynamic know and later find a special name for Harm's
> dynamic engine.
(d) You add now `\dynamic` in a first MR. Eventually, Harm's stuff
gets applied in another MR under the same name, extending your
stuff.[*] IMHO there is no necessity to provide `convert-ly` rules
Hi David,
Am 13.12.21 um 08:05 schrieb David Kastrup:
But the remark in the documentation that, if one
uses a music function instead of an event function, one would always
have to use it with -/_/^, seems to be obsolete now.
No, it isn't. Put \displayLilyMusic (or other music functions)
Lukas-Fabian Moser writes:
> Hi all,
>
> Am 12.12.21 um 22:52 schrieb Lukas-Fabian Moser:
>>
>> Maybe I'm going too far in my belief that "standard tasks best
>> should not require # characters and scheme", but shouldn't we
>> provide a LilyPond syntax interface for this? It's not so uncommon
>>
Hi all,
Am 12.12.21 um 22:52 schrieb Lukas-Fabian Moser:
Maybe I'm going too far in my belief that "standard tasks best should
not require # characters and scheme", but shouldn't we provide a
LilyPond syntax interface for this? It's not so uncommon to want
custom dynamic expressions after
Hi Lukas,
> Maybe I'm going too far in my belief that "standard tasks best should not
> require # characters and scheme"
The limit does not exist. ;)
> but shouldn't we provide a LilyPond syntax interface for this?
Yes.
Do you know Harm's work in this direction?
On 2021-12-12 3:48 pm, David Kastrup wrote:
Aaron Hill writes:
On 2021-12-12 3:19 pm, David Kastrup wrote:
and one could instead define it as
make-dynamic-script =
#(define-event-function (str) (ly:markup?)
(make-music 'AbsoluteDynamicEvent 'text str))
Did you mean just markup? or is
Aaron Hill writes:
> On 2021-12-12 3:19 pm, David Kastrup wrote:
>> and one could instead define it as
>> make-dynamic-script =
>> #(define-event-function (str) (ly:markup?)
>>(make-music 'AbsoluteDynamicEvent 'text str))
>
> Did you mean just markup? or is ly:markup? a special predicate?
On 2021-12-12 3:19 pm, David Kastrup wrote:
and one could instead define it as
make-dynamic-script =
#(define-event-function (str) (ly:markup?)
(make-music 'AbsoluteDynamicEvent 'text str))
Did you mean just markup? or is ly:markup? a special predicate?
-- Aaron Hill
Jean Abou Samra writes:
> Le 12/12/2021 à 22:52, Lukas-Fabian Moser a écrit :
>> Hi Jean,
>>
>>> Use a real dynamic script. These care care of spacing for you.
>>>
>>> \version "2.22.1"
>>>
>>> psubito =
>>> #(make-dynamic-script #{ \markup { p \normal-text \italic "subito" } #})
>>>
>>> {
Le 12/12/2021 à 22:52, Lukas-Fabian Moser a écrit :
Hi Jean,
Use a real dynamic script. These care care of spacing for you.
\version "2.22.1"
psubito =
#(make-dynamic-script #{ \markup { p \normal-text \italic "subito" } #})
{ d'16_\psubito \cresc \repeat unfold 14 d'16 d'\f | }
Maybe I'm
Hi Jean,
Use a real dynamic script. These care care of spacing for you.
\version "2.22.1"
psubito =
#(make-dynamic-script #{ \markup { p \normal-text \italic "subito" } #})
{ d'16_\psubito \cresc \repeat unfold 14 d'16 d'\f | }
Maybe I'm going too far in my belief that "standard tasks best
Le 12/12/2021 à 21:24, Ahanu Banerjee a écrit :
Hello,
When creating a crescendo following a custom dynamic marking (e.g.,
piano subito), I am having trouble moving the start of the spanner to
a point following the dynamic markup.
What would be the best way of doing this? Example below.
Hello,
When creating a crescendo following a custom dynamic marking (e.g., piano
subito), I am having trouble moving the start of the spanner to a point
following the dynamic markup.
What would be the best way of doing this? Example below. Thanks!
\version "2.20.0"
{ d'16_\markup { \dynamic p
13 matches
Mail list logo
