On Tue, May 21, 2024 at 7:10 AM Werner LEMBERG wrote:
>
> You want to position the 'f' sign into the staff lines of the upper
> staff? If yes, then it doesn't fit with the concept of a a `Dynamics`
> context *between* the staves IMHO. Instead, I would attach the 'f'
> sign to
> Interestingly, the following does *not* work, [...]
It's not clear to me how the end result should look like.
> The dynamics context doesn't know that there's a staff above it
> and/ot the piano staff forbids the dynamics from encroaching on the
> staff above.
You want to pos
On Mon, May 20, 2024 at 8:58 PM Werner LEMBERG wrote:
> Since version 2.25.13 the NR contains the attached warning box.
>
Thank you, Werner. Interestingly, the following does *not* work, but I can
kind of understand why. The dynamics context doesn't know that there's a
staff above it
>> > So why would overriding the dynamic line spanner's
>> > outside-staff-priority change where the forte goes? Isn't it
>> > DynamicText? If anyone can clear this up for me, I would be very
>> > appreciative.
>>
>> When there are consecutive dyn
When there are consecutive dynamics like \p \< ... \f \> ... \pp, they
> need to be all vertically aligned. LilyPond achieves that by grouping
> them into a same DynamicLineSpanner, so it's that object which is
> responsible
> for the vertical placement of dynam
> So why would overriding the dynamic line spanner's outside-staff-priority
> change where the forte goes? Isn't it DynamicText? If anyone can clear this
> up for me, I would be very appreciative.
When there are consecutive dynamics like \p \< ... \f \> ... \pp, they
need to be
I am confused. While trying to find a way to move a forte mark up onto the
staff, I came across some very counter-intuitive code:
%%%
\version "2.24.3"
{
% Why does this work...
\once \override DynamicLineSpanner.outside-staff-priority = ##f
\once \override DynamicLineSpanner.Y-offset =
stubs
are not specifically needed if you have an actual BarLine grob. That is
why my earlier workaround worked.
Neither Lyrics nor ChordNames consist the Bar_engraver, so they rely on
Span_bar_stub_engraver. And the issue for ChordNames was the lack of
Pure_from_neighbor_engraver.
Dyn
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_neighbo
.
However, the solution provided by Werner doesn’t seem to transpose
effectively. I tried this to no avail:
This would appear to be related, although a new wrinkle has appeared.
Something to note is that the Dynamics context already consists the
Bar_engraver in order to make use
On Sat, Mar 16, 2024 at 10:20 AM Hans Aikema
wrote:
>
>
> On 16 Mar 2024, at 17:49, Phil Holmes wrote:
>
> Very short hairpins?
>
> Phil
>
> On 16/03/2024 16:27, Ralph Palmer wrote:
>
> Hi, Again -
>
> I've searched the Notation documentation and the LSR, and I cannot figure
> out how to solve
> On 16 Mar 2024, at 17:49, Phil Holmes wrote:
>
> Very short hairpins?
>
> Phil
>
> On 16/03/2024 16:27, Ralph Palmer wrote:
>> Hi, Again -
>>
>> I've searched the Notation documentation and the LSR, and I cannot figure
>> out how to solve this. It looks like a half note with an accent
Very short hairpins?
Phil
On 16/03/2024 16:27, Ralph Palmer wrote:
Hi, Again -
I've searched the Notation documentation and the LSR, and I cannot
figure out how to solve this. It looks like a half note with an accent
followed by a half note with the opposite figure. (You may have to
zoom
Hi, Again -
I've searched the Notation documentation and the LSR, and I cannot figure
out how to solve this. It looks like a half note with an accent followed by
a half note with the opposite figure. (You may have to zoom in a bit!) I
can do the accent, and I seem to remember its opposite, but I
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 pr
g4 r4 r4 |
> c,2. |
> fis2.\pp\( |
> g4\) r4 r4 |
> e2.\( |
> f4\) r4 r4 |
> }
>
> Regards
>
> Ritchie
>
> On Tue, 20 Feb 2024 at 14:49, Stefan Thomas
> wrote:
>
>> Dear community
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?
Thanks,
Stefan
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.
>
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
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\< doe
Hi list!
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
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
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
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
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
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
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
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
On Sat, 16 Sep 2023, Knute Snortum wrote:
> Try moving the Dynamic performer to the Staff level.
Cutting and pasting this code produces two pages of error messages because
it's full of "non-breaking space" characters which LilyPond can't process,
but I was able to get the desired results by
msk...@ansuz.sooke.bc.ca writes:
> Thank you. That works for the given example. However, with more
> complicated music that already contains multiple voices (as is typical of
> the piano music where a between-staff Dynamics context would be used in
> the first place), it
On Sat, Sep 16, 2023 at 6:01 AM wrote:
> On Sat, 16 Sep 2023, David Kastrup wrote:
>
> > Try
> >
> > \new Staff << \MyMusic \MyDynamics >>
> >
> > since otherwise the variables will end up in separate Staff contexts.
>
> With the following code, the notes in the MIDI file still are both at
>
yout { }
> \midi { }
> }
My mistake: Dynamic_performer by default lives at Voice level, so you'd
need \new Voice here in order to issue the dynamics on a level visible
to MIDI.
--
David Kastrup
t; > MyDynamics = { s1\ppp s1\fff }
> >
> > \score {
> > \new Staff << \MyMusic \MyDynamics >>
> > \layout { }
> > \midi { }
> > }
>
> My mistake: Dynamic_performer by default lives at Voice level, so you'd
> need \new Voice here in order to i
On Sat, 16 Sep 2023, David Kastrup wrote:
> Try
>
> \new Staff << \MyMusic \MyDynamics >>
>
> since otherwise the variables will end up in separate Staff contexts.
With the following code, the notes in the MIDI file still are both at
default velocity. Explicitly instantiating the Staff does
msk...@ansuz.sooke.bc.ca writes:
> I'm trying to use a Dynamics context to put dynamics between the staves of
> a PianoStaff. As such, I've got my notes and my dynamics in two separate
> variables. For MIDI output, I'd like to merge the contents of the music
> variable and the dynam
I'm trying to use a Dynamics context to put dynamics between the staves of
a PianoStaff. As such, I've got my notes and my dynamics in two separate
variables. For MIDI output, I'd like to merge the contents of the music
variable and the dynamics variable and generate MIDI from the result.
But I
ve the staff again:
>
> Hello,
>
> Removing "Bar_number_engraver" from the Score context and adding it
> to the Staff context (or the first staff with \with if you have more
> than one staff) will get the bar numbers onto the staff.
> It should give you the same bar numbe
ore context and adding it to the
Staff context (or the first staff with \with if you have more than one
staff) will get the bar numbers onto the staff.
It should give you the same bar number positioning as if the Dynamics
context was not above your staff.
If you have some overrides, change them from the Scor
testing further...
On Sun, 2023-08-27 at 07:50 -0700, Knute Snortum wrote:
> On Sun, Aug 27, 2023 at 7:31 AM Richard Shann
> wrote:
> > If I create a Dynamics staff above the music, the bar numbers are
> > printed on it rather than on the staff with the music. At least
> >
On Sun, 2023-08-27 at 07:50 -0700, Knute Snortum wrote:
> On Sun, Aug 27, 2023 at 7:31 AM Richard Shann
> wrote:
> > If I create a Dynamics staff above the music, the bar numbers are
> > printed on it rather than on the staff with the music. At least
> > this is
> >
On Sun, Aug 27, 2023 at 7:31 AM Richard Shann
wrote:
> If I create a Dynamics staff above the music, the bar numbers are
> printed on it rather than on the staff with the music. At least this is
> why setting the outside-staff-priority doesn't have any effect.
> Is there a way to get
If I create a Dynamics staff above the music, the bar numbers are
printed on it rather than on the staff with the music. At least this is
why setting the outside-staff-priority doesn't have any effect.
Is there a way to get bar numbers onto the staff with the music?
This is my MWE
Le mercredi 31 mai 2023 à 02:20 +0200, Jean Abou Samra a écrit :
> By the way, I'm also curious to understand why you chose to go the "install
> from source" route instead of the "install Flatpak" route
by which I mean “install the Frescobaldi Flatpak package”
> . (I gave it because I thought
Le mardi 30 mai 2023 à 10:00 -0700, Ralph Palmer a écrit :
> Thanks, Jean. I followed the long version as best I could. I'm not skilled or
> super familiar with working from the terminal, so I'm not sure I did
> everything exactly as I was supposed to. My main question would be whether I
> was
On Tue, May 30, 2023 at 9:14 AM Jean Abou Samra wrote:
> (Adding back the list)
>
> Le mardi 30 mai 2023 à 09:09 -0700, Ralph Palmer a écrit :
>
> Jean -
>
> I did get your messages. I took a quick look and felt confused and
> slightly overwhelmed. I'm going to try again. I appreciate your
(sorry, typoed the list address)
Le mardi 30 mai 2023 à 18:14 +0200, Jean Abou Samra a écrit :
> (Adding back the list)
> Le mardi 30 mai 2023 à 09:09 -0700, Ralph Palmer a écrit :
> > Jean -
> > I did get your messages. I took a quick look and felt confused and slightly
> > overwhelmed. I'm
Ralph,
I'm currently running LilyPond 2.24.0 and Frescobaldi 3.2 (still having
> problems figuring out how to install 3.3) under Linux/Ubuntu 22.04.2 LTS.
>
>
>
I'm a bit puzzled here because I tried to help you on
https://groups.google.com/g/frescobaldi/c/gKehyaVmAxo?pli=1
and
In markup, you can use \dynamic to use the dynamics characters. However, only
a small part of the alphabet is provided, as it is normally only used for
actual dynamics; what you want is not normal practice, and would come out
looking like the attached image.
Paul
From: Ralph Palmer
Hi -
I appreciate all the help this list provides. I seem to be helping less
than I used to; not sure why.
I've tried a few times recently to figure out how to make what would
effectively be a markup in dynamic script, with no success. I've looked
pretty extensively on the LilyPond site, as well
rreia.de.verd...@gmail.com>:
> >
> > You can do like this if it’s useful to you, removing the engravers that
> read what you don’t want at a specific place.
> > %%
> > \version "2.25.1"
> >
> > rh = \fixed c' {c4\pp d\
\with {
>\remove Dynamic_engraver }
> \rh
> \new Dynamics %Dynamics context doesn’t have the Note_Heads_Engraver anyway
> \rh
>>>
> }
> %%
>
> Otherwise it is possible to create music functions that replace notes and
> rests w
Minimum Working Example.
It's customary protocol to try to reduce your problem or query to its
basic essence so that people on the list can help out.
MWE's are described here:
https://lilypond.org/tiny-examples.html
MWE is the term that has come into use.
Andrew
On 29/04/2023 1:47 am,
the dynamics using a separate variable.
Suppose that on the first quarter of the tenth measure there is a
"forte" and then on the note of the next bar there is a "piano." If all
the measures have the same "time signature", let's say of 4/4, then it's
pretty easy: just cou
I have infinite esteem in cheerleader so if the message comes from one of
them I will do all what them propose:
- I will study what I can do with the edition engraver
- and wait for your MWE :))
By the way, ahem what is a MWE?
Grazie Kieren!
g.
On Fri, 28 Apr 2023 at 17:13, Kieren MacMillan
Hi Gianmaria!
> And now I understand better the reason for the thread Kieren linked.
> I probably have to go back to study the edition engraver :)
I’m the EE’s biggest cheerleader, so I would never dissuade you from that
study… but I really do think the \sendTo is either already exactly what
Le vendredi 28 avril 2023 à 15:08 +0200, Gianmaria Lari a écrit :
> Dear Robin,
> made some more tests.
> Your code works well but it doesn't solve the problem because it returns the
> "absolute" location of the notes while on the other hand in the variable
> where you write the dynamic you use
Gianmaria Lari wrote:
Your code works well but it doesn't solve the problem because it returns
the "absolute" location of the notes while on the other hand in the
variable where you write the dynamic you use a relative location.
That's why I said primitive.
One way to extend it, would be:
I often do math with those :
{
\override Score.BarNumber.break-visibility = ##(#t #t #t)
% Begin forte
<>\f
% At bar 4, mezzo piano
s1*#(- 4 1) <>\mp
% At bar 20, forte
s1*#(- 20 4) <>\f
% At bar 30, pianissimo
s1*#(- 30 20) <>\pp
s1\fine
}
Sure, you have to carry the
Dear Robin,
made some more tests.
Your code works well but it doesn't solve the problem because it returns
the "absolute" location of the notes while on the other hand in the
variable where you write the dynamic you use a relative location. For
example if I want to put a dynamic on the quarter
Hi Jean,
> Are we talking about the same thing? The \sendTo ideas sound more like
> they're solving the first question in the OP's original post than the second
> question to me.
Yes… I got confused about where we were in the conversation.
Sorry!
Kieren.
Thank you Jean, Kieren and Robin.
I had a look at the edition engraver but it was not trivial to understand
how to install it. Maybe I will try it again in the future.
I had a look at the SendTo thread, thanks!
And finally I tried the Robin code. Well, it looks like it's doing the
job
Le jeudi 27 avril 2023 à 10:14 -0400, Kieren MacMillan a écrit :
> Hi all,
>
> > This sounds like it might be a use case for Jan-Peter Voigt's "Edition
> > engraver" tool.
> > https://github.com/openlilylib/edition-engraver
>
> Ehhh… sounds to me more like a case for that “sendTo“ code we were
Gianmaria Lari wrote:
This thing always seemed so inconvenient to me that I thought it was
practically unusable. Or that there was some trick to maybe have
Frescobaldi tell me the "position" of the note (meant as numbers of quarter
or eight notes from the beginning).
Here is a primitive
Hi all,
> This sounds like it might be a use case for Jan-Peter Voigt's "Edition
> engraver" tool.
> https://github.com/openlilylib/edition-engraver
Ehhh… sounds to me more like a case for that “sendTo“ code we were
brainstorming last year:
Le jeudi 27 avril 2023 à 14:57 +0200, Gianmaria Lari a écrit :
> Regarding my second question, let me try to be more clear
>
> I have a score.
> I want to write the dynamics using a separate variable.
> Suppose that on the first quarter of the tenth measure th
Thank you Leo for your answers and help.
> you’ll probably need to be a little more specific about the use case,
> perhaps also supply example code.
>
Regarding my second question, let me try to be more clear
I have a score.
I want to write the dynamics using a separate variable
You can do like this if it’s useful to you, removing the engravers that read
what you don’t want at a specific place.
%%
\version "2.25.1"
rh = \fixed c' {c4\pp d\p e\f f\ff}
\score {
<<
\new Voice \with {
\remove Dynamic_engraver }
\rh
\new Dy
First question
Suppose I wrote this score:
\version "2.25.2"
rh = \fixed c' {c4\pp d\p e\f f\ff}
\score {
\new Staff \rh
}
Is there any "automatic" way to extract the dynamics in the score (maybe
assigning it to a variable)?
At the end I would like to easily transfo
On Fri, Apr 7, 2023 at 2:02 AM Dario Marrini
wrote:
> Hi lilypond people,
> I tried adding these :
>
> midiMinimumVolume = #0.05
> midiMaximumVolume = #0.95
>
> but I got no so different results;
>
Hmm, with the code below, I got very noticable results:
%%%
\version "2.24.1"
\score {
\new
2023 alle ore 10:14 Dario Marrini <
dario.marr...@gmail.com> ha scritto:
> Hi lilypond people,
> I'm trying to understand how all this works; there is a short code file as
> attachment, with midi and pdf ones; I tried to use dynamics and other
> signs, but the difference on so
Hi lilypond people,
I'm trying to understand how all this works; there is a short code file as
attachment, with midi and pdf ones; I tried to use dynamics and other
signs, but the difference on sound between signed (with 'p' and others
signs) and not signed notes it's quite not hearable; I found
<> ^\markup \bold \italic {"text" }
> > R1*4/4
> > R1*4/4
> > }
> > MII = {
> > R1*4/4
> > R1*4/4
> > c''1
> > %c'''1
> >
> > }
> > \score {
> >
^\markup \bold \italic {"text" }
> > R14/4
> > R14/4
> > }
> > MII = {
> > R14/4
> > R14/4
> > c''1
> > %c'''1
> >
> > }
> > \score {
> > <<
> > \n
t;8><8><8><8><8><8><8><8><8><8><8><8><
> \version "2.24"
> MI = {
> <> ^\markup \bold \italic {"text" }
> R1*4/4
> R1*4/4
> }
> MII = {
>
;8><8><8><8><8><8><8><8><8><8><
> \version "2.24"
> MI = {
> <> ^\markup \bold \italic {"text" }
> R1*4/4
> R1*4/4
> }
> MII = {
>
><8><
\version "2.24"
MI = {
<> ^\markup \bold \italic {"text" }
R1*4/4
R1*4/4
}
MII = {
R1*4/4
R1*4/4
c''1
%c'''1
}
\score {
<<
\new Dynamics \MI
\new Staff \MII
>>
}
8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><
Is this a bug?
Richard
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
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
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
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 n
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 sepa
% Music follows here.
c2 d4 e
}
left = \relative c' {
% Music follows here.
c4 e g r
}
\score {
\new PianoStaff \with {
instrumentName = "Piano"
} <<
\new Staff = "right" \with {
midiInstrument = "acoustic grand"
} \right
\new
Hairpin.self-alignment-Y = #-3 and place them nicely.
Thank You Again and Happy New Year,
Mark
On Tue, Jan 3, 2023 at 9:53 AM Michael Werner wrote:
> 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
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
;
\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. so 0.4 is a rough approximation of 2/3
the
Jan 2023 at 14:30, Mark Mathias 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
On Tue, 3 Jan 2023 at 14:30, Mark Mathias 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 &g
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.
Thank you,
Mark
\version "2.24.0"
\relative c'' {
<<
\new Staff \with {
\m
Awesome, thanks!
On Fri, 23 Dec 2022, 20:06 Jean Abou Samra, wrote:
>
>
> Le 23 déc. 2022 à 20:56, Paul McKay a écrit :
>
>
> Hi
> I'm making a setting of some music with repeated melodies. The dynamics on
> the second repeat are slightly different in that some appea
> Le 23 déc. 2022 à 20:56, Paul McKay a écrit :
>
>
> Hi
> I'm making a setting of some music with repeated melodies. The dynamics on
> the second repeat are slightly different in that some appear to have been
> omitted from the first time. I'd like to use the s
Hi
I'm making a setting of some music with repeated melodies. The dynamics on
the second repeat are slightly different in that some appear to have been
omitted from the first time. I'd like to use the same code, but to show the
"possibly omitted" dynamic marks in a different color. I
ndrew
> >
> > Alberto Simões wrote on 26/06/2022 6:53 AM:
> >> Dear Paul,
> >> I feel ashamed now.
> >> Indeed, I lost it when changing to the new Dynamics.
> >> Thanks for your quick answer.
> >> Its working back ;)
> >>
> >
> >
>
>
>
in the upper staff. I think.
Andrew
Alberto Simões wrote on 26/06/2022 6:53 AM:
Dear Paul,
I feel ashamed now.
Indeed, I lost it when changing to the new Dynamics.
Thanks for your quick answer.
Its working back ;)
, I lost it when changing to the new Dynamics.
Thanks for your quick answer.
Its working back ;)
Dear Paul,
I feel ashamed now.
Indeed, I lost it when changing to the new Dynamics.
Thanks for your quick answer.
Its working back ;)
Alberto
On Sat, Jun 25, 2022 at 9:49 PM Paul Hodges wrote:
> Your snippet doesn't include the Span_stem_engraver, so I guess you lost
> that when
Your snippet doesn't include the Span_stem_engraver, so I guess you lost that
when adding the Dynamics. Here is an extracted part of the score of that I am
just now working on, with /lots/ of cross-staff joins as well as central
dynamics:
\score {
<<
\new Pian
Hello
I am using CrossStaff and everything worked fine.
But after following a snippet that suggest adding the dynamics as an
independent voice of spaces:
\score {
\new PianoStaff = "PianoStaff_pf" <<
\new Staff = "upper" << \upper >>
\new Dynamics
Hi,
Le 14/06/2022 à 02:50, Edizioni Migliori a écrit :
Hi,
Somewhere between 2.23.7 and 2.23.9, the Feta rendering of "mf" and
"mp" has changed, with increased spacing between the letters. It looks
nice, but there is no announcement of the change in the documentation.
Is there a reason for
Hi,
Somewhere between 2.23.7 and 2.23.9, the Feta rendering of "mf" and "mp"
has changed, with increased spacing between the letters. It looks nice, but
there is no announcement of the change in the documentation. Is there a
reason for this?
Also, with the new spacing, it would be great if the
t; | % m41
> | % m42
> | % m43
> \break
> | % m44
> | % m45
> | % m46
> | % m47
> \break
> | % m48
> | % m49
> | % m50
> | % m51
> \break
> | % m52
> | % m53
> | % m54
> | % m55
> \break
> | % m56
> | % m57
1 - 100 of 1390 matches
Mail list logo
