A quite minimal could look like: \version "2.19.82"
\score { << \new Staff {e'2.} \new Staff {g'4. f'4} \new Staff {a'1} >> \layout { \context { \Voice \remove "Note_heads_engraver" \consists "Completion_heads_engraver" completionUnit = #(ly:make-moment 2/4)} } } > 21 maj 2019 kl. 22:08 skrev David Bellows <davebell...@gmail.com>: > > Thomas, > >> Main thing here is >> \stopStaff > > Ok, so \noStaff seems to fix my problem without the need for anything > else. I'll need to test it a lot more but perhaps that will get me > through until/unless this problem gets solved within Lilypond. Thanks > for that! I search and search the documentation and the mail list but > sometimes that one command I really need escapes me. > >> Could you please provide a minimal where it does not? > > I don't know how to make a truly minimal example but I have stripped > out all the unnecessary bits and attached it and the pdf it produces. > Sorry it's not as minimal as it should be -- I often don't understand > what's going on in my own Lilypond files. > > \noBeam fixes the problem with notes that would be beamed unless that > note is tied to a previous one. You can see this in Piano 1 and 6. > > Dave > > On Tue, May 21, 2019 at 12:12 PM Thomas Morley <thomasmorle...@gmail.com> > wrote: >> >> Am Di., 21. Mai 2019 um 18:03 Uhr schrieb David Bellows >> <davebell...@gmail.com>: >>> >>> Hi Thomas, >>> >>> Thanks for jumping in! >> >> Well, without Urs' minimal I wouldn't have. Thanks Urs! >> >>>> At least in the minimal one can workaround with inserting \noBeam: >>> >>> It works in some cases but not when that last pitch it tied to >>> previous notes (see attached pdf). >> >> Here it works with \noBeam: >> << >> \new Staff { c'1 c'1 } >> \new Staff { c'1 c'4~ c'16 \noBeam } >>>> >> >> Could you please provide a minimal where it does not? >> >>> Karim provided a workaround: >>> >>> \once \set Staff.whichBar = "|." \override Staff.Clef.stencil=##f \set >>> PianoStaff.shortInstrumentName = #"" \stopStaff >> >> Main thing here is >> \stopStaff >> >> The other settings may have more to do with a personal workflow, I suppose. >> >> Cheers, >> Harm > <test.pdf><test.ly>_______________________________________________ > lilypond-user mailing list > lilypond-user@gnu.org > https://lists.gnu.org/mailman/listinfo/lilypond-user _______________________________________________ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user