Hello,
Below prints key and time signatures without staff lines after the last bar.
How to print lines too?
\version "2.22.0"
{ c'1 c' \break c' c' \key d \major \time 3/4 }
Trailing symbols are helpful to indicate the attacca to the next score.
I remember staff lines had appeared
Le 04/11/2021 à 21:18, Lukas-Fabian Moser a écrit :
Hi,
But I'm at a bit of a loss about your notion of a StaffMonoid. All
sorts of math puns aside (a CommutativeStaffRing of nonzero
characteristic especially for engraving _Le Spec de la Rose_ by
Berlioz) - what do you mean by a StaffMonoid?
On Nov 2, 2021, at 11:26 PM, Aaron Hill wrote:
>
> Okay, would text replacement be viable as opposed to writing a bunch of
> individual functions?
That does sound nice. There would need to be some helper functions to handle
the formatting issue that Jean pointed out, but I can get that
Hi,
But I'm at a bit of a loss about your notion of a StaffMonoid. All
sorts of math puns aside (a CommutativeStaffRing of nonzero
characteristic especially for engraving _Le Spec de la Rose_ by
Berlioz) - what do you mean by a StaffMonoid?
There is absolutely nothing besides the math pun. It
On Thu, Nov 4, 2021 at 2:31 PM Mark Knoop wrote:
> \tempo is not a postfix command like dynamics and markups. Just put it before
> the g2.
I do so love the simple fixes. Thanks!
At 14:16 on 04 Nov 2021, Kevin Cole wrote:
Hi,
I think I'm making great strides with my wee little transcriptions,
but here's my latest puzzle:
I have the following measure:
g2^\>\tempo \markup { \italic "Slower." } 4 = 65
<<
{ \voiceOne fs8\!\p([ g8]) }
\new
Hi,
I think I'm making great strides with my wee little transcriptions,
but here's my latest puzzle:
I have the following measure:
g2^\>\tempo \markup { \italic "Slower." } 4 = 65
<<
{ \voiceOne fs8\!\p([ g8]) }
\new Voice
{ \voiceTwo fs8 g8 }
>>
On Thu, Nov 4, 2021 at 7:11 AM Aaron Hill wrote:
> On 2021-11-03 4:45 pm, Paolo Prete wrote:
> > Hello Aaron,
> >
> > what if I enlarge the beam angle? (see below)
>
> Okay, my guesswork was wrong. Here is code that was adapted from the
> underlying C++ logic:
>
>
This is HUGE and very useful,
On 2021-11-03 4:45 pm, Paolo Prete wrote:
Hello Aaron,
what if I enlarge the beam angle? (see below)
Okay, my guesswork was wrong. Here is code that was adapted from the
underlying C++ logic:
\version "2.22.0"
#(define (ly:stem::beam-multiplicity grob)
;; Adapted from non-exported
