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

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? Also if I am able to split the work to a group of workers, is it a good idea

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

It'd be best to split the work amongst many workers who each typeset individual instruments. Then, all the parts can be collected in the conductor's score using \include. See here http://lilypond.org/doc/v2.13/Documentation/user/lilypond/Including-LilyPond-files#index-_005cinclude-1 and here

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

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

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

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