Here's a proposed patch for the documentation. I haven't posted it on Rietveld
because I'm having some problems with make doc (that are unrelated to this
change).
-- a/Documentation/learning/common-notation.itely
+++ b/Documentation/learning/common-notation.itely
@@ -275,6 +275,9 @@ Notation
Aaron,
Got it. Thank you!
Mark
-Original Message-
From: lilypond-user
[mailto:lilypond-user-bounces+carsonmark=ca.rr@gnu.org] On Behalf Of
Aaron Hill
Sent: Tuesday, April 24, 2018 9:15 PM
To: lilypond-user@gnu.org
Subject: Re: V 2.19
On 2018-04-24 21:05, Mark Stephen Mrotek wrote:
On 2018-04-24 21:05, Mark Stephen Mrotek wrote:
Aaron,
Thank you. My jargon is limited. Which file do I select?
Mark
Depends on your operating system and which version you want.
The latest development build there is 2.19.81. Here are (probably) the
most relevant links:
Linux (x64):
Aaron,
Thank you. My jargon is limited. Which file do I select?
Mark
-Original Message-
From: lilypond-user
[mailto:lilypond-user-bounces+carsonmark=ca.rr@gnu.org] On Behalf Of
Aaron Hill
Sent: Tuesday, April 24, 2018 8:13 PM
To: lilypond-user@gnu.org
Subject: Re: V 2.19
On
On 2018-04-24 19:58, Mark Stephen Mrotek wrote:
Hello,
Tried to download for Windows. Get a "404 not found" error message.
Please direct me.
Thank you,
Mark
Try here: http://lilypond.org/downloads/binaries/
-- Aaron Hill
___
lilypond-user
Hello,
Tried to download for Windows. Get a "404 not found" error message.
Please direct me.
Thank you,
Mark
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Hi Tim,
The development versions are very stable. I hammer them all day with
massively complex scores, and no problems arise. The term 'unstable' is a
self deprecating conventional trope of modesty used in the open source
world.
Take the risk - it's worth it. And there are so many good new
On 24.04.2018 22:02, foxfanfare wrote:
I missed
more exemples in the huge "Internal Manual"!
I don’t think any will be added, for two reasons:
The technical reason is that the Internals Reference is auto-generated
from the program code, so possibilities to manually add stuff are very
Hi Harm,
> I read
> https://lists.gnu.org/archive/html/lilypond-user/2018-04/msg00741.html
> different, i.e. the OP wants the needed space inserted at the end of the bar.
Hmmm… Looking back, I see that the OP wrote:
> I want the space that is inserted to be at the end of the bar
> so the notes
2018-04-25 0:10 GMT+02:00 Kieren MacMillan :
> That version, while good to know about, doesn’t allow the notes to space
> themselves normally:
>
> I believe the OP wanted (and I definitely want) the notes in that measure to
> be spaced normally.
Hi Kieren,
I
Hi Harm,
> Another hack:
That version, while good to know about, doesn’t allow the notes to space
themselves normally:
I believe the OP wanted (and I definitely want) the notes in that measure to be
spaced normally.
Thanks,
Kieren.
Kieren MacMillan,
2018-04-24 17:09 GMT+02:00 Kieren MacMillan :
> Hi all,
>
>>> It would be nice to be able to arbitrarily set the duration of the moment
>>> that would (if necessary) be stretched.
>> Ah, I follow now. Interesting! Thanks Kieren!
>
> Here’s a hack that shows the
Hi Kieren, David & all,
I was searching for a way to shift the lyric tie around and I found this
thread from a year back. It looked promising and so I tried David's cool
looking tiedLyricOverrides thingy but it only worked partially. I can
adjust the word-space but the left-pad does not have any
If I may intervene here: about the documentation quality, I'd must say I
disagree.
As I said in another post, I find it (globaly) very high ended. I started LP
about 3 weeks from now, I'm just finishing the full notation PDF book of
almost 900 pages!
Of course, I still have a lot more to learn
On Tue, Apr 24, 2018 at 1:58 PM, David Kastrup wrote:
> Except when it's a clever way of getting rid of an unwanted semicolon.
> Or in this case, create a semicolon hole, a negative semicolon count.
> Add one semicolon, and none remains.
:)
Clean forgot about macros in C. I stand
Maurits Lamers writes:
> One of my students came to me with something peculiar with
> accacciatura and appoggiatura when used as the first item in a score
> with multiple staffs.
Issue 34.
--
David Kastrup
___
lilypond-user
On Tue, Apr 24, 2018 at 2:06 AM, Gianmaria Lari
wrote:
> My question is off topic. I hope it will not be a problem.
>
> The following is one excerpt from the Sitt book, 20 studies in Double
> Stops.
>
>
> Why in the first three measures the G, D and A are written as
Lukas-Fabian Moser writes:
>>> One might add that string players sometimes tend to not precisely
>>> adhere to the written note length in polyphonic double stops: Think of
>>> the instances where Bach writes a longer note combined in polyphony
>>> with shorter notes which are _not_
Karlin High writes:
> On Tue, Apr 24, 2018 at 9:18 AM, Robert Hickman wrote:
>> The only way to create good documentation is to listen to your users
>> problems and progressively make improvements.
>
> Yes, exactly! The LilyPond community has a
Robert Hickman writes:
> The only way to create good documentation is to listen to your users
> problems and progressively make improvements.
"your users" paints a false dichotomy. There is no fundamental
difference between you and anybody else writing documentation.
--
On Tue, Apr 24, 2018 at 10:18:42AM -0700, Mark Stephen Mrotek wrote:
> Maurits,
>
>
>
> This is a known glitch. A “dummy” acciaccatura or appoggiatura must be
> added to all other voices. See below
\grace of the same value will do (it's easier to type).
Paul
>
>
>
> From: lilypond-user
Hi Robert (and Karlin),
>> Whatever help I would get from the C-people, getting rid
>> of the semicolons would not be part of it.
>
> This is **NOT** the point I am making
No, of course not — I would imagine Karlin was simply responding to your comment
> Personally I prefer the syntax
Maurits,
This is a known glitch. A "dummy" acciaccatura or appoggiatura must be added
to all other voices. See below
From: lilypond-user
[mailto:lilypond-user-bounces+carsonmark=ca.rr@gnu.org] On Behalf Of
Maurits Lamers
Sent: Tuesday, April 24, 2018 8:12 AM
To: Lilypond-User Mailing
On 24 April 2018 at 16:18, Karlin High wrote:
> On Tue, Apr 24, 2018 at 9:18 AM, Robert Hickman wrote:
>> The only way to create good documentation is to listen to your users
>> problems and progressively make improvements.
>
> Yes, exactly! The
Hi all,
One of my students came to me with something peculiar with accacciatura and
appoggiatura when used as the first item in a score with multiple staffs.
I tried to find any obvious errors in his code, but I couldn't find anything. I
managed to create a minimal working example, included
2018-04-24 12:02 GMT+02:00 Thomas Morley :
> How about below?
It's working perfectly!
> It is ensured the bracketed hairpin is always of equal length as the
> original. Ofcourse this means the visible hairpin is shortened a
> little.
Exactly what I had in mind!
Many
On Tue, Apr 24, 2018 at 9:18 AM, Robert Hickman wrote:
> The only way to create good documentation is to listen to your users
> problems and progressively make improvements.
Yes, exactly! The LilyPond community has a process for this.
Hi all,
>> It would be nice to be able to arbitrarily set the duration of the moment
>> that would (if necessary) be stretched.
> Ah, I follow now. Interesting! Thanks Kieren!
Here’s a hack that shows the desired outcome [in the first measure]:
\version "2.18.2"
{
\partial 2
<<
{
On 4/24/2018 11:04 AM, Kieren MacMillan wrote:
Hi Ben,
I don't quite follow what you're asking.
I know what he’s asking about… It’s something I’ve been asking about for quite a long time
(>5 years): forcing a *measure* or even *group of measures* (in OP's case, a single
measure) to stretch
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user
>
>
> I don't quite follow what you're asking.
>
> Info from other threads a while back, which could assist you:
>
> * The action of
Hi Ben,
> I don't quite follow what you're asking.
I know what he’s asking about… It’s something I’ve been asking about for quite
a long time (>5 years): forcing a *measure* or even *group of measures* (in
OP's case, a single measure) to stretch to accommodate another grob (in OP’s
case, a
On 4/24/2018 10:50 AM, Robert Hickman wrote:
On 24 April 2018 at 15:41, Robert Hickman wrote:
\textLengthOn Makes lilypond format relative to the length of the
textual annotations instead of the notes. However it does this by
inserting a huge gap between the note with
On 4/24/2018 10:41 AM, Robert Hickman wrote:
\textLengthOn Makes lilypond format relative to the length of the
textual annotations instead of the notes. However it does this by
inserting a huge gap between the note with the annotation and the next
note. Is there a command that does the same
On 24 April 2018 at 15:41, Robert Hickman wrote:
> \textLengthOn Makes lilypond format relative to the length of the
> textual annotations instead of the notes. However it does this by
> inserting a huge gap between the note with the annotation and the next
> note. Is there
\textLengthOn Makes lilypond format relative to the length of the
textual annotations instead of the notes. However it does this by
inserting a huge gap between the note with the annotation and the next
note. Is there a command that does the same thing relative to the bar
lines. e.g. formats notes
On Tue 24 Apr 2018 at 08:53:01 (+0200), Gianmaria Lari wrote:
> On 23 April 2018 at 15:48, David Wright wrote:
>
> > On Mon 23 Apr 2018 at 09:43:01 (+0200), Gianmaria Lari wrote:
> > > The following frescobaldi snippet call the "more.com" program with the
> > >
The only way to create good documentation is to listen to your users
problems and progressively make improvements.
On 24 April 2018 at 14:49, Kieren MacMillan
wrote:
> Hi Robert,
>
>> If I misinterpreted it you can guarantee
>> that other people are also doing so.
One might add that string players sometimes tend to not precisely
adhere to the written note length in polyphonic double stops: Think of
the instances where Bach writes a longer note combined in polyphony
with shorter notes which are _not_ legato.
Playing non-legato and repeating the long note
On Tue 24 Apr 2018 at 00:42:32 (-0700), foxfanfare wrote:
> Knute Snortum wrote
> > My tests on Windows 10 indicate that lilypond.exe can't handle UNC
> > notation. This is true even of a local file.
>
> Let me wonder if everybody here use linux!
> Maybe is it time for me to go for it...
All
Hi Robert,
> If I misinterpreted it you can guarantee
> that other people are also doing so.
Well, that’s a faulty generalization… ;) … but IMO more clarity is always
better.
As they say: "Patches [to the docs] are always gratefully accepted."
Cheers,
Kieren.
> On Apr 23, 2018, at 1:13 PM, David Wright wrote:
>
> On Mon 23 Apr 2018 at 11:40:46 (-0400), Arle Lommel wrote:
>> I’ve noticed on the Mac for some time that the first time I invoke Lilypond
>> from an external application after a reboot, it can take quite a while
> The example looks pretty clear to me. "marked with" is not really
> synonymous with "surrounded with" in my book even though it could be
> more explicit about just how the marks are supposed to be made.
>
If I misinterpreted it you can guarantee that other people are also
doing so. The
Robert Hickman writes:
> Personally I prefer the syntax used by ABC notation, with all notes of
> a slur inside the parans, but I don't see it being changed at this
> point.
How does this work for consecutive slurs, like LilyPond's
{ c4( d)( e2) }
?
{ (c4 (d) e2) }
On 24 April 2018 at 14:25, Kieren MacMillan
wrote:
> Hi Robert,
>
>> Instead the correct syntax should be:
>>
>> g (b d g)
>
> No… the correct syntax is
>
> g( b d g)
>
> The ( is attached, postfix, to the first note of the slurred group.
Stating that in the
Hi Robert,
> Instead the correct syntax should be:
>
> g (b d g)
No… the correct syntax is
g( b d g)
The ( is attached, postfix, to the first note of the slurred group.
Hope this helps!
Kieren.
Kieren MacMillan, composer
‣ website:
Robert Hickman writes:
> Actually it's a misinterpretation. The documentation does not make it
> clear that the start of the slur should be after the first note of the
> slur.
>
> a'2 (a'4 a'4 )
What documentation are you talking about here?
--
David Kastrup
Robert Hickman writes:
> The documentation says that slurs can be created by putting notes
> within '()'
What documentation would state that?
--
David Kastrup
___
lilypond-user mailing list
lilypond-user@gnu.org
Hi Karlin
"Unclear documentation can be improved. Need a reference for it,
though; where was this found?"
I'm talking about the following page:
http://lilypond.org/doc/v2.16/Documentation/learning/ties-and-slurs.en.html
The page states:
"A slur is a curve drawn across many notes. The starting
David Kastrup writes:
> Lukas-Fabian Moser writes:
>>
>> One might add that string players sometimes tend to not precisely
>> adhere to the written note length in polyphonic double stops: Think of
>> the instances where Bach writes a longer note combined in polyphony
On 4/24/2018 7:57 AM, Robert Hickman wrote:
The documentation does not make it
clear that the start of the slur should be after the first note of the
slur.
Unclear documentation can be improved. Need a reference for it, though;
where was this found?
--
Karlin High
Missouri, USA
Actually it's a misinterpretation. The documentation does not make it
clear that the start of the slur should be after the first note of the
slur.
a'2 (a'4 a'4 )
On 24 April 2018 at 13:50, Robert Hickman wrote:
> The documentation says that slurs can be created by
The documentation says that slurs can be created by putting notes
within '()' however this does not work in combination with the Larsen
articulation symbols:
{
(a'2 a'4\cut a'4\strike)
}
I get the following error:
error: syntax error, unexpected EVENT_IDENTIFIER
(a'2 a'4\cut
Lukas-Fabian Moser writes:
>>> The following is one excerpt from the Sitt book, 20 studies in
>>> Double Stops.
>>>
>>>
>>> Why in the first three measures the G, D and A are written as
>>> g4~4~4~4 d4~4~4~4 a4~4~4~4 instead of g1 d1 a1? Any idea?
>>
>> That’s clearly due to the
On 4/23/2018 4:45 PM, AikiZen wrote:
Le Mon, 23 Apr 2018 14:57:24 -0400,
Ben a écrit :
Now that I think about it, you may actually find better success with
Music21 - have you heard of it? It's a large collection of goodies
that will tick a lot of boxes for a lot of
The following is one excerpt from the Sitt book, 20 studies in Double
Stops.
Why in the first three measures the G, D and A are written as
g4~4~4~4 d4~4~4~4 a4~4~4~4 instead of g1 d1 a1? Any idea?
That’s clearly due to the pedagogical purpose; since the etudes are
about Double Stops,
I'm using the latest development build, but had notes the same problem using
the latest 2.18 build, so I don't see a way to update to anything more recent
in this case.
I wouldn't have thought of a font cache, but that gives me something to test
and report back on. Perhaps it is a recurrence
2018-04-24 9:51 GMT+02:00 Davide Liessi :
> Dear all,
> I need to engrave a hairpin in brackets after a \fz.
> I tried LSR 771 (http://lsr.di.unimi.it/LSR/Item?id=771) with the
> following results:
>
> \version "2.19.65"
>
> %http://lsr.di.unimi.it/LSR/Item?id=771
>
Dear all,
I need to engrave a hairpin in brackets after a \fz.
I tried LSR 771 (http://lsr.di.unimi.it/LSR/Item?id=771) with the
following results:
\version "2.19.65"
%http://lsr.di.unimi.it/LSR/Item?id=771
hairpinBetweenText =
#(define-music-function (leftText rightText) (markup? markup?)
#{
On 24.04.2018 09:06, Gianmaria Lari wrote:
The following is one excerpt from the Sitt book, 20 studies in Double
Stops.
Why in the first three measures the G, D and A are written as
g4~4~4~4 d4~4~4~4 a4~4~4~4 instead of g1 d1 a1? Any idea?
That’s clearly due to the pedagogical purpose;
On 2018-04-24 00:06, Gianmaria Lari wrote:
My question is off topic. I hope it will not be a problem.
The following is one excerpt from the Sitt book, 20 studies in Double
Stops.
Why in the first three measures the G, D and A are written as g4~4~4~4
d
4~4~4~4 a4~4~4~4 instead of g1 d1
Knute Snortum wrote
> My tests on Windows 10 indicate that lilypond.exe can't handle UNC
> notation. This is true even of a local file.
Let me wonder if everybody here use linux!
Maybe is it time for me to go for it...
--
Sent from: http://lilypond.1069038.n5.nabble.com/User-f3.html
I've added this issue:
https://github.com/jperon/lyluatex/issues/195
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
My question is off topic. I hope it will not be a problem.
The following is one excerpt from the Sitt book, 20 studies in Double Stops.
Why in the first three measures the G, D and A are written as g4~4~4~4 d
4~4~4~4 a4~4~4~4 instead of g1 d1 a1? Any idea?
Ciao, g.
On 23 April 2018 at 15:48, David Wright wrote:
> On Mon 23 Apr 2018 at 09:43:01 (+0200), Gianmaria Lari wrote:
> > The following frescobaldi snippet call the "more.com" program with the
> > parameter "\\readme"
> >
> > -*- python;
> > from subprocess import call
> >
64 matches
Mail list logo