So gentlemen, since this is a regular source of confusion, and it certainly has
had me glued up for many days wondering what is wrong with my code, should this
not be raised as a defect, or at the very least the adjetctive ‘fatal’ removed
fromt he message, and replaced with ‘warning’ or somethin
>> Nice! One minor thing: If space allows, I would move the `3' a bit
>> nearer to the center to reduce the curvature of the slur.
>
> You mean move the `3' nearer to the staff, right?
Yep.
Werner
___
lilypond-user mailing list
lilypond-user@gn
2016-04-15 19:07 GMT+02:00 David Nalesnik :
> Even if it is unlikely that an era of music which favors bow notation would
> require tuplets across bars or line breaks, it still makes sense to allow
> them for consistency.
Agreed. I never considered to disallow tuplets over line-break.
Gould has n
2016-04-15 7:25 GMT+02:00 Werner LEMBERG :
>
>> Meanwhile I recoded it (using make-bow-stencil which is not
>> available in 2.18.2) making things way easier.
>
> Nice! One minor thing: If space allows, I would move the `3' a bit
> nearer to the center to reduce the curvature of the slur.
You mean
2016-04-15 11:06 GMT+02:00 Gianmaria Lari :
> I writing some accordion scores and for this reason I'm trying to create the
> lilypond tools that will make the task more easy.
>
> I started writing the following vaiables:
>
> cC = {c4}
> cc = \chordmode {c4}
> ccC = { \new Voice << {\cC} {\cc}>>}
David Sumbler writes:
> From: David Kastrup
>> > Date: Mon, 11 Apr 2016 09:29:40 +0200
>> >
>> > #... at top level is executed and the result ignored to allow for
>> > #(set! ...) and similar expressions with usually unspecified return
>> > #codes. Just try
>> >
>> > $(if sectionA compileA)
>
I have independently stumbled across what I now now is Issue 1515 "Subdivided
beams are disregarded with \cueDuring".
Here is a (tiny-ish) example based on some code from 2011:
/\version "2.19.39"
music = \relative c'' {
\set subdivideBeams = ##t
\set baseMoment = #(ly:make-moment 1 8)
c16-
Am 15.04.2016 um 19:46 schrieb David Sumbler:
>>> You seem to be ready to *do* some manual changes to your master file
>>> > > (e.g. defining a variable or not). So you could simply put your
>>> > > different scores in individual include files and comment in/out these
>>> > > includes.
>>> > > If
David Sumbler writes:
> As an experiment, I produced this:
>
> File: experimentNotes.ly
>
> \version "2.19.24"
>
> compileA =
> \score {
> \new Staff {
>a' a' a' a'
> }
> \layout { }
> }
[...]
> #(if sectionA #{ \compileA #} )
From: David Kastrup
> > Date: Mon, 11 Apr 2016 09:29:4
On Fri, Apr 15, 2016 at 11:53 AM, Simon Albrecht
wrote:
> On 15.04.2016 10:23, David Kastrup wrote:
>
>> Josquin des Prez? I've sung some Missa from him with wildly augmented
triplets crossing a number of bars. Timing them accurately took some
math because at that speed there was no n
Am 15. April 2016 18:50:48 MESZ, schrieb Simon Albrecht
:
>On 15.04.2016 13:59, Andrew Bernard wrote:
>> Is this expected behaviour? Wouldn’t a complete syntax error stop
>> processing? What am I missing here? Should I be addressing instead
>the
>> bug list?
>
>To me, the oddity would be in th
On 15.04.2016 10:23, David Kastrup wrote:
Josquin des Prez? I've sung some Missa from him with wildly augmented
triplets crossing a number of bars. Timing them accurately took some
math because at that speed there was no natural flow any more really.
That would be early 16th century.
Wouldn't
On 15.04.2016 13:59, Andrew Bernard wrote:
Is this expected behaviour? Wouldn’t a complete syntax error stop
processing? What am I missing here? Should I be addressing instead the
bug list?
To me, the oddity would be in that Lily speaks of a ‘fatal error’ here.
It’s a policy that Lily should
I am writing a lilypond server to process lilypond source files submitted by a
client program to avoid the startup costs of lilypond. This is based on an idea
by Sharon, I think pulled up from past archives, and is a small project Sharon
and Urs and I are working on experimentally.
In relation
I writing some accordion scores and for this reason I'm trying to create
the lilypond tools that will make the task more easy.
I started writing the following vaiables:
cC = {c4}
cc = \chordmode {c4}
ccC = { \new Voice << {\cC} {\cc}>>}%first solution
(In the attached image you can see an
David Kastrup writes:
[...]
> "Phil Holmes" writes:
>
>> So to notate it for singers today, you could do it any way that you
>> choose to make it look sensible.
>
> Which would usually involve triplet brackets rather than hacking this
> into partial note values at measure boundaries. Which is
"Phil Holmes" writes:
> - Original Message -
> From: "David Kastrup"
> To: "Simon Albrecht"
> Cc: "Thomas Morley" ;
> Sent: Friday, April 15, 2016 8:04 AM
> Subject: Re: Tuplet number direction
>
>
>> Simon Albrecht writes:
>>
>>> On 15.04.2016 00:51, Thomas Morley wrote:
(1) Th
- Original Message -
From: "David Kastrup"
To: "Simon Albrecht"
Cc: "Thomas Morley" ;
Sent: Friday, April 15, 2016 8:04 AM
Subject: Re: Tuplet number direction
Simon Albrecht writes:
On 15.04.2016 00:51, Thomas Morley wrote:
(1) The TupletNumbers are always inside the bow, I cod
Simon Albrecht writes:
> On 15.04.2016 00:51, Thomas Morley wrote:
>> (1) The TupletNumbers are always inside the bow, I coded no
>> possibility to print the Number cutting the bow.
>> I maybe add it later.
>> (2) What to do at line-break?
>
> Wouldn’t it better do disallow line-breaks during tup
19 matches
Mail list logo
