On 2021-07-01 10:44 pm, Aaron Hill wrote:
[...]
Also, here's a minor refactor of \localFontSize better separating some
concerns:
\version "2.22.0"
localFontSize =
#(define-music-function
(font-size music)
(number? ly:music?)
(map (lambda (m)
(ly:music-set-property! m
On 2021-07-01 10:11 pm, Dinh Hoang Tu wrote:
Yes, I did try \partCombineChords, but it doesn't seem what I expect.
Expectation is 2 notes on same stem, one upper, one lower, not on
separate
stems.
Below is the test and attached result (2 notes have separate stems)
\version "2.22.1"
On Fri 02 Jul 2021 at 13:15:07 (+1000), Mark Probert wrote:
> Another newbie question. How do I hide a key engraver after the first
> instance? I want it at the top, then not on the following staves, which
> is the default behaviour. I'm sure there is a hide.engraver-thing
> somewhere...
Put
Yes, I did try \partCombineChords, but it doesn't seem what I expect.
Expectation is 2 notes on same stem, one upper, one lower, not on separate
stems.
Below is the test and attached result (2 notes have separate stems)
\version "2.22.1"
localFontSize =
#(define-music-function (font-size music)
Hi.
Another newbie question. How do I hide a key engraver after the first
instance? I want it at the top, then not on the following staves, which
is the default behaviour. I'm sure there is a hide.engraver-thing
somewhere...
--
\version "2.22"
tune = \relative c'' {
\clef treble
\key
If you use the \partCombineChords command in one of the voices (as in the
snippet I sent with last mail) it should override the default behavior of
partCombine and work without tricks or problems. Did you try it?
> 1 juli 2021 kl. 17:44 skrev Dinh Hoang Tu :
>
> Hello Leo,
>
> Thanks for your
Hello Leo,
Thanks for your explanation. Got your point, totally agree it should not
combine when 2 voices are identical, otherwise it's confusing: cannot
distinguish 2 voices.
But when I use different font-sizes to distinguish 2 voices, I can only
combine them when 2 voices are on same side of
Dear list!
I’m attempting to use partCombine on a pair of voices that contain glissandi,
like this:
%%
\version "2.22.1"
\partCombine
{c''8 b' \glissando a'2. }
{e'4 \glissando f'2. }
%%%
Is there any way to make that work?
There is also a possibly harder case I will come across in
As a more general tip: if you want all stems to be pointing up you can specify
that on document or score level in a layout block, like
\layout {
\context {
\Voice
\override Stem.direction = #UP
}}
Or on a staff level in \with statements, like
\new Staff
This is the intended behavior of partCombine. In the usual use case, with the
same notehead size you still want to be able to follow each voice, so
partCombine doesn’t merge them into chords when they’re crossed. (This is
obscured in your first example because you are using \stemUp there,
Robert Gaebler wrote:
I understand to set ragged-right = ##f to get an even (all aligned)
right hand edge, and set ragged-right=##t to get a ragged right edge.
However this setting affects the entire score. I would like to make
occasional exceptions here and there in the score.
Have a
11 matches
Mail list logo
