Am Di., 19. Okt. 2021 um 19:42 Uhr schrieb Jean Abou Samra :
>
> Le 19/10/2021 à 17:47, Thomas Morley a écrit :
> > Hi,
> >
> > please consider:
> >
> > {
> >b4\glissando
> >\once \override NoteColumn.glissando-skip =
> > #(lambda (grob)
> >(pretty-print
> > (list
> >
Perfect! In addition to answering my original question, that even lets me use
"real" small caps, which is certainly my preference.
Many thanks -- that is super helpful.
Jay
-Original Message-
From: lilypond-user On
Behalf Of Xavier Scheuer
Sent: Tuesday, October 19, 2021 11:08 AM
On Tue, Oct 19, 2021 at 11:10 AM Christian wrote:
>
> Hi Knute!
>
> Don't know if this solution would be called clean and doesn't run in other
> problems, but using \voiceOne and \voiceTwo inside the variables to change
> voice-Styles seems to work for me. Had a similar problem a couple of
Hi Knute!
Don't know if this solution would be called clean and doesn't run in other
problems, but using \voiceOne and \voiceTwo inside the variables to change
voice-Styles seems to work for me. Had a similar problem a couple of months
ago.
These were the changes I made:
rightHandUpper =
On Tue, 19 Oct 2021 at 19:49, Jean Abou Samra wrote:
>
>
> Hi Jay,
>
> This is an old bug; try the workaround proposed at
>
> https://gitlab.com/lilypond/lilypond/-/issues/1482#note_339750124
Hello,
And if the font you want to use has real small caps you can use
\override #'(font-features .
Many thanks for your prompt and helpful reply -- the workaround worked
perfectly (once I of course changed the \smallCaps in my original question to
\caps).
Jay
-Original Message-
From: lilypond-user On
Behalf Of Jean Abou Samra
Sent: Tuesday, October 19, 2021 10:49 AM
To:
Le 19/10/2021 à 17:47, Thomas Morley a écrit :
Hi,
please consider:
{
b4\glissando
\once \override NoteColumn.glissando-skip =
#(lambda (grob)
(pretty-print
(list
(cons 'X-parent (ly:grob-parent grob X))
(cons 'Y-parent (ly:grob-parent grob
Le 19/10/2021 à 19:42, t...@projectivespace.com a écrit :
I have a quick question about formatting a title in small caps in Lilypond.
Although I can format scoreTitleMarkup with the usual \bold and \italic for
markups, I am having trouble getting \smallCaps (or \caps) to work with a title
I have a quick question about formatting a title in small caps in Lilypond.
Although I can format scoreTitleMarkup with the usual \bold and \italic for
markups, I am having trouble getting \smallCaps (or \caps) to work with a title
retrieved by \fromproperty. The \smallCaps works fine elsewhere
Is there a way to merge three voices in LilyPond?
My specific problem is displayed in the attached file. Here is
basically what's going on:
The last sixteenth note in the right hand, first voice needs to appear
to be tied to the note in the next measure, which is voice two. This
is not a
Hi,
please consider:
{
b4\glissando
\once \override NoteColumn.glissando-skip =
#(lambda (grob)
(pretty-print
(list
(cons 'X-parent (ly:grob-parent grob X))
(cons 'Y-parent (ly:grob-parent grob Y
#t)
c'
d'
}
I.e. NoteColumn seems to have
David Wright wrote:
I've used the attached, which is from the last, and defunct,
reference in:
https://lists.gnu.org/archive/html/lilypond-user/2017-02/msg00133.html
I haven't checked whether it's been made available elsewhere,
like a snippet.
That defunct reference was a message on this
On Tue 19 Oct 2021 at 12:29:18 (+0200), Lukas-Fabian Moser wrote:
> Am 19.10.21 um 09:55 schrieb Valentin Petzel:
> >
> > You probably want to play around with stuff like break-visibility. By
> > default
> > RehearsalMark as end-of-line-invisible, so they are printed at the begin of
> > a
> >
Am 19.10.21 um 09:55 schrieb Valentin Petzel:
Hi Lukas, Hi Ken,
You probably want to play around with stuff like break-visibility. By default
RehearsalMark as end-of-line-invisible, so they are printed at the begin of a
system, but not at the end.
Also if you want to do something like have
Hi Lukas, Hi Ken,
You probably want to play around with stuff like break-visibility. By default
RehearsalMark as end-of-line-invisible, so they are printed at the begin of a
system, but not at the end.
Also if you want to do something like have the segno at the end of the top
system and the
Hello Valentin,
yes, that would be the best way.
Cheers,
Paolo
On Tuesday, October 19, 2021, Valentin Petzel wrote:
> Hello Paolo,
>
> I did not mean it this way. I meant it like: In most cases one can prepare
> a
> score using Lilypond 2.23 (so using Spontini) that is compatible with a
>
Hello Paolo,
I did not mean it this way. I meant it like: In most cases one can prepare a
score using Lilypond 2.23 (so using Spontini) that is compatible with a
Lilypond 2.18 version.
So Saul can probably use Spontini and 2.23 to do his tweaks and still obtain a
2.18 compatible file.
Hello Valentin,
porting the scheme/LilyPond functions used by Spontini-Editor, in its
internal library, from 2.18 to 2.19, would not complete the compatibility.
In fact, the editor relies on the SVG code generation too, which had
changes during these years of LilyPond development.
Therefore, the
Hi Lukas;
Thank you so much! This will go into my "hints/tips/snippets" collection.
Ken
On Mon, Oct 18, 2021 at 11:41 PM Lukas-Fabian Moser wrote:
>
> Hi Kenneth,
>
> Am 19.10.21 um 07:57 schrieb Kenneth Wolcott
> >So, what is the correct method to obtain these symbols displayed
> >
Hello Saul,
in many cases a 2.23 ly file will be compatible with a 2.18 Lilypond.
The only problematic cases should be when Spontini uses overrides that did not
exist in 2.18 (which shouldn't be that many) or if you are using music function
that have changes names or syntax, which can also be
Hi Kenneth,
Am 19.10.21 um 07:57 schrieb Kenneth Wolcott
So, what is the correct method to obtain these symbols displayed
adjacent to each other?
Thanks,
Ken Wolcott
Would
\version "2.22"
{
g'2 8 4.
\mark \markup {
\musicglyph "scripts.segno"
\musicglyph "scripts.coda"
}
Sorry, this is not possibile.
Best,
Paolo
On Tuesday, October 19, 2021, Saul Tobin wrote:
> Any possibility of using this with a Lilypond 2.18 project?
>
> On Sun, Oct 17, 2021 at 6:21 PM Jon Arnold
> wrote:
>
>> Looks promising. The ability to edit slurs with a mouse is huge.
>>
>> On Sun,
22 matches
Mail list logo
