This compiles well
\version "2.19.65"
\fixed c' {
c4 c c d
(c4) c c c
}
but when I add a \mark like this
\version "2.19.65"
\fixed c' {
c4 c c d
\mark "X" (c4) c c c
}
it doesn't. I know the problem is related to the slur and I can move the
mark before d but why I should not be able to
Am 14.09.2017 um 11:14 schrieb Gianmaria Lari:
c4 c c d
(c4) c c c
[…]
c4 c c d
\mark "X" (c4) c c c
The start of slur belongs to the d, not the c.
Writing
d (c)
is possible and equivalent to
d( c)
but the latter more clearly says what’s going on.
You tried t
It's not the position of the mark that is wrong - it's the slur. This applies
to a note and so must follow the note immediately. Move the ( to the end of
the previous line and all will be well.
--
Phil Holmes
- Original Message -
From: Gianmaria Lari
To: lilypond-user
Sent
Malte Meyn writes:
> Am 14.09.2017 um 11:14 schrieb Gianmaria Lari:
>>c4 c c d
>>(c4) c c c
>
> […]
>
>>c4 c c d
>>\mark "X" (c4) c c c
>
> The start of slur belongs to the d, not the c.
>
> Writing
> d (c)
> is possible and equivalent to
> d( c)
> but the latter more
Am 14.09.2017 um 11:43 schrieb David Kastrup:
Incidentally, current master delivers the following verbiage:
GNU LilyPond 2.21.0
Processing `sll.ly'
Parsing...
sll.ly:4:13: warning: Adding <> for attaching loose post-event
\mark "X"
(c4) c c c
Interpreting music...
sll.ly:4:16:
Am 14.09.2017 um 11:43 schrieb David Kastrup:
Incidentally, current master delivers the following verbiage:
GNU LilyPond 2.21.0
[…]
Is that more helpful than previously?
GNU LilyPond 2.19.80
This looks nice :) Do I understand correctly that after 2.19.65 follows
2.21.0 in the master br
Malte Meyn writes:
> Am 14.09.2017 um 11:43 schrieb David Kastrup:
>> Incidentally, current master delivers the following verbiage:
>>
>> GNU LilyPond 2.21.0
>> Processing `sll.ly'
>> Parsing...
>> sll.ly:4:13: warning: Adding <> for attaching loose post-event
>>\mark "X"
>> (c4)
Malte Meyn writes:
> Am 14.09.2017 um 11:43 schrieb David Kastrup:
>> Incidentally, current master delivers the following verbiage:
>>
>> GNU LilyPond 2.21.0
>
> […]
>
>> Is that more helpful than previously?
>>
>> GNU LilyPond 2.19.80
>
> This looks nice :) Do I understand correctly that after 2
Thank you Malte and Phil!
It works well and your suggestion make sense. I normally didn't pay much
attention to this thing, now I will.
Gianmaria
On 14 September 2017 at 11:27, Malte Meyn wrote:
>
>
> Am 14.09.2017 um 11:14 schrieb Gianmaria Lari:
>
>>c4 c c d
>>(c4) c c c
>>
>
> […]
>
David Kastrup wrote:
> People tend to ignore warnings
> anyway.
I personally ignore warnings only when I don't see them. And I normally
don't see them when they are in a long list of other information (maybe
written in small character etc. etc :))
Ciao, g.
_
One more point: there’s also ‘pedal’ in MusicXML:
C
pedal
Is that just equivalent to having a usual pedal?
JM
> Le 13 sept. 2017 à 11:09, Menu Jacques a écrit :
>
> Hello Mike,
>
> Excellent, thanks!
>
> JM
>
>> Le 13 sept. 2017 à 10:27, Mi
Sorry to ask this that probably is a very trivial question, but I have not
able to find a solution online.
Is there any way to print the pdf file generated by lilypond directly from
Frescobaldi?
Thank you, g.
___
lilypond-user mailing list
lilypond-user
But isn't the start time of this <> the start time of the c4 in the
second line, so that <>( c4) is equivalent to c4(); which causes the
warnings 'cannot end slur' for ')' and 'unterminated slur' for '('?
My guess is that this insertion of <> makes things more complicated for
us, unenlightened u
Rutger Hofman writes:
> But isn't the start time of this <> the start time of the c4 in the
> second line, so that <>( c4) is equivalent to c4(); which causes the
> warnings 'cannot end slur' for ')' and 'unterminated slur' for '('?
Yes and yes.
> My guess is that this insertion of <> makes thi
David Kastrup writes:
> Rutger Hofman writes:
>
>> My preference would be to clearly explain that '(' is an attribute of
>> the note that directly precedes it.
>
> That's what the "loose post-event" bit is supposed to be about.
>
GNU LilyPond 2.21.0
Processing `sll.ly'
Parsing...
On 14-09-17 15:57, David Kastrup wrote:
David Kastrup writes:
Rutger Hofman writes:
My preference would be to clearly explain that '(' is an attribute of
the note that directly precedes it.
That's what the "loose post-event" bit is supposed to be about.
Yes, I understand. But still, I f
Hello Shamus,
Using:
subtitle = \markup {
\override #'(font-family . sans)
{ \center-column { C9 \fret-diagram-terse #"x;3;2;3;3;x;" }
" "
\center-column { "B7#9" \fret-diagram-terse #"x;2;1;2;3;x;" }
" "
\cen
Rutger Hofman writes:
> On 14-09-17 15:57, David Kastrup wrote:
>>
>> Note: another component that may possibly be included in the warning
>> message for this input would be "SlurEvent". Would
>>
>> sll.ly:4:13: warning: Adding <> for attaching loose SlurEvent
>> \mark "X"
>>
Am 14.09.2017 um 12:49 schrieb Gianmaria Lari:
Sorry to ask this that probably is a very trivial question, but I have not
able to find a solution online.
Is there any way to print the pdf file generated by lilypond directly from
Frescobaldi?
File → Print music … or Ctrl+P as in most applicat
This *does not* solve the issue--this is identical to what I attached to
my previous email with the exception that you dropped the flat sign
markup from the third chord (it should be Bbmaj7 with a real flat sign
in it, not Bmaj7). Also, it does not solve the issue with the texts
above the fretboard
Shamus Hammons wrote:
> > In the example I included, you can see that the text for the
> > Bbmaj7 chord is rendered in pieces, and the chord names are generally
> > farther above the diagrams than they should be.
You are using \center-column to get these two things arranged vertically.
It see
This gets closer, but the flat sign is sitting all by itself, as if it
were a separate word and not part of the chord symbol (like so: "B b
maj7"). Also, doesn't address the issue of the chord names floating too
high above the diagrams.
On 09/14/2017 11:26 AM, Robin Bannister wrote:
> Shamus Hammo
Hi to everybody,
I'm a new user trying to learn this wonderful program.
I'm making a transcription that starts with an acciaccatura and noticed it
messes up everything in the other staves.
I know it's a known problem but I need to find a solution. Can someone help?
This is an example:
\language "e
"Marco B." writes:
> Hi to everybody,
> I'm a new user trying to learn this wonderful program.
> I'm making a transcription that starts with an acciaccatura and noticed it
> messes up everything in the other staves.
> I know it's a known problem
Issue 34
> but I need to find a solution. Can som
I've got a piece of music where I'm doing the following ..
\time 2/4 c2 | c4.
\time 6/8 \partial 8 c8 | c2.
This gives me the warning
voiceStaff.ily:38:2: warning: trying to use \partial after the start of
a piece
but it works fine. Without the \partial, though, lilypond gets confused
over the
Shamus Hammons wrote:
This gets closer, but the flat sign is sitting all by itself, as if it
were a separate word and not part of the chord symbol (like so: "B b
maj7").
OK, sorry. Instead of \line use \concat:
\concat { "B" \chordFlat "maj7" }
Also, doesn't address the issue of the chord n
Wols Lists writes:
> I've got a piece of music where I'm doing the following ..
>
> \time 2/4 c2 | c4.
> \time 6/8 \partial 8 c8 | c2.
>
> This gives me the warning
>
> voiceStaff.ily:38:2: warning: trying to use \partial after the start of
> a piece
>
> but it works fine.
I don't get a warning
On 14/09/17 18:30, David Kastrup wrote:
> Wols Lists writes:
>
>> I've got a piece of music where I'm doing the following ..
>>
>> \time 2/4 c2 | c4.
>> \time 6/8 \partial 8 c8 | c2.
>>
>> This gives me the warning
>>
>> voiceStaff.ily:38:2: warning: trying to use \partial after the start of
>> a
Gianmaria,
Try
c4 c c d
(c4^\markup {"X"}) c c c
Mark
From: lilypond-user [mailto:lilypond-user-bounces+carsonmark=ca.rr@gnu.org]
On Behalf Of Gianmaria Lari
Sent: Thursday, September 14, 2017 2:14 AM
To: lilypond-user
Subject: \mark and slur
This compiles well
\vers
Hi,
> warning: Adding <> for attaching loose post-event
I would understand it best if the warning said any of:
Cannot attach slur to preceding expression
Slur is not attached to note or chord
Cannot attach slur to note or chord
No note or chord before this slur to attach it to (is that English?)
"Mark Stephen Mrotek" writes:
> Try
>
> c4 c c d
>
>(c4^\markup {"X"}) c c c
Shrug. If you insist on that kind of organization you can try
\version "2.19.65"
\fixed c' {
c4 c c d
(\mark "X" c4) c c c
}
But it's really a delusion you are getting and becomes rather strained
once
That works perfectly. Thank you!
On 09/14/2017 12:18 PM, Robin Bannister wrote:
> Shamus Hammons wrote:
>
>> This gets closer, but the flat sign is sitting all by itself, as if it
>> were a separate word and not part of the chord symbol (like so: "B b
>> maj7").
>
> OK, sorry. Instead of \line u
Noeck writes:
> Hi,
>
>> warning: Adding <> for attaching loose post-event
>
> I would understand it best if the warning said any of:
>
> Cannot attach slur to preceding expression
> Slur is not attached to note or chord
> Cannot attach slur to note or chord
> No note or chord before this slur to
David,
What I presented was a suggestion that "worked."
In no way, shape, or form was it an "insistence."
With sincere respect for your work,
Mark
-Original Message-
From: David Kastrup [mailto:d...@gnu.org]
Sent: Thursday, September 14, 2017 12:10 PM
To: Mark Stephen Mrotek
Cc: 'Gian
Thank you David, I've found it
Marco
Il giorno gio 14 set 2017 alle ore 19:06 David Kastrup ha
scritto:
> "Marco B." writes:
>
> > Hi to everybody,
> > I'm a new user trying to learn this wonderful program.
> > I'm making a transcription that starts with an acciaccatura and noticed
> it
> > me
Hi,
> Note or chord or rest or skip or bass figure or cluster note or lyrics
> or multimeasure rest. Something like that.
:)
> Slur or phrasing slur or absolute dynamic or annote output or arpeggio
> or articulation or beam or beam forbid or bendafter or crescendo or
> decrescendo or episema or
Noeck writes:
> Hi,
>
>> Note or chord or rest or skip or bass figure or cluster note or lyrics
>> or multimeasure rest. Something like that.
>
> :)
>
>> Slur or phrasing slur or absolute dynamic or annote output or arpeggio
>> or articulation or beam or beam forbid or bendafter or crescendo or
"Mark Stephen Mrotek" writes:
> David Kastrup [mailto:d...@gnu.org] wrote:
>>
>> Subject: Re: \mark and slur
>>
>> "Mark Stephen Mrotek" writes:
>>
>>> Try
>>>
>>> c4 c c d
>>>
>>>(c4^\markup {"X"}) c c c
>>
>> Shrug. If you insist on that kind of organization you can try
>>
>> \version "
> From: Noeck
> Hi,
>
> > warning: Adding <> for attaching loose post-event
>
> I would understand it best if the warning said any of:
>
> Cannot attach slur to preceding expression
> Slur is not attached to note or chord
> Cannot attach slur to note or chord
> No note or chord before this slur to
Hi David,
I know played a little with your fix issue 5181
On current topic:
2017-09-14 15:57 GMT+02:00 David Kastrup :
> David Kastrup writes:
> Note: another component that may possibly be included in the warning
> message for this input would be "SlurEvent". Would
>
> sll.ly:4:13: warni
Thomas Morley writes:
> I'd go for post-event(s)
> Plural, because there may be more than one. See example below
But every one gets its own warning, so each warning is only for one.
> But
> { -\3 -\rightHandFinger #2 d'4 }
> issues the warning, the image doesn't contain the post-events, though.
David,
Understood. Thank you.
Mark
-Original Message-
From: David Kastrup [mailto:d...@gnu.org]
Sent: Thursday, September 14, 2017 1:52 PM
To: Mark Stephen Mrotek
Cc: 'Gianmaria Lari' ; 'lilypond-user'
Subject: Re: \mark and slur
"Mark Stephen Mrotek" writes:
> David Kastrup [mailt
2017-09-15 0:25 GMT+02:00 David Kastrup :
> Thomas Morley writes:
>
>> I'd go for post-event(s)
>> Plural, because there may be more than one. See example below
>
> But every one gets its own warning, so each warning is only for one.
Well, then I'd expect two warnings for:
{ \fermata -- d' }
beca
Thomas Morley writes:
> 2017-09-15 0:25 GMT+02:00 David Kastrup :
>> Thomas Morley writes:
>>
>>> I'd go for post-event(s)
>>> Plural, because there may be more than one. See example below
>>
>> But every one gets its own warning, so each warning is only for one.
>
> Well, then I'd expect two wa
Marco,
To make the staves line up, place a “dummy” acciaccatura, in the “other” voice.
It would be \acciaccatura s32.
Mark
From: lilypond-user [mailto:lilypond-user-bounces+carsonmark=ca.rr@gnu.org]
On Behalf Of Marco B.
Sent: Thursday, September 14, 2017 9:57 AM
To: lilypond-user
"Mark Stephen Mrotek" writes:
> Marco,
>
>
>
> To make the staves line up, place a “dummy” acciaccatura, in the “other”
> voice.
>
> It would be \acciaccatura s32.
From the manual:
Please make sure that you use the ‘\grace’ command for the spacer
part, even if the visual part uses
46 matches
Mail list logo
