I see. For unequal-length measure tracks, we must declare layout for every track separately. However, if this situation occurs very often, maybe we should add a semantic for track, like:
1,2 > 1,2,3 > 1,2,3,4 [image: image.png] For compactness, I suggest utilizing the new line character \n as a grammar token. Personally, I don't think this is very necessary. On Mon, Nov 16, 2020 at 9:16 PM Kieren MacMillan < kieren_macmil...@sympatico.ca> wrote: > Hi, > > >> How does that work with polymetric music? > > Sorry, I don't know what is polymetric music exactly. Can you show an > example? > > See the second example (“Different time signatures with unequal-length > measures”) in this section of the Lilypond docs: > < > http://lilypond.org/doc/v2.18/Documentation/notation/displaying-rhythms#polymetric-notation > > > > Cheers, > Kieren. > ________________________________ > > Kieren MacMillan, composer (he/him/his) > ‣ website: www.kierenmacmillan.info > ‣ email: kie...@kierenmacmillan.info > >
