[subject] How to define a macro that expands to a percussion "pitch"?
input is
m = hh
\drummode { \m 8 \m r4 \m }
expected output should be equivalent to
\drummode { hh8 hh8 r4 hh4 }
actual output (console)
percussion.ly:*:*: warning: Ignoring non-music expression
Thanks, everyone, for your contributions.
First of all Jean. Your code gives me exactly what I wanted. I haven’t learned
to use the internals, but see here that it’s useful.
> Not sure, but my guess is that LilyPond might be trying to make different
> measures have not-too-distant lengths. This
Ole,
Under 2.22 I do not get extra space.
Mark
-Original Message-
From: lilypond-user-bounces+carsonmark=ca.rr@gnu.org
[mailto:lilypond-user-bounces+carsonmark=ca.rr@gnu.org] On Behalf Of Ole V.
Villumsen
Sent: Friday, January 27, 2023 1:35 PM
To: lilypond-user@gnu.org
Ole,
Maybe
\override Score.BreakAlignment?
Mark
-Original Message-
From: lilypond-user-bounces+carsonmark=ca.rr@gnu.org
[mailto:lilypond-user-bounces+carsonmark=ca.rr@gnu.org] On Behalf Of Ole V.
Villumsen
Sent: Friday, January 27, 2023 1:35 PM
To: lilypond-user@gnu.org
On 27/01/2023 22:35, Ole V. Villumsen wrote:
> Hi, I am typesetting a movement with a repeat and a clef change right after
> the repeat. I have a suitable line break where the repeat ends and the clef
> change happens. Default Lilypond sets the new clef within the repeat, before
> the
On Fri, Jan 27, 2023 at 1:36 PM Ole V. Villumsen <
ole.villum...@protonmail.ch> wrote:
> Hi, I am typesetting a movement with a repeat and a clef change right
> after the repeat. I have a suitable line break where the repeat ends and
> the clef change happens. Default Lilypond sets the new clef
Hi, I am typesetting a movement with a repeat and a clef change right after the
repeat. I have a suitable line break where the repeat ends and the clef change
happens. Default Lilypond sets the new clef within the repeat, before the
end-repeat sign, which I don’t want and find meaningless in my
I did of course mess up the alignment part.
Cheers,
Valentin
Am Freitag, 27. Jänner 2023, 21:08:47 CET schrieb Valentin Petzel:
> Hello Werner,
>
> there is no real need to butcher the parser for this (which would then be
> unflexible and unaccessible). You can achieve something like tremolo
>
Hello Werner,
there is no real need to butcher the parser for this (which would then be
unflexible and unaccessible). You can achieve something like tremolo modifiers
simly like this, which is easily adaptable and expandable and does not require
us to mess with the parser.
Cheers,
Valentin
On 27/01/2023 11:06, Christian Hummer wrote:
> Dear specialits,
>
> I'm workin on Choir-Parts with Solists. I store the music in single files
> (e.g. soprano, alto,...). Each of the voices has Solo-Parts while the choir
> is muted. I want to have
>
> 1. the choir partes (print only the choir
Dear specialits,
I'm workin on Choir-Parts with Solists. I store the music in single
files (e.g. soprano, alto,...). Each of the voices has Solo-Parts while
the choir is muted. I want to have
1. the choir partes (print only the choir without the solists' parts)
2. a paritura for the whole
Great! Thank you!
Am Do., 26. Jan. 2023 um 12:55 Uhr schrieb Jean Abou Samra :
>
> On 26/01/2023 10:24, Martín Rincón Botero wrote:
> > Dear Jean,
> >
> > thank you very much for this! I only changed the horizontal distances
> > of the dots to 0.1 as in \pattern #4 #X #0.1. If it's not too hard,
12 matches
Mail list logo