Re: alternative ending splits into extra measure

Thanks Xavier, Problem solved. David Olson \alternative { { \set Timing.measureLength = #(ly:make-moment 5 4) e2. e2 } { \set Timing.measureLength = #(ly:make-moment 6 4) e2. e2. } } ___ lilypond-user mailing list lilypond-user@gnu.org https://li

Re: tighter polyphony

2012/1/6 Werner LEMBERG : > > Is there a possibility to tighten the horizontal distances in > polyphony `chords'?  The Bärenreiter edition of Bach's Chaconne use > only the half distances, approximately. If i remember correctly, these values are hard-coded in c++ code. This is one of the things i'

Re: "include" music-function

On 1/6/12 7:28 AM, "David Kastrup" wrote: > >Now I don't want to repeat old mistakes, but I don't really have the >time for an extended investigation. So if somebody gives me all the >data in a manner that does not require all too much thinking on my side, >I might try putting that kind of funct

Re: alternative ending splits into extra measure

On 6 January 2012 19:17, James wrote: > > You have a dotted 'e2' twice in one alternate and not the other? That's to compensate the partial. David, you need to use \set Timing.measureLength = #(ly:make-moment 6 4) at the start of the second alternative. Actually this kind of case is explained

Re: tighter polyphony

>> Is there a possibility to tighten the horizontal distances in >> polyphony `chords'? The Bärenreiter edition of Bach's Chaconne use >> only the half distances, approximately. > > Looks like \voiceOne \voiceThree \voiceFive > http://lilypond.org/doc/v2.14/Documentation/snippets/simultaneous-n

Re: tighter polyphony

Werner LEMBERG gnu.org> writes: > Is there a possibility to tighten the horizontal distances in > polyphony `chords'? The Bärenreiter edition of Bach's Chaconne use > only the half distances, approximately. Looks like \voiceOne \voiceThree \voiceFive http://lilypond.org/doc/v2.14/Documentation

Re: How is Lily counting measures

Hello Laura, On 6 January 2012 18:15, Laura Conrad wrote: >> "David" == David Kastrup writes: > >    >> From the manual: > >    David>     Upbeats >    David>     ... > >    David>     Partial or pick-up measures, such as an anacrusis or upbeat, are >    David>     entered using the `\pa

Re: alternative ending splits into extra measure

Hello, On 6 January 2012 18:00, dadadharma @dslextreme.com wrote: > In 6/8 time, the second alternative ending splits into two measures. > > PDF file: > > Lilypond file: > > referring page

Re: How is Lily counting measures

> "David" == David Kastrup writes: >> From the manual: David> Upbeats David> ... David> Partial or pick-up measures, such as an anacrusis or upbeat, are David> entered using the `\partial' command, with the syntax David> \partial DURATION

alternative ending splits into extra measure

In 6/8 time, the second alternative ending splits into two measures. PDF file: Lilypond file: referring page: I think my syntax is okay. \repeat

Re: "include" music-function

Jan-Peter Voigt writes: > Here are the two functions I implemented ... still a bit clumsy, but > it works for now ... if you are interested *how* and *why* to use > them, don't hesitate to mail me! If anybody is game for digging up the old discussion: I don't think it makes sense to require a us

Re: "include" music-function

Am 06.01.2012 10:17, schrieb Jan-Peter Voigt: Am 06.01.2012 09:35, schrieb Jan-Peter Voigt: Hello David, the \sourcefilename hint is helpful! Thank you! If I use this in my function and do a ly:parser-clone, the location is up to date: ... Now I will look, if this is working also with ly:par

Re: Chord fingering placement bug?

On Wed, Jan 4, 2012 at 7:09 PM, Nick Payne wrote: > On 05/01/12 07:58, Nick Payne wrote: > >> See below. If the note with the accidental appears first in the chord, >> then the fingering for the other note correctly avoids the accidental. If >> the order of the notes is reversed, the fingering col

tighter polyphony

Is there a possibility to tighten the horizontal distances in polyphony `chords'? The Bärenreiter edition of Bach's Chaconne use only the half distances, approximately. Werner <>___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gn

Re: position of dots

Looks like in this case a "gravity" strategy like those with which window managers snap windows to guides would be appropriate: keep aligned unless this makes dots move to far away from their target, in which case the connection gets severed. > > Or we'd want both a dot_column

Re: position of dots

> Moving the engraver to the voice context gives rise to a new set of > problems: This looks like a plain bug to me which has been hidden up to now. Werner ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinf

Re: position of dots

On 06/01/12 19:33, Werner LEMBERG wrote: Good idea, thanks, but this completely prevents alignment of dots. No no, dots in a chord, within one voice, are still aligned. OK. Remember that dots are not supposed to be aligned between separate voices[1]. Interesting. However, if the dots' dista

Re: "include" music-function

Am 06.01.2012 09:35, schrieb Jan-Peter Voigt: Hello David, the \sourcefilename hint is helpful! Thank you! If I use this in my function and do a ly:parser-clone, the location is up to date: ... Now I will look, if this is working also with ly:parser-include-string while resetting filename and

Re: position of dots

Werner LEMBERG writes: >>> Looks like in this case a "gravity" strategy like those with which >>> window managers snap windows to guides would be appropriate: keep >>> aligned unless this makes dots move to far away from their target, >>> in which case the connection gets severed. >> >> surely +

Re: "include" music-function

Hello David, the \sourcefilename hint is helpful! Thank you! If I use this in my function and do a ly:parser-clone, the location is up to date: --snip-- #(define-public showloc (define-music-function (parser location)() (format #t ">>> ~A\n" (ly:input-file-line-char-column location)) (

Re: position of dots

>> Looks like in this case a "gravity" strategy like those with which >> window managers snap windows to guides would be appropriate: keep >> aligned unless this makes dots move to far away from their target, >> in which case the connection gets severed. > > surely +1 > > bugreport? Mhmm, rathe

Re: position of dots

>> Good idea, thanks, but this completely prevents alignment of dots. > > No no, dots in a chord, within one voice, are still aligned. OK. > Remember that dots are not supposed to be aligned between separate > voices[1]. Interesting. However, if the dots' distances are not too far away from th