Re: Dynamics context doesn't work with polyphony(?)

Hi Aaron, thank you for your reply. I’ll try that later. Perhaps I should consider having a separate dynamics variable in the long run though. Potential issues like this could be so avoided by simply changing the problematic line of code. That would also allow me to have both the “normal” dynamics

Re: Dynamics context doesn't work with polyphony(?)

On 2020-09-11 1:56 am, Martín Rincón Botero wrote: Hello, sorry to bother again. I've been further exploring the Dynamics context. I just noticed that when there's a polyphonic passage, not only dynamics don't align anymore, but also \remove engravers fails to do its job. Is this a bug or is t

Re: Dynamics context

Here is an example of using custom dynamic spanners in the Dynamic Context: %%% \version "2.20.0" rh = \relative c' { c4 c c c| d4^\mf d d d| } lh = \relative c { \clef bass f4_\mp f f f | g4 g g g | } dyn = \relative { s4\ff s s s\pp | \override TextSpanner.bound-details.left.tex

Re: Dynamics context

Hey Ben, good question. I write contemporary classical music. In my score, for example, I have an independent tempo variable as a workaround for the current Lilypond lack of "tempo spanners" like rit., accel., etc. I merge this together in the score, and in the parts. Though not ideal, this is a m

Re: Dynamics context

> On Sep 8, 2020, at 11:50 AM, Ben wrote: > > On 9/8/2020 2:05 PM, Martín Rincón Botero wrote: (snip) >> >> >> -- >> www.martinrinconbotero.com > Martín, > > I'm curious: what would you say the pros/cons are for using a dynamics > context vs. a separa

Re: Dynamics context

On 9/8/2020 2:05 PM, Martín Rincón Botero wrote: Hi Wol, yes, what you mention is indeed a good case for using dynamics in their own variable. The problem comes when using a Dynamics context from an independent dynamics variable for music that by its own nature is not really compatible with t

Re: Dynamics context

> On Sep 8, 2020, at 9:03 AM, antlists wrote: > > On 07/09/2020 17:01, Martín Rincón Botero wrote: >> I wanted to ask if using the Dynamics context is the simplest way available >> in Lilypond for achieving this kind of vertically aligned dynamics. The huge >> drawback of the Dynamics contex

Re: Dynamics context

Hi Wol, yes, what you mention is indeed a good case for using dynamics in their own variable. The problem comes when using a Dynamics context from an independent dynamics variable for music that by its own nature is not really compatible with that approach, or for which the resulting code looks/fe

Re: Dynamics context

Dear Xavier, thank you very much again. This works as expected! I also find this solution more powerful than the one suggested in the Snippet Repository http://lsr.di.unimi.it/LSR/Item?id=450. This last command however, preceded with \once, is the one I normally use when manually positioning a dyn

Re: Dynamics context

On 07/09/2020 17:01, Martín Rincón Botero wrote: I wanted to ask if using the Dynamics context is the simplest way available in Lilypond for achieving this kind of vertically aligned dynamics. The huge drawback of the Dynamics context is that it disrupts the syntax, since dynamics can’t be used

Re: Dynamics context

Thank you very much, Xavier. I’ll try that! On Tue 8. Sep 2020 at 11:58 Xavier Scheuer wrote: > On Tue, 8 Sep 2020 at 11:18, Martín Rincón Botero < > martinrinconbot...@gmail.com> wrote: > > > > For I which I get the attached result. Weirdly, with this minimal > example I'm also getting a bunch

Re: Dynamics context

On Tue, 8 Sep 2020 at 11:18, Martín Rincón Botero < martinrinconbot...@gmail.com> wrote: > > For I which I get the attached result. Weirdly, with this minimal example I'm also getting a bunch of "script direction not yet known". I don't think that was happening before. Anyways, the visual result is

Re: Dynamics context

Hi Kieren, thank you for your answer. Here a MWE: \version "2.20.0" scoreAViolinI = \relative c'' { r2 r4 d,16-.\p\< dis'-. e-. g-. fis,4:32->\ff\>^"sul pont." r\! r2 } \score { << \new Voice \with { \remove "Dynamic_engraver" } \scoreAViolinI \new Dynamics \scoreAViolinI >> \layout

Re: Dynamics context

Hi Martín, > I wanted to ask if using the Dynamics context is the simplest way available > in Lilypond for achieving this kind of vertically aligned dynamics. I believe so. > The huge drawback of the Dynamics context is that it disrupts the syntax, > since dynamics can’t be used next to the fi

Re: Dynamics context and vertical positions

Hi Simon, I think you are right, it's a very specific type of music that benefits from centralized dynamics for single staffed instrument, namely contemporary music with many markings, sometimes with one marking per note. Cheers, Gilberto -- View this message in context: http://lilypond.1069

Re: Dynamics context and vertical positions

On 16.03.2016 11:07, Gilberto Agostinho wrote: \layout { \context { \Dynamics \override VerticalAxisGroup.nonstaff-relatedstaff-spacing.basic-distance = #0 } } I wonder why isn't this the default behaviour though, why would people want the Dynamic context so far away from the rel

Re: Dynamics context and vertical positions

Hi Abraham, Thank you for your quick reply! I believe I understand the problem now, and it seems that it can be solved by using: \layout { \context { \Dynamics \override VerticalAxisGroup.nonstaff-relatedstaff-spacing.basic-distance = #0 } } I wonder why isn't this the default behavi

Re: Dynamics context and vertical positions

Gilberto, On Tue, Mar 15, 2016 at 11:15 AM, Gilberto Agostinho [via Lilypond] < ml-node+s1069038n188571...@n5.nabble.com> wrote: > > The problem I have with it is that I often find the distance between the > dynamics and the staff to be very large and for no apparent reason. > ... [SNIP] ... > So

Re: Dynamics context vs. dynamics in staff

Hi Joram, > The problem is that if I override the Y-offset of a DynamicText, the > skyline changes and the other dynamics of this line are moved, too. > I suppose I should use the extra-offest in most cases. Do you agree? Often, I will use a combination of all three. 1. I will use functions like

Re: Dynamics context vs. dynamics in staff

Hi Simon, > This changed recently, see > . Briefly: > now, Y-offset is considered separately for DynamicText and > DynamicLineSpanner. This means that > – a DynamicLineSpanner can only have it’s Y-offset overridden before it > begins > – fo

Re: Dynamics context vs. dynamics in staff

Am 17.03.2015 um 20:13 schrieb Noeck: Hi Kieren, thanks for your reply. I know this issue you linked and for sure a real solution would be best. I have a few follow-up questions: - Can you point me to the edition engraver? - How do you move dynamics? extra-offset or X/Y-offset? I ask because

Re: Dynamics context vs. dynamics in staff

Hi Kieren, I have two more questions: Is there a way to force the centering of the dynamics context (sometimes it is shifted to the upper staff by notes in the lower staff, even if there is enough space to have it centered between the staves)? How can I move a whole line consistently up or down?

Re: Dynamics context vs. dynamics in staff

Hi Kieren, thanks for your reply. I know this issue you linked and for sure a real solution would be best. I have a few follow-up questions: - Can you point me to the edition engraver? - How do you move dynamics? extra-offset or X/Y-offset? I ask because the effect is not clear to me because I

Re: Dynamics context vs. dynamics in staff

Hi Joram, > What do you do for piano music? I use a Dynamics context exclusively. Actually, I use up to three: (*always*) the standard one between the piano staves, and (*as needed*) one above the top piano staff and/or below the bottom piano staff for dynamics which are exclusive to music in

Re: Re: Dynamics Context

> I found workaround for the dynamics. But this doesn't work for the > pedal statements. I add a "\shift" before each item that collides. Good idea. I think I am also able to add this to a pedal-mark by adding these lines to the shift-command: shift = { \once \override DynamicText #'self-

Re: Dynamics context

Am 16.03.2010 19:17, schrieb Robert Clausecker: Hi all! I have a problem with the Dynamics context: The Dynamics are always shifted to the left side, so they often collide with bars in systems with merged bars. Is there a way to fix this behavior instead of tweaking the properties for each dyna

Re: Dynamics context

Hi Charles, is there a way to have a special instrument (voice, whatever) where I can put markup above the systems for mutli-instrument compositions? 1. Try using \mark instead of \markup. 2. Look (in the docs, list archive, etc.) into examples where a "global" variable is used to hold "scor