Hi Ben,
On 05.10.19 14:24, Ben wrote:
Does your approach allow for clean part-printing? I put together a
quick test and it looks like they all get included for violin 1. I
don't know a straightforward way to accomplish one divisi per violin 1
part in this special situation.
It wouldn't be
Oops, here the missing snippet image...
Am 01.10.2019 um 01:45 schrieb Kieren MacMillan:
Hi Aaron,
Here's my take:
Nice work!
This should be part of the base distro, IMO.
Thanks,
Kieren.
Kieren MacMillan, composer (he/him/his)
‣ website:
Hi Aaron and Kieren,
very nice!
(I really should have read how the markup commands make use of
ly:stencil-aligned-to...)
Here my variant of the code with tweakable alignment. Personally I
prefer the "scheme only-style" but
I agree that the mixed style Aaron used would be shorter.
"Urs Liska" writes:
> Hi all,
>
> is it possible from a stencil callback to retrieve the relative Y
> distance from the grob's staff to another staff given the other
> staff's name?
>
> We want to create frames spanning multiple staves without having to do
> so in separate slices (see
>
Hi all,
is it possible from a stencil callback to retrieve the relative Y distance from
the grob's staff to another staff given the other staff's name?
We want to create frames spanning multiple staves without having to do so in
separate slices (see
En reprenant la psalmodie comme la tienne,
Le sam. 5 oct. 2019 à 09:13, Martial R a écrit :
> Bonjour,
>
> voici le canon et la psalmodie en piece jointe.
>
> Pour info les versions de LilyPond 2.18.2 et 2.19.83 ont de nouvelles
> fonctions bien pratiques par rapport à la 2.14.0.
> la 2.19.83
Bonjour !
En énorme merci à Martial !
Pour ceux qui voudraient faire chanter ce psaume, je vous indique son auteure :
Martine Mertzweiller
Arnaud
>
>
>
>
> >
> >
> >
> >
> >
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
___
On 10/5/2019 4:53 AM, Simon Albrecht wrote:
Hi Ben,
your approach does work. It can be simplified quite a bit, mainly by
using shortInstrumentName and \RemoveAllEmptyStaves, and not using
keepAliveInterfaces, which you don’t even need. See ben-divisi.ly.
On 05.10.19 03:08, Ben wrote:
I
Hi Mike,
I’d recommend using one Voice with all the notes that have lyrics, and
one Voice with all those that don’t. Here’s a more minimal (and sillier)
mockup:
withLyrics = \relative c'' {
\time 3/4
\markLengthOn
\mark "Chorus"
c2.
\mark "Interlude"
Hi Ben,
your approach does work. It can be simplified quite a bit, mainly by
using shortInstrumentName and \RemoveAllEmptyStaves, and not using
keepAliveInterfaces, which you don’t even need. See ben-divisi.ly.
On 05.10.19 03:08, Ben wrote:
I didn't know if I should create the divisi
Pardon me. It's as simple as:
:make | cwindow
Sorry for the noise.
Andrew
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Hello users of vim and gvim,
In one setup on one virtual machine since deconstructed, I feel sure I
remember having gvim set up so that lilypond compile errors would show the
quickfix window and so you could quickly jump to the line in question. Now
on my current system this no longer happens. I
12 matches
Mail list logo
