Hi I am using Lilypond Version 2.22.2 and have started to investigate the
"Include" command, which calls instrument parts, as separate files, and
compiles them into a score.

I really like the way this functionality is working.  However, I have
failed to find out how the Score Title, or identification shall we say, can
engrave on the individual parts, without causing errors in the score.

My anticipation was that I could place a unique header in the parts, which
provide the piece title and date, for example, without any duplication in
the score itself, since it is already there.

Would someone be able to provide some tips?

Seems to me that an instrumentalist could well find themselves asking "what
piece does this part belong to  or what version?"

Michael

Code for Score:
\version "2.22.2"

\language "english"

\header {
      title = "2024 07 19 An Include Test"
      composer = "MTAbrams ( 2024 07 19 )"
     tagline = \markup {
            Engraved at
            \simple #(strftime "%Y-%m-%d" (localtime (current-time)))
            with \with-url #"http://lilypond.org/";
            \line { LilyPond \simple #(lilypond-version) (
http://lilypond.org/) }
      }
}

     \score {

     \new StaffGroup
     <<

\include "ensemble.ly"

\include "viola.ly"

\include "Cello.ly"

     >>

  \layout { }
  \midi {
    \context {
      \Staff
      \remove "Staff_performer"
    }
    \context {
      \Voice
      \consists "Staff_performer"
    }
  }
}

________________________________________________

eg of one of the parts:

\version "2.22.2"

       \new Staff \with
       {instrumentName = \markup {
     \column { "String" \line {"Ensemble "}
     }
      }
     }


       \new Voice = "Strings"
      {
       \set Staff.midiInstrument = #"string ensemble 1"

      \clef treble

      \numericTimeSignature
      \time 4/4
      \tempo 4=72

     c''8 [b'8 a'8 g'8] f'8 [e'8 d'8 c'8] |
     c''8 [b'8 a'8 g'8] f'8 [e'8 d'8 c'8] |
     c''8 [b'8 a'8 g'8] f'8 [e'8 d'8 c'8] |
     c''8 [b'8 a'8 g'8] f'8 [e'8 d'8 c'8] |

    }

Reply via email to