Hi G.
When I write unmetered music, my template is as joined. (It's for piano, so
might need to be adapted.)
HTH,
Claire
On Fri, Oct 2, 2020 at 8:07 PM Gonsolo wrote:
> Is it possible to write music in Lilypond in free time and if yes how?
>
> I have a piece without metrum where notes with a s
Thank you very much !
Claire
On Thu, Sep 17, 2020 at 2:16 PM Xavier Scheuer wrote:
> On Thu, 17 Sep 2020 at 13:23, Claire Meyer <
> claire.meyer.bourhis.lilyp...@gmail.com> wrote:
> >
> > Hi Lukas,
> >
> > Oh, yes, unfortunately, I need a normal (cro
quot;Span_arpeggio_engraver"
} \upper
}
Would someone happen to know how to solve my case ?
Thanks,
Claire
On Mon, Sep 14, 2020 at 6:34 PM David Nalesnik
wrote:
> Hi Claire,
>
> On Mon, Sep 14, 2020 at 10:19 AM Claire Meyer
> wrote:
> >
> > Hi everyone,
> &g
gt; When you use \override it’s supposed to be followed by a Grob name and the
> property that’s going to be overridden, like
> \override Stem.direction = #UP
> When using the commands \stemUp and \stemDown you just write for instance
> \once \stemUp, without \override
>
> HTH
>
ssion. Here, the grace note’s default stem direction
> is overridden and then reverted.
>
> \new Voice \relative {
> \acciaccatura {
> \stemDown
> f''16->
> \stemNeutral
> }
> g4 e c2
> }
>
>
> Cheers,
>
> Martín.
>
>
>
Hi all,
I'm trying to change a grace note's stem direction, to no avail. I tried
both :
\acciaccatura \once \override \stemUp aes
and
\once \override \stemUp \acciaccatura aes
and both produce errors. How do I do it ?
Thanks in advance :)
Claire
Thank you very much, Aaron ! It works.
Cheers,
Claire
On Sat, Sep 12, 2020 at 12:35 AM Aaron Hill
wrote:
> On 2020-09-11 3:25 pm, Claire Meyer wrote:
> > Hi,
> >
> > I've got a problem with a tie not appearing. My problematic bar is as
> > follows :
> >
&
Hi,
I've got a problem with a tie not appearing. My problematic bar is as
follows :
%%
%% VERSION
%%
\version "2.20.0"
%%
%% THEME B
%%
upperHighB = \relative c'' {
d8 bes |
}
upperLowB = \relative c' {
f2 |
}
%
%% STAVES
%
global = {
\tim
e mar. 1 sept. 2020 à 15:02, Martín Rincón Botero <
> martinrinconbot...@gmail.com> a écrit :
>
>> Great! :-)
>>
>> On Tue 1. Sep 2020 at 14:27 Claire Meyer <
>> claire.meyer.bourhis.lilyp...@gmail.com> wrote:
>>
>>> Hi Martin,
>>>
&g
eout #:normal-text #:italic "dolcissimo"))
>
> works?
>
> On Tue 1. Sep 2020 at 14:09 Claire Meyer <
> claire.meyer.bourhis.lilyp...@gmail.com> wrote:
>
>> Hi,
>>
>> I have :
>>
>> [image: image.png]
>>
>> And would like something l
Hi,
I have :
[image: image.png]
And would like something like :
[image: Screenshot_20200901_140443.png]
My dynamic mark looks like :
dolcissimo = \tweak DynamicText.self-alignment-X #LEFT
#(make-dynamic-script
(markup #:normal-text #:italic "dolcissimo"))
Has anyone an idea of how to do that
Thank you !
On Mon, Aug 31, 2020 at 12:13 AM Aaron Hill
wrote:
> On 2020-08-30 2:39 pm, Claire Meyer wrote:
> > Arf, I'm still struggling :
> >
> > dals = \tweak DynamicText.self-alignment-X #LEFT
> > #(make-dynamic-script
> > #{ \markup \normal-t
the first and second line are
left-aligned, and the third is centered).
@Hwaen : your solution gives a weird "horizontal" alignment, the "11" and
"13" are on the left, and the "12" is flushed right, but I appreciate the
effort, thank you :)
On Sun, A
Wow, thank you very much for the comprehensive exemple !
Claire
On Sun, Aug 30, 2020 at 10:46 PM Aaron Hill
wrote:
> On 2020-08-30 1:29 pm, Claire Meyer wrote:
> > Thank you very much ! Would you know as well how to center it
> > vertically on
> > the second line ?
>
Thank you very much ! Would you know as well how to center it vertically on
the second line ?
On Sun, Aug 30, 2020 at 10:12 PM Aaron Hill
wrote:
> On 2020-08-30 12:59 pm, Claire Meyer wrote:
> > Hello,
> >
> > I was wondering if I could write a custom dynamic mark
Hello,
I was wondering if I could write a custom dynamic mark on several lines.
Something along the lines of :
dals = \tweak DynamicText.self-alignment-X #CENTER
#(make-dynamic-script
(markup #:normal-text "l1"
#:normal-text "l2"
#:normal-text "l3"
))
Where l1 is on line 1, l2 is on line 2, and
h for wasting your time with such a trivial problem T___T
Claire
On Sun, Aug 30, 2020 at 1:39 PM Aaron Hill wrote:
> On 2020-08-30 4:29 am, Aaron Hill wrote:
> > On 2020-08-30 2:12 am, Claire Meyer wrote:
> >> Those dynamics are all custom dynamic marks that I constructed like :
&
ns when you move items around
> by overridindǵ their extra-offset properties but seems an issue too ehen
> pushing around the staves themselves.
>
> I don't know if overriding the Y-extent of the dynamics will help here.
>
> ursHTH anyway
>
>
> Am Sonntag, den 30.08
Adding those, in case they are useful.
On Sun, Aug 30, 2020 at 11:57 AM Claire Meyer <
claire.meyer.bourhis.lilyp...@gmail.com> wrote:
> Hi Urs,
>
> Huh !
> > This will give you one cropped pdf plus a number of indexed pdf files
> for each system. The cropping issues sho
clues for understanding the issue.
>
> The most common cause for such cropping issues would be (not in your case)
> moving stuff with extra-offset, which is then not included in the obkjects'
> X/Y-extent.
>
> Urs
>
> Am Sonntag, den 30.08.2020, 11:12 +0200 schri
Hi all,
I'm integrating a score with latex via lyluatex. The .ly file is finished,
and gives no error; the score produced looks good, and I'm at the step
where I just integrate with latex, and touch up the things that need
retouching. I insert system by system, and unfortunately, some dynamics are
Have a good day,
Claire
On Thu, Aug 27, 2020 at 10:52 PM Thomas Morley
wrote:
> Am Mi., 26. Aug. 2020 um 20:42 Uhr schrieb Claire Meyer
> :
> >
> > Hi,
> >
> > I'm trying to reproduce a piano score that has a lot of cross-staff
> notes, some of them collid
gt;
>
> http://lilypond.org/doc/v2.19/Documentation/notation/common-notation-for-keyboards
>
> Attached is my setting of the piece.
>
>
>
> Mark
>
>
>
>
>
> *From:* lilypond-user [mailto:lilypond-user-bounces+carsonmark=
> ca.rr@gnu.org] *On Behalf
Hi,
I've been reproducing an old score, and wanted to be as faithful to the
original layout as possible, so I came up (with the help of several people
on here and in other internet places as well) with a custom dynamic mark,
which *almost* does what I want.
Vertically, the dynamic mark is centere
Thank you very much ! It does help :)
On Wed, Aug 26, 2020 at 6:11 PM Urs Liska wrote:
> Am Mittwoch, den 26.08.2020, 10:08 +0200 schrieb Claire Meyer:
>
> @ Fernando and Urs : Thanks for the additional explanations.
>
> > What you didn't tell us is whether you include t
Hi,
I'm trying to reproduce a piano score that has a lot of cross-staff notes,
some of them colliding. There are 3 voices :
- one for the right hand on the upper staff,
- one for the left hand on the lower staff,
- and for the left hand on the upper staff.
That last voice is the cross-staffed one.
@ Fernando and Urs : Thanks for the additional explanations.
> What you didn't tell us is whether you include the systems by system or
by pages.
> In the latter case all the page layout is done by LilyPond while in the
former
> each system is cropped and included in the document as a paragraph.
orial about it’s use? I have Mac TexLive and LilyPond
> 2.20 installed.
>
> Thanks!
>
> JM
>
> > Le 25 août 2020 à 17:37, David Wright a
> écrit :
> >
> > On Tue 25 Aug 2020 at 17:08:12 (+0200), Claire Meyer wrote:
> >>
> >> Let me preface w
David Kastrup wrote:
> Claire Meyer writes:
>
> > Hi everyone,
> >
> > I have read the documentation and have gone through the archives of the
> > mailing list, and don't understand what I've got wrong. The midi file I
> > generate is empty and doesn
Hi everyone,
I have read the documentation and have gone through the archives of the
mailing list, and don't understand what I've got wrong. The midi file I
generate is empty and doesn't contain music. My .ly file is as follows :
\score {
{c''4 c'' c''}
\layout {}
\midi {\context {
%%
> %%%%%%%
>
> upper = {
>
> \pianoBlock
> { c''4 c'' c'' c'' }
> { a\mf_"foobar" a\mp b b }
>
> \pianoBlock
> { r1 r }
> { a\pp a }
>
> }
>
> %
Hi everybody,
I'm a new user (~1 month old) wondering about best practice for score
structure. Let's say I've got a piano score, with two voices per hand, and
the occasional third voice here and there, and all my dynamics between the
two staves of the piano. Then I'll probably write it with :
- f
32 matches
Mail list logo