Folks,
consider:
\version "2.19.82"
<<
\new PianoStaff <<
\new Staff { R1 \stopStaff s1*15 \startStaff R1 }
\new Staff { R1 \stopStaff s1*15 \startStaff R1 }
>>
\new Staff { R1*10 \break R1*10 }
>>
Is there a way to obtain the system start delimiters, clefs etc. at the
point
> This is of course a total hack, but basically you could pretend that the
> measures are 2/4 rather than 4/4. Then by hiding every other bar line, it
> *looks* like it is 4/4.
That's pretty clever. I'll play around with that approach to see how
flexible it is. I generate Lilypond files
On 2019-04-04 5:24 pm, David Bellows wrote:
Lilypond groups beams automatically according to the beat. If you use
the "Completion_heads_engraver" you can get Lilypond to automatically
split long notes at bar lines tying them together.
So I'm wondering if Lilypond can automatically split long
Lilypond groups beams automatically according to the beat. If you use
the "Completion_heads_engraver" you can get Lilypond to automatically
split long notes at bar lines tying them together.
So I'm wondering if Lilypond can automatically split long notes
according to the beat and if I am just
Hi Valentin,
On Thu, Apr 4, 2019 at 6:10 PM Valentin Villenave
wrote:
> On 4/4/19, N. Andrew Walsh wrote:
> > how do I ensure that only the lyrics in \altvocoLyricsSop get
> > attached to it, then resume following \voceMusicSop afterwards?
>
> You can \set the associatedVoice property to
I'm trying to create something a bit like an ossia voice which should be
overlaid on top of the principal voice, but without affecting the layout of
each; i.e. ignoring all collisions.
In the following example, ideally the Dots and Ties on the Gs in the first line
should have the same
On 4/4/19, N. Andrew Walsh wrote:
> how do I ensure that only the lyrics in \altvocoLyricsSop get
> attached to it, then resume following \voceMusicSop afterwards?
You can \set the associatedVoice property to another Voice’s name
whenever you want; see
Hi List,
I have the following MWE:
\version "2.19.82"
\layout {
\context {
\Lyrics
\name AltLyrics
\alias Lyrics
\override LyricText.font-shape = #'italic
}
\context {
\StaffGroup
\accepts AltLyrics
}
}
%% Doesn't do a lot, apart from avoid warnings when
On Thu, 4 Apr 2019 at 13:28, David Kastrup wrote:
> Gianmaria Lari writes:
>
> > Is this the correct way to create a function alias in lilypond or there
> is
> > a shorter/better way?
> >
> > \version "2.21.0"
> > extremelyLongNameFunction =
> > #(define-music-function (music) (ly:music?)
> >
Gianmaria Lari writes:
> Is this the correct way to create a function alias in lilypond or there is
> a shorter/better way?
>
> \version "2.21.0"
> extremelyLongNameFunction =
> #(define-music-function (music) (ly:music?)
>(let ((varOne #{ a b b a #}))
> #{
>$varOne $music
Hi Gianmaria,
Would this do?
\version "2.19.83"
extremelyLongNameFunction =
#(define-music-function (music) (ly:music?)
(let ((varOne #{ a b b a #}))
#{
$varOne $music $varOne
#}))
#(define anAlias extremelyLongNameFunction)
\anAlias { c c c c }
That's just Scheme coding,
On Thu, 4 Apr 2019 at 13:07, Andrew Bernard
wrote:
> Hi Gianmaria,
>
> Would this do?
>
> \version "2.19.83"
> extremelyLongNameFunction =
> #(define-music-function (music) (ly:music?)
>(let ((varOne #{ a b b a #}))
> #{
>$varOne $music $varOne
> #}))
>
>
> #(define
On Thu, 4 Apr 2019 at 11:28, Gianmaria Lari wrote:
> Is this the correct way to create a function alias in lilypond or there is
> a shorter/better way?
>
> \version "2.21.0"
> extremelyLongNameFunction =
> #(define-music-function (music) (ly:music?)
>(let ((varOne #{ a b b a #}))
> #{
Is this the correct way to create a function alias in lilypond or there is
a shorter/better way?
\version "2.21.0"
extremelyLongNameFunction =
#(define-music-function (music) (ly:music?)
(let ((varOne #{ a b b a #}))
#{
$varOne $music $varOne
#}))
alias =
Great explication Malte!
Consider to add it somewhere in the manual in case it is not already there
(if it is, I didn't find it).
Thank you, Gianmaria
On Thu, 4 Apr 2019 at 10:43, Malte Meyn wrote:
>
>
> Am 04.04.19 um 10:23 schrieb Gianmaria Lari:
> > I don't understand how lilypond manages
Hi Pedro,
I've now looked into the code, and the issue is the following
\loadPackage \with {
option = "B"
} local
will set the option correctly, but only *after* loading the package.
This means the option is available within your test.ly file after
loading the package. This
Am 04.04.19 um 10:23 schrieb Gianmaria Lari:
I don't understand how lilypond manages the stem direction in the
following code. Why the difference in the two scores?
\partCombine is for combining a first and a second (or upper and lower)
part in a score, like flute 1 & flute 2 or soprano &
I don't understand how lilypond manages the stem direction in the following
code. Why the difference in the two scores?
\version "2.21.0"
\partCombine {c' d' e' f'} {a b c' d'}
\partCombine {a b c' d'} {c' d' e' f'}
Thank you, g.
___
lilypond-user
On Wed, Apr 03, 2019 at 11:06:37PM +0200, Lukas-Fabian Moser wrote:
> The corresponding objects are Script and AccidentalCautionary.
Thanks!
> But your syntax is quite old (really ancient!) - which Lilypond version are
> you using?
GNU LilyPond 2.18.2, but my files are tagged with \version
Thank you to everybody for your code !!
... and especially to Valentin for the comments about my code.
g.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
20 matches
Mail list logo
