Quick answer, and I’m not sure it will help much:
\dynamicUp affects the context (Voice) in which it’s placed.
\partCombine combines its arguments into new Voices and \dynamicUp
ended up in a different voice than the p
Thank you for your answer.
When you remove \dynamicUp ALL dynamics appea
Quick answer, and I’m not sure it will help much:
\dynamicUp affects the context (Voice) in which it’s placed. \partCombine
combines its arguments into new Voices and \dynamicUp ended up in a different
voice than the p
Thank you for your answer.
When you remove \dynamicUp ALL dynamics appea
Quick answer, and I’m not sure it will help much:
\dynamicUp affects the context (Voice) in which it’s placed. \partCombine
combines its arguments into new Voices and \dynamicUp ended up in a different
voice than the p
Thank you for your answer.
When you remove \dynamicUp ALL dynamics appea
I presume that partCombine overrides the dynamic placement so that
dynamics for the two parts are placed above and below, which seems a
reasonable approach when the parts are more distinct than in the given
example. Using ^ to override it in this case seems a tolerable alternative.
Thank you
From: Michael Gerdau
To: lilypond-user
Sent: 13/10/2023 11:30
Subject: Dynamics placement in partCombine
Hi list,
the following code places the 2nd \p under the music but I'd like it
above. I know I could explicitly add a placement (like ^\p) but wonder
why \dyna
Quick answer, and I’m not sure it will help much:
\dynamicUp affects the context (Voice) in which it’s placed. \partCombine
combines its arguments into new Voices and \dynamicUp ended up in a different
voice than the p
> 13 okt. 2023 kl. 12:32 skrev Michael Gerdau :
>
> Hi list,
>
> the fo
Hi list,
the following code places the 2nd \p under the music but I'd like it
above. I know I could explicitly add a placement (like ^\p) but wonder
why \dynamicUp doesn't do its job.
- snip - snip - snip - snip - snip - snip - snip -
\version "2.25.9"
musa = { \dynamicUp c'4\p \repeat unfol
On Wed, 2016-03-23 at 11:47 +0100, Xavier Scheuer wrote:
> I use Graham (Percival)'s "make-dynamic-extra", which has two main
> advantages :
> 1. The dynamic only, and not the whole "dynamic + text", is centered
> on the note (i.e. like a "normal" dynamic).
> 2. The dynamic is affecting the MIDI.
2016-03-23 13:21 GMT+01:00 Graham King :
> (bug-lilypond: a regression with note-spacing in proximity to dynamic
> text.)
>
> On Wed, 2016-03-23 at 11:38 +0100, Thomas Morley wrote:
>
>
>> a minimal example would have been:
>>
>> \version "2.19.38"
>>
>> music = { g'8(\p f'!) s2. }
>> \new Staf
(bug-lilypond: a regression with note-spacing in proximity to dynamic
text.)
On Wed, 2016-03-23 at 11:38 +0100, Thomas Morley wrote:
> a minimal example would have been:
>
> \version "2.19.38"
>
> music = { g'8(\p f'!) s2. }
> \new StaffGroup \new Staff \music
Wow. To get to that, I thin
On Tue, 2016-03-22 at 22:18 -0400, Kieren MacMillan wrote:
> Hi Graham,
>
> > The unwelcome spacing between the 4th and 5th notes goes away if one:
>
> … uses
>
> mpdolce = -\tweak X-extent #empty-interval #(make-dynamic-atr-script "mp"
> "dolce”)
>
Thanks Kieran,
that's very helpful. I've
On 22 March 2016 at 23:41, Graham King wrote:
>
> I've adopted Simon Albrecht's excellent suggestion in an earlier
> thread [1], and am now using code based on snippet 739 [2] to typeset
> some long dynamic markings. This has solved a host of layout problems;
> however, it has introduced this nas
2016-03-23 2:56 GMT+01:00 Graham King :
> Here is a compilable example. It is a bit long, but I think it is pretty
> close to minimal.
>
> In its defence: the first 32 lines are, effectively, snippet 739 modified
> to produce "dynamic text" instead of "text dynamic" (in this case, "mp
> dolce" in
Hi Graham,
> The unwelcome spacing between the 4th and 5th notes goes away if one:
… uses
mpdolce = -\tweak X-extent #empty-interval #(make-dynamic-atr-script "mp"
"dolce”)
=)
Hope this helps!
Kieren.
Kieren MacMillan, composer
‣ website: www.kierenmacmillan.
Here is a compilable example. It is a bit long, but I think it is
pretty close to minimal.
In its defence: the first 32 lines are, effectively, snippet 739
modified to produce "dynamic text" instead of "text dynamic" (in this
case, "mp dolce" instead of, say, "meno f").
The remaining few lines a
Ah yes, a minimal compilable example. This is going to be tough,
especially as I've just noticed that some
_functionally_indistinguishable_code_ a few bars earlier yields this:
which is precisely the behaviour I'm after.
Nevertheless, I'll try to produce a minimal compilable example. It
might
Hi Graham,
you did a nice and good job listing all the links:
2016-03-22 23:41 GMT+01:00 Graham King :
> [...]
> Notes:
> [1] https://lists.gnu.org/archive/html/lilypond-user/2016-03/msg00556.html
> [2] http://lsr.di.unimi.it/LSR/Item?id=739
> [3]
> http://www.lilypond.org/doc/v2.19/Documentatio
Hello Graham,
please give an actual code example, as small as possible, to start with.
Best, Simon
On 22.03.2016 23:41, Graham King wrote:
I've adopted Simon Albrecht's excellent suggestion in an earlier
thread [1], and am now using code based on snippet 739 [2] to typeset
some long dynamic m
I've adopted Simon Albrecht's excellent suggestion in an earlier thread
[1], and am now using code based on snippet 739 [2] to typeset some long
dynamic markings. This has solved a host of layout problems; however,
it has introduced this nasty spacing issue:
r2 r8 bes8(\mfdolce a bes) |
On Mittwoch, 29. April 2009 18:55:13 Reinhold Kainhofer wrote:
> Thanks to the nice solution by Neil, I was able to move the dynamic signs
> inside the staff, but I'm still running into several problems, mainly in
> connection with hairpins... Attached is a sample file with all the issues
> and som
20 matches
Mail list logo
