Re: Help with String Orchestra Template Please

[Ben]

On 10/5/2019 4:53 AM, Simon Albrecht wrote:

Hi Ben,

your approach does work. It can be simplified quite a bit, mainly by using shortInstrumentName and \RemoveAllEmptyStaves, and not using keepAliveInterfaces, which you don’t even need. See ben-divisi.ly.

On 05.10.19 03:08, Ben wrote:

I didn't know if I should create the divisi staffgroups at the start of the piece and then hide it until it's needed, or just use it on the fly as needed (which is what I did here).

I think it’s more ‘messy’ and complicated creating them on the fly. I’d much rather keep one of them filled with music throughout, have the others quote that, and make full use of the keepAliveInterfaces approach. In all but the most complicated cases one won’t really need meddling with instrumentNames, which also removes the need to meddle with manual breaks. But of course that’s also possible—see demo-string-divisi.ly.

Best, Simon

Simon,

Wow this is so helpful thank you for that code. My brain never even registered doing that as a possibility! Oops.

This looks great, much better. I do have one follow up question though...

Does your approach allow for clean part-printing? I put together a quick test and it looks like they all get included for violin 1. I don't know a straightforward way to accomplish one divisi per violin 1 part in this special situation.

It wouldn't be the end of the world if you had to include all 6 parts on every file but the players may have some frustrations about having to highlight their part or something (assuming this 6-part divisi goes on for several pages of the full score).

I figured I'd ask if there was a way. :)

Thanks!

*attached png*

%%%%% from ben.divisi.ly %%%%%%

\score {
 \new Staff \violinIPart
  \layout {
    \context {
      \Staff
      \RemoveAllEmptyStaves
    }
  }
 
}

6 divisi part.png
Description: PNG image

ben-divisi.ly
Description: Text Data