Re: Dynamics in Lyrics?

Peter Chubb writes: >> "David" == David Kastrup writes: > > David> if you want a > David> context to engrave dynamics, it needs the respective engravers. > > Thanks David, >This all kind-of-works. It'll probably do for my immediate >needs; but the output is a bit ugly. I'l

Re: Dynamics in Lyrics?

> "David" == David Kastrup writes: David> if you want a David> context to engrave dynamics, it needs the respective engravers. Thanks David, This all kind-of-works. It'll probably do for my immediate needs; but the output is a bit ugly. I'll have to have a think about

Re: Dynamics in Lyrics?

This is perfect, but I'll add something else to keep in mind: you can use "\markup \dynamic f" to add dynamics in markup. Thanks, -William On 8/11/24 04:20, David Kastrup wrote: Peter Chubb writes: Hi Folks, Is there a simple way to add dynamic markings to lyrics? In a multi-verse

Re: Dynamics in Lyrics?

Peter Chubb writes: > Hi Folks, >Is there a simple way to add dynamic markings to lyrics? In a >multi-verse song, the dynamics can be different verse to verse. > >I'd like to do something like this: > > \score { > << > \new Staff \context Voice = tune {\repeat volta 2 { c c c c

Re: Dynamics collide with span bar

On 2024-03-22 5:30 pm, Michael Bret wrote: Then, it should be added that transposing your first fix (namely, BarLine.bar-extent = #'(0 . 1) and transparent = ##t) DOES solve the issue WITH “Bar_engraver” consisted. How does that make sense? I probably don’t get what "Span_bar_stub_engraver gett

Re: Dynamics collide with span bar (was Re: Chord names collide with span bar)

Many thanks, Aaron. So here is a cleaner MWE, with your fix: \version "2.25.13" #(ly:set-option 'debug-skylines #t) \layout { \context { \Score \override NonMusicalPaperColumn.show-horizontal-skylines = ##t } } \layout { \context { \Dynamics \consists Pure_from_neighbor_engraver \

Re: Dynamics collide with span bar (was Re: Chord names collide with span bar)

left = \relative do' { \key sol \major sol,8 (re' si' re,) sol, (re' do' re,) | sol, (re' sib' re,) sol, (re' do' re,) | } dynamics = { s1 | \override DynamicText.extra-spacing-width = #'(-1 . 1) s8 \ppp s8 s8 s8 s8 s8 s

Re: dynamics in coulour

Hi Stefan, On Tue, Feb 20, 2024 at 9:49 AM Stefan Thomas wrote: > Dear community, > is it possible to display the dynamics, also haipins and other things like > crescendo etc., in coulour? > Could someone could give me a hint? > Sure can. Most (if not all) grobs have a color property that can b

Re: dynamics in coulour

Thanks, I'll check it out! Best, Stefan Am Di., 20. Feb. 2024 um 16:33 Uhr schrieb Ritchie Fraser < euphoge...@gmail.com>: > Hi Stefan, > > I did just that last week I need to do the same thing for a cue part. This > is how I achieved it. > > > \new CueVoice { >\override Staff.StaffSymbol.col

Re: Dynamics [pl|sp]acing weirdness

Hi MIchael, > While that works, wrapping that combo isn't required all the time. E.g. when > you have > dynamicsA = { > s2. s4\mf\< | s2 s2\f | > } That’s because this version does not use \after, which is a music function that expects a single musical expression as its first parameter. > th

Re: Dynamics [pl|sp]acing weirdness

Hi Kieren, thanks for answering :) I've come across some placing or spacing weirdness with dynamics. In the attached example \dynamicsA is what I tried to code, aka the \< starts directly after the \mf. What I expected is what you see in \dynamicsB. However it seems as if the combo \mf\< does

Re: Dynamics [pl|sp]acing weirdness

Hi Michael, > I've come across some placing or spacing weirdness with dynamics. > In the attached example \dynamicsA is what I tried to code, aka the \< starts > directly after the \mf. What I expected is what you see in \dynamicsB. > However it seems as if the combo \mf\< does use some musical

Re: Dynamics placement in partCombine

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

Re: Dynamics placement in partCombine

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

Re: Dynamics placement in partCombine

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

Re: Dynamics placement in partCombine

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

Re: Dynamics placement in partCombine

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. Paul F

Re: Dynamics placement in partCombine

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

Re: Dynamics for both staves

On 2023-02-07 12:47, Jean Abou Samra wrote: On 07/02/2023 12:44, p...@ocmatos.com wrote: On 2023-02-03 17:41, Knute Snortum wrote: What I do is have a separate dynamics variable, then include that variable in both staves of the piano staff in the midi block.  Then I switch the dynamic performe

Re: Dynamics for both staves

On 07/02/2023 12:44, p...@ocmatos.com wrote: > On 2023-02-03 17:41, Knute Snortum wrote: >> >> What I do is have a separate dynamics variable, then include that >> variable in both staves of the piano staff in the midi block.  Then I >> switch the dynamic performer to the staff level.  It looks lik

Re: Dynamics for both staves

On 2023-02-03 17:41, Knute Snortum wrote: What I do is have a separate dynamics variable, then include that variable in both staves of the piano staff in the midi block. Then I switch the dynamic performer to the staff level. It looks like this (for only one staff): Thanks. What is the mean

Re: Dynamics for both staves

On Fri, Feb 3, 2023 at 8:41 AM Knute Snortum wrote: > > On Fri, Feb 3, 2023 at 12:21 AM Paulo Matos wrote: > > > > Hi, > > > > I am trying to apply dynamic marking like piano and so forth to both > > staves. > [...] > > i.e. start a new group called Dynamics and add the dynamics there but > > thi

Re: Dynamics for both staves

On Fri, Feb 3, 2023 at 12:21 AM Paulo Matos wrote: > > Hi, > > I am trying to apply dynamic marking like piano and so forth to both > staves. [...] > i.e. start a new group called Dynamics and add the dynamics there but > this seems suboptimal as it makes the typesetting separate from the > notes

Re: dynamics: sf vs sfz

Am 06.01.2022 um 18:09 schrieb Kenneth Wolcott: Thank you for your elaboration on the dynamics; much appreciated. On Thu, Jan 6, 2022 at 6:11 AM Kieren MacMillan wrote: Hi all, As composer, pianist, and conductor, I can offer that the consensus among most of the musicians I know is that sfz

Re: dynamics: sf vs sfz

Thank you for your elaboration on the dynamics; much appreciated. On Thu, Jan 6, 2022 at 6:11 AM Kieren MacMillan wrote: > > Hi all, > > As composer, pianist, and conductor, I can offer that the consensus among > most of the musicians I know is that sfz is [in modern practice] considered > diff

Re: dynamics: sf vs sfz

Hi all, As composer, pianist, and conductor, I can offer that the consensus among most of the musicians I know is that sfz is [in modern practice] considered different from sf, especially with respect to the envelope of the note: in "equation" terms, one might write sfz = sf + >. An analogous d

Re: dynamics: sf vs sfz

Hi Ken, sfz is sforzando, sometimes also fz (forzando) or sforzato or forzato or whatever. sf can be used as sforzando, but sometimes you find sf and sp also for subito forte and subito piano. Cheers, Valentin Am Donnerstag, 6. Jänner 2022, 04:19:58 CET schrieb Kenneth Wolcott: > Hi; > > M

Re: Dynamics and tempo alignment?

On Thu, Nov 4, 2021 at 2:31 PM Mark Knoop wrote: > \tempo is not a postfix command like dynamics and markups. Just put it before > the g2. I do so love the simple fixes. Thanks!

Re: Dynamics and tempo alignment?

At 14:16 on 04 Nov 2021, Kevin Cole wrote: Hi, I think I'm making great strides with my wee little transcriptions, but here's my latest puzzle: I have the following measure: g2^\>\tempo \markup { \italic "Slower." } 4 = 65 << { \voiceOne fs8\!\p([ g8]) } \new Voic

Re: Dynamics line above staff

Am 21.05.2021 um 21:37 schrieb Jean Abou Samra: > > > Le 21/05/2021 à 21:15, Bernhard Kleine a écrit : >> The dynamic line ist above the text (snippet) for the soprano. I would >> like to see it below the text, but on top of the staff that the "Mädel >> gib acht" is on top. I hope this is better ph

Re: Dynamics line above staff

Le 21/05/2021 à 21:15, Bernhard Kleine a écrit : The dynamic line ist above the text (snippet) for the soprano. I would like to see it below the text, but on top of the staff that the "Mädel gib acht" is on top. I hope this is better phrased. KR Bernhard I see. How about this? \version "2.

Re: Dynamics line above staff

The dynamic line ist above the text (snippet) for the soprano. I would like to see it below the text, but on top of the staff that the "Mädel gib acht" is on top. I hope this is better phrased. KR Bernhard Am 21.05.2021 um 17:47 schrieb Jean Abou Samra: > > > Le 21/05/2021 à 16:19, Bernhard Klein

Re: Dynamics line above staff

Le 21/05/2021 à 16:19, Bernhard Kleine a écrit : By the way, would it be possible to have the dynamics the single soprano text . Sorry, I don't understand the question. Could you rephrase it, please? Best, Jean

Re: Dynamics line above staff

Am 21.05.2021 um 16:19 schrieb Bernhard Kleine: > Am 21.05.2021 um 14:40 schrieb Jean Abou Samra: >> \new Dynamics = "page1" \with { >>   alignAboveContext = "sa" >>     } > The error was the "with" instead of "\with. > > Thank you for analysing. By the way, would it be possible to have the >

Re: Dynamics line above staff

Am 21.05.2021 um 14:40 schrieb Jean Abou Samra: > \new Dynamics = "page1" \with { >   alignAboveContext = "sa" >     } The error was the "with" instead of "\with. Thank you for analysing. By the way, would it be possible to have the dynamics the single soprano text . That would be very much

Re: Dynamics line above staff

Le 21/05/2021 à 14:23, Bernhard Kleine a écrit : here is the MWE: \version "2.21.1" \language "deutsch" \header {   title = "Ländler"   tagline = "Bernhard Kleine 2021" } \paper {   #(set-paper-size "a4") } global = {   \key d \major   \numericTimeSignature   \time 3/4 } soprano = \rela

Re: Dynamics line above staff

here is the MWE: \version "2.21.1" \language "deutsch" \header {   title = "Ländler"   tagline = "Bernhard Kleine 2021" } \paper {   #(set-paper-size "a4") } global = {   \key d \major   \numericTimeSignature   \time 3/4 } soprano = \relative c'' {   \global   % Die Noten folgen hier.   d4^\rfz^-

Re: Dynamics line above staff

Am 21.05.2021 um 11:09 schrieb Bernhard Kleine: > Hi, > > this snippet raises an error > >> \new Dynamics = "page1" with { >>   alignAboveContext = "sa" >>     } \dynamicI >> > while this does not: > >> \new Dynamics = "page1" \dynamicI >> > What is the proper was to place the dynamic line abo

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 offset suddenly changes

Hi Andrew, I couldn't answer that question without some sort of code example. Best, David On Tue, 26 Mar 2019, 5:24 p.m. Andrew Bernard, wrote: > Hi David, > > Why does \alterBroken move some and not others? > > Andrew > > > On Wed, 27 Mar 2019 at 02:18, David Nalesnik > wrote: > >> >> But yo

Re: Dynamics offset suddenly changes

Hi David, Why does \alterBroken move some and not others? Andrew On Wed, 27 Mar 2019 at 02:18, David Nalesnik wrote: > > But you are applying alterBroken to the Hairpin, not to the > DynamicLineSpanner, so of course the Hairpin will be moved > independently. > > __

Re: Dynamics offset suddenly changes

On Tue, Mar 26, 2019 at 8:38 AM Andrew Bernard wrote: > > Hi David, > > What I mean is that I thought alterBroken just affected the single shot > hairpin (wrong). In my score I have about 200 pages where there are hairpins > ending on dynamics on the next page, and after the erroneous call to >

Re: Dynamics offset suddenly changes

Hi David, What I mean is that I thought alterBroken just affected the single shot hairpin (wrong). In my score I have about 200 pages where there are hairpins ending on dynamics on the next page, and after the erroneous call to \alterBroken to adjust Y-offset, only some hairpins 80 pages or so awa

Re: Dynamics offset suddenly changes

Hi David, Aha! But it's funny that it only affects some down the line, with many of the same case not being affected. Andrew On Tue, 26 Mar 2019 at 23:40, David Nalesnik wrote: > > \once \alterBroken ... > > ___ lilypond-user mailing list lilypond-u

Re: Dynamics offset suddenly changes

On Tue, Mar 26, 2019 at 8:07 AM Andrew Bernard wrote: > > Hi David, > > Aha! But it's funny that it only affects some down the line, with many of the > same case not being affected. > > Andrew > I'm not clear what you mean here. But, if you suspect \alterBroken, you could retool the code given

Re: Dynamics offset suddenly changes

On Tue, Mar 26, 2019 at 6:07 AM Andrew Bernard wrote: > > Hi All, > > Thanks to Aaron's wonderful hairpin colouring function I have been able to > really focus in on the hairpin behaviour. > > I found the issue with my score. I am somewhat dumbstruck by this. There is a > call as follows at one

Re: Dynamics offset suddenly changes

Andrew Bernard writes: > Hi Aaron, > > Thank you for looking into this. As mentioned in my original post, I am not > using a Dynamics context as this New Complexity score is very, very complex > rhythmically, and it would tale a month to go back and figure out all the > spacer rests to use a dyna

Re: Dynamics offset suddenly changes

Hi All, Thanks to Aaron's wonderful hairpin colouring function I have been able to really focus in on the hairpin behaviour. I found the issue with my score. I am somewhat dumbstruck by this. There is a call as follows at one and only point point in the score: \alterBroken Y-offset #'(0 4) Hairp

Re: Dynamics offset suddenly changes

Sorry, Andrew. I've been buried in work for my choir. Allow me to try to address the questions/comments in a single mail to catch up. On 2019-03-25 5:04 pm, Andrew Bernard wrote: The pink arrow lines - how does lilypond work out this distance? It seems to be that that is jumping around

Re: Dynamics offset suddenly changes

Hi Aaron, The pink arrow lines - how does lilypond work out this distance? It seems to be that that is jumping around. Can you help me understand that? Andrew On Tue, 26 Mar 2019 at 08:18, Aaron Hill wrote: > > > Consider the following: > > > \version "2.19.82" > \paper { indent = 0 line

Re: Dynamics offset suddenly changes

Hello Aaron, Your hairpin marker code is astounding. Does this attached image from my score indicate anything awry? Andrew ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Dynamics offset suddenly changes

Hi Harm, My issue can't be related to stopping and starting staves, as that does not occur in my score. But it has a hint of being somehow related. Andrew On Tue, 26 Mar 2019 at 07:20, Thomas Morley wrote: > > A minimal triggering the problem (\break\stopStaff \startStaff needed) > and showin

Re: Dynamics offset suddenly changes

Hi Aaron, Thank you for looking into this. As mentioned in my original post, I am not using a Dynamics context as this New Complexity score is very, very complex rhythmically, and it would tale a month to go back and figure out all the spacer rests to use a dynamics context. I'd rather not do that

Re: Dynamics offset suddenly changes

Hi Harm, I am critically aware of the need to provide MWE's. I spent all yesterday trying to write one, and all works fine. It's only in the context of my large score that it shows up. What's more, it only just started happening, and all used to be fine. I raised the post to see if anybody has ha

Re: Dynamics offset suddenly changes

Hi Aaron, Thanks you. But the hairpins in question in my code all end on dynamics such as p or f, and were working fine up until a couple of days ago. I can't see what has changed, except the quartey score is now 110 pages. I am very sorry I cannot stimulate this in a small MWE. I am using 2.19.8

Re: Dynamics offset suddenly changes

On 2019-03-25 2:15 pm, Aaron Hill wrote: On 2019-03-25 2:42 am, Andrew Bernard wrote: Anybody? I have tried experimenting with large values of \override DynamicLineSpanner.staff-padding to no avail. I am stumped. Is it a bug? While it may not be ideal, to me this is not a bug. **DynamicLineS

Re: Dynamics offset suddenly changes

On 2019-03-25 2:42 am, Andrew Bernard wrote: Anybody? I have tried experimenting with large values of \override DynamicLineSpanner.staff-padding to no avail. I am stumped. Is it a bug? While it may not be ideal, to me this is not a bug. DynamicLineSpanners behave differently when not starte

Re: Dynamics offset suddenly changes

Am Mo., 25. März 2019 um 10:42 Uhr schrieb Andrew Bernard : > > Anybody? > > I have tried experimenting with large values of \override > DynamicLineSpanner.staff-padding to no avail. I am stumped. Is it a bug? > > Andrew > > > On Sun, 24 Mar 2019 at 20:48, Andrew Bernard wrote: >> >> I have a sco

Re: Dynamics offset suddenly changes

Anybody? I have tried experimenting with large values of \override DynamicLineSpanner.staff-padding to no avail. I am stumped. Is it a bug? Andrew On Sun, 24 Mar 2019 at 20:48, Andrew Bernard wrote: > I have a score with a lot of dynamics, a string quartet. There is more or > less a continuum

Re: dynamics and pedal as separate "voices"

Hi Kieren, Many thanks for your advice. This is a new LilyPond-terrain for me and It will certainly take me some time to implement it. Best regards, Robert Blackstone On 2 Nov 2018, at 14:24 , Kieren MacMillan wrote: > Hi Robert, > >> For my pianoscores I use a "dynamics voice" (\new Dyna

Re: dynamics and pedal as separate "voices"

Hi Robert, > For my pianoscores I use a "dynamics voice" (\new Dynamics = "dynamics" > \dynamics) and a "pedal voice" (\new Dynamics = "pedal" \pedal). An excellent design choice! > On the whole they work perfectly but compared to dynamic marks attached to > notes I find their possiblities a b

Re: dynamics and line spanning

Reilly Farrell writes: > Hi All, > > Is there an easy way to configure dynamics and markup text so that they > occupy they share the same vertical alignment relative to the staff? My > hope is that I can align regular dynamic marks with special dynamic > instructions (\cresc won't cut it in this

Re: dynamics and line spanning

Hi Reilly, How about : \version "2.19" << \new Staff { c1 1 1 1 } \new Dynamics { s1\p s s-\markup { cresc. poco a poco } s } >> Cheers, Pierre 2018-06-20 6:24 GMT+02:00 Reilly Farrell : > Hi All, > > Is there an easy way to configure dynamics and markup text so that they > occupy they sha

Re: Dynamics not centered

On 6/16/2018 3:21 PM, Torsten Hämmerle wrote: SoundsFromSound wrote Can someone tell me why the dynamics marking is not centered (like the default) when using it as a 'compound' command/variable markup? Hi Ben, That's because your declaration is a TextScript markup, and by default, a TextScrip

Re: Dynamics not centered

2018-06-16 21:21 GMT+02:00 Torsten Hämmerle : > SoundsFromSound wrote >> Can someone tell me why the dynamics marking is not centered (like the >> default) when using it as a 'compound' command/variable markup? > > Hi Ben, > > That's because your declaration is a TextScript markup, and by default,

Re: Dynamics not centered

SoundsFromSound wrote > Can someone tell me why the dynamics marking is not centered (like the > default) when using it as a 'compound' command/variable markup? Hi Ben, That's because your declaration is a TextScript markup, and by default, a TextScript will be set flush left-aligned. "Real" dy

Re: Dynamics within divisi

Hi, On Fri, 2017-09-15 at 09:42 -0700, SoundsFromSound wrote: > Alistair Millar wrote > > When I use the following divisi, I get the error message: > > "(De)crescendo > > with > > unspecified starting volume in MIDI." A \f is set a couple of bars > > before > > the > > divisi bar. > > > > << > >

Re: Dynamics within divisi

Alistair Millar wrote > When I use the following divisi, I get the error message: "(De)crescendo > with > unspecified starting volume in MIDI." A \f is set a couple of bars before > the > divisi bar. > > << > {r8\< c'4-.\> c8-.\!} > \\ > {g4-. c,-.} >>> > > How do I overcome this? Thanks > > Al

Re: Dynamics within divisi

Alistair Millar wrote > When I use the following divisi, I get the error message: "(De)crescendo > with > unspecified starting volume in MIDI." A \f is set a couple of bars before > the > divisi bar. > > << > {r8\< c'4-.\> c8-.\!} > \\ > {g4-. c,-.} >>> > > How do I overcome this? Thanks > > Al

Re: Dynamics inside a chord?

Not sure if that's also acceptable, but what *does* work is use of simultaneous voices: \version "2.19.44" \new Voice << { a } { b\p } >> Am 14/09/16 um 14:49 schrieb David Kastrup: Menu Jacques writes: Hello folks, Just for a try: \version "2.19.44" \relative { }

Re: Dynamics inside a chord?

On 14.09.2016 13:27, Menu Jacques wrote: Hello folks, Just for a try: \version "2.19.44" \relative { } runs fine without any message, but also without displaying the \p mark. A valid request, I think, so: Best, Simo

Re: Dynamics inside a chord?

Thanks David. JM > Le 14 sept. 2016 à 14:49, David Kastrup a écrit : > > Menu Jacques writes: > >> Hello folks, >> >> Just for a try: >> >> \version "2.19.44" >> >> \relative { } >> >> runs fine without any message, but also without displaying the \p mark: > > Not supported. >

Re: Dynamics inside a chord?

Menu Jacques writes: > Hello folks, > > Just for a try: > > \version "2.19.44" > > \relative { } > > runs fine without any message, but also without displaying the \p mark: Not supported. -- David Kastrup ___ lilypond-user mailing list

Re: Dynamics & simultaneous notes yield "programming error"

Hi Joel, it looks like this hasn’t been answered yet. I can’t reproduce the bug on Ubuntu, but could you make a minimal example and report on the bug list? There was recent development in that field, so it would be perfect if you could narrow down arou

Re: Dynamics & simultaneous notes yield "programming error"

Yesterday, I wrote: > Compiling the attached file (Lilypond 2.19.46, Windows 10) yields errors of > the sort > >> programming error: asked to compute volume at +1.00 for dynamic span of >> duration 1.00 starting at 1 >> continuing, cross fingers Okay, this is interesting. If I replace

Re: Dynamics & simultaneous notes yield "programming error"

On 2016-08-28 17:52, Joel C. Salomon wrote: Compiling the attached file yields errors of the sort programming error: asked to compute volume at +1.00 for dynamic span of duration 1.00 starting at 1 continuing, cross fingers Don't know why but the error occurs when the midi is create

Re: Dynamics & simultaneous notes yield "programming error"

On Aug 28, 2016 12:07 PM, "Phil Holmes" wrote: > Which version of Lilypond, which operating system? 2.19.46 on Windows 10. —Joel C. Salomon ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Dynamics & simultaneous notes yield "programming error"

Which version of Lilypond, which operating system? -- Phil Holmes - Original Message - From: "Joel C. Salomon" To: "LilyPond Users" Sent: Sunday, August 28, 2016 4:52 PM Subject: Dynamics & simultaneous notes yield "programming error" Compiling the attached file yields errors of t

Re: Dynamics to the left of the note

On Thursday, August 25, 2016, Evan O'Dorney wrote: > Glad I could brighten your day. For the record, it's simply > > \once \override DynamicText.X-offset = -3 > > for dynamics attached to a note. > Ah, yes. No need for the initial Dynamics context. Good catch. -- Abraham ___

Re: Dynamics to the left of the note

Glad I could brighten your day. For the record, it's simply \once \override DynamicText.X-offset = -3 for dynamics attached to a note. Best, Evan On Thu, Aug 25, 2016 at 4:38 PM, Abraham Lee wrote: > > > On Thursday, August 25, 2016, Evan O'Dorney wrote: > >> Hi all, >> >> Could someone plea

Re: Dynamics to the left of the note

On Thursday, August 25, 2016, Evan O'Dorney wrote: > Hi all, > > Could someone please remind me how to print a dynamic mark to the left of > a (ledger-line) note, instead of above or below it? I know it's in the > manual, but Google is not being merciful to me today. > > MWE: > > d\f > Fantastic

Re: Dynamics placement

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.

Re: Dynamics placement

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

Re: Dynamics placement

(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

Re: Dynamics placement

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

Re: Dynamics placement

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

Re: Dynamics placement

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

  1   2   3   4   >