David,
Wow, so simple.
Thank you for the remedy.
Mark
-Original Message-
From: David Kastrup
Sent: Saturday, September 16, 2023 2:44 PM
To: Mark Stephen Mrotek
Cc: lilypond-user@gnu.org
Subject: Re: slurs
"Mark Stephen Mrotek" writes:
> Hello All:
>
>
>
> \version "2.22.2"
>
>
Graham King writes:
> Many thanks David!
>
> (In the course of trying to convert the \note syntax, I discovered the
> existence of \note-by-number which solved 90% of my problem. Sorry for
> the confusing reference to \note.)
Well, \note-by-number #1 #0 #UP is essentially the same as \note {2}
Many thanks David!
(In the course of trying to convert the \note syntax, I discovered the
existence of \note-by-number which solved 90% of my problem. Sorry for
the confusing reference to \note.)
On Sun, 2023-09-17 at 00:38 +0200, David Kastrup wrote:
> Graham King writes:
>
> > I'm trying to
Graham King writes:
> I'm trying to convert a naive Scheme function which has been broken by
> the new syntax for \note. Some arithmetic gives me the index (in this
> MNWE, 96) to a list of pairs, foo, from which I want to extract some
> markup.
>
> The 300-LOC problem seems to boil down to
I'm trying to convert a naive Scheme function which has been broken by
the new syntax for \note. Some arithmetic gives me the index (in this
MNWE, 96) to a list of pairs, foo, from which I want to extract some
markup.
The 300-LOC problem seems to boil down to this:
> Is is possible to conditionally execute the #@ expression based on
> whether the 'textArray' variable is bound?
\version "2.24.2"
textArray = <<
{ \lyricmode { \set stanza = "1" fo -- o bar } }
{ \lyricmode { \set stanza = "2" fo -- o bar } }
>>
\score {
<<
\new Voice = "soprano"
"Mark Stephen Mrotek" writes:
> Hello All:
>
>
>
> \version "2.22.2"
>
> \relative c'' {
>
> \slurDown 4
>
> (bes16) (a c bes d c ees d)
>
> }
Good example why it is a bad idea to use non-standard input formatting
for aesthetic reasons: you lose a proper idea about what you are
actually
Hello All:
\version "2.22.2"
\relative c'' {
\slurDown 4
(bes16) (a c bes d c ees d)
}
Produces this
What must be done to produce this?
Thank you for your assistance.
Mark
> On 16 Sep 2023, at 21:50, Phil Hanna wrote:
>
>
> I have a short passage (6 measures) of a trumpet duo. I am using a staff
> group for the two trumpet staves. How do I increase the vertical distance
> between the two staves?
>
> Phil Hanna
Phil, have looked at
You can do so by modifying the staff-staff-distance property either
globally or for the staff in question.
\new StaffGroup \with {
\override StaffGrouper.staff-staff-spacing.padding = #0 %adjust
to you needs
\override StaffGrouper.staff-staff-spacing.basic-distance = #1
%adjust to you needs
}
I have a short passage (6 measures) of a trumpet duo. I am using a staff
group for the two trumpet staves. How do I increase the vertical distance
between the two staves?
Phil Hanna
We are happy to announce the release of LilyPond 2.25.8. This is termed
a development release, but these are usually reliable for testing new
features and recent bug fixes. However, if you require stability, we
recommend using version 2.24.2, the current stable release.
Please refer to the
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 doesn't work. For
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
>
msk...@ansuz.sooke.bc.ca writes:
> 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
On Sat, 16 Sep 2023, David Kastrup wrote:
> > With the following code, the notes in the MIDI file still are both at
> > default velocity. Explicitly instantiating the Staff does make a
> > difference in the visual output.
> >
> > MyMusic = { c'1 c'1 }
> > MyDynamics = { s1\ppp s1\fff }
> >
> >
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 dynamics variable
19 matches
Mail list logo
