|
From: | Mark Stephen Mrotek |
Subject: | RE: spurious partial in 2nd repeat abc->ly |
Date: | Sat, 20 Feb 2021 12:46:25 -0800 |
Joe, I have made some minor changes to conform with performance. See the attached. The code has a great deal of “stuff” that is not necessary (from the source?). Mark From: Joe McCool [mailto:tangent.gardner@googlemail.com] On Fri, 19 Feb 2021 at 19:45, Mark Stephen Mrotek <carsonmark@ca.rr.com> wrote:
Thanks for the help Mark et al.
But there is no \partial there in the source code, hence my problem. With the source as shown in my original post the resulting PDF shows a partial and bar lines struck through beams, which is absurd in this context. Given your hints, I have dotted the last notes in the alternatives as this: %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% \version "2.18.2" %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% This compiles fine and the resulting PDF looks OK, sort of. But this is cheating. My understanding is that if a part starts with a \partial, then the last bar should consist of 5 quavers, not six. Remember my original route to this ly was: python abc2xml.py file.abc > test.xml;musicxml2ly test.xml" I have taken the liberty of attaching the PDF resulting from abcm2ps (which is what I am trying to emulate). To me it seems more legal in that it features 5 quavers in the alternatives. In Part C, I have not yet worked out how to show the 1,2 and 3,4 alternatives. But that is another day's work. BTW, I love Lilypond dearly and am so grateful for its tolerance of my musical ignorance. -- Thanks. (44)7802572441 |
Jig.ly
Description: Text Data
[Prev in Thread] | Current Thread | [Next in Thread] |