Thank you - I meant to reply to the list. I have the following:
\version "2.19.82"
\header {
title = "CLOUDS AND SUNSHINE"
subtitle = "or, I'VE JUST ARRIVED FROM DIXIE"
composer = "George H. Coes (1828?-1897)"
}
\paper {
#(set-paper-size "a4")
}
\layout {
\context {
\Voice
Am Mi., 31. Okt. 2018 um 19:09 Uhr schrieb Pierre-Luc Gauthier
:
>
> Hi there,
>
> Not sure if this is a bug or if I am using it wrong.
>
> I've started using :
> \consists "Mark_engraver"
> \consists "Bar_number_engraver"
> , etc
> inside StaffGroups since it is now working.
> (Fixed with I think
Am Mi., 31. Okt. 2018 um 18:11 Uhr schrieb joelhamme :
>
> My fellow singers in choir have been asking me to improve the visual chunking
> of choir staves. They wanted to have closed bar lines on the right edge of
> each choir staff.
>
> Adding the `Span_bar_engraver` to `ChoirStaff` adds a lot of
Have also used the \override VerticalAxisGroup.remove-first = ##t and can
confirm this works with 2.18.2 when added to score block.
\score {
<<
\flutePart
\pianoPart
>>
\layout { #(layout-set-staff-size 22)
\context { \Staff \RemoveEmptyStaves
Hello Joel,
when I typeset choir scores, which I do most often, I use the
self-alignment-X override for long syllables:
words = \lyricmode {
Breathes | \once \override LyricText.self-alignment-X = #-.5 \markup {
\with-color #red breathes } |
br | \markup { \with-color #green breathes } |
Hi there,
Not sure if this is a bug or if I am using it wrong.
I've started using :
\consists "Mark_engraver"
\consists "Bar_number_engraver"
, etc
inside StaffGroups since it is now working.
(Fixed with I think 622cab6a34 (Thanks to Dan Eble))
But I get a strange and inconsistent result with
My fellow singers in choir have been asking me to improve the visual chunking
of choir staves. They wanted to have closed bar lines on the right edge of
each choir staff.
Adding the `Span_bar_engraver` to `ChoirStaff` adds a lot of clutter and
results in collisions with the lyrics, which is
My fellow singers in choir have been asking me to improve the visual chunking
of choir staves. They wanted to have closed bar lines on the right edge of each
choir staff.
Adding the `Span_bar_engraver` to `ChoirStaff` adds a lot of clutter and
results in collisions with the lyrics, which is
My fellow singers in choir have been asking me to improve the visual chunking
of choir staves. They wanted to have closed bar lines on the right edge of
each choir staff.
Adding the `Span_bar_engraver` to `ChoirStaff` adds a lot of clutter and
results in collisions with the lyrics, which is
My fellow singers in choir have been asking me to improve the visual chunking
of choir staves. They wanted to have closed bar lines on the right edge of
each choir staff.
Adding the `Span_bar_engraver` to `ChoirStaff` adds a lot of clutter and
results in collisions with the lyrics, which is
Gianmaria Lari wrote
> Ciao Torsten,
>
> I'm sorry, I don't understand. Why I would like to display twice a chord
> if
> I write c4~4 ? Maybe could you write a simple example (if possible!).
Ah, yes, right, Gianmaria!
I only was thinking of chord changes in general, but now I see that it's
On Wed, Oct 31, 2018 at 10:48 AM Torsten Hämmerle
wrote:
> Yes, I'm on the dev list.
> And I'll appreciate a co-operation regarding makam issues.
> After all, you and Hans can provide valuable practical examples, and one
> important point after finally having added my new accidental glyphs, all
On Wed, 31 Oct 2018 at 15:45, Torsten Hämmerle
wrote:
> Gianmaria Lari wrote
> > But I was wondering why it should not work my
> > obvious solution :)
>
> Ciao Gianmanria,
>
> Probably because your obvious solution isn't that obvious from a technical
> point of view.
> In this simple example, it
Adam Good-3 wrote
> Are you on the dev list? If you'd be willing to help me out some more I
> can
> send you a couple of files that are under development and we can address
> specifically the two makams that have this issue.
Yes, I'm on the dev list.
And I'll appreciate a co-operation regarding
Gianmaria Lari wrote
> But I was wondering why it should not work my
> obvious solution :)
Ciao Gianmanria,
Probably because your obvious solution isn't that obvious from a technical
point of view.
In this simple example, it is totally clear that we only want to see
changes.
But just imagine the
Torsten that's GREAT! Very very nice and works so well. But it's working a
little too well for my purposes :)
Are you on the dev list? If you'd be willing to help me out some more I can
send you a couple of files that are under development and we can address
specifically the two makams that have
Adam Good-3 wrote
> Thank you Torsten, unfortunately this doesn't satisfy the criteria of #3
> request, working across transpositions. If I ask for:
> \key c \KeySig
>
> ...it prints a ces in the key signature. […]
Hi Adam,
Yes, unfortunately, my trickery only works for keys with a "sharp"
> I don't regard this as done and dusted yet.
Thanks!
> It fails on a Mac pristine install for High Sierra. This is not good
> at all. I'm am continuing to look further into this very pinpoint
> specific failure pattern. It's odd.
What about trying the MacPorts version? The package is called
Gosh,
once again I'm flabbergasted about the expertise and helpfulness of the
folks on this list. Thanks a ton!
As far as I can tell, your corrected version works like a charm (and
even fixed a minor misalignment of the "à" syllable that I did not spot
earlier). And IIUC, the only drawback
On 2018-10-31 1:59 am, Andrew Bernard wrote:
Hi All,
It's something much more subtle than the system/user font location. On
my
system, despite Kieran's success, it does not work, and when K upgrades
the
mac it may not work for him. In correspondence with the typographer of
the
font, we have
Hi All,
It's something much more subtle than the system/user font location. On my
system, despite Kieran's success, it does not work, and when K upgrades the
mac it may not work for him. In correspondence with the typographer of the
font, we have all definitively established what the correct
On Wed, 31 Oct 2018 at 09:21, David Kastrup wrote:
> Gianmaria Lari writes:
>
> > The following code...
> >
> > \version "2.19.82"
> > \new ChordNames \chordmode { c8~c2 }
> >
> >
> > displays C C. How can I make it display a single C chord that last 8~2?
>
> You got a number of workarounds in
Gianmaria Lari writes:
> The following code...
>
> \version "2.19.82"
> \new ChordNames \chordmode { c8~c2 }
>
>
> displays C C. How can I make it display a single C chord that last 8~2?
You got a number of workarounds in different answers. There may also be
some point in treating this as a
Am 31.10.18 um 09:00 schrieb Gianmaria Lari:
The following code...
\version "2.19.82"
\new ChordNames \chordmode { c8~c2 }
displays C C. How can I make it display a single C chord that last 8~2?
Durations may be modified using factors: since 2 is 4x 8 (hehe), you can
write
On 2018-10-31 1:00 am, Gianmaria Lari wrote:
The following code...
\version "2.19.82"
\new ChordNames \chordmode { c8~c2 }
displays C C. How can I make it display a single C chord that last 8~2?
Would either "c8 s2" or "c8*5" work for you? (I think the second one
would be needed for MIDI
Am 31.10.18 um 09:00 schrieb Gianmaria Lari:
The following code...
\version "2.19.82"
\new ChordNames \chordmode { c8~c2 }
displays C C. How can I make it display a single C chord that last 8~2?
There are several possibilities:
%%%
\version "2.19.82"
\new
Try C8*5.
Best,
Robert
> On 31 Oct 2018, at 09:00, Gianmaria Lari wrote:
>
> The following code...
>
> \version "2.19.82"
> \new ChordNames \chordmode { c8~c2 }
>
> displays C C. How can I make it display a single C chord that last 8~2?
>
> Thank you, g.
>
The following code...
\version "2.19.82"
\new ChordNames \chordmode { c8~c2 }
displays C C. How can I make it display a single C chord that last 8~2?
Thank you, g.
___
lilypond-user mailing list
lilypond-user@gnu.org
(Replying to list, assuming you wrote to me personally only by accident,
as implied by your wording):
Am 31.10.18 um 00:42 schrieb Rohan Srinivasan:
Could any of you give me an example of how \RemoveAllEmptyStaves is
used? I have:
\layout {
\context {
\Staff
\RemoveAllEmptyStaves
On 2018-10-31 12:34 am, David Kastrup wrote:
Federico Bruni writes:
Hi all
I'm trying again to make lilypond-invoke-editor work in Windows.
Someone managed to make it work using Windows Subsystem for Linux,
that is installing the LylyPond Linux binary in Windows. But I'd like
to use the
Federico Bruni writes:
> Hi all
>
> I'm trying again to make lilypond-invoke-editor work in Windows.
> Someone managed to make it work using Windows Subsystem for Linux,
> that is installing the LylyPond Linux binary in Windows. But I'd like
> to use the installation for Windows.
>
> I think I'm
Hi all
I'm trying again to make lilypond-invoke-editor work in Windows.
Someone managed to make it work using Windows Subsystem for Linux, that
is installing the LylyPond Linux binary in Windows. But I'd like to use
the installation for Windows.
I think I'm really close to it.
The easiest
32 matches
Mail list logo
