Maybe StaffCollection would be a suitable name? SystemStartBracket etc.), and from which StaffGroup and all the otherĬontexts should be derived. Logical grouping and has no hardwired visual grouping elements (SpanBar, I think this is a good opportunity to add something I've wantedįor a long time, namely a staff grouping context that provides _only_ Might be reasonable not to have SystemStartBracket's etc. Grouping staves visually by a bracketed instrument name means that it \consist the standard Instrument_name_engraver, whereas the groupingĬontexts should have the Group_name_engraver. Then could be changed such that only Staff (and TabStaff etc.) contexts The context definitions of StaffGroups etc. (Group_name_engraver?) that mimicks and extends the Might make it reasonable to create a dedicated engraver The ability to deal with the needs of multi-staff groups specifically Reasons of backwards compatibility, it should probably stay that way. New Layout object / by a new engraver, or if this should be added to theįunctionality of InstrumentName and the Instrument_name_engraver.Ĭonceptually, I was never really happy with the staff group names beingĬalled InstrumentName's, but I have to admit it's convenient, and for I'm not sure if "staff-group names with brackets" should be done as a We also both did not bother try to do the horizontal alignment the right In system-start-text::calc-y-offset, the standard callback for ![]() Necessary computations of the StaffGroup's total Y extent are contained (Probably we were both inspired by the fact that the Y-offset calculation using a procedure that changes the stencil as a What Harm provided: We both had the same cruel idea of hijacking the Well, the code I sent Kieren off-list was more-or-less equivalent to The good old methods: define two new grobs and an For a new featureĪdded to LilyPond proper, I don't see a way around Others, if they’re offered - with an eye to eventually submitting a Maybe we can/should discuss the pros and cons of each approach - and Lukas sent me a totally different solution that was also ![]() Nice! This definitely solves the basic problem nicely. Whitespace around each snippet.Re: Manipulating instrument names and staff group names Without much try-and-error to produce a pdf with equal and consistent What I still don't get is how the size of the lilypond snippet is set Here, is fully sufficient to answer my question. Things with lilypond and in further insights. I am always interested in how others (especially experts like you) do > commissions, so my “spare time” is very limited.) > to have the enviable obstacle that I’m constantly working on composing new > them into version control, and sharing them with the whole ‘Pond… but I seem > ongoing intention of simplifying all my templates and stylesheets, getting > non-documented, etc., and so I wouldn’t inflict it on you. ![]() This means, you have to choose the height and width of the \paper forĮvery snippet? I am thinking about small scores of one or two measures > I don’t use pdfcrop - I simply have Lilypond output the PDF file at the Enjoy the fruits of the labours of many, many brilliant programmers. Using TeXShop, compile the following template ![]() Using Frescobaldi (or, of course, just Lilypond by itself), generate the Re: StaffGroup bracket cut off by lilypond-book (issue 720)
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |