Re: The fastest way to typeset orchestral scores, especially when splitting the work to many workers

[Tim McNamara]

On May 27, 2009, at 8:10 PM, Cameron Horsburgh wrote:

> On Thu, May 28, 2009 at 11:56:29AM +1200, Daryna Baikadamova wrote:
> > I plan to typeset some orchestral works.  Within a movement, is it
> > faster to typeset a instrument at time, or an orchestral page (i.e.
> > open edit display for all instruments, so I need to 13 tabs in my
> > editor) at a time?
>
> I would do one instrument at a time. I find it easier to keep track of
> what I'm doing that way, especially if there are a few different clefs
> and keys to work in.

Not being able to think in multiple keys at once, unlike musicians  
with actual training, I have been trying the following:  writing all  
the parts out in concert to ensure accuracy and then doing a  
transposition on the individual instruments requiring them.   
LilyPond's \transpose function allows this and it makes my cognitive  
life easier!

> I normally start with the top one and work down. Or, depending on how
> well my brain's working, I might do them all according to clef and
> key. It can take me a bit to get used to working in bass clef (I only
> play treble clef instruments) and I can confuse myself if I'm working
> quickly.


I not only play only a treble clef instrument, I only play an  
instrument written in an octave concert pitch (guitar).  The other  
transposing instruments baffle the heck out of me.