If I'm understanding the problem correctly I solved this for myself
like this:
First I set up several files;
piece-defs.ly
-- contains all of the musical information (notes, keys)
part-defs.ly
-- contains individualized information for all of the parts, instrument
names etc.
axA = "Instrum
Cameron Horsburgh wrote:
On Mon, 2004-05-10 at 18:14, Mats Bengtsson wrote:
Cc: bug-lilypond; feature request included below!
If you have one \header{...} block at the top level of the file
and another one included withing \score{...}, it seems that LilyPond
combines the settings from both thes
On Mon, 2004-05-10 at 18:14, Mats Bengtsson wrote:
> Cc: bug-lilypond; feature request included below!
>
> If you have one \header{...} block at the top level of the file
> and another one included withing \score{...}, it seems that LilyPond
> combines the settings from both these header blocks. T
Cc: bug-lilypond; feature request included below!
If you have one \header{...} block at the top level of the file
and another one included withing \score{...}, it seems that LilyPond
combines the settings from both these header blocks. This may be a
solution to your problems, since you could simpl
Hi folks,
Thanks to the authors for a great piece of software! I'm actually able
to hold my head up when I take my arrangements to band...!
There is one thing that I would love to be able to do. The band I
arrange for has around 15 different parts. I have two separate files for
each instrument, f
