On Tue, 26 May 2020 at 20:49, Valentin Villenave <[email protected]> wrote: > > On 5/26/20, Lib Lists <[email protected]> wrote: > > For example, I'd start with the concertmaster's part, then duplicate > > it and edit it to generate the music the second soloist, then the > > other soloists, then desks, divisi and so on. > > Greetings, > I wouldn’t recommend to “duplicate” any code. As Xavier said, you can > easily use multiple for files to enter variables containing music for > each instrument, then \include these files in a common file to > generate the full score or the set of individual parts. Even if there > are some differences needed, you can do pretty much anything with > different tags and then \keepWithTags or \removeWithTags as needed. > > > The other option would be to create temporary staves when needed, but > > I'm not sure which one is the best strategy. > > Generally speaking, Xavier’s trick is definitely what would be best > suited to that sort of situations. If you need advice on particular > cases, you’ll need to be more specific.
Hi, I attach here a modified version of the example linked by Xavier that hopefully clarifies what I mean. Let's say this is for the violin part, not for the score (although the staff names are clearly setup to be used in a score). In the first 10 bars I initially wrote the content on both voices but couldn't find a way to merge the stems so that the final result looks like one voice. My solution was to write the part only to the 'first' first violins. While that works, it's a bit confusing as both violin groups actually play those notes. Moreover, the stem is upward, even though there's no material on another voice and I thought that \skip wouldn't create any output. The second problem (related with the first) is that starting from bar 11 the voices are separated, which is correct. However, in some cases (for example if both voices have same rhythm, no other complexity of any kind, as in this case) I'd want have the voices merged in chords, and just leave 'div.' to mark it. I don't understand how to do it. Finally, adding a \shortInstrumentName in the StaffGroup gives an error, but the resulting pdf is otherwise correct. Thank you for your help! > > Cheers, > -- V.
200519_LILYPOND_Violin_Divisi_Solution_002_001.ly
Description: Binary data
