Hi Alasdair,
I play bass gamba - I've always wanted to do the lovely curved beams
(and for Bach,. and the lot!). No chance lilypond will ever be able to,
I don't think!
Andrew
Hi Pierre,
Bass gamba in France has very detailed markups, such as poussez (p) and
tirez (t), push and pull (up and down bow), and a whole swag more. I'll
dig up some Marin Marais and send to you.
Andrew
On 23/08/2020 2:35 pm, Pierre Perol-Schneider wrote:
Hi Alasdair,
I've never seen suc
Hi Alasdair,
I've never seen such notation. I'd be curious to see an example.
Maybe this could help: http://lsr.di.unimi.it/LSR/Item?id=1068
E.g.:
\version "2.20.0"
#(define-markup-command
(circled-pattern layout props radius angle num arg)
(number? number? number? markup?)
(interpret-marku
I am trying to typeset some early 18th century French music for viola da
gamba. The standard notation, which I would like to keep, is that the
string is indicated by a row of dots above the finger number. That is, for
example, a 4 with three dots over it (generally in a slight arc, rather
than in
Hello Aaron,
thanks for the quick and detailed answer!
You wrote:
> The Dynamic_performer is part of the Voice context; and the
> construct << ... \\ ... >> implicitly creates new Voice contexts.
That is what I had assumed: the voice context _initializes_ its dynamics
to the default value rega
On 2020-08-22 8:52 am, Dr. Thomas Tensi wrote:
I am using lilypond as the frontend for audio production and now I have
a problem where I do not understand lilypond's internal logic for
transferring MIDI settings into embedded contexts.
[ . . . ]
This means that the embedded voices are in the MI
In NR 3.2.6 (version 2.21.5) a new formatting for the table of contents
is described. The documentation suggests the formatting, which defaults
of bold, will only be applied in the case of a hierarchical table of
contents, whereas the bold formatting is applied also for a flat table
of contents
Dear all,
I am using lilypond as the frontend for audio production and now I have
a problem where I do not understand lilypond's internal logic for
transferring MIDI settings into embedded contexts.
The file
-
\version "2.19.82"
\score {
<<
\new Staff = piano \with { midiInstru
