Re: partcombine/divisi framework - let the fun begin!

Janek Warchoł gmail.com> writes: > I'm working on putting together a set of functions for handling parts > that split into multiple voices and/or staves > Attachment (definitions.ily): text/x-lilypond, 2359 bytes > Attachment (example.ly): text/x-lilypond, 825 bytes > Attachment (example.pdf):

would 'gn' for G-natural be useful in \language "english" ?

Dear user list, The suggestion quoted below from the bug-lilypond list makes sense to me, as an addition to the \language "english" note-names. It would not fit in German-style pitch-names, where 'cis' and 'ces' get comple

Re: partcombine/divisi framework - let the fun begin!

2014-08-28 19:23 GMT+02:00 Janek Warchoł : > I attach a first version and i'd be interested in your comments. PS this code requires LilyPond 2.19.13, which has not yet been released. Anyone wishing to try out the example should compile LilyPond from source; take a look at https://github.com/janek

Re: Context order

Hi, 2014-08-28 19:21 GMT+02:00 Samuel Speer : > Hi list, > > I'm wondering if there is a simple way to keep the PianoStaff at the bottom > of the vertical group, regardless of contexts being created / destroyed > above it. > > Basically, I've created a ChoirStaff with non-simultaneous music and gr

Context order

Hi list, I'm wondering if there is a simple way to keep the PianoStaff at the bottom of the vertical group, regardless of contexts being created / destroyed above it. Basically, I've created a ChoirStaff with non-simultaneous music and grouped it with the PianoStaff: << ChoirStaff << {

partcombine/divisi framework - let the fun begin!

Hi all, I'm working on putting together a set of functions for handling parts that split into multiple voices and/or staves (using functionality David Kastrup implemented in https://code.google.com/p/lilypond/issues/detail?id=3518). I attach a first version and i'd be interested in your comments.

Re: brainstorming a really smart system engraver

Hi all, > The example attached to the last comment of the related issue > https://code.google.com/p/lilypond/issues/detail?id=2779> goes a > bit further towards creating an ad-hoc interface rather than just > pulling the low-level levers. Thanks! This looks very good in the code… but I’ll have to

Re: brainstorming a really smart system engraver

Kieren MacMillan writes: > Hi all, > >>> I think that issue 3518 (pushed recently) does just this: >>> https://code.google.com/p/lilypond/issues/detail?id=3518 >> >> It doesn't do the automatic "AI nightmare" part. > > Yes, unfortunately... > >> However, it provides the low level machinery for p

Re: brainstorming a really smart system engraver

Janek Warchoł writes: > 2014-08-28 1:40 GMT+02:00 Kieren MacMillan : >> Hi all, >> I think that issue 3518 (pushed recently) does just this: https://code.google.com/p/lilypond/issues/detail?id=3518 >>> >>> It doesn't do the automatic "AI nightmare" part. >> >> Yes, unfortunately... > >

Re: Modifying barline right before a stave is hidden

Janek Warchoł writes: > Hi all, > > is it possible to write a function that does something based on > whether the current context will be visible or hidden in the next > system? For example, i have > > \version "2.19.12" > > \layout { > \context { > \Score > \RemoveEmptyStaves > } >

Modifying barline right before a stave is hidden

Hi all, is it possible to write a function that does something based on whether the current context will be visible or hidden in the next system? For example, i have \version "2.19.12" \layout { \context { \Score \RemoveEmptyStaves } } fooBarline = {} << \new Staff { \fooBar

Re: brainstorming a really smart system engraver

Hi, 2014-08-28 1:40 GMT+02:00 Kieren MacMillan : > Hi all, > >>> I think that issue 3518 (pushed recently) does just this: >>> https://code.google.com/p/lilypond/issues/detail?id=3518 >> >> It doesn't do the automatic "AI nightmare" part. > > Yes, unfortunately... Yes, sorry - i should've trimmed

Re: Best practice for parts with varying number of staves

Hi Kieren, 2014-08-28 1:43 GMT+02:00 Kieren MacMillan : > Hi Janek, > >> What's the status of your "partcombining framework”? > > It stalled last year, usurped by a constant stream of paid commissions. > > However, my father-in-law has generously offered to sponsor me to take a few > weeks > and