On 27.10.2016 13:40, David Kastrup wrote:
This concerns << ... \\ ... \\ ... ... >>
If we have more than one voice, voices are assigned in order:
1/2, 1/2/3, 1/2/3/4, 1/2/3/4/5, 1/2/3/4/5/6 ...
while the documentation is quite explicit that, ordered from top to
bottom, assignments should be mo
Now I’ve read up the whole thread, I might add some clarification on my
thoughts.
On 01.11.2016 11:42, Simon Albrecht wrote:
The current mechanism at least provides consistency between the
\voiceOne, \voiceTwo… command names and the order in << \\ \\ >>. And
I don’t see how strict top-down num
On 01.11.2016 00:30, Andrew Bernard wrote:
Hi Ilja,
Like Harm, I do not think the slur is too long in this case. That is
right that it extends past the stem and over the flag.
There is a very powerful slur shape function called \shapeII in the
openlilylib project. You may want to look into
Andrew,Here is the .ly file.
I did further compile, now the error appear on left piano bar 54.
Thank you for your help.
Immanuel,Ming
From: Andrew Bernard
To: MING TSANG
Cc: Lilypond-usermailinglist
Sent: Tuesday, November 1, 2016 12:21 AM
Subject: Re: Exited with return code -1073741
Hi Ming,
We have been through this before, I am sorry to say. You write lilypond code in
a way that compiles, yes, but it is pathological in the extreme, to put it
mildly. You set each and every bar as a variable, and when there are several
voices, introduce new parallel voices in every bar.
Hi Simon,
Strangely no, although perhaps I need to look more closely now that you say
so. But no obvious vertical spacing errors arise from my extensive usage,
and I am pretty sure I would be quick to complain! :-) Odd, this, then.
Andrew
-Original Message-
From: Simon Albrecht
Sent: T
Simon Albrecht wrote Tuesday, November 01, 2016 10:42 AM
>On 27.10.2016 13:40, David Kastrup wrote:
>> This concerns << ... \\ ... \\ ... ... >>
>>
>> If we have more than one voice, voices are assigned in order:
>>
>> 1/2, 1/2/3, 1/2/3/4, 1/2/3/4/5, 1/2/3/4/5/6 ...
>>
>> while the documentation
After reading these replies I may not be wiser...but it did occur to me that
there might be a flaw in my thinking as I do the "programming" with
Frescobaldi. Does that have an impact on any of these issues? Would have
been changed looking back to the "old days" when I used my own editor I
wrote i
"Andrew Bernard" writes:
> Hi Ming,
>
>
>
> We have been through this before, I am sorry to say. You write
> lilypond code in a way that compiles, yes, but it is pathological in
> the extreme, to put it mildly. You set each and every bar as a
> variable, and when there are several voices, intro
"Trevor Daniels" writes:
> Simon Albrecht wrote Tuesday, November 01, 2016 10:42 AM
>
>>On 27.10.2016 13:40, David Kastrup wrote:
>>> This concerns << ... \\ ... \\ ... ... >>
>>>
>>> If we have more than one voice, voices are assigned in order:
>>>
>>> 1/2, 1/2/3, 1/2/3/4, 1/2/3/4/5, 1/2/3/4/5/6
Edward Ardzinski writes:
> After reading these replies I may not be wiser...but it did occur to
> me that there might be a flaw in my thinking as I do the "programming"
> with Frescobaldi. Does that have an impact on any of these issues?
> Would have been changed looking back to the "old days" w
2016-10-20 12:11 GMT+02:00 Marc Hohl :
> Am 13.09.2016 um 22:41 schrieb Thomas Morley:
> [...]
>>
>> 2016-09-13 8:33 GMT+02:00 Marc Hohl :
>
>
>>> I hope to find the source somewhere to provide you a scan of how it
>>> should
>>> look like.
>>
>>
>> Would be great.
>>
>
> I finally found some examp
I'm not a heavy user, so take my thoughts with whatever grain of salt
you want, but this is how I would naively expect these constructs to work:
<< \\ \\ \\ >>
The voices would be entered in order from top to bottom. In this way
the physical structure of the code would resemble the structure o
- Original Message -
From: "David Kastrup"
To: "Trevor Daniels"
Cc:
Sent: Tuesday, November 01, 2016 2:42 PM
Subject: Re: Changing voice order...
There are by now two components to my proposal: fading out \voiceOne
... \voiceFour since they _never_ correspond to voices 1/2/3/4 in a
Il giorno mar 1 nov 2016 alle 16:02, Thomas Morley
ha scritto:
Federico,
in a private mail you asked about Ties in interplay with bends.
General excluding tied notes from being bend is possible but not a
good idea (see some of the examples in bend-issues-02-excerpt.ly)
These examples are diff
"Phil Holmes" writes:
> - Original Message -
> From: "David Kastrup"
> To: "Trevor Daniels"
> Cc:
> Sent: Tuesday, November 01, 2016 2:42 PM
> Subject: Re: Changing voice order...
>
>
>
>> There are by now two components to my proposal: fading out \voiceOne
>> ... \voiceFour since the
"Br. Samuel Springuel" writes:
> I'm not a heavy user, so take my thoughts with whatever grain of salt
> you want, but this is how I would naively expect these constructs to
> work:
>
> << \\ \\ \\ >>
> The voices would be entered in order from top to bottom. In this way
> the physical structure
On Tue 01 Nov 2016 at 15:23:21 (+0100), David Kastrup wrote:
> "Andrew Bernard" writes:
> > Hi Ming,
> > We have been through this before, I am sorry to say. You write
> > lilypond code in a way that compiles, yes, but it is pathological in
> > the extreme, to put it mildly. You set each and every
David Kastrup writes:
> "Br. Samuel Springuel" writes:
>
>> I'd default the flag to the old behavior while the new one is being
>> worked on and then default it to the new behavior once a stable state
>> has been reached.
>
> I don't see that "the new one" will be worked on for any significant
>
On Tue 01 Nov 2016 at 17:11:30 (+0100), David Kastrup wrote:
> "Phil Holmes" writes:
>
> > - Original Message -
> > From: "David Kastrup"
> > To: "Trevor Daniels"
> > Cc:
> > Sent: Tuesday, November 01, 2016 2:42 PM
> > Subject: Re: Changing voice order...
> >
> >> There are by now tw
David Wright writes:
>
>> Now the Voice contexts are still going to be assigned sequentially as
>> "1"/"2", "1"/"2"/"3", "1"/"2"/"3"/"4" (nothing else makes sense really).
>> So in order not to cause confusion by having "1"/"2"/"3"/"4" correspond
>> to "One"/"Three"/"Four"/"Two", I want to rename
HI Folks,
I am not sure for whom you mean error prone - the user, or the compiler.
It seems like after many many repetitions of the variable constructs
representing each bar lilypond just loses the plot and runs out of
resources. It's probably a really obscure bug. It's a use case hardly worth
te
2016-10-28 1:46 GMT+02:00 Thomas Morley :
> 2016-10-27 13:40 GMT+02:00 David Kastrup :
>>
>> This concerns << ... \\ ... \\ ... ... >>
>>
>> If we have more than one voice, voices are assigned in order:
>>
>> 1/2, 1/2/3, 1/2/3/4, 1/2/3/4/5, 1/2/3/4/5/6 ...
>>
>> while the documentation is quite exp
Hi all,
A fascinating thread, for a number of reasons…
Regardless of how the individual functions are ultimately named, might I
recommend we add a *lot* of syntactic sugar? I have custom functions called
“splitX” (workhorses in my code), which remove the need for me to remember how
to code suc
David Kastrup wrote Tuesday, November 01, 2016 4:11 PM
> I want to rename the \voiceXXX constructs
> as well. The old ones will be available still but no longer promoted
> and/or documented prominently, instead using something like \voiceUp,
> \voiceDown, \inner \voiceUp, \inner \VoiceDown ...
On 31.10.2016 06:10, Jay Anderson wrote:
On Sun, Oct 30, 2016 at 5:35 PM, Christopher Heckman
wrote:
I stumbled on this hack, and it doesn't appear to be anywhere online.
As is, you can't have a hairpin run until the very end of a score; it
will stop before the last note. You also can't add \!
On 28.10.2016 21:50, Noeck wrote:
Btw, having the new list syntax in mind I wondered whether this would
work in recent development versions:
\compoundMeter 4/4,1/3
But it does not the 4/4 translates to (4 . 4) and not (4 4).
\compoundMeter (4,4),(1,3) does not work either. Can this list syntax
Hi Chris,
we use to always keep communication on-list, except in special
circumstances. Thus everybody will be able to follow and see whether
there has been a solution, or look it up in the archives. So ‘reply all’.
On 01.11.2016 23:02, Christopher Heckman wrote:
On Tue, Nov 1, 2016 at 2:55
What's the default midi volume in case I don't specify an absolute dynamic
mark (like \p \f etc)? Is there any way to change this default value?
A crescendo mark that's not ending with an absolute dynamic mark how much
does increase or decrease the midi volume?
In case I separate the dynamics fro
Hi all,
> [pseudocode:]
> \splitUD { topmusic \with UP } { bottommusic \with DOWN }
> \splitUUD { topmusic \with UP } { middlemusic \with UP } { bottommusic
> \with DOWN }
> \splitUDD { topmusic \with UP } { middlemusic \with DOWN } { bottommusic
> \with DOWN }
> etc.
If I was better
Am 01.11.2016 um 23:40 schrieb Kieren MacMillan:
> Hi all,
>
>> [pseudocode:]
>> \splitUD { topmusic \with UP } { bottommusic \with DOWN }
>> \splitUUD { topmusic \with UP } { middlemusic \with UP } { bottommusic
>> \with DOWN }
>> \splitUDD { topmusic \with UP } { middlemusic \with DOWN
Hi Phil,
> Who uses four voices on one stave in vocal setting?
Why would this functionality be limited to vocal setting? Here is a screenshot
of a three-voice section in my Chaconne for unaccompanied violin:
There are many uses for multiple [musical] voices that don’t involve "vocal
setting”.
Hi Urs,
> I'm not sure how to write a function that accepts an arbitrary
> number of music expressions.
Couldn’t the function “look forward” the number of entries in the udududud list?
> that seems to call for a "list of music expressions”,
> but I'm not sure to what extent that would make the s
Hi Kieren,
On 11/01/2016 08:32 PM, Kieren MacMillan wrote:
I'm not sure how to write a function that accepts an arbitrary
number of music expressions.
Couldn’t the function “look forward” the number of entries in the udududud list?
I don't think that can work, because the function has to be
On 11/01/2016 09:50 PM, Paul wrote:
so I'm not sure how or even whether this kind of thing can be done in
user space (at least not with existing functions like map-some-music).
Well, here's a start on something, but still not sure how to pull it off
fully:
\version "2.19.49"
split =
#(defi
> 1) The kievan dot for a notehead on a line moved to a space, when it
>should have stayed on a line.
>
> 2) When notes are displayed without a staff, the dot should stay on
>the same level as the notehead, but it shifts up a half space.
>
> I'd welcome a critical review of the regtests to
> To make it more visible I coded a small snippet annotating some info
> to NoteHeads in
> << .. \\ .. \\ ... ... ... >>-constructs.
>
> Output attached.
Thanks!
What about a two-step process: You first set up the order of the
voices, then you input from top to bottom.
Example:
% current
<
37 matches
Mail list logo
